|
From: Christian S. <chr...@ep...> - 2004-05-18 23:15:33
|
Hi! See the latest LSCP draft as an proposal for LSCP extension to be able to configure audio output and MIDI input drivers: http://www.linuxsampler.org/api/draft-linuxsampler-protocol-05.sxw http://www.linuxsampler.org/api/draft-linuxsampler-protocol-05.pdf Instead of defining commands and parameters for each driver individually, I proposed with this draft a general protocol to obtain all available drivers, their supported parameters, purpose of each parameter and possible values or range AT RUNTIME! Not sure if you are happy with this, because that makes the protocol a bit abstract and complicated, but it has the big advantage, that frontends can be implemented independently from already implemented drivers and independently from which parameters these drivers offer. So even if we add a new driver one day with very abscure parameters, the GUI frontend will be able to handle it without any change. Additions: - added commands for loading / unloading and configuring audio output drivers (chapter 3.1 et seqq.) and MIDI input drivers (chapters 3.2 et seqq.) Changes: - redefined output fields of "GET CHANNEL INFO" command (3.3.8) - redefined command "SET CHANNEL AUDIO_OUTPUT_CHANNEL" command (3.3.13) - MIDI port is now a number for the virtual MIDI port of a MIDI driver (=MIDI input device) in LS instead of a driver dependent port identifier (e.g. 3.3.14) - MIDI channel can now also be set to ALL to listen on all 16 MIDI channels (e.g. 3.3.15) Again, this is only a suggestion so far. Critics, suggestions, improvements always appreciated! If it's still unclear from the specification, or if you're too lazy to really read it :) I can also make a short example to show you how I thought it to work. CU Christian P.S. chapter 4 ("Command Syntax" et seqq.) is not yet updated for the changes. |