This began happening in Cubase 11 recently and is also occurring in my trial version of 12 that I just installed. I’m using my Korg Trinity workstation keyboard (not rack or VST) as MIDI keyboard to record and play back, and have only one MIDI in/out.
The notes are either all on or off in terms of what I hear. The screenshots of the short midi piano arpeggio show that there are velocity variations.
Meaning that when I test this issue as I select single notes or all of them and progressively lower velocities on all the notes, nothing changes in what one hears until I go down to 0 = no sound at all.
The list editor shows no pitch bend or other modifiers happening.
So it seems they are playing at 127 or something even though the data shows otherwise. I think I have the right Preferences set, but maybe I’m wrong.
As state in the OP, it’s my Korg Trinity workstation.
It came out in 1995 but it was “the” workstation at the time used by dozens of top musicians at the time. And it still works, though when I sometimes change sound bank on it, Cubase will play the MIDI file (that I recorded using it) out of tune. It’s random, but hasn’t happened in this instance.
I tend to record all my playing in MIDI with it so that I can go back and edit when needed. It’s my way of having a master file of each track.
I could, but then I’d have to reload everything (not hard, it’s just that I’ve totally rearranged much of the sound banks – called Combi and Programs – and edited many of them so they are custom ones).
All these sit on backup floppy disks*. (*Yup, that shows it’s age - lol.)
Maybe first look at what Cubase is actually sending in the midi monitor mdi insert to make sure that’s all good before getting in the time machine to use those floppies.
Here is an export of the MIDI Monitor for that file. It shows the same data as the List Editor (only Note On, nothing else). I looks all jumbled up for not in columns. See next post for partial in-Cubase screenshot.
You only needed to make sure that Cubase was sending the data. Then you know that cubase is not not sending it, and you can look at the next step in the chain. Any device that’s between the computer and the Trinity need to be checked.
@steve - Pardon my ignorance but from everything I’ve provided above, is Cubase sending the correct data (it seems like it to me as per List Editor and MidiMonitor)?
The only interface I have between the computer and the Trinity is a Behringer UMC204HD. One Stereo In, one out + MIDI in/out connection.
I haven’t touched it during the time that this issue started, so I don’t know how it could be the problem, but I’ll try to disconnect and reconnect everything.
I had pasted in the .txt file export of the MidiMonitor which I stated didn’t come out right (jumbled). At some point a mod or admin must have fixed it for there is now that notice above it in the screen shot below.
It wasn’t anywhere near “30 screens long” at all – basically 8 bars, but I still would like to do this right in the future. Where is the Forum Guide for such things?
I edited it. In some browsers, especially phones, a long string can seem infinite. I exaggerated to make the point.
Anyway, Since you have found that Cubase is sending the right data, shall we assume the Behringer device is also? That leaves the Trinity as the culprit.
It does sound like the kind of thing that could go wrong on a keyboard synth. If I were in your position, I’d go ahead and reset it. Since we could not determine the fault definitively, this still might or might not work.
I’ll edit the title to display a bit more info- maybe a Korg Trinity user will jump in here.
Are you saying you record into the onboard sequencer of the Trinity, and then are sending it to Cubase? (not that it matters, I just didn’t understand that detail)
Finally, feel free to edit your title as much as you like, I have increased your permissions for the forum.
@steve - Thanks for reply. As to the Trinity, I haven’t used the on-board sequencer for many years since I got Cubase. I record by playing it live so to speak, first as a MID track and file, then when satisfied, create an Audio track using the Trinity’s audio I/O.
In terms of solving this issue, the Trinity gives me an option to load only Global settings separately, so I’ll use the latest backup saved to floppy and see if that fixes the issue.
If not, I’ll load the original factory Global and Combi/Programs, then my own Global, then my Combi and Programs backups.
@steve - Well, I did a manual factory reset (pressing 0 and Enter on keyboard while powering up), loaded up the original 1995 Global, Combi and Programs - tested that. It fixed the issue. Then loaded my own saved backups… so far so good. So thanks for the solution.
(Ah these computers, amazing stuff but… one tiny glitch somewhere in all of those 1s and 0s, and things go kaputty.)
