Midi-CC Controller lane is not removed although i cannot see it anymore

Hi, this is a bug report.

Midi-CC controller lane number 41 that controls the Cutoff of Filter 2 of my Virus Ti is still moving the Cutoff of Filter 2 although this controller lane is completely removed. Right now there is spooky automation going on. It looks like the visual effect (disappearing of the controller lane) is not really happening inside the code.

This reminds me a bit of internet cookies that sometimes have to be removed on my PC. Is there a similar principle, like some kind of cache with midi-clutter that has to be cleared?

Do we have to close Cubase 13 and open it again everytime we remove a controller lane?

Cubase 13, Win 10, latest driver Access Virus Ti

Tried MIDI reset, Reset on stop, Insert reset events after record these hints did not work

Hi,

Did you really delete the MIDI data, or did you just hide (remove) the Controller lane?

You don’t specify, but it sounds like you are referring to cc Data in the Key Editor and not as Automation on a Track.

When you say you removed the Controller Lane, what exactly do you mean?

The Lanes in the Key Editor aren’t actual MIDI Data that does anything. They are basically a display mechanism in the Key Editor. If you used the List Editor to examine a MIDI Part you’d see the the Note & cc Messages are all mixed up together. The Key Editor displays different types of MIDI data in different display areas to make editing easier. So the cc Data is displayed in Lanes. Because there are 128 different cc Messages, there are too many to show at once so each Lane can be set to be visible or not. But this has no impact on the underlying data. If there is data on the Track it will be played regardless of the Lane’s visibility. A diamond indicates which Lanes have data to show.

This is the intended behavior and not a bug of any sort.

In the editor section one can add Controller Lanes. The data that is put in there works. I recorded a take with automation that was according to my plan. So i am surprised you tell me that it does not do anything. It did in my situation.

To put it very simple. I’ve added CC41 in the menu and selected this option as a controller lane. Fine. It worked on a recording. But now i want to get rid of it and i cannot although the menu gives the option to remove it. Please tell me how i can get rid of that (Ghost-)automation which is now going on. Where do i delete it?

To Martin: I removed the controller lane. Obviously it just is hiding and not removed. Please tell me how to remove it, get rid of it. To me it looks like i can create it but cannot delete it.

For me it has gotten over-complicated in the Cubase Midi department. Contra intuĂŻtieve. Bad implementations. Hope to solve this to finish a track i am working on and then move on.

This is what the previous users tried to explain: The “remove this lane” command is simply hiding this lane, it is not deleting any data at all.

Say you have this editor view:

Click on the down arrow at the bottom of this view:

image

Now click on Show/Hide Controller Lanes:

A lane for a CC is shown, in the case of my example, pitchbend:

Click upon the “Pitchbend” (or whatever your setup shows). This will get you to a list of your CCs:

Choose your CC41, so now your view will show something like this:

Click on the label “Control 41 CC41”, you’ll get the context menu as before:

Instead of clicking on “Remove this Lane”, click on “Select All Events on Lane”.

Now press “Delete” or “Backspace” on your keyboard and you’re done.

4 Likes

Use of language is vague. “Remove” should be “Hide”, as that is what occurs.
Also, (as I am a paid-up member of the Pedant Police), CCs are not Automation. CCs derive from controlling synths, etc, Automation derives from mixing desk, er, automation. Admittedly, they appear the same. Like oranges and tangerines.
Here endeth the lesson.

thank you very much i will follow your instructions and report back.