Author |
Topic: Problems sending SysEx files to Keyboard (Read 5777 times) |
|
M1KORG
New Member
MIDI-OX Rules!
Posts: 5
|
 |
Problems sending SysEx files to Keyboard
« on: Feb 26th, 2009, 12:52pm » |
 Quote  Modify
|
Ok, so i have only been tinkering with this software since yesterday. I have read thru a lot of the help section and understand some things, but its still very complicated to me.
I have an M1 Korg keyboard hooked up to my computer with a USB MIDI interface.
Everything seems to be partially working here..
I am trying to upload non-factory patches.
I am able to only send 1 or 2 sounds at a time. And the rest do not work. In the Program mode of the keyboard where the multi sounds (patches) are stored, the first two sounds 00 and 01 work great. The other 97 patches just show gibberish ( random characters) on the screen and have no sound.
I should be able to send an entire "bank" of sounds to the keyboard with MIDI-OX right? I know the SysEx files i am sending have more than one sound in them.
My goal here is to have 100 different sounds on the keyboard just like it came from the factory, but with different sounds. I think MIDI-OX can do that, i just need to change a setting, but i dont know how.
For instance, after i donwload the original 100 factory patches from KORG, i should be able to send all the patches at one time with MIDI-OX, right? Or if i choose to, send different sounds individually?
|
|
 IP Logged |
|
|
|
JerryJorgenrud
New Member
MIDI-OX Rules!
Posts: 0
|
|
Re: Problems sending SysEx files to Keyboard
« Reply #1 on: Feb 27th, 2009, 8:35am » |
Quote Modify
|
Does this apply to your problem?
Regarding:
The transmission of corrupt sysex messages when using a MIDI USB device that uses the Windows-supplied USB class driver. These devices do not require an additional driver to be installed when installing them on Windows. In other words the box probably had the words "class compliant" on it somewhere and when you first plugged it in Windows did not ask for a driver installation disk.
The problem:
The Windows USB audio class driver requires a single sysex message, and only one, to fit in one sysex buffer and will not tolerate splitting a sysex message across buffers.
The solution:
1) Probably the best solution is to buy a different (quality) MIDI interface. Devices from Roland/Edirol or MOTU ship with their own drivers and these do not have this problem.
2) If you must work with the Windows driver you need to set the size of the output sysex buffers in MIDI-OX large enough so one sysex message will fit in it. You also need to check "Delay after F7" in the "Configure" box. This forces MIDI-OX to switch to the next buffer after the F7 ends the message so that only one message is in the buffer. You can reach both of these settings in the Sysex view under Sysex -> Configure. I would also specify at least a 10 to 30 second delay between buffers, especially for vintage gear.
Points to note:
Most sysex messages are not very big. SysEx *Files* that are big, like a patch bank, tend to be composed of many smaller sysex messages. It's only the bytes between (and including) F0 and F7 -- one sysex message -- that need to fit in one buffer. So if you have a bank file of 128 patches and each patch is only 24 bytes long, all you really need is a size of 24 bytes even though the file you send is much bigger than that.
If you do actually need to set a really high size for the output buffers, type the number in rather than trying to use the "spinner". The spinner stops spinning at 32k. In addition to the "spinner" problem, the box is not wide enough to see the whole number very clearly if you need to go to five figures. Ordinarily one would never need to go this high absent the buggy driver. The maximum size you can type in is 65k (65,535). If your single sysex message is larger than that (very rare) then MIDI-OX will not be able to work with the Windows USB driver.
M1 and other vintage gear specific: They need to be coddled a bit. It's a faster world. Experiment with delay settings. Make sure you know how big the buffer needs to be and avoid setting it too much bigger. Unplug the output MIDI cable from the synth when you are loading patches on its input cable. I've seen active sensing cause sysex garbling in some USB interfaces. I possess a cheap USB class compliant MIDI interface that randomly inserts null bytes in sysex and other messages. No amount of fussing will make that one work correctly 100% of the time.
|
|
IP Logged |
|
|
|
M1KORG
New Member
MIDI-OX Rules!
Posts: 5
|
|
Re: Problems sending SysEx files to Keyboard
« Reply #2 on: Feb 27th, 2009, 1:09pm » |
Quote Modify
|
I finally did it...success! 
I tweaked the settings in configure, and after about an hour, it finally worked.
90 percent of the sounds work, and a few a not quite right. But with some time, i'll get everything working perfect.
thanks for the help
|
|
IP Logged |
|
|
|
simondlambert
New Member
MIDI-OX Rules!
Posts: 1
|
|
Re: Problems sending SysEx files to Keyboard
« Reply #3 on: Apr 1st, 2009, 7:48pm » |
Quote Modify
|
Thanks for your advice. Saved my sanity!
Just for the record, I have been using Windows XP and a Tascam 122 usb midi interface to my Korg M1. The latter has just had its battery changed so I needed to upload the Korg factory presets. As we have discovered, the Midi-ox defaults don't make the M1 happy. I found that using 2 buffers of 1024 each with an 'F7 delay' of 10,000 ms did the job first time! I was very pleased after taking hours to seek out a solution to this perplexing hurdle.
Best regards,
Simes
|
|
IP Logged |
|
|
|
|
User Forum ::
Powered by YaBB
Home 
Help 
Search 
Members 
Login 
Register
Reply
Notify of replies
Send Topic
Print