Cubase 13 - Mackie Control: "insert position marker" not working

Hello all,
I’ve just updated to Cubase 13 and I’m really happy so far. However, I am struggling with inserting new position markers via external controllers. Right now I am using a Behringer X-Touch ONE Controller, which is setup as a Mackie Control Device. All functions are working as expected (e.g. "jump to next / previous position marker), except for inserting a new marker?!?

I tested the X-Touch by monitoring it’s MIDI-Output via MIDI-OX, the device seems to work properly. In addition, I digged out my old Presonus Faderport Controller and gave it a try - unfortunately with the same result: Everything works like a charm, except for the insertion of a position marker.

Beeing not the most experienced user, the problem might be sitting in front of the PC :wink: However I wonder if perhaps someone else may have encountered this issue. I would be grateful for every hint. In the meantime, I insert my markers via keyboard-shortcuts.

Greetings and have a nice sunday
Christoph

Hi,

Is it new in Cubase 13? Do you have a chance to verify this in Cubase 12, please?

Which MIDI Message is it sent, when you press the button, please?

Screenshot 2023-11-05 141413

I’ve recorded the outputed Midi messages by the controller and attached a screenshot. For reference I included the “jump to next marker” command (see comments at the beginning of the lines.)

I never encountered these issues with previous Cubase versions (10 and 12). Unfortunately I have deinstalled Cubase 12 and thus don’t have the opportunity to crosscheck at the moment. As a workaround I configured one of the assignable “F”-buttons to the insert-marker function in the devices menue, which worked as expected.

I have the same issue both on a XTouch Behringer and a Mackie Controller.

In Cubase 12 (latest versino) the Add Marker worked without issues.

The Previous and Next buttons work as well as the buttons Left, Cycle and Right.

Quick solution was to create a User Defined function on the Mackie / XTouch doing the Add Marker for Active Track

1 Like

Hi,

You are using the “old” Mackie Control, not the MIDI Remote script, right?

Yes a real Mackie Controller (The MCU as they call it). Very old but it worked in v12, v11, v10… and it still works but not that one command, the Add Marker command.

Hi,

I will test it tomorrow…

Hi,

Thank you for the detailed support.

I can reproduce it here on my side.

Reported to Steinberg. Thank you.

Hello Martin, thanks for testing. I thought I was doing something wrong but as previous said, it has worked flawlessly in the past. Good to know it’s not me but can’t wait until an update as this is strongest feature for me with the Faderport.

1 Like

I can confirm.
Icon QCon Pro X + XS (MCU protocol): no chance to add a marker with the control surface as usual in C12 (and previous versions).

Cubase 13 can’t be used until this problem is fixed.

Hi,

Could you please verify for me (I have no Mackie in front of me right now), that the “Go to Left Locator” [MIDI Note 0x55; C6] and “Go to Right Locator” [MIDI Note 0x56; C#6] commands don’t work neither on the Mackie device? Am I right?

Hi,

Is this affecting also your MIDI Remote scripts?

As far as I can see, the original Transport > Insert Marker command has been removed. Instead, there are 2 new commands available:

  • Marker > Add Position Marker on Active Track
  • Marker > Add Position Marker on Selected Track

Steinberg will specify, which one, is going to replace the Insert Marker for the Mackie Control device. For the MIDI Remote scripts, the author of the script has to decide.

1 Like

Left and Right are working here.

Hi,

I have a chance to test it… Yes, it works for me too.

As far as I can see, the original Transport > Insert Marker command has been removed. Instead, there are 2 new commands available:

  • Marker > Add Position Marker on Active Track
  • Marker > Add Position Marker on Selected Track

However, this means that we now need two different scripts.
One script for Cubase 12 and another for Cubase 13.

Please reactivate the old command.
Adding new commands is good, but removing existing commands is bad.

Hi,

Please, wait calmly for the fix. I believe Steinberg has a solution for this. This is not the only Key Command, that changed in C13 comparison to C12.

You (Steinberg) should actually solve this by keeping the old command for compatibility reasons and adding the two new, more detailed commands. Then each script producer can decide whether he wants to require a specific Cubase version for his script or whether he wants to create an universally usable script. This is the usual standard.

None of this worked:
‘Marker’, ‘Add Position Marker on Active Track’
‘Marker’, ‘Add Position Marker on active Track’
‘Marker’, ‘Add Position Marker On Active Track’
‘Marker’, ‘Add Position Marker On active Track’
‘Marker’, ‘Add Position Marker on Selected Track’
‘Marker’, ‘Add Position Marker on selected Track’
‘Marker’, ‘Add Position Marker On Selected Track’
‘Marker’, ‘Add Position Marker On selected Track’
‘Transport’, ‘Add Position Marker on Active Track’
‘Transport’, ‘Add Position Marker on active Track’
‘Transport’, ‘Add Position Marker On Active Track’
‘Transport’, ‘Add Position Marker On active Track’
‘Transport’, ‘Add Position Marker on Selected Track’
‘Transport’, ‘Add Position Marker on selected Track’
‘Transport’, ‘Add Position Marker On Selected Track’
‘Transport’, ‘Add Position Marker On selected Track’

Is the command different?
Where capital letters are and where lower case letters are, is important.

Hi, you should get the commands as found in the README_v1.html, because there are commands that don’t share the same name in the UI and in scripting.

In this case the command is :
‘Marker’, ‘Insert Marker’

2 Likes