Korg Forums

What MIDI Interface are people using with their OASYS, and does it work on Windows 7 with lengthy SysEx dumps?

I'm having the following problem:
Windows 7 Professional SP1. M-Audio MIDISport 2x2. Latest drivers installed.

When I try to do a lengthy SysEx dump from the OASYS (i.e. Global > MIDI > Dump Program > Single A000), the dump gets garbled.

Using MIDI-OX, it shows that it receives a single block of 256 Bytes (which as you can see does not end with F7), then gets confused and turns subsequent SysEx into Note-Off messages, and basically garbles the whole dump. (see image).

Short SysEx messages (i.e. < 256 bytes) work absolutely fine. Furthermore, this Interface has always worked perfectly well with Mac OS X, Windows XP, and Windows Vista (as far as I recall).

So, I bought a second MIDI Interface, a Roland UM-ONE because I could swear I read somewhere that it works with long sysex dumps on Windows 7. This one is even worse. Again, short sysex messages work fine; anything resembling a dump doesn't come through.

Anybody able to receive a full SysEx Dump like this with Windows 7, and what MIDI Interface are you using?

Hi Stephen,

I use the Roland UM-1EX without problems:
http://www.rolandus.com/products/details/732

I haven't tried it with my Oasys yet with regards to dumps, but use it with my JD800 via Windows 7.

The UM-1EX has FPT (Fast Processing Technology) which helps with fast sysex dumps.

Stupid question:
Is there a way to set the transfer rate within the Oasys?

What I eventually discovered is that this is caused by the fact that the OASYS continually transmits MIDI clock all the time when Sync Mode is set to internal, and this corrupts the MIDI SysEx dumps on Windows 7+. If you put the OASYS into external sync mode so that it stops sending clock, the problem goes away. Very strange, I know, but absolutely the case. I suspect the manufacturers could correct their drivers for these problems, if they wanted to... but I tested three different companies MID Interfaces (M-Audio, Roland, MOTU) and they all did the same thing with Win7. Hope this saves somebody else some time...

Great advice, thanks a lot!

I can confirm that the M3 also continuously transmits MIDI clock and I would assume that all Korg workstations do the same.

Bald Eagle wrote:I can confirm that the M3 also continuously transmits MIDI clock and I would assume that all Korg workstations do the same.

Well, that's not entirely true. Sorry for not providing more details.

The M3 continuously transmits MIDI clock only in Seq mode. When you switch to Combi or Program Mode, it stops. I believe it's the same for the Kronos.

However, the OASYS does it in all modes, all the time.

Secondly, if I recall correctly (not going to retest it today), the sending of MIDI clock does not interrupt the bulk sysex dumps when using the Korg USB Driver. In other words, it's just not a problem when using the USB hookup.

However, the OASYS has no USB driver or port to connect to the computer. Therefore, you must use a standard legacy MIDI interface. And these interface's drivers all seem to have the same issue.

StephenKay wrote: The M3 continuously transmits MIDI clock only in Seq mode. When you switch to Combi or Program Mode, it stops.

I have OS version 2.04 on my M3 and it does transmit the clock in Program, Combi, Sequencer and Global modes. It only stops on mine in Sampling and Media modes.

Bald Eagle wrote:

StephenKay wrote: The M3 continuously transmits MIDI clock only in Seq mode. When you switch to Combi or Program Mode, it stops.

I have OS version 2.04 on my M3 and it does transmit the clock in Program, Combi, Sequencer and Global modes. It only stops on mine in Sampling and Media modes.

How are you verifying/determining this? I watched output of my M3 into an analysis program today. I don't know which version it is but it likely doesn't matter, it's probably 2.04. But I'll check tomorrow.

And also, why exactly do you care (just curious), since this is about the OASYS, and since everyone using an M3, Kronos, or M50 uses the USB cable and Korg driver, and none of these have any issue like this at all. It's only the OASYS, with a standard legacy third-party MIDI interface.

StephenKay wrote:
How are you verifying/determining this? I watched output of my M3 into an analysis program today. I don't know which version it is but it likely doesn't matter, it's probably 2.04. But I'll check tomorrow.

I'm using MIDI-OX.

StephenKay wrote: And also, why exactly do you care (just curious), since this is about the OASYS, and since everyone using an M3, Kronos, or M50 uses the USB cable and Korg driver, and none of these have any issue like this at all. It's only the OASYS, with a standard legacy third-party MIDI interface.

I don't really care about the specific issue you were facing. I just had an unrelated issue with timing signals and the M3 and thought I would share the information in case it would be helpful to anyone. Perhaps a post in the M3 forum would have been more appropriate.

Actually, you are correct, and I was mistaken. The M3 sends clock in Program and Combi modes, as well as Global and Sequencer. I don't know what I was seeing yesterday.

But in any case, again there is no problem with this specific issue with the M3 or Kronos, because of the USB and Korg MIDI Driver. This is only a problem for the OASYS...

Perhaps if one tried using the M3 with a standard legacy MIDI Interface, they would have the same problem.