From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <177d8cde7f98f14a1580d45e8930d612@quintile.net> From: "Steve Simon" Date: Wed, 12 Aug 2009 10:30:23 +0100 To: 9fans@9fans.net In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] audio standards -- too many to choose from Topicbox-Message-UUID: 43e6b7e0-ead5-11e9-9d60-3106f5b1d025 Here is how I think it would work - please correct me if I am wrong. the status file gives a list for the supported features and the current state of each. If particular hardware does not support mu-law then no state is displayed for it and the application layer can decide to emulate a mu-law table or report the problem to the user and give up. I do think that thought needs to be given to how a combined audio and video player would be inplemented - ensuring correct lipsink at a minimum. also, might I suggest that the application level tools live in aud/xxx or audio/xxx - I think it is a shame that the image manipulation tools are not in img/xxx -Steve