From mboxrd@z Thu Jan 1 00:00:00 1970 From: Florian Faber Subject: Re: Documentation Request Date: Wed, 04 Sep 2013 10:18:33 +0200 Message-ID: <5226ECD9.7060202@faberman.de> References: <522685BA.2030904@blennerhassett.gen.nz> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from linuxproaudio.org (70.52.11.217.in-addr.arpa.manitu.net [217.11.52.70]) by alsa0.perex.cz (Postfix) with ESMTP id 636BD2654D8 for ; Wed, 4 Sep 2013 10:18:34 +0200 (CEST) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: alsa-devel-bounces@alsa-project.org To: alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org Carl, > Thanks for your response, but I think that is a very poor solution. [ignorant blah] > > Surely an experienced core ALSA developer could create such a demo [more blah] How about: You write the documentation, given your 'fresh' experience with ALSA to help others in your situation. Or even better: Accept recommendations from other developers and use jack. You would have finished after half an hour and your application would cooperate with all other audio applications. All you have now is two wasted weeks of your life span and a non-cooperative application. And other new ALSA users are still in the same situation as you were. Flo -- Machines can do the work, so people have time to think. public key 8D073185 x-hkp://subkeys.pgp.net