jasonbassin
09-28-2009, 07:30 PM
Everytime i plug in my mbox 2 pro (say i'm listening to a tune on itunes) the computer will automatically switch to the mbox as the output source, as it should, but i will only get maybe one or 2 seconds of audio and then it will stop on me. this never happened with 10.5.x. the computer still recognizes the mbox as the output source after this has happened.
also i am getting the same problem with the coreaudio midi drivers that others are having. (see another post.) the solution offered there is to delete one of the midi drivers, (digidiomidi.plugin i believe) but this isn't working either. protools still freezes upon reaching the "setting up midi drivers" section of boot up. i have to force quit and repeat multiple times. if it does finally boot up, the mbox will stop sending me audio after a few seconds. it has lasted long enough before for me to start checking a mic, at which point the input stopped working as well. when this happens, although i am not hearing any audio, the slider in the mix window will show a constant level of whatever level i was at when it stopped working.
the funny thing is, even with all the frustration, it did suddenly decide to work for a while this afternoon enough for me to have a 2 or 3 hour session. while it was running it was perfectly stable. after that i used it to do some mixing on an old track. took a break for a while, came back and it was just incredibly broken and i've been unable to get in for at least 2 hours. this is killing me.
the only thing i can think of that i did wrong was enter the wrong number for my authorization code the first time i tried to run 8.0.3pr. when that happened i quit, rebooted my cpu, loaded it again and made sure to type it in correctly. did i screw up badly in doing this?
am i just hooped? should i go back to leopard? did i break something?
my system is as follows: macbook pro 13 2.26 core2 duo, 2gigs ram, running 10.6.1 with 64-bit kernel (the problem happens in 32-bit kernel as well)
using a seagate free agent firewire hd daisy chained to an mbox 2 pro (cpu->hd->mbox which is digi's recommendation)
also i am getting the same problem with the coreaudio midi drivers that others are having. (see another post.) the solution offered there is to delete one of the midi drivers, (digidiomidi.plugin i believe) but this isn't working either. protools still freezes upon reaching the "setting up midi drivers" section of boot up. i have to force quit and repeat multiple times. if it does finally boot up, the mbox will stop sending me audio after a few seconds. it has lasted long enough before for me to start checking a mic, at which point the input stopped working as well. when this happens, although i am not hearing any audio, the slider in the mix window will show a constant level of whatever level i was at when it stopped working.
the funny thing is, even with all the frustration, it did suddenly decide to work for a while this afternoon enough for me to have a 2 or 3 hour session. while it was running it was perfectly stable. after that i used it to do some mixing on an old track. took a break for a while, came back and it was just incredibly broken and i've been unable to get in for at least 2 hours. this is killing me.
the only thing i can think of that i did wrong was enter the wrong number for my authorization code the first time i tried to run 8.0.3pr. when that happened i quit, rebooted my cpu, loaded it again and made sure to type it in correctly. did i screw up badly in doing this?
am i just hooped? should i go back to leopard? did i break something?
my system is as follows: macbook pro 13 2.26 core2 duo, 2gigs ram, running 10.6.1 with 64-bit kernel (the problem happens in 32-bit kernel as well)
using a seagate free agent firewire hd daisy chained to an mbox 2 pro (cpu->hd->mbox which is digi's recommendation)