From: Phil K. <phi...@el...> - 2002-11-06 20:32:27
|
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. So, what data does the GUI need? An instance identifier. What MIDI chan. is it on. Patch details (sample info, adsr, filter, loop points). Effect details. JACK connection info. ..... Others The GUI would be greatly enhanced if it can display waveform data so there should be a mechanism of passing this from the engine. It doesn't need to be a dump of the sample data, just enough info to do editing. I think most of the other controls of the engine will be MIDI based data: notes, pitchbend, cc data. What about uploading samples from the GUI to the engine remotely? Thoughts? -P Quoting Steve Harris <S.W...@ec...>: > On Wed, Nov 06, 2002 at 05:34:21PM +0000, Phil Kerr wrote: > > For config data using XML has clear cross-platform advantages and > > XML-RPC is a lot lighter than SOAP and could serve our needs well. > > I was thinking of raw XML, not XML-RPC. > > > For real-time control DMIDI would be good as it allows hardware > control > > and the syntax checking is minimal. This is where using XML instead > of > > CC or SYSEX messages would be too heavy. > > Argh, yes! I think we were talking at cross purposes. I was just > thinking > of the service discovery phase, obviously the control protocol wants to > be > be binary nad lightweight. > > > I think it would be good if we could find a split point between what > can > > be controlled by a GUI and what can be controlled by MIDI hardware, > even > > though there's overlap to an extent. > > Yes, probably. > > - 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 > |