Pan Automation Bug

[ZEUSS]

I am having problems with pan Automation. Protools is not following pan automation correctly. Anyone else seeing this? It is totally off and staying panned in the wrong direction. Here is a test session. Easy to repeat.


https://copy.com/JNl29pcWLotzR6Lp

[jasonthurley]

Interesting.

It does have an issue with a simple open and playback. If I delete you r panning automation and redraw it it works exactly right.

[Drew Mazurek]

Corrupt session.

Bugs are repeatable on all systems.

Take your session, delete the pan automation, draw in your own, then undo back to your original pan data and it's good. No idea what's going on, but it's not a bug.

[joachim]

Originally Posted by ZEUSS

Easy to repeat.

Yes, in your session on that track. Weird, like a look-ahead-glide. Win7.
Within your session, creating a new track : problem does not occur there.
Apart of your session : never ocurred to me.

[ZEUSS]

Originally Posted by Drew Mazurek

Corrupt session.

Bugs are repeatable on all systems.

Take your session, delete the pan automation, draw in your own, then undo back to your original pan data and it's good. No idea what's going on, but it's not a bug.

I first came across the problem on another session that I did volume automation on. This test session is a fresh new session. Barely any audio on an up to date clean installed system. Others can see the issue on other systems. Doing it again on another track or undoing makes no sense to me when others see the issue.

I will create another fresh basic session and see if it happens there. So far 2 separate sessions here. How many corrupt sessions does it take to consider this a bug?

[joachim]

Zeuss, a question :
Did you use glide-to-all-enabled in your session ?
(It looks like a glide, without it documented in the automation lane)

[Drew Mazurek]

Originally Posted by ZEUSS

Doing it again on another track or undoing makes no sense to me when others see the issue.

everything matters when trying to nail down a repro case for a bug. It's the only way they get fixed.

[joachim]

I was able to reproduce the bug, but cannot remember all the steps and their order, but it included :
track set to ticks ,
tempo operations while track view set to pan , stretch (+100%) and scale, ... , while having a selection that contains an abrupt change from pan 0 to right 100 ,
track set back to samples.
It seems, those tempo operations leave some under-the-hood and not-documented-by-breakpoints pan information.

[Drew Mazurek]

If we can get a solid repro case, I will submit it.

Please try to document it if you have the time, thanks.

[joachim]

While having a track set to ticks and applying tempo operation stretch , as depicted on the screen shot, and playing back the clip, one can already see the "weird" (intended?) panning -
what was funny, still not reproducable - others might chime in : at some "situation" the track reverted itself "automatically" to samples. Then the pan effect was frozen to the glide behaviour versus the abrupt breakpoints.