Today I needed to bust out my old MU100 for a specific sound, so I connected everything and needed a sysex xg midi reset.
I haven’t used the list editor in over 10 years and quickly grew very unimpressed of the “improved” new sysex dialog.
First of all, you can only edit a hex value one by one - this is tedious! Coming from the world of XG midi expanders, I always kept a list of HEX codes handy for certain things, e.g. a XG Midi reset or a drum part initialization for any other channel than 10. The Beggar’s XG Sysex guide contains a lot of useful information on sysex. And it worked well at the time, when we had just one single little text input in which we could just copy and paste the hex strings as we needed.
Now to the import function: to my surprise, a binary created sysex file I made at the command line is imported and Cubase simply adds faulty bits at the end, rendering my sysex invalid!
This is what I do at the mac terminal:
echo "F0 43 10 4C 00 00 7E 00 F7" | xxd -r -p > ~/Desktop/xg_reset.syx
Importing the sysex in cubase, I end up with this:
The top one is a sysex xg reset I imported from a working midi file. When I hit play, it resets my Midi module successfully.
The bottom one is the imported syx file I created at the command line. I used all the right hex bits. WHY is cubase adding this nonsense? When I hit play on this one, my MU100 displays a “SYSEX DATA ERROR” message.
I kinda miss the simple text field I had back in Cubase 4 where I simply double clicked the “comments” column and could enter all my HEX values separated by a comma. Why was this removed?
Why are we being forced to use this weird hex editor? It is very restrictive and I would appreciate an option to just switch over to a plain text field in which we can just enter our own values.
(checking in sysex librarian)
