Title
clip gain info disappears after audiosuite render, this script gets it back for a single clip. how to mod for multiple clips?
What do you expect to happen when you run the script/macro?
clip gain info disappears after audiosuite render, this script gets it back for a single clip.
Are you seeing an error?
script only works on a single clip, not on a selection of multiple clips.
What happens when you run this script?
works well one a single clip, not on a selection of multiple clips.
How were you running this script?
I used a keyboard shortcut within the target app
How important is this issue to you?
5
Details
{
"inputExpected": "clip gain info disappears after audiosuite render, this script gets it back for a single clip.",
"inputIsError": true,
"inputError": "script only works on a single clip, not on a selection of multiple clips.",
"inputWhatHappens": "works well one a single clip, not on a selection of multiple clips.",
"inputHowRun": {
"key": "-Mpfwh4RkPLb2LPwjePT",
"title": "I used a keyboard shortcut within the target app"
},
"inputImportance": 5,
"inputTitle": "clip gain info disappears after audiosuite render, this script gets it back for a single clip. how to mod for multiple clips?"
}
Source
sf.ui.proTools.clipGainCreateBoundaryBreakpoints();
Links
User UID: qxvuxIROjqhCgyum17n87NP7TKo2
Feedback Key: sffeedback:qxvuxIROjqhCgyum17n87NP7TKo2:-NOENINpWN_7OQIh6hU1
In reply todaniel_perez⬆:Raphael Sepulveda @raphaelsepulveda2023-02-14 21:08:39.856ZHey @daniel_perez,
I'm going to need a little more clarification on this one.
When you render an AudioSuite process on a clip, the clip gain gets consolidated as part of the render, and the clip gain gets reset to 0dB in the newly created clip. Is that what you mean when you say that the clip gain info disappears?
If so, how are you getting that back with
sf.ui.proTools.clipGainCreateBoundaryBreakpoints();? I couldn't repro this behavior.From what I gather, you want to copy the clip gain (... and possibly clear the clip gain so you don't get double the clip gain?), process the clip with an AudioSuite process, then paste the clip gain back. And do this for every clip selected. Does my assumption sound right?
Daniel Perez @daniel_perezrendering clip by clip and individual files, removes the clip gain info (using most of the plugins.) it's a pt bug, never adressed. this script gets the clip gain info back. but the script only works on a single clip, not on a selection of clips. auto align post for example is one of the plugins removing the clip gain info.
Raphael Sepulveda @raphaelsepulveda2023-02-14 21:17:51.868ZAh, interesting.
If it's just a matter of applying that function to all the selected clips, then you can use this:
sf.ui.proTools.clipDoForEachSelectedClip({ action: () => sf.ui.proTools.clipGainCreateBoundaryBreakpoints() });- Daniel Perez @daniel_perez
thank you! i will try it. i hope it works, so we don't need a jump through one clips at a time script.
- Raphael Sepulveda @raphaelsepulveda2023-02-14 21:44:50.171Z2023-02-14 21:55:53.581Z
Yeah, unfortunately, this is one of those scripts lol
I looked more into this and was able to repro the bug—by rendering with a Channel Strip AS plugin.
I was also able to distill what part of
sf.ui.proTools.clipGainCreateBoundaryBreakpoints();is amending the issue and it comes down to this:sf.ui.proTools.menuClick({ menuPath: ["Edit", "Clear Special", "Clip Gain"] }); sf.ui.proTools.menuClick({ menuPath: ["Edit", "Paste"] });(clearing the clip gain, which apparently also copies the clip gain before doing so, and then pasting it)
You can run this on multiple clips at once but, unfortunately, only the clip gain value of the first clip gets copied and applied to all the others. So this is only helpful if all the clips have the same clip gain. If not, then my first suggestion seems to be the most bearable workaround to deal with this bug.
Definitely something worth reporting to Avid.
- In reply toraphaelsepulveda⬆:Daniel Perez @daniel_perez
does avid actually care about reports like this? i think they don't have very good channels to receive user feedback and don't really allocate the capacity to fix bugs properly.
- Raphael Sepulveda @raphaelsepulveda2023-02-15 20:47:01.707Z
One can only hope. Seems to be the only thing we can do.
