Mac SysEx Editor import dialog doesn't enable file selection

Cubase
,
#1

Hello, searched the forum but couldn’t find this covered, so here:

I’m trying to use the MIDI SysEx Editor in Cubase Pro 10.5.20 on macOS Big Sur 11.1. I managed to create a SysEx event in the List Editor and open the SysEx Editor by clicking the Comment field, but there are two problems that are making it difficult to work there:

  1. If I insert bytes into the message, they show in black text. I can’t seem to set the SysEx editor background to anything more bright than nearly black, so I can’t really see what I’m doing too well. The Editor Area Background color setting in Preferences does not seem to affect the SysEx Editor background. Is there some other color setting I should use?

  2. I can’t import SysEx files. The file picker does not let me select files with the .syx extension.

Can anyone verify these? Are they user errors, or should I file issues with support?

EDIT: Sorry, I just read some more forum material, and it seems that a post with the ‘issue’ tag is kind of a bug report. I should have done my homework.

#2

hi jerekapyaho

the ‘issue’ tag is fine :slight_smile: and thanks for checking - some of the categories are not so strictly defined - and we are often not sure what is a bug and what is a ‘feature’ (@steve will probably correct me here :smiley: ) - FWIW you should be able to edit the tags afterwards if you decide it’s not an issue ?

Hopefully somebody will confirm either way soon (I’m not in front of cubase at the mo !).

You are welcome to log the issue with support - and will do no harm - But let’s see if you get feedback here first as it may save the effort ?

#3

Hello, thanks for your reply. Yes, I’ll stick by and see if someone can take the time to verify this on their Cubase.

#4

Looks like not that many forum users are too interested in MIDI SysEx editing, but for my workflow it’s important. I work a lot with “vintage” digital synths and rack modules that live and breathe SysEx messages.

On my old PC laptop with Windows 8.1, the MIDI SysEx Editor in Cubase AI 8.0.40 works just as expected. With all settings at default, the contrast is fine. Also, importing SysEx files (with the .syx extension) works.

I’m starting to think this is a regression in Cubase Pro 10.5, related to the new color schemes implementation. As for the inability to import SysEx files, I don’t have a theory.

I haven’t upgraded to Cubase Pro 11 yet, but if someone is able to verify that these have been fixed, that might nudge me to upgrade sooner than later.

I did go to the Steinberg Download Assistant to see if I could have a look at the Cubase 11 release notes, but there weren’t any.

#5

did you log the issue with Steinberg support ? I’d be interested in what they say (if anything!)

#6

Just filed a support request with Steinberg. The contrast issue seems to have magically corrected itself, maybe because of a restart of Cubase. But the inability to import SysEx files still remains. You can’t even import back a SysEx file that you have just exported from the MIDI SysEx Editor. I’m attaching here the same screenshot as in the support request.

Cubase-MIDI-SysEx-Editor
Cubase-MIDI-SysEx-Editor1626×1022 139 KB

#7

can you post a sysex here (zip it up) ? maybe somebody can take a look - not sure I have any sysex files here.

#8

Sure, here is a ZIP file with the same three files you see in the screenshot.

SysExTest.zip (3.4 KB)

One of them is just a single voice from a Yamaha TG77 (not SY, but I must have been tired), the other is a DX7-compatible sound bank from Dexed, an the third one is just a quick test of the export (it is also the only one that is invalid, in the sense that it doesn’t have a proper header or data, but that shouldn’t make any difference since you should still be able to import).

1 Like
#9

More testing: Cubase Elements 9.5.50 / OS X El Capitan (10.11.6) - SysEx files import just fine, except that the MIDI SysEx Editor shows an extra F7 (SysEx message terminator byte) in the message.

For a moment I thought that this could be a macOS Big Sur file access limitation. The macOS privacy settings show that Cubase has access to Documents, Desktop, and Network Volumes. So I moved a SysEx file to the Desktop, and tried again, but that didn’t make any difference, not even after restarting Cubase.

#10

Filed a support request 15 days ago, but no response yet (status is “open” at MySteinberg).

Would still appreciate if some forum reader had the time to verify if they are getting the same behaviour in version 10.5. Or to verify that they are not getting this in other versions. I’m interested to find out how this is in version 11.0.

#11

I’ll test the issue if you can please post the steps to reproduce like in How to report a bug in Cubase

#12

Here are the steps to reproduce this issue:

  1. Unzip the attached archive SysExTest.zip to your macOS desktop.
  2. Start Cubase.
  3. Create a new empty project.
  4. Create a new MIDI track in the project.
  5. Create a new empty MIDI part in the track.
  6. Select the MIDI part and open the List Editor (MIDI > Open List Editor).
  7. Add a SysEx event to the part.
  8. Click the Comment field of the SysEx event to open the MIDI SysEx Editor.
  9. Click the “Import…” button. to open the file open dialog.
  10. Navigate to your macOS Desktop folder.
  11. Try to select any of the SysEx files from step 1.

What was expected to happen:
You would be able to select a SysEx file from the file open dialog for editing in the MIDI SysEx Editor.

What actually happened:
The selection of SysEx files is disabled in the file open dialog. (See attached screenshot.)

System information:

  • iMac (Retina 5K, 27-inch, 2019) + macOS Big Sur 11.2.1
  • Cubase Pro 10.5.20
#13

All works fine on Windows. But it seems there is one issue only, that the file picker doesn’t allow sysex type files to be selected. Correct? POst an image of the pertinent dialog and menu please.

#14

Thank you for your response.

This issue is about Cubase Pro 10.5 on macOS. I’m not able to test on Windows at this time.

I posted the screenshot I referred to earlier in this thread, it is up there at Jan 27. Please scroll up to find it.

#15

But that’s the issue, yes? And not

#16

Yes, that’s the issue.

Sorry that I originally conflated two issues. As I wrote above:

The contrast issue seems to have magically corrected itself, maybe because of a restart of Cubase. But the inability to import SysEx files still remains. You can’t even import back a SysEx file that you have just exported from the MIDI SysEx Editor.

Does that make it more clear to you?

EDIT: Thanks for updating the post title. I was looking for a way to do that earlier, but didn’t immediately find it. Maybe I will eventually.

#17

I filed a support request about this with Steinberg on January 27, in the My Requests section of MySteinberg . That’s five weeks ago, but I don’t know if anyone has even seen it yet. The status is still just “open”. I guess they must be really swamped with support requests.

#18

I have added this reply to my support request (which has not been acknowledged yet) at MySteinberg support:

I have just updated to Cubase Pro 10.5.30, and this problem still exists. That was as expected, because I saw no mention of it in the release notes, but I wanted to check it in practice before adding to this request.

Since it seems like 10.5.30 is the last update to the 10.5 line, I would like to know if this problem still exists in version 11. I hope you understand that based on my experiences with this problem so far on the Steinberg Forums and with this support request, I’m very hesitant to upgrade to version 11.

#19

It seems that the support ticket I created has disappeared from My Steinberg / My Support, without any communication. Thank you for reading.

#20

Hi,

I have tried on macOS 10.14, Cubase 10.5.30 and Cubase 11.0.10. I can load all your 3 *.syx files in both Cubase versions.