Greetings Everyone -
I have a Pulsar II card in a Mac G4 400 under OS 9.2.2 running Scope, Digital Performer 2.72, OMS and Peak. The setup has been working quite well for months.
Now, for reasons that I cannot define, Digital Performer will not load the Audio Driver upon launch, and will give MIDI only. When I try to engage the Audio - DP crashes giving error(s) 2 or 3.
PEAK works fine - can engage Creamware ASIO etc - all no problemm it is only DP that is a problem.
I have reinstalled DP, Disk Doctored and Defragged everything, trashed prefs etc - all several times - but the problem remains, DP cannot find or see the Creamware ASIO Driver /Creamware Audio driver.
Actually when I try to launch DP pre-Scope launch - the error message is "DP cannot load Creamware ASIO" - and - if I try to launch DP post Scope launch - the error message is: "Audio Driver not loaded - MIDI only"
If anyone has any input I appreciate it greatly
I am like...way stuck.
thanks in advance -
Ed
Mac>DP>Audio Driver
sounds very weird...
did you tryto renew the CWA audio driver in the DP driver folder?
I don't know/use DP, so I can't help really
Also, go to the sound controll panel and get back to the start position: choose 'cd' as input, and 'build in' as output, if you don't have this already.
After that start Peak and reset audio output to soundmanager, to 'free' the audio routing 100%.
Restart the mac.
See if it works, tell us what happens
good luck
did you tryto renew the CWA audio driver in the DP driver folder?
I don't know/use DP, so I can't help really

Also, go to the sound controll panel and get back to the start position: choose 'cd' as input, and 'build in' as output, if you don't have this already.
After that start Peak and reset audio output to soundmanager, to 'free' the audio routing 100%.
Restart the mac.
See if it works, tell us what happens

good luck
These are great suggestions Hubird and I was SURE they were going to resolve the situtation - but to my surprise:not
regardless it is a good routine to remember
This must be some weird DP issue...that i have never encountered in 4 years of constant use...
i think i need a Mac OS9 Sequencers forum, if anyone knows of one, please post
thanks again -
Ed
regardless it is a good routine to remember
This must be some weird DP issue...that i have never encountered in 4 years of constant use...
i think i need a Mac OS9 Sequencers forum, if anyone knows of one, please post
thanks again -
Ed
Hi Ed 
Ok, maybe it's something adventurous, as I use Cubase on pc....but sometimes in the past, after a Cubase crash, Cubase itself wouldn't recognize the asio drivers anymore...
As Cubase has a panel to choose the audio drivers and eventually switch them, I could cure it by providing in my Scope project both Asio and "Wave" drivers (common higher latency system drivers), so it would load the last ones instead of Asio, then going to his panel and switching Asio back...
At least this worked in my system, as Wave drivers allowed Cubase to load audio engine, and I could then switch to Asio...
I never saw DP in my life, so I don't pretend this is a solution, but just a phenomenon that "could" have some analogy with yours.
Ciao

Ok, maybe it's something adventurous, as I use Cubase on pc....but sometimes in the past, after a Cubase crash, Cubase itself wouldn't recognize the asio drivers anymore...
As Cubase has a panel to choose the audio drivers and eventually switch them, I could cure it by providing in my Scope project both Asio and "Wave" drivers (common higher latency system drivers), so it would load the last ones instead of Asio, then going to his panel and switching Asio back...
At least this worked in my system, as Wave drivers allowed Cubase to load audio engine, and I could then switch to Asio...
I never saw DP in my life, so I don't pretend this is a solution, but just a phenomenon that "could" have some analogy with yours.
Ciao

Well - yes. Somehow between all of this toggling + trashing all prefs again and reinstalling OMS...everything now works.
Overall I have found that successful work in SFP on the Mac is a result of careful ordering of procedures - once you get it down and understand what order things must be opened and closed in, everything works. I did do some work recently in which I varied that order, and I thought everything was fine, but apparently not.
Thanks again Hubird and Alfonso
Ed
Overall I have found that successful work in SFP on the Mac is a result of careful ordering of procedures - once you get it down and understand what order things must be opened and closed in, everything works. I did do some work recently in which I varied that order, and I thought everything was fine, but apparently not.
Thanks again Hubird and Alfonso
Ed
glad you fixed it, Alfonso's trick is also nice 
and yes, the order of things IS important, never close Scope before closing Cubase!
It takes one or two restarts plus trashing prefs of soundpanel and Cubase-ASIO prefs to get the audio link repaired.
But...on mac you don't have to doubt the hardware setup together with the operating system, and that's gold ladies and gentlemen...!
sorry for this interruption 

and yes, the order of things IS important, never close Scope before closing Cubase!
It takes one or two restarts plus trashing prefs of soundpanel and Cubase-ASIO prefs to get the audio link repaired.
But...on mac you don't have to doubt the hardware setup together with the operating system, and that's gold ladies and gentlemen...!


