logik9bar
New Member

 MIDI-OX Rules!
Posts: 1
|
 |
Dropping MIDI messages and delays
« on: Feb 13th, 2005, 12:00pm » |
Quote Modify
|
Years ago I used to always use Hubi's MIDI loopback on Win9x to work around single client MIDI drivers. Over the past couple of years I've been using MIDI OX / Yoke to use a couple of editors (XGEdit, AN1xEdit) and sequencer (Sonar 4) to control my SW1000XG. MIDI OX is a great program, I love all the filtering features and controller mapping .. fantastic. I use a simple configuration in MIDI OX sending the output of MIDI Yoke #1 to SW1000XG #1. My first problems is that MIDI OX seems to occassionally drop MIDI messages sent to my SW1000XG card (via MIDI Yoke #1) when I load up XGEdit banks (hence performing large SYSEX / controller / patch change dumps). I work around this by hitting the refresh button in XGEdit which sends all of the data again hopefully managing to send the data it missed the first time. Is this a bug with MIDI OX or XGEdit? My other gripe is that if I send data via MIDI Yoke #1 from my sequencer the MIDI data is randomly delayed between 1ms to about 20ms! I timed this recording a metronome and measuring the times between each tick. If the delay was constant I could deal with it in the sequencer. When I send data directly to the SW1000XG midi output I get a variance of around 1ms which is fine. My work around for this is that the SW1000XG drivers allow 2 apps to open the MIDI ports at the same time so I open the port directly in my Sequencer and MIDI OX only using the MIDI Yoke ports for the editors where timing doesn't matter.
|