MachFive and crashing in 10.5.5/DP6.01: Update

[sdfalk]

Anyone else having crashes with the most recent version of MacFive and the most recent (10.5.5) version of OSX?
I'd post a crash report, but apparently that goes over a certain number of characters allowed.

Core 2 Duo 2.2ghz Black Macbook
4gb of ram
Saffire Le
Novation X-Station 61

Any ideas would be greatly appreciated

The Stand alone version doesn't work at all on my system

Here's the thread that apparently crashed..thread 0

Thread 0 Crashed:
0 ??? 0x3052b195 0 + 810725781
1 GLEngine 0x2b8cfd9a gleDrawArraysOrElements_ExecCore + 266
2 GLEngine 0x2b8d0cf8 gleDrawArraysOrElements_IMM_Exec + 1080
3 libGL.dylib 0x913fcd7d glDrawArrays + 45
4 com.motu.M5II 0x1fb20810 uvi::AutomationSelection::OnOk(nuiEvent const&) + 55142
5 com.motu.M5II 0x1fb0e4f2 uvi::ControlSignalMapper::~ControlSignalMapper() + 9520
6 com.motu.M5II 0x1f9146c9 uvi::ParamKnob::ParamKnob(uvi::SynthDbProxy*, nuiContainer*, nglString const&, unsigned int) + 38585
7 com.motu.M5II 0x1fb0e548 uvi::ControlSignalMapper::~ControlSignalMapper() + 9606
8 com.motu.M5II 0x1f9146c9 uvi::ParamKnob::ParamKnob(uvi::SynthDbProxy*, nuiContainer*, nglString const&, unsigned int) + 38585
9 com.motu.M5II 0x1fb0e548 uvi::ControlSignalMapper::~ControlSignalMapper() + 9606
10 com.motu.M5II 0x1f9146c9 uvi::ParamKnob::ParamKnob(uvi::SynthDbProxy*, nuiContainer*, nglString const&, unsigned int) + 38585
11 com.motu.M5II 0x1fb0e548 uvi::ControlSignalMapper::~ControlSignalMapper() + 9606
12 com.motu.M5II 0x1f9146c9 uvi::ParamKnob::ParamKnob(uvi::SynthDbProxy*, nuiContainer*, nglString const&, unsigned int) + 38585
13 com.motu.M5II 0x1fb0e548 uvi::ControlSignalMapper::~ControlSignalMapper() + 9606
14 com.motu.M5II 0x1f9146c9 uvi::ParamKnob::ParamKnob(uvi::SynthDbProxy*, nuiContainer*, nglString const&, unsigned int) + 38585
15 com.motu.M5II 0x1fb0e548 uvi::ControlSignalMapper::~ControlSignalMapper() + 9606
16 com.motu.M5II 0x1f9146c9 uvi::ParamKnob::ParamKnob(uvi::SynthDbProxy*, nuiContainer*, nglString const&, unsigned int) + 38585
17 com.motu.M5II 0x1fb0e548 uvi::ControlSignalMapper::~ControlSignalMapper() + 9606
18 com.motu.M5II 0x1f9146c9 uvi::ParamKnob::ParamKnob(uvi::SynthDbProxy*, nuiContainer*, nglString const&, unsigned int) + 38585
19 com.motu.M5II 0x1fb0e548 uvi::ControlSignalMapper::~ControlSignalMapper() + 9606
20 com.motu.M5II 0x1f9146c9 uvi::ParamKnob::ParamKnob(uvi::SynthDbProxy*, nuiContainer*, nglString const&, unsigned int) + 38585
21 com.motu.M5II 0x1fb0e548 uvi::ControlSignalMapper::~ControlSignalMapper() + 9606
22 com.motu.M5II 0x1f9146c9 uvi::ParamKnob::ParamKnob(uvi::SynthDbProxy*, nuiContainer*, nglString const&, unsigned int) + 38585
23 com.motu.M5II 0x1f901b89 uvi::ParamDesc::SetModulationType(uvi::ModulationType) + 5369
24 com.motu.M5II 0x1f96a07d uvi::FXBrowser::Browse(nuiContainer*, nglPath const&, uvi::FXBrowser::FXBrowserAction, nuiRect const&) + 92711
25 com.motu.M5II 0x1f9147b1 uvi::ParamKnob::ParamKnob(uvi::SynthDbProxy*, nuiContainer*, nglString const&, unsigned int) + 38817
26 com.motu.M5II 0x1f92b10d uvi::Image::Serialize(nuiXMLNode*, bool) const + 61161
27 com.motu.M5II 0x1f9279da uvi::Image::Serialize(nuiXMLNode*, bool) const + 47030
28 com.motu.M5II 0x1feb863d std::_Rb_tree<nuiEventSource*, std::pair<nuiEventSource* const, std::list<nuiEventTarget<uvi::ParamKnob>::Link*, std::allocator<nuiEventTarget<uvi::ParamKnob>::Link*> > >, std::_Select1st<std::pair<nuiEventSource* const, std::list<nuiEventTarget<uvi::ParamKnob>::Link*, std::allocator<nuiEventTarget<uvi::ParamKnob>::Link*> > > >, std::less<nuiEventSource*>, std::allocator<std::pair<nuiEventSource* const, std::list<nuiEventTarget<uvi::ParamKnob>::Link*, std::allocator<nuiEventTarget<uvi::ParamKnob>::Link*> > > > >::erase(nuiEventSource* const&) + 60665
29 com.motu.M5II 0x1f962a10 uvi::FXBrowser::Browse(nuiContainer*, nglPath const&, uvi::FXBrowser::FXBrowserAction, nuiRect const&) + 62394
30 com.motu.M5II 0x1f96296c uvi::FXBrowser::Browse(nuiContainer*, nglPath const&, uvi::FXBrowser::FXBrowserAction, nuiRect const&) + 62230
31 com.motu.M5II 0x1f95edaf uvi::FXBrowser::Browse(nuiContainer*, nglPath const&, uvi::FXBrowser::FXBrowserAction, nuiRect const&) + 46937
32 com.motu.M5II 0x1f95bdb3 uvi::FXBrowser::Browse(nuiContainer*, nglPath const&, uvi::FXBrowser::FXBrowserAction, nuiRect const&) + 34653
33 com.motu.M5II 0x1f95c17e uvi::FXBrowser::Browse(nuiContainer*, nglPath const&, uvi::FXBrowser::FXBrowserAction, nuiRect const&) + 35624
34 com.apple.CoreFoundation 0x90984b45 CFRunLoopRunSpecific + 4469
35 com.apple.CoreFoundation 0x90984cf8 CFRunLoopRunInMode + 88
36 com.apple.HIToolbox 0x9294f480 RunCurrentEventLoopInMode + 283
37 com.apple.HIToolbox 0x9294f299 ReceiveNextEventCommon + 374
38 com.apple.HIToolbox 0x929add4e _AcquireNextEvent + 58
39 com.apple.HIToolbox 0x929ac4ab RunApplicationEventLoop + 207
40 com.motu.DigitalPerformer 0x005cea30 0x1000 + 6085168
41 com.motu.DigitalPerformer 0x00002ec6 0x1000 + 7878
42 com.motu.DigitalPerformer 0x00002ded 0x1000 + 7661

[MIDI Life Crisis]

Have you tried running M5 in stand alone? Perhaps it is the plug in only that is the issue? That would lead me to believe there is an AU issue in the new OS. Also, have you tried using the DP 5 MAS bundle?

I haven't done the 10.5.5 update, but there are a fair # of reports on other problems as well. It seems like one of those updates that Apple will have to update in and of itself.

Sorry to hear about M5 issues there. I haven't updated because I am in a project that can't be screwed up by wanton (or eggroll) updates. By the time I get around to it, both DP and Leo will probably have updates

[sdfalk]

Thanks for the input as always..

Yes I've tried both standalone mode and AU in Digital performer vs MAS..
No luck.

I have a tech note in with Motu..
here's hoping for a fast reply..
Otherwise a complete reinstall of 10.5.4...I have a backup of the 10.5.4 update file
thank god.

[MIDI Life Crisis]

Thanks for the input as always..

Yes I've tried both standalone mode and AU in Digital performer vs MAS..
No luck.

I have a tech note in with Motu..
here's hoping for a fast reply..
Otherwise a complete reinstall of 10.5.4...I have a backup of the 10.5.4 update file
thank god.

Thanks big (IMO). And you've done the usual trashing and nashing of plists...?

[sdfalk]

I have indeed sir

[Kubi]

Wow, and I was about to install 10.5.5

Phew!!!

Anyone else can verify this? Is anyone running MachFive 2 under 10.5.5 successfully?

[sdfalk]

yeah..lucky me...

So you're fine under 10.5.4 then?

[MIDI Life Crisis]

yeah..lucky me...

So you're fine under 10.5.4 then?

All cool here.

[sdfalk]

Ah Well..whatcha gonna do..
I guess it's time for the big reinstall then..
Ah well..such is life..

[Kubi]

Fine under 10.5.4 in DP5.13 - do you have the MachFive/10.5.5 crashes in DP5.13 as well, or only in DP6.01?

[sdfalk]

5.13-6.01..and standalone=crashes

[Kubi]

Thanks much, you saved my hide. I'm in mid-project but somehow still thought I may update OS. I would have had a clone, but still big interruption... I owe you one...!

So, can anyone else confirm this? Any other MachFive v2 in 10.5.5 testimonials out there?

[MIDI Life Crisis]

Any other MachFive v2 in 10.5.5 testimonials out there?

Maybe that should be testeconials?

Definition: TESTECONIAL

Having the balls to upgrade and then telling everyone about how badly it went.

[sdfalk]

Any other MachFive v2 in 10.5.5 testimonials out there?

Maybe that should be testeconials?

Definition: TESTECONIAL

Having the balls to upgrade and then telling everyone about how badly it went.

[Shooshie]

Well, you know how these things go. There's always SOMEONE who doesn't have any problems. In this case, that would be me. Maybe it depends on which instruments you load, or something like that, but I've been running MachFive2 all evening without a single incident. I'm in DP 6.01 and OSX 10.5.5.

I've been running MachFive2 as standalone with about 16 instruments in it, utilizing lots of its effects. No problems. (same for the plugin) So, I don't know what to tell you, except that you probably ought to go with your gut feeling and if you are afraid of losing functionality in M5.2, then don't upgrade. Let's just say I lucked out and haven't had a single problem with it. ...Yet.


Shooshie