[sdiy] Anyone know of a device that does no-added-delay MIDI filtering?

[Bob Weigel]

Hmm.  Ohhhh I see what you're saying I think.  This is another question 
I'd have to write a file with the data and just send it out my midi data 
transmitter from spg to test.  Some old synths *may* be expecting to see 
the data after a note on for instance.  Otherwise they may hang. 

So you are suggesting rather than sending data to just skip it and send 
another staus byte instead?  Hmm.  Well if the machine were already on 
running status with notes on the channel it's *supposed* to be 
responding to, then we wouldn't want to do that now would we?

See..say we had another channels' controller message come in in the 
middle of a chord for instance that was being played on the channelized 
machine.   You'd either have to complete the message by sending the 
previous stored controller value for that machine on the channelized 
port.. or do what I think you are suggesting and instead just send 
another Note on message on the channelized port.  And that might work 
and save a byte here and there in the process. (Or..I should say send 
the last 'potentially running' status byte again.) 

I just am not sure if that will work on some of the clunky old 
firmware.  Good idea though and I'll try it if I ever get around to 
doing this. -Bob

ASSI wrote:

>On Montag, 6. März 2006 01:07, Bob Weigel wrote:
>  
>
>>I'm not sure what you mean below.  To 'switch status' requires...a
>>status byte.  Is that what you are calling an 'intervening message'?
>>    
>>
>
>You send one status byte and you'd normally send the corresponding 
>message, a Note On event for instance (consisting of note number and 
>velocity). Instead you could chose to send a different status byte (for 
>a Control Change perhaps) directly.
>
>
>Achim.
>  
>