Studio one 5 automation issues.....

[noise-impresssion]

Hi.

I don`t quiet understand automations in Studio one.
As an example: I have assigned a hardware controller keyboard, lets say to the "cutoff" of a software synth.
If I hit record, it will store the cutoff automation data in my midi cc. But what I expected is actually an extra automation lane for that.
I could hit "A" on the top left corner to create a separate automation lane before recording and set it to write. But then if I would like to record midi notes and automation at the same time, it pretty much ignores the automation lane and just records my cutoff changes into midi cc again.
Also I find it quite inconvenient to always create the automation lane first, setting it on write, and then on read after recording, instead of just hitting the record button like it would work with recording midi cc and actually with any other DAW.

I feel like I don`t quite understand the difference between a midi cc cutoff automation in my example and the automation via automation lane. It confuses me a bit that I can actually record automation in two different ways.
Or is there a way to tell Studio one when controlling parameters via a controller to use the automation lane instead midi cc?

If someone could help me out with this that would be amazing, I am sitting here for days and just dont get it

[gentleclockdivider]

I feel your pain .
I never use automation lanes in studio one ( except for effects), instead I create a new empty track (pointed to the instrument )and record midi cc in that track , much easier to handle afterwards .
Never saw the advantage of the dedicated automation lanes , afaik they have the exact same resolution as those found in the regular clips .

[EnGee]

On thing I learnt that in Studio One, there are two ways to record the hardware automation. One is stored inside the midi clip, and one is separated from the midi clip (stored in the song). I don't remember which is which now, but one you can record with the automation lanes and one is recorded inside the piano roll. Sorry, I mixed now as I don't use Studio One that much these days.

[gentleclockdivider]

Exactly , but you don't have to record the automation in the same clip where the note data resides .
Just create new tracks , point them all to the same vst and record in those tracks, clips .
Easy as pie , muting that cc track just mutes the midi cc inside it .

[apoclypse]

This is not the first time people have brought this up. The way S1 handles automation is not ideal.

Basically if you press record and move some knobs around S1 record will that automation into the clip. If you instead use the Touch automation mode it will write that that to the automation track. To do that you should see a button in the plugin window right under the Activate and Bypass Automation buttons that says Auto:off. Change that to Touch and it will record your automation to an automation lane versus the clip. However, stupidly it only works if you don't press record and have already recorded your midi notes in so you can't automate while recording a midi sequence as far as I'm aware.

It's facepalm levels of stupid. I've never seen any other other DAW do it this way.

[THE INTRANCER]

Just use the drawing tools, it's much easier and faster than doing automation by hand on external hardware knobs.

To put Studio One's automation tools to test some years ago, I created this track. Almost everything was automated from start to finish using the drawing tools. There's around 40 tracks used in this composition, and it was completed in 10 hours.

https://soundcloud.com/scott-moncrieff- ... -acid-rain

[antic604]

Yeah, that one's weird. Even Reason has a preference to choose which behaviour user wants

[noise-impresssion]

Thanks for everyone's help.
I wasn't sure if I just didn't understand it properly but it really seems thats the way Studio One is handling automation, which is very odd. There is so much I love about S1, with actually lots of creative and smart ideas, but there are still quite a few "features" I can't really understand. Also deeply missing the grab tool to move or pan arround, but thats another story i guess

However, stupidly it only works if you don't press record and have already recorded your midi notes in so you can't automate while recording a midi sequence as far as I'm aware.

Yep, thats what I was also wondering, pretty confusing
Also, it seem like when I close my VST instrument, even I have the right Track selected, the automation lane ignores my inputs. Or is there maybe a solution for that?

[EnGee]

Just use the drawing tools, it's much easier and faster than doing automation by hand on external hardware knobs.

To put Studio One's automation tools to test some years ago, I created this track. Almost everything was automated from start to finish using the drawing tools. There's around 40 tracks used in this composition, and it was completed in 10 hours.

https://soundcloud.com/scott-moncrieff- ... -acid-rain

The main problem is if you don't know which cc number you are automating! So, it is faster to record the automation first by recording the movements.

Also, sometimes you just can't make it like the moved one by hands. Sometimes it's just better to record the movements once by feel instead of keep guessing or doing it by counting.

Yes, Studio One takes it the old way. I think it was like that in Cubase and Logic or maybe just Logic. Latch, touch, write and read are confusing. One of them just record the current movement then when not moving, it return to previous state, while the other just keep writing the last value when stop moving the knob for example. I keep forgetting which is which, but just reading skimming over the manual or watching a little video can refresh my weak memory! I also keep forgetting how to setup my sends as pre/post fader usually post but sometimes it's confusing

Maybe it's better to keep small notebook to record important info like that and some shortcuts that not usually used.

That's why keep using one DAW has this advantage by not mixing and forgetting which is which! <--- advice to myself

[THE INTRANCER]

Latch, touch, write and read are confusing.

Yeah... it's not really not clear what the terminology infers. Tool-tip information is not included either, which doesn't help make clear what these different states are, nor vie the interactive help menu.

Many years ago, I created a digital overlay that would act as a help system that could be animated through for Studio One. I posted a thread on it here somewhere. It was more for shortcut keys though.

[EnGee]

Well, you only learn it once and note it down, then it becomes normal thing. Nothing extraordinary! Here is a video I found in less than 5 mins searching (and I'm a lazy guy ):

[middle_color]

...

...

...

I think you should write an automation after you composed a midi part:
1. Select target VSTi.
2. Make sure this track is not "arm"-ed
3. Bind a knob to VSTi's parameter.
4. While parameter still in focus click "Edit Automation" (the "A" icon) near parameter's name.
5. You see the automation over you midi part.
6. Change "Auto: Off" to "Write" (or another mode consult to Youtube or the manual)
7. Star song playback, tweak parameter. Observe automation curve envelopes knob's movement.
...
99. When done writing automation, change "Write" to "Read". Unmap used knob to avoid accidental overwriting.

PS. you can choose where to show automation data: on the same lane as midi or on "nested" lanes.

s1-auto.png

[gentleclockdivider]

Yes, I assume most of us know that already , it's just standard automation like in any other daw .
The op specifically wondered about the two different systems .
One being the automation , the other being data recorded in clips ( which can be any parameter and not just midi cc's ) which is also automation but doesn't need or uses the automation read/write /latch stuff

[AdvancedFollower]

This is not the first time people have brought this up. The way S1 handles automation is not ideal.

Basically if you press record and move some knobs around S1 record will that automation into the clip. If you instead use the Touch automation mode it will write that that to the automation track. To do that you should see a button in the plugin window right under the Activate and Bypass Automation buttons that says Auto:off. Change that to Touch and it will record your automation to an automation lane versus the clip. However, stupidly it only works if you don't press record and have already recorded your midi notes in so you can't automate while recording a midi sequence as far as I'm aware.

It's facepalm levels of stupid. I've never seen any other other DAW do it this way.

Also for parameters that can't be mapped to MIDI, it's impossible to record into the clip. It will always be a separate lane.

I like having both options available. Sometimes the automation is indeed part of a MIDI performance, and you want that automation to follow the clip when you duplicate it, move it around etc. Other times you want a traditional automation lane that isn't linked to any clip. However the confusing way in which Studio One presents those options isn't ideal...

I'm hoping they overhaul the automation in 5.5 or 6.0. There's also the old bug that sometimes automation isn't rendered when you export a song/mixdown unless you periodically move the progress box around, which is pretty stupid.

[antic604]

...and you want that automation to follow the clip when you duplicate it, move it around etc.

Gosh, I really wish they added an icon somewhere on the top bar indicating what's the status of that option, like almost every other DAW has (Reason doesn't either, which is a funny coincidence since both Reason & S1 also use the non-standard Ctrl+MW to resize tracks vertically and Shift+Ctrl+MW to scroll them horizontally).

I honestly never know if I have it on or off and I need to check it in the "wrench" menu or move the clip to see if automation is following