Maybe I’m doing something wrong, maybe my controller isn’t good enough, but from my perspective - this is something good innovative coding can account for.
I’m using Korg padKontrol rotary pot faders to write the automation. I’ve played with the reduction level in Cubase but can never really seem to get a result or response I am happy with. It’s either removing too much or is too inaccurate, or it’s stepped and blocky. Slow adjustments are stepped with the reduction low, so you adjust the reduction to be high, but then fast adjustments/curves are triangulated.
A few things, first, this could just generally be improved I’m sure.
I would like to see a a feature in Cubase that gives automation lanes “track versions”. The first “track version” is a raw data track that shows the basic midi input values 1-127 which would looked stepped. This track would always (or maybe by option) be a background track version, as Cubase would automatically create a automation track version that features algorithmic smoothing/reduction/etc, - ie this is what you would see when you are writing automation (should be able to be down in “real time”, minor delay) and what is shown when finished. If you need to, or are unhapy with certain sections, you can go to the raw data track version for reference and take automation points and copy them to the other track or create a new one and combine the best of both.
But absolutely automation writing in Cubase needs to improved greatly. It’s actually fairly useless.