Tempo knob unresponsive to Midi DAW control (U-Sync) while fully connected

[Wessel]

Midronome loses Midi connection to the tempo knob, making it unresponsive to changing the DAW's tempo. Only completely removing U-Sync (application, the script, the VST3 plugin) and reinstalling the software momentarily resolves the issue. It is unclear if the problem is caused by Cubase Pro 14 or MacOS Sequoia.

The sync led is on, the daemon says both DAW and Nome are connected. The VST3 plugin is loaded and the remote Midi is connected. I can play and stop the Nome via the DAW. The Midi input is set to control the DAW control.

Both the Nome I and U-Sync have the latest firmware/update. Same applies to Cubase Pro 14 and MacOS Sequoia.

How can I resolve this?

Thanks in advance!

[Simon]

Hi Wessel

Thanks for asking here. You are saying that the Nome will still sync to Cubase (when you press play), but that you cannot change the tempo of CUbase using the Nome's tempo knob, correct?

The issue you are experiencing is 100% related to the Cubase MIDI Remote, nothing else. Nothing to do with the U-SYNC VST3 plugin or its track. You do not need to (and should not) set any MIDI input on the U-SYNC track.

I'll suggest you double-check the MIDI Remote setup, follow the steps in the U-SYNC Manual, section 6.3. In particular, verify that the correct MIDI ports are selected.

(note that the SYNC led should not be on unless the sync is "active", i.e. Cubase is currently playing - is this not the case?)

[Wessel]

Hi Simon,

You are welcome and thank you for your response. And yes, that is correct. I can change the tempo on the Nome I and as soon as I hit play in Cubase the Nome 1's tempo changes back to the tempo set in Cubase.

I changed the Midi input because in one occassion it had an effect.
I followed the steps described in the manual but it had no effect. Could there be another Midi or USB Midi device hijacking the connection? If that might be the case should I disconnect all Midi / USB Midi devices and see if the Nome 1 works (and then connect each USB Midi device until the issue returns)?
Unless you would call Nome a DAW controller there is no DAW controller in use. The other Midi device is a Midiman USB Midi Hub/router.

The manual says nothing about the Project Synchronization Setup Dialog, could settings in there interfere with the Midi side of the Nome I?

The sync Led turns on only when Cubase is playing/recording.

Thanks in advance!

[Simon]

Hi Wessel

I just tested with the latest Cubase, 14.0.41, with Nome FW 5.2 and U-SYNC 1.4.1, on macOS Tahoe, and everything works.
It should work just as well on Sequoia, I do not think the OS has any impact on this.

There must be something missing in your setup. Can you try to
* Unplug the Nome
* Open the "Audio MIDI Setup" app
* Open the "MIDI Studio" window
* Delete in that window anything called Midronome or Nome
* replug the Nome
* restart Cubase
* then double-check the setup in the MIDI Remove in Cubase

If that does not help, then please share screenshots of your setup in Cubase.

Simon

[Wessel]

Hi Simon,

Unfortunately following your steps (I also completely removed and reinstalled U-Sync and flashed the Nome 1 with the 5.2 firmware) did not resolve the issue. However I did find a workaround by doing a "Have you tried turning it off and on again"
After Cubase has booted up I need to unplug and plug in the Nome 1, after that the Tempo MIDI Command works. It keeps on working until the next system reboot. Which made me think it is most likely a USB issue connectivity issue. I replaced the USB cable that came with the Nome 1 and that resolved the issue. The Nome 1 is built like a tank, the cable not so much

Thanks again for your help Simon and cheers!

Update:
It appears that the issue still is not entirely resolved. However the workaround is that I boot up Cubase and then either turn on/plug in (after turning off/unplugging) the Nome 1. Then the Nome 1 works as expected. This issue only happens after a system reboot.

[Simon]

Hi Wessel

The cable could be faulty indeed. Our factory checked and tested every single cable, and that would be the first faulty cable out of 3000+ cables, but yes they are still humans and mistakes can happen. If that's the case please send an email to support@simntonic.com and we can sort it out - we will probably send you a new one.

My guess though is that the issue has nothing to do with the cable - if it was faulty you would have all sorts of other issues, not just the Remote Control in Cubase. Have you updated to the newest 5.2 firmware? The Remove Control handling in the firmware has been improved and might be more stable.

[Wessel]

Hi Simon,

Thank you for offering to replace the cable, but I think you are right and it is not related to a faulty cable.

I had updated to the newest firmware (5.2) before I removed and reinstalled U-Sync, but unfortunately that did not resolve the issue.
I did however notice more issues reported on the Steinberg forums about other Remote control/Midi devices that are not found or lose their connection, so it could be a Cubase error. I will contact their support and keep you updated through this topic.

Update:
Link to post on Steinberg forums:
https://forums.steinberg.net/t/nome-1-m ... up/1018529

[Simon]

Great - please feel free to update us here.

To make things simple for Cubase/Steinberg, you can literally remove U-SYNC entirely from the problem.

In simpler terms:
SETUP: External hardware device (Nome) sending MIDI commands to Remote script in Cubase. The Cubase Remote is changing the tempo/transport accordingly.
ISSUE: the Remote cannot find or loses connection to the hardware device (though is that correct? You have not sent any screenshot of the Cubase Remote setup so I'm not sure).

If you need to find the remote script (it's very simple, it's in Javascript), it will be in Documents/Steinberg/Cubase xx/MIDI Remote/Driver Scripts/Local/SimnTonic/Nome.

[Wessel]

Thanks Simon, I also created a support ticket since the forum post is not getting any tracking.
When Steinberg reacts I will use your simplified version of the issue.

I have added screenshots as you requested and the JavaScript file is in the directory you specified.

[Simon]

Ok this is useful info - are these screenshot when it stops working? From the screenshot everything should be working.

Another question: when it stops working, is the one-directional U-SYNC still working (i.e. when you press play in Cubase the "Locked" LED turns on and the Nome follows Cubase's tempo)?

[Wessel]

Yes, those screenshots are from when it stops working. Exactly, so it makes no sense to me.

Yes, U-Sync is acting one-directional, when you hit play in Cubase the following happens:
- The "Locked" LED turns on and the Nome follows Cubase's tempo.
- If you change the tempo on the Nome (and change it into something else than Cubase's tempo) and then hit play in Cubase, the Nome's tempo switches to Cubase's tempo.
- When you hit stop in Cubase the Nome stops (both Play and Stop messages are being show in the Nome's display).

[Simon]

I see.

Can you check using the MIDI Monitor app (or any similar app), that the MIDI CC messages are actually sent by the Nome on "DAW Control"?
For example when you press play/stop it should send CC 103 on channel 12: value 1 for Play, value 11 for stop.

[Wessel]

I used the Midi Monitor App from here https://www.snoize.com/MIDIMonitor

It did not show any CC messages only Clock, Song Position Pointer, Continue and Stop messages.I hope the Midi Data is still usuable.

When the tempo knob is unresponsive the Nome only gets Clock, Song Position Pointer, Continue and Stop messages from Cubase when you hit start or stop on the transport panel:

13:14:55.322 To Midronome Commands Clock

13:14:55.322 To Midronome MIDI Out 1 Clock

13:14:55.322 To Midronome MIDI Out 2 Clock

13:14:55.337 To Midronome MIDI Out 2 Stop

13:14:55.337 To Midronome MIDI Out 1 Stop

13:14:55.337 To Midronome Commands Stop

13:14:55.337 To Midronome MIDI Out 2 Song Position Pointer 47 1

13:14:55.337 To Midronome MIDI Out 1 Song Position Pointer 47 1

13:14:55.337 To Midronome Commands Song Position Pointer 47 1

13:14:55.343 To Midronome Commands Clock

13:14:55.343 To Midronome MIDI Out 1 Clock

13:14:55.343 To Midronome MIDI Out 2 Clock

13:14:55.364 To Midronome Commands Clock

I purposely turned the tempoknob up so that it's at a higher tempo than Cubase's project tempo and then hit play, the Nome's tempo got switched back to Cubase's project tempo:

13:18:25.410 To Midronome Commands Continue

13:18:25.410 To Midronome Commands Clock

13:18:25.410 To Midronome MIDI Out 1 Continue

13:18:25.410 To Midronome MIDI Out 1 Clock

13:18:25.410 To Midronome MIDI Out 2 Continue

13:18:25.410 To Midronome MIDI Out 2 Clock

13:18:25.430 To Midronome Commands Clock

13:18:25.430 To Midronome MIDI Out 1 Clock

13:18:25.430 To Midronome MIDI Out 2 Clock

13:18:25.451 To Midronome Commands Clock

When I turn off and turn on the Nome (and the tempo knob is responsive) the clock messages are constant flooding. I can use the tempo knob and the project's tempo is automatically adjusted to match the Nome's tempo:

13:21:20.377 From Midronome Clock Clock

13:21:20.397 From Midronome Clock Clock

13:21:20.418 From Midronome Clock Clock

13:21:20.439 From Midronome Clock Clock

[Wessel]

I was able to filter out Midi Commands / CC messages:

When the tempo knob is not responsive to change the project's tempo:

14:05:47.650 To Clarett 4Pre MIDI SysEx Universal Non-Real Time 6 bytes F0 7E 7F 06 01 F7

14:05:48.055 To Midronome Commands SysEx Universal Non-Real Time 6 bytes F0 7E 7F 06 01 F7

14:05:48.471 To Midronome MIDI Out 1 SysEx Universal Non-Real Time 6 bytes F0 7E 7F 06 01 F7

14:05:48.887 To Midronome MIDI Out 2 SysEx Universal Non-Real Time 6 bytes F0 7E 7F 06 01 F7

14:05:52.711 To Midronome Commands SysEx Unknown Manufacturer 8 bytes F0 00 3B 6C 3F 66 17 F7


When the Nome has been turned off and on again and the tempo knob is responsive to the cnange the project's tempo:

14:01:57.264 To Clarett 4Pre MIDI SysEx Universal Non-Real Time 6 bytes F0 7E 7F 06 01 F7

14:01:57.674 To Midronome Commands SysEx Universal Non-Real Time 6 bytes F0 7E 7F 06 01 F7

14:01:58.090 To Midronome MIDI Out 1 SysEx Universal Non-Real Time 6 bytes F0 7E 7F 06 01 F7

14:01:58.506 To Midronome MIDI Out 2 SysEx Universal Non-Real Time 6 bytes F0 7E 7F 06 01 F7

14:02:07.749 To Midronome Commands SysEx Unknown Manufacturer 8 bytes F0 00 3B 6C 3F 66 17 F7

14:02:21.536 From Midronome DAW Control Control 12 Controller 23 0

14:02:21.536 From Midronome DAW Control Control 12 Controller 20 91

14:02:21.536 From Midronome DAW Control Control 12 Controller 85 0

14:02:21.536 From Midronome DAW Control Control 12 Controller 86 121

14:02:21.536 From Midronome DAW Control Pitch Wheel 12 -4163

14:02:21.722 From Midronome DAW Control Control 12 Controller 23 0

14:02:21.722 From Midronome DAW Control Control 12 Controller 20 92

14:02:21.722 From Midronome DAW Control Control 12 Controller 85 0

14:02:21.722 From Midronome DAW Control Control 12 Controller 86 122

14:02:21.722 From Midronome DAW Control Pitch Wheel 12 -4118

14:02:21.965 From Midronome DAW Control Control 12 Controller 23 0

14:02:21.965 From Midronome DAW Control Control 12 Controller 20 93

14:02:21.965 From Midronome DAW Control Control 12 Controller 85 0

14:02:21.965 From Midronome DAW Control Control 12 Controller 86 123

14:02:21.965 From Midronome DAW Control Pitch Wheel 12 -4074

14:02:23.376 From Midronome DAW Control Control 12 Controller 23 0

14:02:23.376 From Midronome DAW Control Control 12 Controller 20 94

14:02:23.376 From Midronome DAW Control Control 12 Controller 85 0

14:02:23.376 From Midronome DAW Control Control 12 Controller 86 124

14:02:23.376 From Midronome DAW Control Pitch Wheel 12 -4030

14:02:23.799 From Midronome DAW Control Control 12 Controller 23 0

14:02:23.799 From Midronome DAW Control Control 12 Controller 20 95

14:02:23.799 From Midronome DAW Control Control 12 Controller 85 0

14:02:23.799 From Midronome DAW Control Control 12 Controller 86 125

14:02:23.799 From Midronome DAW Control Pitch Wheel 12 -3986

14:02:32.040 From Midronome DAW Control Control 12 Controller 23 0

14:02:32.040 From Midronome DAW Control Control 12 Controller 20 94

14:02:32.040 From Midronome DAW Control Control 12 Controller 85 0

14:02:32.040 From Midronome DAW Control Control 12 Controller 86 124

14:02:32.040 From Midronome DAW Control Pitch Wheel 12 -4030

14:02:32.230 From Midronome DAW Control Control 12 Controller 23 0

14:02:32.230 From Midronome DAW Control Control 12 Controller 20 93

14:02:32.230 From Midronome DAW Control Control 12 Controller 85 0

14:02:32.230 From Midronome DAW Control Control 12 Controller 86 123

14:02:32.230 From Midronome DAW Control Pitch Wheel 12 -4074

14:02:32.445 From Midronome DAW Control Control 12 Controller 23 0

14:02:32.445 From Midronome DAW Control Control 12 Controller 20 92

14:02:32.445 From Midronome DAW Control Control 12 Controller 85 0

14:02:32.445 From Midronome DAW Control Control 12 Controller 86 122

14:02:32.445 From Midronome DAW Control Pitch Wheel 12 -4118

14:02:32.963 From Midronome DAW Control Control 12 Controller 23 0

14:02:32.963 From Midronome DAW Control Control 12 Controller 20 91

14:02:32.963 From Midronome DAW Control Control 12 Controller 85 0

14:02:32.963 From Midronome DAW Control Control 12 Controller 86 121

14:02:32.963 From Midronome DAW Control Pitch Wheel 12 -4163

14:02:33.164 From Midronome DAW Control Control 12 Controller 23 0

14:02:33.164 From Midronome DAW Control Control 12 Controller 20 90

14:02:33.164 From Midronome DAW Control Control 12 Controller 85 0

14:02:33.164 From Midronome DAW Control Control 12 Controller 86 120

14:02:33.164 From Midronome DAW Control Pitch Wheel 12 -4207


To my understanding and to what I am seeing being output is that the Clock messages that are being send (by Cubase/Focusrite) are received (by the Nome) regardless if the tempo knob is responsive or not. But the Midi Commands/CC messages are not until the Nome has been restarted after a system reboot. Am I unto something here Simon?