Author |
Topic: Sysex Output devices message (Read 13812 times) |
|
paulc
New Member
MIDI-OX Rules!
Posts: 1
|
 |
Sysex Output devices message
« on: Jan 4th, 2007, 5:24pm » |
 Quote  Modify
|
Hi there,
I am using MIDI-OX for the first time to tansmit a Sysex file from my PC to my Korg M1 keyboard via a Tbox USB MIDI interface.
I am getting the following message:
SysEx output devices: The port is transmitting data to the device. Wait until the data has been transmitted, and then try again.
Can anyone help me to send this SysEx file successfully?
thanks alot.
|
|
 IP Logged |
|
|
|
JerryJorgenrud
New Member
MIDI-OX Rules!
Posts: 0
|
|
Re: Sysex Output devices message
« Reply #1 on: Jan 5th, 2007, 8:20am » |
Quote Modify
|
I think you may be caught in this issue described elsewhere on this board in the MIDI-OX Bug List section in the thread called Sysex Bug. Perhaps a quick reference to this one post near the end will tell you if this is your problem:
http://www.midiox.com/cgi-bin/yabb/YaBB.pl?board=bugs;action=display;num =1130961608;start=24
What might make your problem more difficult to resolve is the error message you mentioned means that the sysex message is coming in to the M1 at a rate faster than it can handle. The "solution" mentioned in the post referenced above will likely make the data arrive even faster. Normally we would have you open the Configure Box and specify a delay between buffers. But if your TBox is a "class compliant" USB device, it will want only one buffer. I looked at a factory preload at the Korg site and it is a 50k file, all one sysex message. If that's what you're trying to send you would have to try an output buffer size, typing it in as mentioned above, of 50,000 bytes. But as I say that might make data arrive even faster than before. According to John from jwpgroup the TBox should be controlling the flow so that doesn't happen, but ...
Korg UK has a tutorial available on how to use MIDI-OX to send data to the M1 but they aren't accounting for the TBox issue.
http://www.korguksupport.co.uk/page.cfm?pageid=359
You might visit this M1 user's page:
http://www.geocities.com/tlittle72/
He has a list of sysex utilities that he says will work with the M1
|
| « Last Edit: Jan 5th, 2007, 8:32am by JerryJorgenrud » |
IP Logged |
|
|
|
jwpgroup
Member
MIDI-OX Rules!
Gender: 
Posts: 12
|
|
Re: Sysex Output devices message
« Reply #2 on: Jan 6th, 2007, 9:09am » |
Quote Modify
|
Jerry & Paulc
This message only happens when the size of &/or the number of output buffers is not sufficent to encompass your file (I don't know why, but that's the problem). I've now seen it here (using a 'T' box) and can stop it happening by increasing the number of buffers (or their size, or both).
Note that (as Jerry mentions) dependent on the make up of your file (i.e. if it includes multiple F0/F7 combinations or not) and subject to whether you are using a 'class compliant' T box, you may need to send it as one large buffer anyway to avoid corruption.
Jerry's post clarifies what to try.
Hope this helps
John
|
|
IP Logged |
|
|
|
RUSH2112
New Member
Gender:
Posts: 2
|
|
Re: Sysex Output devices message
« Reply #3 on: Jul 16th, 2009, 1:03pm » |
Quote Modify
|
on Jan 4th, 2007, 5:24pm, paulc wrote:Hi there,
I am using MIDI-OX for the first time to tansmit a Sysex file from my PC to my Korg M1 keyboard via a Tbox USB MIDI interface.
I am getting the following message:
SysEx output devices: The port is transmitting data to the device. Wait until the data has been transmitted, and then try again.
Can anyone help me to send this SysEx file successfully?
thanks alot. |
|
Like yourself, I have an M1 that was displaying "INIT" and not playing the proper sounds. Searched the Internet and found that the battery would need replaced. I replaced the battery and found several different websites explaining how to get the factory M1 sounds loaded back in.
From a Korg M1 standpoint, I have successfully loaded the factory sounds back onto my keyboard. Here is what I did to get this to work (trust me, i spent days upon days trying different things until these settings worked).
I hope this helps anyone with an M1 or anyone else who gets the "Sysex output device: Port transfers data to unit. Wait until transfer is finished and try again" error
Under the sysex view and scratch pad, click Sysex, then configure, you will change both Input and Output buffers to 2500. The Num channels set at 16. The Delay after F7 change to 500 ms and change Ms between buffers delay to 120
|
| « Last Edit: Jul 16th, 2009, 1:15pm by RUSH2112 » |
IP Logged |
|
|
|
dsb
New Member
MIDI-OX Rules!
Gender:
Posts: 1
|
|
Re: Sysex Output devices message
« Reply #4 on: Jan 20th, 2010, 6:19am » |
Quote Modify
|
on Jul 16th, 2009, 1:03pm, RUSH2112 wrote:
Like yourself, I have an M1 that was displaying "INIT" and not playing the proper sounds. Searched the Internet and found that the battery would need replaced. I replaced the battery and found several different websites explaining how to get the factory M1 sounds loaded back in.
From a Korg M1 standpoint, I have successfully loaded the factory sounds back onto my keyboard. Here is what I did to get this to work (trust me, i spent days upon days trying different things until these settings worked).
I hope this helps anyone with an M1 or anyone else who gets the "Sysex output device: Port transfers data to unit. Wait until transfer is finished and try again" error
Under the sysex view and scratch pad, click Sysex, then configure, you will change both Input and Output buffers to 2500. The Num channels set at 16. The Delay after F7 change to 500 ms and change Ms between buffers delay to 120
|
|
Thanks for this great advice. It part fixed the same problem i had today with my Korg M1 and Soundblaster Platinum Pro. After I followed your advice- approx. half of the patches were successfully uploaded before the error message re-appeared. Setting both buffer sizes to 5000 completely fixed the problem!
|
|
IP Logged |
|
|
|
Angels
New Member
MIDI-OX Rules!
Posts: 1
|
|
Re: Sysex Output devices message
« Reply #5 on: Jul 12th, 2011, 12:55am » |
Quote Modify
|
I found that slowing everything down and keeping it small worked best. I set the Buffer size to 8 bytes and the number to 8192 and set the Output Timing to 500 Milliseconds.
This can all be accessed vua:
SysEx View & Scratchpad
SysEx
Configure
|
|
IP Logged |
|
|
|
|
User Forum ::
Powered by YaBB
Home 
Help 
Search 
Members 
Login 
Register
Reply
Notify of replies
Send Topic
Print