omnispheres and DP 6.01

[michael77]

Hey Folks..........

Omnisheres is crashing DP6.01 fairly consistently. Atmospheres won't work at all in DP6.
Any ideas....... Anyone with the same problem? Is is a motu problem or a
Spectrasonics problem?



G5 dual 2.5 power pc mac os 10.4.11 DP6.01, Stylus RMX, EW orch Platinum Plus,
B4, Mach Five 2,

[Aramis]

Hello !
I have used it with LogicStudio and DP6.01 and it does fine for me but I have OSX 10.5.5 on INTEL .


Aramis

Hey Folks..........

Omnisheres is crashing DP6.01 fairly consistently. Atmospheres won't work at all in DP6.
Any ideas....... Anyone with the same problem? Is is a motu problem or a
Spectrasonics problem?



G5 dual 2.5 power pc mac os 10.4.11 DP6.01, Stylus RMX, EW orch Platinum Plus,
B4, Mach Five 2,

[waxman]

Same here. I really think there is starting to be a break down between new software and older versions. A huge gap has developed. We are no longer talking apples and apples...

Intel and the latest OSX is becoming a complete different system. PPC Tiger and DP 4 or 5 is just working totally different. I am seeing more dual updates for things... PPC users turn left... Intel users proceed with caution. Very strange days. I also believe the recession is going to slooooooowwwwww way down the R&D which is going to create even more trouble.

so that is my happy thought for the day... your welcome

[michkhol]

As for the AU plugin problems, I don't think it is the difference between the operating systems, but the difference between Apple AU and MAS AU host implementations. I'm sure every plugin developer tests his plugins with the Apple supplied AU testing tools. Somehow I don't think MOTU gives away similar tools to test the plugins for their own MAS-based AU host. And even if it did, who would bother? To MOTU's disadvantage there's no (obviously) Apple supplied AU host testing tools. To make the things worse, the PPC and Intel architectures are substantially different and what worked for one will not work for another. The purpose of an AU host is to conceal all these complexities from the plugin developer and provide him with a unified well-behaving interface. MOTU obviously just does not do this job well enough.

[musicarteca]

Omnisheres is crashing DP6.01 fairly consistently. Atmospheres won't work at all in DP6.
Any ideas....... Anyone with the same problem? Is is a motu problem or a
Spectrasonics problem?

G5 dual 2.5 power pc mac os 10.4.11 DP6.01, Stylus RMX, EW orch Platinum Plus,
B4, Mach Five 2,

I have a very similar system that the one you have, actually a slightly slower 2gig dual ppc with OS 10.4.11 and DP 6.01, and Omnisphere works quite well, but it consumes a lot of CPU, so I am always watching the CPU monitor and keeping the number of voices only to those that I am using. How much Ram do you have? You should have at least 4 gigs. All the Atmosphere patches are included in Omnisphere, why would you want to open it?

[modular]

Hey Folks..........

Omnisheres is crashing DP6.01 fairly consistently. Atmospheres won't work at all in DP6.
Any ideas....... Anyone with the same problem? Is is a motu problem or a
Spectrasonics problem?



G5 dual 2.5 power pc mac os 10.4.11 DP6.01, Stylus RMX, EW orch Platinum Plus,
B4, Mach Five 2,

I had a similar problem with Omnisphere and 5.13. Trashing the preferences seemed to correct things (fingers crossed).

[kwiz]

Hey Folks..........

Omnisheres is crashing DP6.01 fairly consistently. Atmospheres won't work at all in DP6.
Any ideas....... Anyone with the same problem? Is is a motu problem or a
Spectrasonics problem?



G5 dual 2.5 power pc mac os 10.4.11 DP6.01, Stylus RMX, EW orch Platinum Plus,
B4, Mach Five 2,

I had a similar problem with Omnisphere and 5.13. Trashing the preferences seemed to correct things (fingers crossed).

Works fine for me on an Intel quad 3ghz using DP5.13. I gave up on DP6 until the next update.
Like Modular stated, I'd try trashing the prefs.

[rikp]

No problem with DP5.13 on a PPC Quad5 with system 10.4.11. Works GREAT! And I love the program My new sage wisdom..never upgrade until you have no other option!

Peace

rikp

[bralston]

All the Atmosphere patches are included in Omnisphere, why would you want to open it?

I could think of a couple reasons.

If anyone needs to open up older files or go back and revisit older tracks.

And/or

Atmosphere uses less CPU on those original patches than Omnisphere does in recreating the Atmosphere patches. If one is already maxing out their CPU due to a lot of V.I.'s running, they can instantiate an Atmosphere patch with a lot less CPU headroom needed, than doing the same thing on Omnisphere...when using a slower computer. But again...I can see a lot of this tied to needing to revisit tracks or cues from the past for some reason.

The last film I scored got a re-edit about 1 year after I turned in the original score and we had the "final mix". I was hired to go back in a re-score and edit cues to match the new visual re-edits as well as add new music. I had to go back to previous cues, reopen them and alter what was there compositionally. Many of those tracks had Atmosphere patches used in some fashion. Luckily, I still have my Dual G5 I could do this on...so I was easily able to go back in and quickly re-score these scenes with the original Atmosphere patches and the custom settings I had used. Re-doing this on another machine using only Omnisphere would have been almost prohibitive considering all the adjustments made to the original ATM patches and settings, especially given the new time frame the re-scoring had to be done in.

So...I can think of some reasons why using Atmosphere rather than the Atmosphere "patches" in Omnisphere would be necessary.

[daveyboy]

I agree with the intel/ppc comment. Since I've had my intel mac I think things just run better on it. I would assume that the developers are coding things more efficiently for intel since it's the future. I wonder how much longer there will be universal binary versions of plugs and software?

[jlaudon]

I haven't had any problems with Omnisphere, but there a few hiccups until I changed it to 'always run in real time'.

[Johnna]

DP 6.1
Dual 2.5 (10.4.11) 5.5 gigs Ram
Omnisphere

Works flawlessly - never had a single crash (using Omnisphere)
Try Spectrasonics group:
http://launch.groups.yahoo.com/group/spectrasonics
Hope this helps
-J

[celestial]

I've just found another seemingly repeatable crash involving Omnisphere in 6.01 (Intel 10.5.5) - namely if I close the Omnisphere window, DP crashes.

And there is another completely repeatable crash which both Spectrasonics and MOTU have been informed about, which involves bouncing to disc. After a BTD Omnisphere tries to reload a different multi (the last one in the list - Xylophonic Springs) - at the same time Play (the East West sample player) will also try and reload the last patch loaded, and doing both at once can crash DP.

Very tiresome.

Here's the first bit of the crash report for the window closing crash (the full thing goes on pages) if anyone can make sense of it:

Process: Digital Performer [256]
Path: /Applications/MUSIC APPS/Digital Performer 6.01.app/Contents/MacOS/Digital Performer
Identifier: com.motu.DigitalPerformer
Version: 6.01 (6.01)
Code Type: X86 (Native)
Parent Process: launchd [106]

Date/Time: 2008-10-20 11:52:11.743 +0800
OS Version: Mac OS X 10.5.5 (9F33)
Report Version: 6

Exception Type: EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes: 0x0000000000000001, 0x0000000000000000
Crashed Thread: 0

Thread 0 Crashed:
0 ??? 0x180ccfd0 0 + 403492816
1 com.spectrasonics.Amber 0x6cb6afba main_macho + 231900
2 com.spectrasonics.Amber 0x6cba952d CVST2AUPluginEntry + 174293
3 com.spectrasonics.Amber 0x6cb453c3 main_macho + 77285
4 com.spectrasonics.Amber 0x6cba952d CVST2AUPluginEntry + 174293
5 com.spectrasonics.Amber 0x6cba952d CVST2AUPluginEntry + 174293
6 com.spectrasonics.Amber 0x6cb5ed32 main_macho + 182100
7 com.spectrasonics.Amber 0x6caaec87 0x6ca94000 + 109703
8 com.spectrasonics.Amber 0x6cb31dfd 0x6ca94000 + 646653
9 com.spectrasonics.Amber 0x6cb7da5c MusicDeviceBase::ComponentEntryDispatch(ComponentParameters*, MusicDeviceBase*) + 7882
10 com.spectrasonics.Amber 0x6cb72bef main_macho + 263697
11 com.spectrasonics.Amber 0x6cb7664c AUBase::ComponentEntryDispatch(ComponentParameters*, AUBase*) + 704
12 com.spectrasonics.Amber 0x6cb7bc85 MusicDeviceBase::ComponentEntryDispatch(ComponentParameters*, MusicDeviceBase*) + 243
13 com.spectrasonics.Amber 0x6cb7ecc2 CVST2AUPluginEntry + 106
14 ...ple.CoreServices.CarbonCore 0x949c1ded CallComponentDispatch + 29
15 ...apple.audio.units.AudioUnit 0x955da883 AudioUnitSetProperty + 67
16 com.MOTU.MAS.AudioUnitSupport 0x1afdc206 AudioUnits::Base::setClassInfo(AudioUnits::PropertyList const&) + 82
17 com.MOTU.MAS.AudioUnitSupport 0x1afdc364 AudioUnits::Base::readClassInfo(IMotuStream*) + 84
18 com.MOTU.MAS.AudioUnitSupport 0x1affb607 MasAUSupportSettings::ReadSetting(MotuException*, long, long, long, IMotuStream*) + 367
19 com.motu.MAS.framework 0x01695108 MAS83147 + 114
20 com.motu.DigitalPerformer 0x000cc9c3 0x1000 + 833987
21 PerfEngine.dylib 0x01aebf80 EffectSettingsImpl::ReadSettings(CStream&, long) + 148
22 com.motu.DigitalPerformer 0x000c71f2 0x1000 + 811506
23 PerfEngine.dylib 0x01a66a9b InsertsSet::SyncToState(InsertSettingsMgr&, sorted_vector_set<InsertsSetIterator, std::less<InsertsSetIterator>, std::allocator<InsertsSetIterator> > const&) + 217
24 PerfEngine.dylib 0x01a5cc41 AudioInsertsSet::WithUpdatesCompleted::WithUpdatesCompleted() + 2077
25 PerfEngine.dylib 0x01a5ccc5 AudioInsertsSet::WithUpdatesCompleted::WithUpdatesCompleted() + 2209
26 PerfEngine.dylib 0x01be5cd5 non-virtual thunk to SelectionAndMemoryTimesLink::PlayChunkModifyCalled(short, void*) + 9821
27 PerfEngine.dylib 0x01a5d28f AudioInsertsSet::WithUpdatesCompleted::WithUpdatesCompleted() + 3691
28 PerfFoundation.dylib 0x02022d1e CIdleChore::IdleAndReturnNextIdleTime() + 432
29 PerfFoundation.dylib 0x02022e47 CIdleChore::Idle(bool) + 11
30 PerfFoundation.dylib 0x02051e1b PeriodicEvents::Timer::DoAction() + 187
31 PerfFoundation.dylib 0x02051adc UIEventUtil::ReceiveNextEvent(unsigned long, UIEventUtil::UIEventTypeSpec const*, double, std::auto_ptr<UIEvent>&) + 162
32 com.apple.CoreFoundation 0x952bdb45 CFRunLoopRunSpecific + 4469
33 com.apple.CoreFoundation 0x952bdcf8 CFRunLoopRunInMode + 88
34 com.apple.HIToolbox 0x9408e480 RunCurrentEventLoopInMode + 283
35 com.apple.HIToolbox 0x9408e299 ReceiveNextEventCommon + 374
36 com.apple.HIToolbox 0x940ecd4e _AcquireNextEvent + 58
37 com.apple.HIToolbox 0x940eb4ab RunApplicationEventLoop + 207
38 com.motu.DigitalPerformer 0x005cea30 0x1000 + 6085168
39 com.motu.DigitalPerformer 0x00002ec6 0x1000 + 7878
40 com.motu.DigitalPerformer 0x00002ded 0x1000 + 7661

[celestial]

Running all plugins in real-time will prevent the Omnisphere "close-the-window" 100% repeatable crash - but not the BTD one.

[bralston]

I've just found another seemingly repeatable crash involving Omnisphere in 6.01 (Intel 10.5.5) - namely if I close the Omnisphere window, DP crashes.

And there is another completely repeatable crash which both Spectrasonics and MOTU have been informed about, which involves bouncing to disc. After a BTD Omnisphere tries to reload a different multi (the last one in the list - Xylophonic Springs) - at the same time Play (the East West sample player) will also try and reload the last patch loaded, and doing both at once can crash DP.

Very tiresome.

Here's the first bit of the crash report for the window closing crash (the full thing goes on pages) if anyone can make sense of it:

Are you contacting Spectrasonics about this and sending them the crash logs you are experiencing as well?????

Their tech support is very responsive. Probably the best in the biz. And I know they are in the process of hiring more tech support guys to handle the influx of new Omnisphere users...if they have not already hired more. Since Eric Persing and the Spectrasonics guys only have a presence on a few internet forums and since these forums are not an official tech support avenue for them...please let them know what you are experiencing with your rig and all the details. It is the only way they will be able to fix these things on the hundreds if not thousands of different computer configurations out there. On my rig...which is an older Dual 2.7 G5 with OS 10.4.11, it is running pretty solid, although heavy on the CPU which they have warned us to expect.