Bit Crush/Project Crash Bug

[someone]

anyone know of a solution to pro tools' bit crush bug that takes over a project now and then? you know, you're in the middle of working on a project that's starting to get fairly intricate and then the audio drops out and suddenly turns all horrible sounding, like it's all being run thru a severe bit crush setting. with some projects this happens so severely that the only way to recover them seems to be to start a new session and import all audio data from the previous now corrupted session.

it's been happening since probably like every version of pro tools ever. pretty lame.

[albee1952]

Not much chance of any help with zero info on your setup. I haven't heard this on my rigs in several years and several versions

[climber]

Never come across this one in 15 years.

[Southsidemusic]

Had this happen on our older Mac Pro computers and we just goto playback engine and choose any other engine and then back again or buffer settings to make it go away. Haven't seen this in the years since we went Trashcan MacPro's and MBP's so maybe its a glitch fromolder OSX.

[john1192]

i am not sure the OP is talking about the Glitchy Sound that can be solved by Toggling the PLayback Engine or not .. been holding off replying until the OP gives more info ..

[remute]

Originally Posted by someone

anyone know of a solution to pro tools' bit crush bug that takes over a project now and then? you know, you're in the middle of working on a project that's starting to get fairly intricate and then the audio drops out and suddenly turns all horrible sounding, like it's all being run thru a severe bit crush setting. with some projects this happens so severely that the only way to recover them seems to be to start a new session and import all audio data from the previous now corrupted session.

it's been happening since probably like every version of pro tools ever. pretty lame.

If this is what I call the "ring modulation" sound that happened with ever overload warning, the only way to stop it was to uncheck Host Engine: "Ignore errors during playback/record" under Setup: Playback Engine.

[someone]

it's an error where you first get a CPU dropout and then all audio in the session is sent to bitcrusher hell until you close and reopen it. just a real nuisance to have to keep bothering with that when a project decides to become prone to this glitch.

specs:

MacBook Pro (Retina, 15-inch, Mid 2015)
2.8 GHz Intel Core i7
16 GB 1600 MHz DDR3
AMD Radeon R9 M370X 2048 MB
Pro Tools 12.5.1

[john1192]

Originally Posted by someone

it's an error where you first get a CPU dropout and then all audio in the session is sent to bitcrusher hell until you close and reopen it. just a real nuisance to have to keep bothering with that when a project decides to become prone to this glitch.

specs:

MacBook Pro (Retina, 15-inch, Mid 2015)
2.8 GHz Intel Core i7
16 GB 1600 MHz DDR3
AMD Radeon R9 M370X 2048 MB
Pro Tools 12.5.1

see Post #5 .. does this solve your issue ??? toggling PLayback Engine ..

[cshaw]

Yep. Toggle the buffer settings in the playback engine. ex. go from 1024 to 512 and back again. You can do it without having close and reopen the playback window too.


Sent from my iPhone using Tapatalk

[someone]

ah ok, yeah, that does seem to work. well toggling the buffer settings occasionally is not too overwhelmingly inconvenient i guess. thanks for the help!