C15: When selecting automation in the Project Window, I can't see which ones are being used

Awesome. I wish I could change the original post, as I can now see how it might be difficult to understand. :slight_smile:

Now that I’ve made it crystal clear what the issue definitely is, I would like to hear from Steinberg about acknowledging it. Thank you for the help.

Here is the issue that is new with C15 and needs to be fixed: When we hit the Select Parameter Box for automation lanes, we need to able to see the first 15 automated parameters, just as we could before in previous Cubase versions. We can still have the 5 Last Touched parameters (the new C15 function) be the first 5 of those 15, if that function is enabled.

2 Likes

Bumpus amungus.

See the post above for the clearest explanation of the issue, that leaves no doubt.

Apologies if I got this wrong, but isn’t the difference that v15 now shows ā€œlast touchedā€ parameters whereas previous versions show parameters with automation data? The last touched parameter may or may not have automation data written to its track so you would basically need two lists to satisfy both features.

Yes, good point. The tradeoff now is a bad one for me, not only because I can’t see a nice list of the first 15 automated parameters, but also the ā€œlast touchedā€ gets reset every time you close and re-open a project.

So the solution is to have the former behavior be there if you turn off the ā€œlast touchedā€ feature. The new ā€œlast touchedā€ feature is great, but the cost of it isn’t worth it for those of us who rely on the former behavior.

1 Like

Bump. I’m gonna be annoying with this one because it’s a big hindrance for me. Please let me know that this is acknowledged. thank you!

When ā€œLast Touchedā€ is disabled in Preferences, restore the former behavior of seeing the first 15 automated parameters in the Select Parameter box for automation in track headers.

1 Like

Gonna keep on bumpin bumpin bumpin. Would love to get acknowledgement of this issue and what needs to happen: When ā€œLast Touchedā€ is disabled in Preferences, restore the former behavior of seeing the first 15 automated parameters in the Select Parameter box for automation in track headers.

2 Likes

Just your friendly Wednesday morning reminder for acknowledgment of this request to give us the option for the old Select Automation Parameter box behavior that got mistakenly taken out with the new Last Touched feature:

When ā€œLast Touchedā€ is disabled in Preferences, restore the former behavior of seeing the first 15 automated parameters in the Select Parameter box for automation in track headers.

1 Like

Small advise for people that get annoyed by a rebumped topic:
At the bottom of each topic you have the option to mute it. This means you won’t see it again.

yes!!!

the written automation HISTORY from previous versions in the list is MISSING.

i need to see my WHOLE list of written automation, not just 4-5 that keep changing all the time, its very confusing and now i cant find my automation!

please add the ā€œfull-star-listā€ back, or put in down on the button below everything else, or make it an option…

3 Likes

yes this exactly, i also prepped screenshots, but you did exactly the same… thanks!

i reinstalled CB 15 to see it was a faulty install or something

now i keep going back to Cubase 14, such a shame

1 Like

yes

They can show ā€œlast touched parameterā€ on the top, maybe just one instead of 5 i really dont need it :wink:

after that there was a list of all the WRITTEN automation, you know…with all those stars…this is now gone.

automation appears when writing but is hard to find once lanes are closed.

at least on my mac, and a few others i know

i think we want that list back :stuck_out_tongue:

1 Like

One way to quickly find them is to use the command Show Used Automation on Selected Tracks.

1 Like

yes, i have that on keycommand thanks

it would show me a gazillion lanes, its just way more organized to choose the lanes i want

like before a drop, i use different delays, filters, decay, release, eq, sidechain automation etc etc for different tracks… im sure you know what i mean.
this adds up to many lanes of automation…too much to always show, so i hide them with the little + and - thingie. But i cant do that anymore because now the written automation doesnt show up in the menu.

Dont get me wrong, it could be something I simply have to get used to, but right now im not feeling it… So i went back to 14.

Maybe I just use the keycommand and always have a gazillion lanes. Its frustrating after so many years of great production flow. Why change that? So you can see the ā€œlast parameterā€? I dont get it…i always write the last parameter and it shows up in CB 14. I think the whole concept is unnessesary and bloat.

2 Likes

I’m just wondering if it was better to backup the preference folder before doing anything like trashing the content, rather than creating a new profile?

Now, when I’m finishing a bigger project (over 300 tracks) I’m starting to see more issues with this new implementation. At least on a Mac. Didn’t got that far on PC yet.

  • Description of some parameters is vague at best, eg. ā€œLevelā€ for Send level. I have to mouse over it to see which Send it is
  • Sometimes plugins are not showing last touched parameter at all and I need to do the old ā€œpress W, move the buttonā€ technique. Then next time they do. It’s random
  • With a lot of automation, when Cubase is additionally opening new automation lane for any touched button or knob, it’s becoming even more convoluted than it is already. So it’s a double-sword situation

Overall, it’s a mess and still not as good as in any other DAW. I prefer the new implementation but it really needs to be tided up. It feels unfinished and messy.

3 Likes

This! It’s a clumsy mess to do it this way compared to the simple ease of how it’s been for so many years.

Agreed. All that’s needed for now IMO is that when the feature is turned off we get the behavior we had before.

1 Like

yes that would be great

1 Like

Bumping just to get recognition of this issue from someone from Steinberg. Thanks!