Can you post a regular screenshot (not another animated gif) that shows the items you have manually selected and also the items that became selected on their own. Please circle or otherwise indicate which were specifically chosen & which ones ‘self-selected’. Also make sure the Info Line is visible.
We really don’t need to see evidence that the problem is occurring, we trust you on that. What we’re looking for is clues as to why this might be occurring in your specific situation. Animated gifs aren’t very useful for this because they are small, often blurry moving targets. A static image that can be magnified and examined in detail works much better.
I have seen this behavior once in Cubase 12. I don’t think I would be able to reproduce it since it only happened in one project.
I can’t remember how I resolved it. Try grouping all events and then ungroup them.
Grouping and ungrouping doesn’t solve the issue. Besides, I never group events at all.
@raino I’ll make some screenshots eventually. If the GIFs are too small, try right-click and select open image in new tab (this allows inspecting them in more detail).
The problem is, there is also a Signature event selected with other objects. You cannot move the Signature event freely; you can move it by Bars only. As the event remains in its original position, the range length changes.
Okay, that would explain the “odd” behavior when using the range selection to move the events. But it does not explain why more events are selected after moving a “normal” selection of events in my initial post.
The second screenshot shows what happened after the selected events have been moved to the right. I’ve pressed the shortcut P again to indicate that the selection range has magically extended.
Any subsequent moving of the active selection will also move the spontanously selected events which of course breaks the project.
→ Do you agree that this is unexpected behavior or do you expect Cubase to behave in this fashion?
And in case anyone asks: None of the events are grouped. And yes, I also tried to “Group/Ungroup” the events inside the folders with no change in the tool behavior. Today Cubase selected events in the “Git” folder, whereas yesterday it only selected events in the “Bass” folder.
→ Looks to me like some “uninitialized variable” (or similar) programming error.
P.S.: The screenshots were made with Cubase 15.0.5 (but the same behavior occurs for Cubase 14/13/12).
What exactly do you mean when you say the spontaneously selected items become selected “after” the move? At the time these become selected are they in their original locations or were they also moved?
Exactly that. After moving the initial selection the other events (marked in the screenshot) become selected. And yes, they stay in their original position, but moving the active selection again will then cause these events to be moved as well - which is definitely not desired.
This can be observed in the animated GIFs in my initial post btw.
What happens if you use use ‘Move To Cursor’ instead of dragging?
I think I did encounter this bug a long time ago and forgot about it, because I ended up using Move To Cursor and Insert Silence as a more stable method of moving large amounts of events.
After checking the project on C15/W10, I can confirm the phenomenon. Based on my observations, there is (at least) a conflict between the “Bass RAW” and “Bass DI” tracks in the “Bass” folder in the time range of Song 9. Moving either track out of the folder will fix the incorrect marking behavior.
Thanks for trying it out and confirming the issue. My follow-up question would be what can I do about that in general? How can I identify if there a “conflict”/”problem” within a folder?
Is that something for Steinberg support, or am I just “holding it wrong”?
Unfortunately, I don’t have an explanation for this behaviour either, but I think it’s an application error that occurs rarely and only under certain circumstances. Basically, troubleshooting always works best according to the principle of narrowing down the problem, i.e., trying to divide the problem into smaller areas and checking each one individually. In this specific case, the simultaneous presence of two tracks in one folder to me seemed to cause the problem, for whatever reason.
