Problem with the Transport mode

Cubase
1

I’m having a problem with the Transport mode of the script for Novation launchkey mk4. Moving locators via encoders only works to the right. Impossible to move backwards.
Am I the only one with this problem?

I’m using Windows 10 64bit and Cubase 14.0.32

1 Like
2

Hi,

Do you use MIDI Remote or any other way? This was broken in Cubase 14.0.30, but it was fixed in 14.0.31 and .32.

3

Just checked the script of the mk4, and indeed there is an issue with moving the locators to the left, only when we have our primary time display set to Bars+Beats. All other time formats work as expected.

I noticed that it is setup to increase/decrease the locator (left or right) position by one quarter.

However, when we move left, there’s no decrease of the bar position when we hit the “0”-quarter of the previous bar. Thus it will stop working.

Anyway, if instead of quarters, we go for bars, it will work as expected.
The line of code that has to be altered in this case is 138 in …novation/common/base_utils.js:

return incrementTimeString(text, 1, delta, '.', [1, 1, 1, 0]);

This is setup for quarter notes length. If we want bars, it has to be set as:

return incrementTimeString(text, 0, delta, '.', [1, 1, 1, 0]);

This will work.

If the quarter note step is required, then the incrementTimeString has to be altered to include the case our quarter reaches 0. Then we have to decrease the bar. EDIT: Nothing really wrong with the script as long as the issue mentioned in this post gets addressed: Problem with the Transport mode - #7 by m.c

Just to be clear, @Florian34, these are not instructions for you, but can provide a hint to the coder of the script, if you or perhaps @Martin.Jirsak forwards it.

2 Likes
4

Hi,

This is exactly the issue, which was in Cubase 14.0.30 and which was fixed in Cubase 14.0.31. :astonished_face: We observed the issue on Mackie Control and CC121 devices.

I will have a look.

5

I know, still this is in the MIDI Remote script, not the MCU implementations. Not knowing though if somehow there’s common coding over such segments.

6

Thank you for your efficiency!
At least for now we have a workaround.

1 Like
7

@Martin.Jirsak, just checked the script in CB13.0.55. No issues there, though I used the identical script. This means, that internally Cubase 14, when we reach the 0 quarter, doesn’t move to the previous bar.

If you open CB13 and set the cursor, for example to the position 2.0, you will see that (correctly) it goes to 1.4. Now if you try the same in CB14 (0.32) instead of decrementing, it goes to 2.1. This is surely the issue, not sure how the hotfix was done, perhaps they concentrated just on the MCU side.

8

Hello. Did this issue get resolved? I just connected my launchkey MK4 to Cubase 14 Pro on 2 different PCs. The transport issue was not present on my 2nd PC…until I updated Cubase to 14.0.032 then the transport could no longer scroll left.

I’m using the Midi Remote only (the LaunchKey MK4 is automatically recognized)
I saw the workaround is to update the script to:
return incrementTimeString(text, 0, delta, ‘.’, [1, 1, 1, 0]);
but I didn’t see that line in the file: “launchkey_mk4_common.js”

I do not understand scripting - could you send me the corrected script file or tell me what the script file name is that needs to be updated?

Thanks in advance!

9

Hello,
The line of code is in the file: base_utils.js (in documents/steinberg/cubase/MIDI Remote/Driver Scripts/Public/novation/common)

10

Hi and welcome to the forum,

This has been fixed in Cubase 14.0.31 for Mackie Control and CC121 only, but it’s still present for the MIDI Remote. This is going to be fixed in the next maintenance update.

2 Likes
11

Thanks for the quick reply!

I updated the file w\ notepad but still can’t scrub left. Two thing to note in my testing:

  1. Same issue no matter what Time Display mode I’m in
  2. the base_utils.js file gets overwritten from a “default file” dated 6/18/2025 when I create an empty project

Am I missing something?

12

You should copy the whole folders structure of the script from the “public” folder into the “Local”. Then disable the official script. However, since an update will be published as @Martin.Jirsak mentioned, not sure if it’s worth the effort…

13

Thank you all! Replacing the “Local” folder structure worked!

1 Like
14

Hi,
If you’re interested, I’ve added a command to the script that allows us to position the cursor at the start of the selection loop by pressing shift+cycle button on the keyboard.

You need to add a piece of code to the host_bindings.js file in the bindTransport() function.

Just after this code:
page
.makeValueBinding(
ui.transportSection.cycle.mSurfaceValue,
page.mHostAccess.mTransport.mValue.mCycleActive
)
.setTypeToggle();

add this:
page
.makeCommandBinding(
ui.transportSection.cycle.mSurfaceValue,
‘Transport’,
‘To Left Locator’
)
.setSubPage(subPages.shifted);

15

I searched for this issue …. Thanks :folded_hands:t4:
hope for the Update soon .

1 Like
16

There is a simpler temporary workaround to this issue:

In the ‘Project Setup’ window, choose ‘Seconds’ for ‘Time Format’ and click ‘OK’ to close the window, then, in the ‘Project’ window (main cubase window), right click on the time lane and choose ‘Bars+Beats’. Now the knobs work both ways and the time display show the bars.

Thank to m.c and Florian34 for the script improvements. Cheers!

3 Likes
17

Wow, Yesss. :smiling_face_with_three_hearts: you are right !!! Thanks.. :+1: