This is causing me so many mistakes and undos.
Nuendo 13 and always - select a range of audio. Hit delete key. Audio is deleted in the selection and the selection is de-activated.
Nuendo 14 - select range, hit delete - Selection remains active.
Was this new behaviour asked for?
We need this behaviour to be an option . 13 versions of Cubase /Neundo muscle memory editing techniques later this change is really hard to work with
What particular workflow that you use causes the new behaviour to be an obstacle? Please give a step-by-step example. Or is this purely a dislike of it from a muscle memory point of view?
Thatās true.
I hadnāt noticed it because to be honest I donāt usually work with deleting ranges.
Do you mind explaining to me what is the difference to you if the range is still selected VS it deactivates and the cursor goes to the starting point of the selection?
Honest question.
I believe the essence of the problem for some users might be that after deletion applying fades with the range tool is difficult because you have to click somewhere else outside of the current range to de-select it, when proceeding to a subsequent edit. However, one workaround is to simply hold shift when dragging within the currently selected range, or indeed just learn to click and drag in a different area when performing a subsequent edit. And yes, this might mean learning new muscle memory in one particular workflow.
The range remaining after deletion may be helpful in other circumstances like when cutting head or tail. And I believe the new range tool behaviour helps when nudging range selections and directly muting range tool selections.
Iām assuming in the case you pointed out youād want to apply a fade to a region adjacent to the one you just deleted, right? In that case you can also drag the new range from outside of the current selection range. No shift needed and no extra click. But sometimes youād have to select in Arabic. =)
Exactly. Thatās what I meant by āclick somewhere elseā.
And just to be clear Iām not saying the new behaviour gets in the way in my case. I donāt mind the new behaviour. FYI thereās a detailed topic on this here: Cubase 14 | New Range Tool Issue!
Same here. The issue affects also automation:
I use a lot the loop function. When I didnāt need it I just clicked on another place in the timeline so that the cursor moved and the selection range went to 0.
Now itās messing completely with the automation, as it writes the new values inside the range even if Iām not in the range of selection!!!
Please Steinberg fix this ASAP!
But you can still do that right?
Not getting that. Please clarify with a description of the workflow you are using.
A couple of days into N14 here and found myself stumbling with this too. Specifically when selecting a range to top or tail the event length and then trying to make a selection from the end of the range to drag the mouse to the point where I want the fade out to start.
In order to click+drag the new range, I now must click outside of previous (arbitrary point, as it was only selected to delete) end of range, which might have other regions nearby which cannot be included in the selection or they will get an inadvertent fade. Or, click+drag from within the event, hoping to get this click in the exact right place as it will be the anchor side of the selection.
Considering all the range tool improvements, Iām happy to find some new muscle memory and work around it, but I do find myself having to fiddle around a lot more than Iām used to.
Iāll try to make a video of workflow it affects.
before that - In description if I select a range and hit delete -
now I want to further clean that cut up on the edge of the audio before or after the deleted range
if I put my range tool across the still selected range the cursor goes to a āhandā.
I cant use the range to now select over the empty space and the edge of the part that I cut
Instead a move command on that range happens.
This means that if I move the cursor on what used to be a range selection now it turns into a move range to new position - before the behaviour change I was immediately free to make a new selection on the bounds of the parts I was working on
I also have the issue (experienced now) that the cursor starts always from the left range point, even if I donāt have the play mode āstart from selectionā enabled.
I guess the issue has something to do with punchpoints and locators not working together (even if the lock in the transport bar is active)
Yes, you can if you select Shift or if you click and drag outside of the current range selection dragging in the opposite direction, for example. If you must drag right to left then using the Shift modifier may be your best option. In any case, after deleting you could just click once anywhere to be rid of the current selection and then proceed with dragging.
Yes, itās a change of behaviour so it means learning a slightly different workflow for certain scenarios. The new behaviour helps in many other situations but means a slightly different workflow in the particular circumstance you are referring to. IMO a change of muscle memory in this particular circumstance may be the best approach.
Having said all this maybe Steinberg could consider a change in behaviour just for the Range tool delete case.
An alternative could be to use this macro
Same here, very annoying to have the selection stay highlighted. Requires an extra keystroke or mouse click to get rid of it.
Yes this macro solves it and implemented it a while back. But the unnecessary change in default behaviour is puzzling.