Interesting 12.6.1 bug - stereo tracks

[biasrocks]

While mixing today I ran across a totally new issue that I've never had.

Recording my stereo mix back into Pro Tools from tape. Monitored while recording back in, sounded and looked fine. Went to play it back after recording finished and it was in mono, both side were identical.

Restarted Pro Tools and that seemed to resolve the issue, but it did come back a few times. Drove me nuts.

Anyone else run into this issue?

I'm on Win 7.

Mark
Sharktankpro.com

[Drew Mazurek]

Originally Posted by biasrocks

While mixing today I ran across a totally new issue that I've never had.

Recording my stereo mix back into Pro Tools from tape. Monitored while recording back in, sounded and looked fine. Went to play it back after recording finished and it was in mono, both side were identical.

Restarted Pro Tools and that seemed to resolve the issue, but it did come back a few times. Drove me nuts.

Anyone else run into this issue?

I'm on Win 7.

Mark
Sharktankpro.com

I get this occasionally as well. Next time just deactivate/reactivate the track and it'll come back, no need to restart PT. Haven't been able to pin down a repeatable way to make it happen yet.

[TimNielsen]

What is TRULY terrifying about bugs like these, and many others we've been finding lately, where PT will simply stop following a pan, or just not output certain tracks, or mistakenly re-order the output of a 5.1 track, say all to the left...

What is terrifying, is that the basic CORE of ProTools is broken, if these are possible to happen. When we're working with a thousand tracks on a film, when something like this happens, we may not notice it. If the person above hadn't been paying attention, maybe they would have shipped to a client a dual-mono mix instead of stereo.

That these are now happening in PT11 and PT12 ought to scare the hell out of us. A crash is one thing. But these random screw-ups with the core of what PT or any DAW does, is truly awful.

And Avid seems to have NO clue as why they are happening. And we've been telling them about it for MANY versions of PT now, and they seem no closer to being able to fix it. How can this even BE?

[P_J]

These kind of bugs are the worst possible. Another ghost bug I have witnessed is random audio cuts (playback). Suddenly audio track starts to have silent moments with no reason. Deactivate/reactivate track doesn't help, only restarting PT helps. This affects both bounce and playback, but it's very rare. It happens only when you have been working for several hours without restarting PT.

[strangeLoop]

Yes, a bug like this would make film/TV postproduction impossible with Pro Tools.
An error discovered down the line would cost a lot of money to repair. I have seen it happen where a small error in a stem can cause an M&E to get rejected a week or two later when the crew is on to a new project, or out of the country....

[drums77]

Same problem here with my HDX and PT HD 12.6

[JFreak]

I haven't seen this here, but now you got me worried

[sleepingtiger]

Originally Posted by TimNielsen

What is TRULY terrifying about bugs like these, and many others we've been finding lately, where PT will simply stop following a pan, or just not output certain tracks, or mistakenly re-order the output of a 5.1 track, say all to the left...

What is terrifying, is that the basic CORE of ProTools is broken, if these are possible to happen. When we're working with a thousand tracks on a film, when something like this happens, we may not notice it. If the person above hadn't been paying attention, maybe they would have shipped to a client a dual-mono mix instead of stereo.

That these are now happening in PT11 and PT12 ought to scare the hell out of us. A crash is one thing. But these random screw-ups with the core of what PT or any DAW does, is truly awful.

And Avid seems to have NO clue as why they are happening. And we've been telling them about it for MANY versions of PT now, and they seem no closer to being able to fix it. How can this even BE?

This. It is so maddening to no longer be able to count on Pro Tools' core functionality. In another thread I outlined how a client recently called me the day after a session to alert me to an insane offline bounce that I had inadvertently given him where the audio had been bizarrely scrambled on the timeline. Not only was the bounce garbage but the audio on the timeline in the session was affected. This is just one of a handful of these types of instances on top of endless 9xxx errors and all sorts of interface glitches.

It's sad but after 20 years of Pro Tools I'm looking around for another DAW. I would rather stick with PT but I can't afford to take the inherent risks with clients. Despite being completely fiendish with backups and redundancies I'm constantly paranoid now as to what I'm going to find when I open up sessions each day. Yes, these sorts of things are rare but they should never be happening at all.

[climber]

Originally Posted by sleepingtiger

=In another thread I outlined how a client recently called me the day after a session to alert me to an insane offline bounce that I had inadvertently given him where the audio had been bizarrely scrambled on the timeline. Not only was the bounce garbage but the audio on the timeline in the session was affected.

the bug IS a drag, tho so far it's not affected me. and apparently it's not hugely widespread, or more would be affected.

that said, I am very surprised you would send a client a bounce without listening to it all the way through.

[arche3]

I always bounce into protools and monitor real-time. I never trusted bounce to disk or now offline bounce. But I'm making records so each song is only 3 minutes long. And commercials are 30 seconds so that's not a big deal. For people who score films I can see monitoring all the stems in realtime can be troublesome.

Sent from my SM-G935V using Tapatalk