|
|
Post by tonycamphd on Mar 20, 2015 11:15:06 GMT -6
what the hay is this? i cant open any of my sessions without getting this pop up, i've restarted everything, double checked my set up, everything is as it was, all i did last night was convert/up sample some 44.1/24 bit audio files into a new session, and now NONE of my session work and all get that pop up. Any ideas? thanx  |
|
|
|
Post by Johnkenn on Mar 20, 2015 11:39:37 GMT -6
Do you have any program like melodyne open?
|
|
|
|
Post by brucerothwell on Mar 20, 2015 11:44:07 GMT -6
I've seen that error, too.
Somehow, something is making Pro Tools think you are trying to use a different audio playback engine, even though I did not specifically change it _within_ Pro Tools.
It must be a glitch.
|
|
|
|
Post by indiehouse on Mar 20, 2015 11:48:37 GMT -6
What's your playback engine set to? Sometimes mine will change to something like SPDIF, especially if I forget to turn the RM DAC on first. I get the exact same error message.
|
|
|
|
Post by tonycamphd on Mar 20, 2015 11:49:52 GMT -6
Thanx fella's, i closed all other open programs, restarted, i went into prefs and selected the 002 straight up, i guess i need to see if any plugs are odd, all i did to this new session last night was edit, and filter, nothing really? weird. Next i'm going to repair all the disk permissions..
|
|
|
|
Post by jcoutu1 on Mar 20, 2015 12:04:35 GMT -6
Thanx fella's, i closed all other open programs, restarted, i went into prefs and selected the 002 straight up, i guess i need to see if any plugs are odd, all i did to this new session last night was edit, and filter, nothing really? weird. Next i'm going to repair all the disk permissions.. I would guess that you had iTunes (or similar) open and linked with your 002. When you tried opening the session at a higher rate, it couldn't open because iTunes had it locked in. |
|
|
|
Post by drbill on Mar 20, 2015 12:15:06 GMT -6
Thanx fella's, i closed all other open programs, restarted, i went into prefs and selected the 002 straight up, i guess i need to see if any plugs are odd, all i did to this new session last night was edit, and filter, nothing really? weird. Next i'm going to repair all the disk permissions.. I would guess that you had iTunes (or similar) open and linked with your 002. When you tried opening the session at a higher rate, it couldn't open because iTunes had it locked in. This. PT used to not open when that happened. Now it seems to open, but lock you out. And for good reason. |
|
|
|
Post by tonycamphd on Mar 20, 2015 12:41:34 GMT -6
I got it, funny, i never, ever change this set up, but somehow it switched to the aggregate under playback settings? i went in there and simply switched back to 002, and it rebooted PT and seems ok, jcoutu1 that is the one thing that conflicts here, i always have to make sure itunes is shut down or no go... thanx for the help guys 8) |
|
|
|
Post by jdc on Mar 21, 2015 16:59:09 GMT -6
a few weeks ago i took the motu 16a to a friend's house to record some bass for a project we're working on and pro tools decided that my default playback engine should be his AirPlay and not the thunderbolt-connected hardware device I had been using the previous day. The problem gave me this same error message you had tony, I had to reselect the 16a every time I opened a new session.
How does pro tools mistake a never-before-seen wireless network for THE DEFAULT PLAYBACK ENGINE I JUST USED YESTERDAY?
Anyways, glad to see you're up and running again!
|
|
|
|
Post by tonycamphd on Mar 21, 2015 19:21:10 GMT -6
a few weeks ago i took the motu 16a to a friend's house to record some bass for a project we're working on and pro tools decided that my default playback engine should be his AirPlay and not the thunderbolt-connected hardware device I had been using the previous day. The problem gave me this same error message you had tony, I had to reselect the 16a every time I opened a new session. How does pro tools mistake a never-before-seen wireless network for THE DEFAULT PLAYBACK ENGINE I JUST USED YESTERDAY? Anyways, glad to see you're up and running again! hmmm, so now the last three time I opened up pro tools and then a session, I get the same error message, and need to reset and relaunch PT? WTH? i did nothing different than ever? weird.... |
|
|
|
Post by drew571 on Mar 22, 2015 1:41:32 GMT -6
Yeah, I've been trying to reproduce this error and for the life of me haven't been able to. Oh, that's right, I'm in Cubase.
|
|
|
|
Post by Ward on Mar 23, 2015 8:24:12 GMT -6
Anyone heard of the "7.3 exception" error?
|
|
|
|
Post by NoFilterChuck on Mar 24, 2015 6:29:04 GMT -6
a few weeks ago i took the motu 16a to a friend's house to record some bass for a project we're working on and pro tools decided that my default playback engine should be his AirPlay and not the thunderbolt-connected hardware device I had been using the previous day. The problem gave me this same error message you had tony, I had to reselect the 16a every time I opened a new session. How does pro tools mistake a never-before-seen wireless network for THE DEFAULT PLAYBACK ENGINE I JUST USED YESTERDAY? Anyways, glad to see you're up and running again! i'm not a software developer, but i've been tinkering with programming. I'd bet that bug has to do with a permissions thing, meaning that ProTools can't write or save the .plist file whenever you exit a session. the .plist (mac) is the preferences file that stores a program's settings. Just a guess, tho. |
|
|
|
Post by Ward on Mar 24, 2015 6:58:22 GMT -6
a few weeks ago i took the motu 16a to a friend's house to record some bass for a project we're working on and pro tools decided that my default playback engine should be his AirPlay and not the thunderbolt-connected hardware device I had been using the previous day. The problem gave me this same error message you had tony, I had to reselect the 16a every time I opened a new session. How does pro tools mistake a never-before-seen wireless network for THE DEFAULT PLAYBACK ENGINE I JUST USED YESTERDAY? Anyways, glad to see you're up and running again! i'm not a software developer, but i've been tinkering with programming. I'd bet that bug has to do with a permissions thing, meaning that ProTools can't write or save the .plist file whenever you exit a session. the .plist (mac) is the preferences file that stores a program's settings. Just a guess, tho. in that case, try deleting the preferences files and then restarting PT. Some times that's all it takes. |
|
|
|
Post by jdc on Mar 24, 2015 10:56:41 GMT -6
i'm not a software developer, but i've been tinkering with programming. I'd bet that bug has to do with a permissions thing, meaning that ProTools can't write or save the .plist file whenever you exit a session. the .plist (mac) is the preferences file that stores a program's settings. Just a guess, tho. in that case, try deleting the preferences files and then restarting PT. Some times that's all it takes. Ahh that makes sense. I'll mess with this after I finish this session and my docket is cleared. Thanks guys! |
|
