What's your solution to this automation-overdub problem?

[wary hare]

Dear Bitwig people, here's a question for all of you live musicians, who use the Cliplauncher and control automation via controllers: Imagine you have a Midi-Clip already recorded in the launcher and now want to automate a parameter of the VST instrument via your external controller, by activating the "Write Clip Launcher Automation" button of Bitwig, and then moving the knob of your controller. How do you record the automation in a way, that won't result in something like the screenshot attached here? The latest state of the controller-knob "bleeds" into the beginning of the Clip, as the Loop starts anew. Any tricks to prevent this, aside from being insanely fast at deactivating the "Write Clip Launcher Automation" button right at the last tick of the running loop?😅

[fading umbra]

is that button avaible for a keyboard shortcut maybe?

[wary hare]

yea it is - however, i think it's quite inconvenient/detrimental to flow-state, having to keep in mind to press this right at the last millisecond of the ongoing loop 😄

I have already an idea for a scripted workaround, which automatically deactivates this button, as soon as the clip loop reaches its end -> but i'll have to wait for Bitwig to give us /clip_playback_progress via the API

[drowsy kayak]

yeah... that is something i need as well along with automation control in the api.

For turning off launcher automation you would want to get the automation loop the moment it hits it and turn it off with some sort of event. probably done through an observer method in the api. any other way you would still end up with the same results of the screenshot.

Ideally too you would be able to get/set the automation loop positions as well as knowing the playback positions of those. It would be massive.

[wary hare]

mhm!! so you're sharing the solution-approach-thoughts, yea! Almighty playback-pogress-information is needed 😅

[drowsy kayak]

ok... back to solution oriented what can we do now approach... damn i really wouldn't know other than to read the beat time clock out of transport and somehow combine them with the clip playback state. but it still wouldn't be time accurate enough. would either stop before the clip is done or after.

and again the loop point of automation can be different than the clip!

so badly want this

[wary hare]

Maybe if i can filter out the 8th, out of the /beat/str of the drivenbymoss script, and then tell the button to turn off when the 8th beatcount is reached, yea

only thing missing is the length of the clip

BUT now that i think of it, ha

IF i'm working with fixed clip length anyway (post recording actions), i could link my post recording action-settings to the script. So when i have fixed clip length of 2 bars, the script would know that it has to wait until the 16th beatcount is reached!

But i think that's a really unpleasant project to script, - i better try to forget about the issue, until Bitwig helps us out

[drowsy kayak]

yeah you'd need to capture the beat time when the clip starts and then continually check beat times until you get the value you want. far from ideal... man would LOVE all of this to be in API world

bitwigs automation is so damn awesome too. with the different automation types

although i don't think there is a way to record into Plus or Multiply mode.

you got me dreaming again !!!!

[jade path]

so Latch automation mode doesn't apply to clip launcher?

right, seeing it, those modes for arranger only

[glacial axle]

Yeah, Punch In/Punch Out for the Clip Launcher would be handy