ok, here’s another one, it’s a combo of a macro and a PLE script. it does pro tools style automation trim, without having to resort to ‘trim’ or ‘loop’ functions on the automation panel.
(what it does is, you select a range, it creates automation events on the edges of the selection, then jumps a frame to the left of the left edge and creates a point, and a frame to the right of the right edge, then selects the inner left and right points and switches back to the the select tool, so you are ready to go and scale / trim your selection, without affecting the rest of your automation curve. pretty cool, for my needs anyways.)
if you use the line over existing automation, you will overwrite whatever is already written there; this is more like ‘trim’ without using actual trim functionality on the automation pane (=you can scale the curve that resides in your selected area).
it’s the rest that has proven quite a challenge. anyhow, here’s the macro as best as i could tweak it thus far. there is still an issue, and i’m hoping you can help me fine-tune that one: if there are more automation tracks for the given channel, the PLE script (=the last step in the macro) selects all the automation events inside the range for all the automation tracks on the given channel. in other words, i need to write a PLE script that selects the automation events inside the cycle, but only on the track for the one parameter you are trying to trim.
(edit: you could actually see this as an added functionality… in that all the parameter automation on the given track in the given range gets selected, so you are free to make adjustments to more parameters. still, i am wondering if someone can make a 'select automation events for the parameter on the selected track in the selected range. no matter what combination of PLE commands i tried i couldn’t come up with one.)
–the macro:
edit - copy
edit - paste
transport - locate selection
transport - nudge -1 frame
edit - left selection side to cursor
transport - locate selection end
transport - nudge +1 frame
transport - nudge +1 frame
edit - right selection side to cursor
edit - copy
edit - paste
transport - locate selection
transport - locate next event
edit - left selection side to cursor
transport - locators to selection
tool - select tool
process project logical editor - “your PLE script to select automation inside cycle” (see below)
–the PLE script:
media type equals automation
position inside cycle PPQ
//
function - select
Why? Either way, You won’t edit all parameters at once. Let say, I wanna edit volume, but Macro selected pan events either, but when I move volume curve, my actions have no effect on the pan automation. So, why be bothered?
But, if in Prefs you’ve got “Track selection follows event selection” checked, it’ll be easy.
Edit -> Select all on tracks
PLE:
(Property ______Is set________event is selected___and
Media Type is __Equal________Automation_______and
Position_______Inside cycle______PPQ ____________).
But, if you don’t use “Track selection follows event selection”, i don’t know…yet. But, sure, you can choose track manually.(but you need always remember to do that)
there’s one area that could tighten this up even more. as it is, my macro is using ‘frame nudges’ to create neighbouring automation events as close as possible. this still produces ~30-45 ms gap between the adjacent automation events. i wondered if there is a way to nudge the transport in ticks using a macro / kc / PLE. i can easily nudge an event in ticks using PLE, but how would one do this with the cursor? (possibly using a workaround… an automation event nudged in ticks, then using the ‘locate selection’ command. oh well…)
not sure, working 100% now here on cubase 6.0.7; also tested as working in a nuendo 4 studio (though nuendo 4 doesn’t offer the new automation scaling possibilities introduced in c6)
(my c7 demo has expired and not planning on buying, it sucks for what i do, so i cannot test it).
It almost worked. But the macro won’t create the 2 events at start and end borders, I think. Maybe C7 is different… Or it’s a question of OsX/Windows version. I will try to understand what’s the problem.
Hi,
in C7 everything works as expected with the original macro from lukasbrooklyn. His macro has “transport - nudge +1 frame” string doubled, you can skip 1.
BTW, here’s another Macro to do the same job, but operating with seconds not frames.
The last string refers to PLE Macro form the previous version.
But sorry guys, nothing comes for free, to use this Macro you’ll need to set your Ruler Display Format to Seconds and set Grid Type to 1ms manually. When all your editing is done you can switch your Ruler Display Format back (if needed). I know it takes time and clicks, but sometimes it’s much easier, than putting all those new nodes around the range of automation you want to select and edit.
Cool. This is a brilliant discovery. The rest is easy. Thanks.
