Chris Cannam wrote: > On Wednesday 10 Dec 2003 7:38 am, Clemens Ladisch wrote: > > Chris Cannam wrote: > > > I'm particularly intrigued by the SND_SEQ_EVENT_INSTR_* types > > > which look suspiciously like they might be intended for something > > > useful such as enabling soft-synths or samplers to report on > > > their available program or patch sets. Are they? > > > > Yes, they are exactly that, i.e., _intended_ for something useful. > > So in the hypothetical situation where a soft synth application really > wanted to be able to tell the world of ALSA sequencer clients about > what instruments, controllers etc it had available, it would have to > use some other communication layer than the ALSA sequencer?
It could use some user-defined event (but as you wrote, it's hard to detect support for this). Or somebody could define the format and the semantics of the _INSTR_INFO/FINFO/LIST events, and use those. > I suppose one could define a simple protocol for something like > the above based on the existing unused instrument event types > [...] but how would you then discover whether or not a client > supported that protocol? This protocol would be part of the official ALSA API (just like INSTR_PUT already is), so ALSA could define a new port type flag. Regards, Clemens ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
