From mboxrd@z Thu Jan 1 00:00:00 1970 From: Clemens Ladisch Subject: Re: Alsa timing question Date: Tue, 30 Aug 2011 09:49:56 +0200 Message-ID: <4E5C9624.6040405@ladisch.de> References: <4E55F6A2.3040307@ladisch.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by alsa0.perex.cz (Postfix) with ESMTP id D104D24503 for ; Tue, 30 Aug 2011 09:49:52 +0200 (CEST) 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: Raymond Toy Cc: alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org Raymond Toy wrote: >> However, if you're using the dmix plugin, the period size of your >> application's device will not necessarily be identical with the period >> size of the hardware device. > > Would dmix allow me to control this better than pulse audio? These parameters must be chosen by dmix before the first dmix device is used, so applications cannot control them directly. The defaults for dmix's period_size, period_time, and periods are 1024, -1, and 16. They can be overridden by setting the configuration values defaults.dmix.DRIVER.period_size/period_time/periods, where DRIVER is the internal driver name (the name between the colon and the hyphen in /proc/asound/cards, or the file name in /usr/share/alsa/cards/). Regards, Clemens