[sdiy] MIDI merging info requested

[Ingo Debus]

Am Donnerstag, 12.05.05 um 23:16 Uhr schrieb ASSI:

> However there are useful and practical scenarios where one
> device sends Clock and another device sends Start/Stop/Continue.

Ah I see. I didn't think of this.

> Active Sensing doesn't really work anyway,

Well, it works if the devices support it. Hold down the key on a 
keyboard with a MIDI sound module connected and pull the MIDI plug 
while holding the key down. The sound module should stop sounding.

>  much less if you merge.

Depends on how smart the merger is ;-)
I must confess in the merger I have built this feature isn't 
implemented (yet).

> This would be useful for situations where one input had timing critical
> data while the other is used for editing. Prioritization makes sure
> that the timing critical data survives the merging while none of the
> editing gets lost (provided the buffer is large enough and the edit
> data doesn't consist of long reams of sysex).

Well yes. But you'd be truncating the data from the low priority input 
all the time, and starting again when the high priority data are 
finally sent. This would generate a lot of MIDI garbage (uncompleted 
messages) and use up a lot of bandwidth.

> The store-and-forward
> allows to make better use of running status for the de-prioritized
> channels

I don't understand. Can you please explain?

Ingo