Yes, you can pasted the entire raw MIDI message into the incoming trigger which even allows multi-line. However I would recommend you just pick the unique portion of the message that you want as I anticipate parts of this message are also used for other purposes as well. The message probably varies depending on which registration you picked. I suggest you look at the messages for each registration and just find the unique part that you want to use.
Also, please change all FO (Letter "“O”) to F0 (number zero).
Attached is an example of launching windows notepad.
First, I’m on Mac.
I tried to copy the whole Sysex out of the window in translator but when I click it only copies 1 of all of them.
To show the whole sysex i made a screenshot and copied it out of the screenshot (I know that there must be 0 the copie showed Os)
Then I send the message, select and copy the entire message.
Then using a text editor I delete the text that is not Raw MIDI text. I usually use the editors global search and replace function
Then I select and copy the resulting text into the Incoming box of the translator.
You can expand the incoming box to a larger size if you have log SysEX messages like this.
I know this takes extra steps which is one of the reasons I said it might be better to just select the SysEX that is unique to that preset and only use that line. Also if there are other devices sending on that port, the order or the SysEX messages may change and if that happens, the translator will not trigger as the match will need to be exact.
Thanks, you must be using Google Translate or similar. This helps a lot but sometimes things get lost in machine translation.
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz