From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Clemens Ladisch" Subject: Re: Broken playback Date: Thu, 22 Nov 2007 09:14:26 +0100 Message-ID: <1195719266.22048.1222696087@webmail.messagingengine.com> References: <1195644962.10939.1222529331@webmail.messagingengine.com> <1195658907.11141.1222567701@webmail.messagingengine.com> <1195661375.18942.1222573455@webmail.messagingengine.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by alsa0.perex.cz (Postfix) with ESMTP id 39CB0243AA for ; Thu, 22 Nov 2007 09:14:27 +0100 (CET) Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: Gabriele Melia Cc: alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org Gabriele Melia wrote: > > snd_pcm_hw_params_set_buffer_size_near(), but the allowed values are > > hardware dependent. You might want to add your own circular buffer that > > is bigger than ALSA's. > > So your suggestion is to limit my buffer_size after decode to be same of > ALSA's? No; my suggestion is to use your own buffer which is big enough for your decoder, and use this buffer to fill ALSA's buffer, whenever possible. If one call to your decoder function needs so much time that ALSA's buffer can become emptied, you need another thread to re-fill the ALSA buffer in parallel with the decoding. Regards, Clemens