From: Abramo Bagnara Subject: Re: (no subject) Date: Sun, 21 Jul 2002 01:04:02 +0200 Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: <3D39EC62.4E6ADC04@libero.it> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: Received: from smtp2.libero.it (smtp2.libero.it [193.70.192.52]) by alsa.alsa-project.org (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id BAA19876 for ; Sun, 21 Jul 2002 01:05:02 +0200 Errors-To: alsa-devel-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: To: Fernando Pablo Lopez-Lezcano Cc: Jaroslav Kysela , Takashi Iwai , Gary Scavone , Paul Davis , "alsa-devel@alsa-project.org" List-Id: alsa-devel@alsa-project.org Fernando Pablo Lopez-Lezcano wrote: > > > > > on a related note, although the above suggestion will fix this > > > > particular problem, it seems that it might be wise to consider adding > > > > a parameter order information field to the driver API, so that drivers > > > > can say "you have to set param P first, then param N, then param > > > > O". the default would obviously be "don't care", but for devices that > > > > lose certain capabilities when certain parameters are set, it would > > > > make things very much easier. > > > > > > agreed that it's good to have such one. > > > but how to implement this? > > > from the design of hw_constraint, i don't think it's so easy... > > > > I think that this implementation will create a big mess for the > > application developers. Also, I'm not sure, if it's really needed, because > > our refining code should already reduce the available configurations. > > Applications should use *_near() functions in order of their priority. You > > can't predict, if rate or count of channels or any other parameter is more > > important for a specific application. > > [not exactly an answer but more details on what is actually happening] > > I think this is what is happening with the current driver (Gary, please > correct me if I'm wrong): The application looks at the configuration > space and selects from it one particular sampling rate. Then it looks at > the channel count and sees a range of channel counts (10:18 - or some > numbers like that, I don't remember). The application chooses the minimum > channel count and the set function fails. > > IMHO at that point the configuration space should have changed the number > of channels available to match the sampling rate selected so that the > channel count as advertised is legal (ie: if the selected sampling rate is > one of the "single speed" rates then the range of channels should be > 18:18, if the sampling rate is one of the "double speed" rates then the > range should be 10:10). > > The reverse is also true, if the application first selects number of > channels the sampling rates should be constrained to the set of rates that > can be supported by that number of channels. > > If it is not possible to do this with the current api, then the next best > solution I can imagine is to have a switch that changes the mode of the > card between single and double speed (that would make the dependency > between sample rate and number of channels dissapear). I've designed current refine API to do exactly what you've described. If this don't work for the specific card it's a card driver bug. -- Abramo Bagnara mailto:abramo.bagnara@libero.it Opera Unica Phone: +39.546.656023 Via Emilia Interna, 140 48014 Castel Bolognese (RA) - Italy ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf