Glide Automation bug in PT 10.3.4

[mgoorevich]

Just thought it's important to be a separate thread:

Glide Automation Command - Glide to Current / All Enables DOES NOT work as it should in PT HD 10.3.4 (Shift+Opt+ / )
Instead of slope I get the straight line with break points.
It worked perfect in 10.3.3.

[joachim]

I switched yesterday from 10.3.2 to 10.3.4, and was confused, that my old surround panning habit did not work anymore :-(.

Did you use glide-to-all-enabled while editting in the edit window over existing automation or
while moving a parameter on the fader/surroundpanner to the position to be glided to ?

I did the first possibility and it gave me also the straight lines.
But making a selection and changing the position in the surround panner and then glide-to-all-enabled produced the desired ramp.

[Danny Caccavo]

Originally Posted by mgoorevich

Just thought it's important to be a separate thread:

Glide Automation Command - Glide to Current / All Enables DOES NOT work as it should in PT HD 10.3.4 (Shift+Opt+ / )
Instead of slope I get the straight line with break points.
It worked perfect in 10.3.3.

Actually, it's been broken since 10.3 at least, and only just now fixed in 10.3.4. Could you post an exact recipe for what you are seeing?

[mgoorevich]

Originally Posted by Danny Caccavo

Actually, it's been broken since 10.3 at least, and only just now fixed in 10.3.4. Could you post an exact recipe for what you are seeing?

Have a plugin automation for several parameters (or even just the volume)
Make the selection between two different levels A and B, and hit Sh+Opt+/ or just Opt+/ for current.
It will result that all the automation in B area will be wiped to the automation level of A instead having a gentle slope from A to B (glide).

[joachim]

Originally Posted by mgoorevich

Make the selection between two different levels A and B, and hit Sh+Opt+/ or just Opt+/ for current.
It will result that all the automation in B area will be wiped to the automation level of A instead having a gentle slope from A to B (glide).

Did you make the different level for B using the fader, or for plugin,
with the plugin open and moving the knobs ?
It seems, it is not working afterwards with area A and B already having different levels and than assigning an area where the slop should be.


PT Ref Guide , p.1057
4. Change the automation parameter to the value you want at the end of the selection.
For example, to glide automation volume to –Infinity, move the Volume fader to –Infinity.

[mgoorevich]

Originally Posted by joachim

Did you make the different level for B using the fader, or for plugin,
with the plugin open and moving the knobs ?
It seems, it is not working afterwards with area A and B already having different levels and than assigning an area where the slop should be.


PT Ref Guide , p.1057
4. Change the automation parameter to the value you want at the end of the selection.
For example, to glide automation volume to –Infinity, move the Volume fader to –Infinity.

Ok the most simple case:
On the volume graph make selection. With a trim tool decrease the volume to -10 db.
Now try to perform the Glide to current command by selecting area from 0db to -10 db.
In my situation even this does;t work. And yes, in auto enable window, the volume is enabled.

[Danny Caccavo]

Originally Posted by mgoorevich

Ok the most simple case:
On the volume graph make selection. With a trim tool decrease the volume to -10 db.
Now try to perform the Glide to current command by selecting area from 0db to -10 db.
In my situation even this does;t work. And yes, in auto enable window, the volume is enabled.

It's not supposed to work this way. You're supposed to make a selection, change the parameter, and "glide to." The result is that it will glide to the new position you just changed the parameter to.

Now, here's the odd thing - somehow it must have changed to do what you're talking about in 10.3.3. It doesn't work this way even back in 9.0.5 - it was never meant to.

So now Avid has the unenviable task of incorporating the "useful mistake" they made into their NEXT point release!

[mgoorevich]

Originally Posted by Danny Caccavo

It's not supposed to work this way. You're supposed to make a selection, change the parameter, and "glide to." The result is that it will glide to the new position you just changed the parameter to.

...And this is where I noticed it happened (actually NOT) for the first time.
So I always perceived that the glide automation is designed to "softly" change parameters between two automation areas.
I used it often in the preview mode, after "write to all" command to eliminate clicks and artefacts at newer created automations lines.

[Danny Caccavo]

Actually, if you just select that area and do "cut" you get the same result as "glide to" in 10.3.3. Well, at least on that one playlist.

[joachim]

Originally Posted by mgoorevich

Ok the most simple case:
On the volume graph make selection. With a trim tool decrease the volume to -10 db.
Now try to perform the Glide to current command by selecting area from 0db to -10 db.
In my situation even this does;t work. And yes, in auto enable window, the volume is enabled.

"volume graph" : you mean Track View set to volume ?

You CANNOT use glide-to-all-enabled making selections of areas containing existing automation (anymore).

Try this :
one clip , volume 0
selection of clip , write to all enabled (volume only in automation window)(to add breakpoints at start and end)
now : selection middle of clip to end of clip
fader (not the volume line in the edit window !), move to -10dB
glide-to-all-enabled
result : from the middle of the clip to the end the volume goes continuously from 0 to -10

The ref guide talks about using the VOLUME FADER, not the volume automation lane line, NOT about using the TRIM TOOL, it is about using the knob/fader/poti parameter.