The “enter project cursor position” key command no longer works correctly. When pressed, instead of auto-selecting the bar number, it now selects the beat number.
This worked fine in Cubase 13.0.10.
The “enter project cursor position” key command no longer works correctly. When pressed, instead of auto-selecting the bar number, it now selects the beat number.
This worked fine in Cubase 13.0.10.
Ugh
Confirmed re: the locators. For me, I use shift-num 1 or shift-num 2 for “Goto X Locator,” but now all it’s doing is nudging ±1 beat.
Also strange: If the time displays in the transport bar are closed and you then press Shift-P (or Shift-L / Shift-R), then the measure number is correctly selected in the input field that opens:
@Martin.Jirsak Would you please confirm this bug and forward it to Steinberg.
THX!
Confirming the same bug.
Confirm same bugs, for all the above commands.
I’ll add one more: adding a new cycle used to focus highlight on the textbox as well (but this was in C12)
Confirmed - “enter project cursor position” key command no longer works
Edit: Just noticed the “enter locators” commands are similarly affected.
Edit #2: Just wound back to v13.0.10 (from a Time Machine backup) until Steinberg posts a fix for this.
Need this fixed asap, please - it’s such a workflow disrupter.
Everyone can also do that themselves in the steinberg support page:
Bumping for a very inconvenient bug that needs immediate restoration
Yes! same here! cant key in the bar number instead of beat number… very bad…
that’s very annoying and it was working well in all the previous versions…
Ran into this issue last night…confirmed.
Has anyone from Steinberg acknowledged this bug yet?
Did anyone of you make a proper bug report on the mysteinberg page, as suggested here?
www.steinberg.net: My Support
If not, then how should Steinberg aknowledge it?
@Martin.Jirsak reports many bugs that are posted here in the forum to Steinberg
Yes, but many do not know that you can do it by yourself.
Hi,
It rings a bell for me. I will check tomorrow.
Yeah, ditto, and I want to include that if you used to be able to hit for example NumPad 1 and then Enter and the Cursor would move to 1.1.1.0. Now if you hit left arrow to move the bar number the rest stays so if you want to go to 1.1.1.0 the old way you just hit your Key Command and 1 and the rest was reset. Now if you’re having your cursor at 34.2.1.27 and do the old maneuver plus left arrow you land at 1.2.1.27 which is in a way even worse than defaulting to beat number instead of bar number. Not good enough.
HI there, same problem here - that bug report page is in German though