Author |
Topic: Mapping to sysex - delay (Read 856 times) |
|
monoman
New Member

 MIDI-OX Rules!
Posts: 2
|
 |
Mapping to sysex - delay
« on: Jan 6th, 2005, 5:55pm » |
Quote Modify
|
Hi, I've mapped a rotary control on my keyboard to a sysex message (using the excellent midi-ox) so that i can control extra parameters on my sw1000xg such as the varation effect parameters. This works fine except that if i sweep the rotary control whilst playing some notes it takes cubase a while to catch up. I've tryed messing around with the buffer size/ number of buffers which has improved it, but not enough. I've noticed also that if i play around with the same control in xgedit the same problem is exhibited. I'm i missing something?
|
|
IP Logged |
|
|
|
Jamie OConnell
Administrator
    


Gender: 
Posts: 2027
|
 |
Re: Mapping to sysex - delay
« Reply #1 on: Jan 7th, 2005, 2:12am » |
Quote Modify
|
Some devices DO use real time SysEx messages to adjust parameters. Unfortunately I don't have anything like that to experiment with, but there may not be that much that can be done anyway under Windows, to improve it. Particularly since you mentioned that using XGEdit cause the same thing. I do know that these SysEx messages are usually pretty small in size ( < 128 or 256 bytes) and numerous in frequency so many small buffers might help, but might add to the delay too if there are many queued up in the output driver.
|
|
IP Logged |
--Jamie Music is its own reward.
|
|
|
monoman
New Member

 MIDI-OX Rules!
Posts: 2
|
 |
Re: Mapping to sysex - delay
« Reply #2 on: Jan 10th, 2005, 10:19am » |
Quote Modify
|
If i output from midi-ox straight to the soundcard, it's fine. It's only when i send the sysex to cubase via midi yoke that it becomes really choppy. It surprises me because the sysex messages are only a bit bigger than a normal ctrl message. I'll have to see if there's a way to record normal ctrl changes into cubase and then convert them to the equivalent sysex messages in cubase. Thanks anyway.
|
|
IP Logged |
|
|
|
|