jzhwu
New Member
Hey everyone, first time poster here and new to composing.
I saw another thread from a couple of years ago that seems relevant to the issue I'm experiencing: https://vi-control.net/community/th...-track-region-automation-in-logic-10-4.72536/
So this is specifically with recording automation such as adjusting expressing + dynamics with CC controls. (both using the mod wheel, and audioswift mapping touchpad => CC events) Based on the linked thread which talks about experiencing this in Logic I don't think this issue is specific to Ableton.
What (I think) happens is that both track and midi CC automation is recorded separately into the sequencer, and on playback they start fighting each other when the recorded values aren't exactly 1:1. I noticed this issue because the re-enable automation button kept lighting up when the playhead hit the clip I recorded and that the values weren't always changing based on what the track automation values were.
So there's a couple of solutions to this I figured out:
1. Disable host automation on the BBSCO plugins. This would stop recording track automation and only CC automation. The problem with this is that it's hard for me to see at a glance what the curve looks like across multiple clips, and I kinda like how Ableton shows the automation curves inline with the clip on the sequencer. Pro with this is that it'll just work, but one potential downside I see is that if at any point in the future I decide to change the CC mapping on an instrument, older compositions that assumed the old CC values are borked. Don't know how much this really matters though.
2. Manually delete CC automation post recording. This keeps the track automation, but I'll have to do this for every clip I record with touch controls. It's an annoyance, but it'll work.
How do most of you deal with this? Is there another option that I'm not aware of?
I saw another thread from a couple of years ago that seems relevant to the issue I'm experiencing: https://vi-control.net/community/th...-track-region-automation-in-logic-10-4.72536/
So this is specifically with recording automation such as adjusting expressing + dynamics with CC controls. (both using the mod wheel, and audioswift mapping touchpad => CC events) Based on the linked thread which talks about experiencing this in Logic I don't think this issue is specific to Ableton.
What (I think) happens is that both track and midi CC automation is recorded separately into the sequencer, and on playback they start fighting each other when the recorded values aren't exactly 1:1. I noticed this issue because the re-enable automation button kept lighting up when the playhead hit the clip I recorded and that the values weren't always changing based on what the track automation values were.
So there's a couple of solutions to this I figured out:
1. Disable host automation on the BBSCO plugins. This would stop recording track automation and only CC automation. The problem with this is that it's hard for me to see at a glance what the curve looks like across multiple clips, and I kinda like how Ableton shows the automation curves inline with the clip on the sequencer. Pro with this is that it'll just work, but one potential downside I see is that if at any point in the future I decide to change the CC mapping on an instrument, older compositions that assumed the old CC values are borked. Don't know how much this really matters though.
2. Manually delete CC automation post recording. This keeps the track automation, but I'll have to do this for every clip I record with touch controls. It's an annoyance, but it'll work.
How do most of you deal with this? Is there another option that I'm not aware of?
