Well, if the computer "talks" through the XT alright, but the hardware device does not, I can only surmise that the hardware device is doing something incompatible with the XT that the computer software corrects in the pathway.īut now I would give MOTU a call (they always pick up pretty quickly nowadays most times of the day): (617) 576-3066. Most devices I have have Sysex transfers smaller than 130 bytes (it breaks the transfer into many smaller messages, which may be why they're successful).Īll other MIDI functions are working great. It only fails when the MOTU is in between, and only between some devices. If I connect the hardware devices directly without the computer, the transfer works. If I do the routing via the computer, using MidiOX or similar, the transfer works. There is no computer in the loop anywhere - this is purely hardware to hardware via the MOTU. If I incorporate the MOTU into the mix, the dumps suddenly go to between 753 bytes and 759 bytes - information is going missing. If I connect the Moog directly to the Kronos or QY700, a dump is 760 bytes and works correctly. I am running the MOTU standalone to perform MIDI routing. So in my case, the issue is manifesting when trying to do a SysEx dump from a Moog Sub 37 to a Korg Kronos or a Yamaha QY700. TL DR: I suspect you have a different problem. Are you certain this report does not pre-date the firmware update that was made to fix the sysex problems? So maybe MidiQuest is more conservative in how it gathers its info.) However, 130 bytes is such a small amount that I really doubt this person's report reflects everyone's experience. Perhaps they ALL use smaller chunks? (I seldom send large dumps from the units themselves. Like I said, I shuttle sysex to and from my units many times a week using MidiQuest to the Ensoniq ESQm, Yamaha TX81Z, a Kawai K5000s and two Korg Wavestations (one an SR). That is very strange sounding to these ears. (multiples of 64) you have the same value for consecutive positions the latter byte will be dropped. If your SysEx message is longer than 130 bytes, and in the byte positions of 64, 128, 192, 256, 320 etc. After generating thousands of valid SysEx messages, carefully looking at forwarded messages, comparing corrupted messages to the originals I finally discovered the exact edge case that causes the bug to appear.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |