Re: [DSSI] Sysex in DSSI

[Sean B. <smb...@jp...>]

On Jan 24, 2007, at 7:44 AM, Chris Cannam wrote:
> The host can pass sysex to the plugin, and the failure of 
> jack-dssi-host to do
> so is probably (?) just an implementation shortfall.

One could argue that, but I left it that way in ghostess on purpose -- 
since
sysex messages are not channelized, the host must pass each message
to _all_ of the plugins it is hosting.  That just seemed too ugly to 
me, and
counter to DSSI's abstraction of the host-to-plugin event interface (as 
soon
as we start talking about what sort of _MIDI_ data the host should pass,
we've lost something, I think.)

> There are two ways I can think of to work around this with the current 
> DSSI:
>
>  1. Provide an alternative way to send sysex to the UI, and make the UI
> respond by updating its own state and sending a configure call to the 
> plugin
> to tell it to update its.  Hexter does this by (I think) creating a
> completely separate ALSA sequencer port in the UI process that's only 
> used
> for receiving sysex.

Correct.  It's awkward, but functional and works with the existing DSSI
spec.

-Sean