Old Motifator threads are available in the Archive.
wonderer
Total Posts: 30
Joined 10-11-2017 status: Regular |
Hi, In my search for undocumented MOXF sysex messages, I found a set about “Quick Setup”. In this forum there’s a thread about it from 2014 that came very close to the solution: http://www.motifator.com/index.php/forum/viewthread/472675/
Parameter change:
Parameter request:
If and when I find more, I will post them in this thread |
Vetalexy
Total Posts: 32
Joined 07-20-2015 status: Regular |
Thank you! This is very useful information! |
wonderer
Total Posts: 30
Joined 10-11-2017 status: Regular |
Some more undocumented sysex’s and expanded on one already found before http://www.motifator.com/index.php/forum/viewthread/475646/.
Parameter change:
|
Vetalexy
Total Posts: 32
Joined 07-20-2015 status: Regular |
The behavior of Yamaha is very strange! Not only do they not correct their mistakes (not synchronous transfer of midi data to the sequencer on the computer). So they still hide the information about the sysex commands! |
wonderer
Total Posts: 30
Joined 10-11-2017 status: Regular |
I think they don’t want to share this information because it’s meant for communication between the software editor and the MOXF. Maybe they just never imagined it could be useful for other purposes. I also own a Roli Seaboard Rise, and Roli doesn’t give any information about sysex. So it’s not just Yamaha that holds back information. |
Vetalexy
Total Posts: 32
Joined 07-20-2015 status: Regular |
There is very need the editor for the sequencer. For direct editing of patterns and songs. I wanted to try to do some editor myself, but I do not have enough information about sysex. And I do not know at all - is this possible in principle. |
wonderer
Total Posts: 30
Joined 10-11-2017 status: Regular |
I never worked with the sequencer, but it doesn’t seem to send midi sysex info out while changing parameters, so it’s very unlikely that it’s possible.
I found a lot of undocumented sysex messages that I have no idea (yet) what they do or mean. If someone else wants to take a shot at them, let me know and I’ll publish them here. |
Vetalexy
Total Posts: 32
Joined 07-20-2015 status: Regular |
Thanks for the answer. Address scanning is a very big job with an unknown outcome. I also tried to scan addresses, but I got answers who can not be deciphered. This is blindlyng work. Yamaha it would be possible to ignore clients less! |
wonderer
Total Posts: 30
Joined 10-11-2017 status: Regular |
Hello again. Just found a sysex that sends back the display contents in 17 sysex messages.
Parameter request:
Response from MOXF:
F0 43 00 7F 1C 08 06 00 51 00 01 00 00 78 78 78 78 78 78 78 …
Sysex 17:
Sysex 1: (00 0F) might be the nr of sysex’s that follow, the next 4 bytes give the dimensions (01 70 = 240 pixels width) - (00 040 = 64 pixels height)
Sysex’s 2 to 16 are 1039 bytes in length and hold the image in a kind of pixel format, 1024 pixels per sysex. Every value is 1 pixel (00 or 78).
Sysex 17 seems to have something to do with “last changed leds”. Must not be too hard for a Windows programmer to build a little program that sends the sysex, catches the response and converts it into a bitmap. I will have a go at it for Linux when i am finished searching for undocumented sysex’s. ;-) |
5pinDIN
Total Posts: 11891
Joined 09-16-2010 status: Legend |
Thanks for making the effort and posting your results. I don’t have a MOXF, but I’ve determined that by changing the model ID from 1C 00 to 12 the following Parameter Request messages that you posted work with the Motif XF:
I haven’t tried them on my Motif XS, but it’s likely they would work if the model ID was changed to 03.
If you post the positive results of the ranges you already tried, I could see if they work with the XF (by changing the model ID), and then try to determine what they are. I’d suggest that if you do make that available, it might be best to place it in a text file, ZIP that, and attach the ZIP to a post. |
wonderer
Total Posts: 30
Joined 10-11-2017 status: Regular |
Your welcome, I hope the results enable people to do some things they weren’t able to do before.
Thanks for verifying these sysex’s also work on the Motif XF, that makes them usable for a lot more people. Soon I will post the positive results in a .ZIP file, I first have to recheck them as my home-brew software had a problem with large sysex’s that only surfaced when I got to the screendumps. Just to make sure there aren’t any hiccups. |
5pinDIN
Total Posts: 11891
Joined 09-16-2010 status: Legend |
You’re welcome - I’m glad to help. I checked further, and indeed they also work with the XS by changing the model ID. |
wonderer
Total Posts: 30
Joined 10-11-2017 status: Regular |
Hi again, Added to this post is a ZIP file with a plain text document that I hope will show as intended. It should be viewed with a fixed font.
This text is about undocumented parameter requests and the responses from the MOXF in voice mode only.
I would really appreciate any comments and ideas from anyone interested in this matter. What really would help is to share “undocumented sysex” responses from a MO, MOX, MOXF or Motif that has been filled with user Songs, Voices, ARPs etc. That way some things might surface that otherwise remain hidden.
The next ZIP is about undocumented dump requests in voice mode but it will take a while to put together.
Found more info about the 01 00 nn addresses.
File Attachments
Moxf - Undocumented voice parameter requests.zip (File Size: 6KB - Downloads: 322) |
5pinDIN
Total Posts: 11891
Joined 09-16-2010 status: Legend |
Thanks for posting the ZIP file. I checked several of the Parameter Request messages, using the correct model ID for the Motif XF. Most did not result in a response from the XF. That’s not surprising - there are certainly differences between the MOXF and Motif XF.
I’ve only been able to verify the following Parameter Requests work with the XF…
YC-3B is an organ emulation (Hammond B3?) VST, provided by Yamaha. It’s not integral to the MOXF - I presume it was in use when the SysEx testing was done. I’m not sure what to make of the CC# assignments, since the XF doesn’t respond to those messages (using its model ID). |
wonderer
Total Posts: 30
Joined 10-11-2017 status: Regular |
You’re welcome, and thank you for checking out these requests on the Motif XF/XS. The next zip with dump requests is almost done, I expect to post it later today.
Maybe you already noticed that i updated the ZIP file yesterday. I added some new info in the 51 00 00 section. That section is only for reading the display and leds, sending parameter changes to it doesn’t do anything. I would be very interested in the responses it generates on a Motif (if any).
|
5pinDIN
Total Posts: 11891
Joined 09-16-2010 status: Legend |
No response by the Motif XF to those Parameter Requests. By the way, in your previous post you said “Found more info about the 50 00 00 and 50 00 02 adresses.” It appears you meant 51 00 00 and 51 00 02 - if so, you might want to edit that post.
Â
Based on that, I did a bit more research. I took a look at an 8L26OS_.PGM (MOXF firmware) file, using a hex editor, and found a section headed with “YC-3B”. It has CC# and other assignments, and is apparently a template for that VST. It’s followed by others for FM8 and Massive (Native Instruments VSTs), Trilian (Spectrasonics), Nexus 2 (reFX), etc. Perhaps the YC-3B response to the Parameter Request is due to it being the default loaded VST template. I suppose you could try selecting a different VST template and see if the response changes. Further searching the firmware with a hex editor might provide other clues, if you’re so-inclined. |