|
Post by bgrotto on Aug 31, 2022 21:08:56 GMT -6
After years (decades) of running PT, I recently ran into a problem that was stopping me dead in my tracks. Literally. The only way I could solve it was to trash preferences, restart, reset preferences, etc.. A PITA - but it got things going again. But today, I decided to get to the bottom of it. Although I normally work on my own sessions as of late, I had to jump back and forth to a clients sessions at a higher sample rate. Randomly, pro tools just wouldn't go into play. After searching Youtube and listening to all the "usual" reasons which pretty much any PT user would know, I ran across this bug fix that Josh seawell found, documented and put up for dummies like me : No more needing to trash preferences to get things working. THANKS JOSH!!!! I learned something today! Woohooo!! Much appreciated!! Hope you have a great day! This happens when your 88.2 or 96 sample rate session is set to 2048 buffer size, then you switch to a 44.1 or 48 sample rate session. PT remembers the 2048 buffer size, however, that buffer size isn't an option at rates below 88.2, so you gotta open that playback engine window and select 1024 (or lower). It's dumb, but it sorta makes sense as well.
|
|
|
Post by drbill on Aug 31, 2022 21:12:54 GMT -6
After years (decades) of running PT, I recently ran into a problem that was stopping me dead in my tracks. Literally. The only way I could solve it was to trash preferences, restart, reset preferences, etc.. A PITA - but it got things going again. But today, I decided to get to the bottom of it. Although I normally work on my own sessions as of late, I had to jump back and forth to a clients sessions at a higher sample rate. Randomly, pro tools just wouldn't go into play. After searching Youtube and listening to all the "usual" reasons which pretty much any PT user would know, I ran across this bug fix that Josh seawell found, documented and put up for dummies like me : No more needing to trash preferences to get things working. THANKS JOSH!!!! I learned something today! Woohooo!! Much appreciated!! Hope you have a great day! This happens when your 88.2 or 96 sample rate session is set to 2048 buffer size, then you switch to a 44.1 or 48 sample rate session. PT remembers the 2048 buffer size, however, that buffer size isn't an option at rates below 88.2, so you gotta open that playback engine window and select 1024 (or lower). It's dumb, but it sorta makes sense as well. Gotcha! Thx for the explanation. Makes perfect sense. Kinda....
|
|
|
Post by bgrotto on Aug 31, 2022 21:14:15 GMT -6
This happens when your 88.2 or 96 sample rate session is set to 2048 buffer size, then you switch to a 44.1 or 48 sample rate session. PT remembers the 2048 buffer size, however, that buffer size isn't an option at rates below 88.2, so you gotta open that playback engine window and select 1024 (or lower). It's dumb, but it sorta makes sense as well. Gotcha! Thx for the explanation. Makes perfect sense. Kinda.... Totally. It's one of those things that when I figured it out, I face-palmed first for how fucking obvious it was, then again for how fucking stupid it was. Classic Avid 🤣
|
|
|
Post by seawell on Aug 31, 2022 23:41:54 GMT -6
Yes, that makes total sense, lol! Hope you can figure it out. Eh just ended up restarted Protools each time. Not super fast but worked. oddly only did it in one session. Other was fine. Man that stinks...are you setting the file type in the export to MP3 or exporting a wav and checking the "add mp3" box?  Just file type to MP3. Try doing a wav bounce with the add mp3 option & see if it makes a difference.
|
|
|
Post by bchurch on Sept 1, 2022 5:18:28 GMT -6
Funny enough, Cubase does the same thing on my home system, except that it "plays" but no sound comes out. The solution is the exact same too...maybe Mac OS has a bug that causes the system to loose the audio driver? I keep telling myself, "don't change the interface, don't change the interface.... it won't fix it.... let's try another restart.... DAMMIT" Because once that happens... *POOF* I now get to manually reassign about 24 external hardware loops. One by glorious one. Steinberg "is aware" that saving hardware configurations doesn't include external effects. Grrrrr..... Cubase can be easy to love most days, but there are some things that definitely need addressing.
|
|
|
Post by Tbone81 on Sept 1, 2022 10:57:28 GMT -6
Funny enough, Cubase does the same thing on my home system, except that it "plays" but no sound comes out. The solution is the exact same too...maybe Mac OS has a bug that causes the system to loose the audio driver? I keep telling myself, "don't change the interface, don't change the interface.... it won't fix it.... let's try another restart.... DAMMIT" Because once that happens... *POOF* I now get to manually reassign about 24 external hardware loops. One by glorious one. Steinberg "is aware" that saving hardware configurations doesn't include external effects. Grrrrr..... Cubase can be easy to love most days, but there are some things that definitely need addressing. I just updated from Cubase 9 to 12 and couldn’t believe they didn’t add an option to save hardware I/o configurations. So dumb, especially since you can save input configurations.
|
|
|
Post by bchurch on Sept 1, 2022 11:10:27 GMT -6
It’s un-fekking-believable that this known issue hasn’t been addressed after years and years and years DECADES of people asking for it.
You know what people aren’t asking for? A fourth mixer window. Or another 25GB of r&b loops (that you have to manually untick when installing). Thanks, I already got rid of the copy of GarageBand on my Mac (and all its canned audio).
Every time I get stuck in the “no output loop” and hope that my combined restarts, reboots, and screaming in poorly-translated German will work, I pray I don’t wind up manually clicking through 48 individual drop down menus to reroute my external configuration. Invariably, it still happens.
It seems like it should be such an easy fix. Cubase is a imperfect relationship. I still believe it is a vastly superior DAW - but YamaBerg don’t seem to really have their finger on the pulse of what their user base are asking for on their own forums. how hard of a feature could this possibly be to implement? ProTools has had it since v1.
|
|