A Pro Tools Glitch Killed My Monitors!

hm, when i read this, i really like the issues i had with cubase 4 today.. because basically it was not doing what it was supposed to do, like playing the recorded part in the same track i has been recorded in. i had to drag it to another track and then back into the origin track...

thank god its not the random white noise

after this production i will upgrade to cubase 5, but ill see if it has even more issues...
 
I'm running m-powered protools 7.4 and this has happened to me twice, the most recent being thursday. Before that some time in January of February. Fucking scares the shit out of me. I've never had to restart the program because of it, it stops after a couple of seconds and it has only done this to me when opening a session.

I'm not sure if this is completely true but its only happened to me when I've opened sessions that are using Revalver MKIII (with a vst wrapper of course).
 
I had this happen recently for the first time, but it was only when I was running my PLAY EastWest Symphonic Choirs with the standalone Wordbuilder software... I haven't experienced the issue otherwise.
Yeah, I have seen these sorts of issues and they have always been plugin related. Sometimes wrapped plugs can cause weirdness and sometimes seemingly minor updates to Protools (7.0-->7.4 for example) will require updates to some of your plugin to function correctly. That's why all bets are off when you use cracked plugs...particularly huge packs such as Waves bundles.
 
Yeah, I have seen these sorts of issues and they have always been plugin related. Sometimes wrapped plugs can cause weirdness and sometimes seemingly minor updates to Protools (7.0-->7.4 for example) will require updates to some of your plugin to function correctly. That's why all bets are off when you use cracked plugs...particularly huge packs such as Waves bundles.

:rolleyes:
 
I get this regularly after I audition a section of audio I've conformed with BD. Sends a burst of whitenoise through the cans at the start of playback... gives me some pretty nasty acoustic shock. My bet is that it relates to PT not being able to get the audio off the drive quick enough but starting playback anyway and fucking up your ears in the process.