From: Pieter Palmers Subject: Re: documentation - yeah right! Date: Thu, 22 May 2003 16:51:19 +0200 Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: <3ECCE3E7.2060603@student.kuleuven.ac.be> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Return-path: Errors-To: alsa-devel-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: To: "alsa-devel@lists.sourceforge.net" List-Id: alsa-devel@alsa-project.org Jaroslav Kysela wrote >The question is, if we have to create another library or integrate "basic" >API for simple applications inside alsa-lib. > >I think that most of applications are simple players or recorders. Then we >might design very simple API which can have some similar functionality as >OSS for developers recoding the OSS applications or for developers >expecting very simple API. > >I see three groups of applications: > >1) players (expecting mostly stereo output, maybe 4.0 and 5.1 or simple multichannel) >2) recorders (expecting mostly stereo input - might be enhanced to any number of channels) >3) full-duplex (same requirements as players or recorders) > >All groups also usually want to control the mixer settings. We have >already requests from audio conference tool developers to integrate >such feature to our API. Actually, there is no direct connection between >PCM outputs and mixer settings. These applications don't want to handle >many controls. I think that these will be quite sufficient: > >1) Master Playback Volume >2) PCM Playback Volume >3) Capture Gain >4) Capture Source (Mic, Line, Aux - might be enumerated) >5) Playback -> Capture Loopback Switch (to disable echo for conferences > and other tools) > >All these controls are quite abstract and some hardware might have >missing some of them or the routing might be very complex. > >The main goals for simple interfaces should be: > >1) offer unified simple abstract way >2) offer to describe (user might change it) the relations > between simple abstract and HAL (current alsa-lib) > > Jaroslav > > Totally unproductive remark: this is a great idea. More productive (mabye): In my opinion it should also be possible to mix both simple API & complex API. Sometimes all you need is the simple API functionallity, but for one function/method/action that isn't included in this simple API. It would be a pitty if this one thing should prevent developers to use the complex API for all of the work. Maybe this is an obvious remark, but nevertheless I think it's important. Pieter ------------------------------------------------------- This SF.net email is sponsored by: ObjectStore. If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software. http://www.objectstore.net/sourceforge