DP6.02 crash thread - can you read it?

[303creative]

Hi DP6 users.
I am having regular crashes where this comes up in the prob report.
It could take MOTU months to reply so I thought I might ask any of you if you have experience of this.
Here is the offending crash thread:

Thread 60 Crashed:
0 com.MOTU.MAS.AudioUnitSupport 0x1ad2dc55 MasAUSupportProc::Process(MotuException*, float**, MasBufferInfo*, IMasEffectContext*) + 1399
1 com.motu.MAS.framework 0x016aedf8 0x1678000 + 224760
2 com.motu.MAS.framework 0x016a308d 0x1678000 + 176269
3 com.motu.MAS.framework 0x016d10b7 MAS83180 + 137
4 DPPart2.dylib 0x01093ec6 WrappedMasRenderCache::PushBufferThroughEffects(MasRenderCacheBuffer&) + 50
5 PerfEngine.dylib 0x01b66e1a PerfAudioPlayTrack::GenerateAudio(PerfMutexLite::Lock&) + 306
6 PerfEngine.dylib 0x01b66f21 PerfAudioPlayTrack::DoWork() + 125
7 PerfFoundation.dylib 0x0207075b GetUnitTestRandomLong() + 191
8 libSystem.B.dylib 0x93863155 _pthread_start + 321
9 libSystem.B.dylib 0x93863012 thread_start + 34

Thread 60 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x1ad2d6ef ecx: 0x00000000 edx: 0x00000000
edi: 0x24795330 esi: 0x24795330 ebp: 0xb4a18c18 esp: 0xb4a18910
ss: 0x0000001f efl: 0x00010286 eip: 0x1ad2dc55 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x0000001f gs: 0x00000037
cr2: 0x00000010

It means nothing to me.
I get a pause, followed by about 4 seconds of beach ball - then blank screen. Very frustrating.
If I had a client over my shoulder I would prob check out Logic! But no, I'm sticking with DP, for now.

Thanks, 303

[wylie1]

It would help if you posted some sys info.
could be plugin related.
When you repair permisions do you get any errors?

[michkhol]

You have an AU plugin on one of your tracks that crashes the MOTU AU-to-MAS wrapper. DP usually assigns a thread per track and you seem to have a lot of them. It is very hard to identify the particular offending track, so try to remove the plugins from your tracks one at a time and see what happens. I know, slow and tedious but there is no other choice for now. Start with the fewest instantiated ones (like once or twice) in the project.

[303creative]

Thanks for your input Michkhol and Wylie1.
The track I'm working on has to get finished, so I havent the time, just now, for what Mich suggests - removing plugs one-by-one. I will struggle through and have a go once mixed. Looking at my AU plugs I notice there are a few. Here is a run down in case anyone can spot a potential offender!
MW EQ
MW Leveller
MAS Delay
Omnisphere
Kontakt 3
Play (Ministry of Rock) (was in there, but since removed)
Pianoteq 3
SampleTank 2 (was in there, but since removed)
MV2 (parts of Waves)
Doubler (parts of Waves)
Kore2 as FX
Superior Drummer 2
Melodyne
TC Thirty (amp modelling)
Vocal Intensifier 1.04

That's the lot.
Intel mac, 10.5.7, 2x2.8 GHz, 12 gig mem.

[michkhol]

You can safely exclude all MAS plugins from your list like the whole MW series, I'm not sure about others. Go to the plugin manager and include in your list only those plugins that are Audio Units, not MAS.

[303creative]

It would help if you posted some sys info.
could be plugin related.
When you repair permisions do you get any errors?

Getting back with update: errors continue after reapir perms. Do that often.

But thanks Mich/Wylie, I have noticed that Vccal Intensifier crashes it. It is specified in the crash log!
Also Melodyne removed helps with the productivity.
I use Mel creatively - moving and re-pitching some old tracks of mine to suit new ones - so I have to freeze track and then remove the plugins regularly.
Wonder whether this is down to MOTU or Melodyne?

Nearly completed my mix then I can get stuck in to the problem solving.

Thanks all, 303

[cbergm7210]

Do a Save Copy As to work with a backup copy, and start deleting tracks by groups. Delete half of the tracks and see if it goes away. If not, Undo and delete the other half. If one group deletes and it's normal, then you know the offending plug (or track) is in that group, so divide that group in half and keep deleting groups and getting smaller until you find the one(s) that offend.

I just recently narrowed down a similar situation to yours to two tracks and it turned out to be a bus that was coming into the two Audio tracks. It was a temp bounce bus that I had created, so I deleted the bus (thereby the two Audio tracks had no inputs coming into them) and everything went back to normal. So, it could be a plug in or could be an input into an Audio track as well.

Chris