nSCOURGE

I'm asking this(again) because I've read that Kx drivers introduce midi buffer overflow issues with large(?) sysex transfers to external hardware through UART.

I've also read that setting midi output buffer to 128 byte blocks might alleviate this(in programs that allow for it; sonar, xgworks - unfortunately NOT nord modular editor), but was wondering if anyone has actually tried this .

Finally, I would like to forego an external midi interface in favor of one that attaches to the back of my soundcard's joystick/midi port(1 midi in and 1 midi out), with the 'out' cable connected to a 3x8 midi thru box(so each synth/module can have it's own dedicated 'in' cable from the thru box) and then the lone midi 'in' cable to my master keyboard's midi 'out'. But I'm curious if anyone can percieve potential problems from this setup?

I don't care about being limited to 16 midi channels, and since I wouldn't be using the midi thru ports on ANY of my synths/modules I would hope this would preclude any signal problems from 'daisy chaining' modules together via midi thru ports.

If I can get by for now with a simple 3x8 midi thru box I'd like to forget about a dedicated external midi interface for now seeing how any midi interface with more than 4 outs is going to cost 3 times(at least!) as much as the thru box, and this isn't even considering the complications I'm bound to run into with the USB interface and the SIS chipset I have in my SIS 645 Ultra Mobo.

I would appreciate feedback from anyone familiar with these issues(especially those with firsthand experience), and some insight as to whether I should forget kX as hybrid solution to driving both external hardware & soft synths.

Eugene Gavrilov

>> midi buffer overflow issues

yep. under certain conditions, large SysEx messages aren't handled correctly
this cannot be fixed at the moment (probably, in the future)

/E