|
From: Mark K. <mar...@gm...> - 2005-03-02 16:24:29
|
On Wed, 2 Mar 2005 16:08:43 +0100, Christian Schoenebeck <sch...@so...> wrote: > Es geschah am Dienstag 01 M=E4rz 2005 21:23 als Mark Knecht schrieb: > > Christian, > > Thanks. Very clear description and very helpful. Te thought that I > > had to set the number of ports was in my mind but I couldn't figure > > out from the LSCP document exactly how to do it. Seems like I was > > close asking for parameters and finding ports but I somehow never > > found the instructions to add PORTS=3D2 to that command. >=20 > Yeah, my fault. You know LSCP was actually intended primarily for the use= by a > frontend application. And the usual way to create a new or alter an exist= ing > audio/MIDI device would be the frontend to "ask" the sampler for details > about drivers and driver parameters at runtime, that is the frontend woul= d > ask what drivers are there, which paramters those drivers offer, what the > purpose of those driver parameters are, type, possible values, default va= lue, > dependencies, etc. > So that way the LSCP language is absolutely independent of the implementa= tion > of each driver and independent of what drivers are actually there and tha= t's > why those driver details are not covered by the LSCP specs at all. It all makes sense, and even more sense now since your response yesterday. It just never dawned on me the answer was quite so simple and straight forward. That's cool. I understand about not having enough time. This could also be handled through more examples on the web site. Maybe my scripts can help in that way? Put up chunck of LS-script code with a little bit of info on what I'm trying to do? Maybe that way the user community can grow the knowledge database more over time? (A wiki maybe?) >=20 > I planned to make extra specs for the drivers we have, so you could read = what > parameters each driver offers, but haven't found the time yet to do it. I= f > somebody likes to start such a documentation, it would be very much > appreciated! Docbook for instance might be a good choice. >=20 > CU > Christian >=20 Cheers, Mark |