Re: [Linuxsampler-devel] Sampler engine / GUI communication

[Phil K. <phi...@el...>]

Quoting Steve Harris <S.W...@ec...>:

> On Wed, Nov 06, 2002 at 09:49:40 +0000, Phil Kerr wrote:
> > Aaaah, I see :)
> > 
> > So we have n number of engines and a GUI broadcasts a message to see
> what's
> > there.  Each engine reponds with config data.
> 
> I was thinking there would be a broker, and that could do the selection.
> Broadcast is a bit problematic.
> 
> Probably the only info needed would be that engine the UI is for, and
> what version of the UI protocol it speaks (internal to the UI<->engine
> connection), eg:
> 
> <engine>
>   <type>linux-akai</type>
>   <protocol major="0" minor="1" micro="1" />
> </engine>
> 
> Other stuff can be done between the UI and engine privatly, other things
> dont need to be able to understand it.
> 

Yes, this looks good.

> > I think most of the other controls of the engine will be MIDI based
> data: notes,
> > pitchbend, cc data.
> 
> Right, but that is more of a realtime control thing, than a UI thing.
> The
> UI could use those (eg. for testing), but doesn't have to. MIDI can be
> received either my alsa midi, or dmidi or whatever.

It could be a mixture of both.  I can alter, for example, filter setting from
either the front panel or via sysex.  

-P

> 
> - Steve
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by: See the NEW Palm 
> Tungsten T handheld. Power & Color in a compact size!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
> _______________________________________________
> Linuxsampler-devel mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
>