DP Rosetta Instability on Start [Resolved]

[dix]

I need to access an older, larger project that relies on VEP, so I'm trying to run DP11.11 in Rosetta mode, and I'm running into two problems.

1. DP usually crashes at least one time on launch. Once it's up and running with a project it's mostly stable, but more prone to crashing than running native. Reexamining the MAS engine, after reconfiguring plugins etc, causes a crash every time.

2. The Abbey Road One plugin gives an Error 1 when DP is running in Rosetta, but not when DP is running natively....this is actually the bigger issue at the moment, since this project is using quite a bit of AR1. I've tried the AU, VST2, VST3 versions. Spitfire LABS is fine

Any advice on how to improve Rosetta stability? And is anyone else able to run AR1 while DP is running in Rosetta?

Thx!

[mikehalloran]

No idea what AR1 is and I don't use VEP. Sorry.

DP 11.11 is running fine for me Native or over Rosetta 2 on my M1. Some of my plugs are not yet Native or never will be.

[dix]

No idea what AR1 is and I don't use VEP. Sorry.

DP 11.11 is running fine for me Native or over Rosetta 2 on my M1. Some of my plugs are not yet Native or never will be.

AR1 = Abbey Road One, which I mention as my No.2 problem. …presumably you don’t have this instrument.

Any ideas why DP might crash on launch? It’s a new one on me.

Thx!

[dix]

After further investigation, it looks like you have to do a Repair of Abbey Road One while the Spitfire (downloader) App is running in Rosetta if you want to run AR1 in Rosetta. However, doing this breaks native compatibility! So in order to get back to native compatibility you have to do the Repair operation again while the Spitfire App is running native.

This is sort of a cumbersome workaround, but at least Abbey Road One can run in either Rosetta or native mode.

[HCMarkus]

You are a resourceful man, dix.

I'm keeping my 5,1 Mac Pro in the machine closet, just in case an old project resurrection ever gives me trouble.

[dix]

You are a resourceful man, dix.

I'm keeping my 5,1 Mac Pro in the machine closet, just in case an old project resurrection ever gives me trouble.

Well, the resource in this case was a Spitfire help document that I stumbled on! My old 5,1 stands at the ready too, but have yet to be forced to use it. Nearly was with this issue though.

I'm still confounded by the crash-on-startup when running in Rosetta. I have a crash log if anyone wants to have a look. Nothing jumps out at me from it...but i have no real idea of how to read it.

Another, probably unrelated, annoyance about crashing while running DP in Rosetta is that if you use the Relaunch option on the crash log page, DP opens in native mode. To remain in Rosetta I have to launch the DP manually. Wondering if anyone else has noticed this.

[HCMarkus]

I've been running DP exclusively Native. I have had a crash here and there and have noted the common issue Crash Reporter lists is Video Access Thread (when working on a score) as the cause of the crash. I've taken to keeping BackBlaze off while working; this may be the conflict, but I'm not 100% certain.

I don't recall encountering your issue, but I don't recall trying to reopen under Rosetta after a crash either.

Those crash logs can be lengthy, but I've noticed that there is usually a listing near the top identifying the thread that crashed.

I'm still confounded by the crash-on-startup when running in Rosetta. I have a crash log if anyone wants to have a look. Nothing jumps out at me from it...but i have no real idea of how to read it.

Another, probably unrelated, annoyance about crashing while running DP in Rosetta is that if you use the Relaunch option on the crash log page, DP opens in native mode. To remain in Rosetta I have to launch the DP manually. Wondering if anyone else has noticed this.

[dix]

I've been running DP exclusively Native. I have had a crash here and there and have noted the common issue Crash Reporter lists is Video Access Thread (when working on a score) as the cause of the crash. I've taken to keeping BackBlaze off while working; this may be the conflict, but I'm not 100% certain.

I don't recall encountering your issue, but I don't recall trying to reopen under Rosetta after a crash either.

Those crash logs can be lengthy, but I've noticed that there is usually a listing near the top identifying the thread that crashed.

Yeah, the crashed thread was the only one I bothered to copy, but I could see nothing relevant.

BUT it looks like I solved this. I noticed that MachFive3 was the last plugin to go by on startup logo before the crashes. Removing that AU seems to have solved the issue. Thanks all!