Sorry, but the “Midi Monitor” in Cubase 14 is is unusable.
You CANNOT expand the row of the incoming SYSEX message, as followed up in the picture, the message is cut off. So you have to export the how thing as file, open it in an external monitor? nope - this is not how we need a monitor!
And sorry, for SYSEX it’s not a “comment” it’s the whole message!
ok, even the exported file is nuts:
MIDI Monitor Log:
Status Val1 Val2 Val3 Ch. Length Position Comment
SysEx 1 4:28:20.903 F0002032..
SysEx 1 4:34:54.957 F0002032..
SysEx 1 4:34:56.934 F0002032..
SysEx 1 4:34:59.195 F0002032..
SysEx 1 4:35:01.674 F0002032..
SysEx 1 4:35:03.801 F0002032..
That’s bordering on sloppiness.
Hi,
What happens, if you extend the Comment column, please?
Cubase doesn’t impose a length limit on Sysex messages, they can in theory be several hundred bytes or kilobytes long, so it does make sense to shorten them in the MIDI Monitor (which I guess was simply not conceived as a full blown MIDI tool like MIDI-OX). So I don’t think it is a bug, it is most likely a deliberate decision. I agree though that displaying a few bytes more wouldn’t have hurt…
A tool like MIDI-OX would perhaps be the better option for you.
Sorry, if Cubase wont show at least(!) 256 bytes Sysex the should shut of the function. Not even 8 Bytes are shown. Please do not try to excuse Steinberg, because this is simply a complete blunder. Displaying such a short Sysex string is completely pointless, and one has to conclude that the person responsible has never had anything to do with Sysex in their life. An NO I do not use MIDI-OX simultaneously with virtual MIDI cables, solely to eliminate the inadequacy of Cubase. Even Cubase on my Atari ST was better for MIDI.
..guess! RIGHT! Nothing, see my exported output.
Why are you expecting the MIDI Monitor to do this? Just record the sysex to a track and then use the List Editor.
No, YOU conclude that. You seem really angry, man. I mean, you’re steaming up the Cubase forum with your insults to everyone because you don’t understand how to use MIDI Sends. And you’re a “developer of VSTs?” Really? If you hate Cubase so much, go get Reaper. I mean, problem solved. But to come here and personally insult people based on your assumptions is rather childish. Seriously.
I hope things get better for you, though. Good luck out there.
4 Likes
Dear MrSoundman: The idea was to use a MIDI editor to display SysEx data in real time, essentially a debugger for testing plugins in Cubase. That’s why I was appalled that while this MIDI plugin offers this functionality, it’s essentially useless for SysEx in its current form.
I’ve since quickly written my own “helper” VST3 SysEx monitor that serves this purpose (at least on the input side).
As mentioned before, there was a fundamental misunderstanding on my part:
I thought the Steinberg developers were present here. Unfortunately, the SDK subforum is too general – so the only option seems to be the classic route via direct support – hoping that bugs will be reported. In the case of the missing VST3 integration in MIDI tracks (according to my research, these requests go back over 10 years), this will probably be unsuccessful. It’s simply unfortunate, as users are deprived of the ability to access “total recall” settings for external hardware directly, without confusing intermediate routings and sub-tracks.
I’ll definitely wait for the Windows 11 “MIDI 2.0” update; I’m curious to see if it will work smoothly, especially regarding backward compatibility with older hardware. (I use an ancient Emagic AMT8 interface that’s been working for over 20 years and is rock-solid, even with RT SysEx.)
MIDI 2.0 should make it possible (as has been the case for ages under Linux/OSX) for multiple applications to access the same MIDI driver/port. This would allow a plugin in Cubase to bypass the missing routing and directly connect to the desired synth. Of course, this also carries risks, especially when high data traffic (such as with SysEx) is accompanied by relevant RT messages (MTC, MIDI clock) – it wouldn’t be entirely clean.
@Thor.HOG can you please ignore my from now on? It’s really the better way for us both.