Jump to content

SEQ15 - CC hidden automation writing with interference curve result

Recommended Posts

Dear Community,

In the video (link) you see a bit of automation writing in the background into the object automation. It does not delete any of the old lane curves, which is confusing. When you extract the barely visible automation curves to the lanes, though, they get merged with the old ones, which is not intended with a hardware controller realtime run.


This implies some questions for a workflow:


How to write hardware controller data to the lanes only not confusing with the object automation?

How to avoid the interference when overdubbing automation curves per se?

(will load up video asap)




Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now