From: Takashi Iwai Subject: Re: period time in async handler Date: Wed, 11 Jun 2008 18:31:49 +0200 Message-ID: References: <484F39E0.2010205@crossthread.com> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mx2.suse.de (ns2.suse.de [195.135.220.15]) by alsa0.perex.cz (Postfix) with ESMTP id 2D32D2488D for ; Wed, 11 Jun 2008 18:31:50 +0200 (CEST) In-Reply-To: <484F39E0.2010205@crossthread.com> 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: Tim Pushor Cc: alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org At Tue, 10 Jun 2008 20:35:12 -0600, Tim Pushor wrote: > > Hi Friends, > > I have a need to have an audio player kick off things at various points > of time through playback of an audio file. I'm trying to hack aplay as a > proof of concept. > > If I understand correctly, the asynchronous handler seems to do what I > want. I hacked in a handler to aplay and it works, but not quite like > how I expected. Oh, forget about async handler. It's a horrible hack, and in principle, never guaranteed to work. We really need to put DONT_USE tag to async handler APIs... Takashi > I counted the number of times that the handler got called, and thought > that if I multiplied that by the period time that I'd end up with the > total audio length but that doesn't seem to be the case. I was under the > assumption that the handler was called once per period. > > I must not understand the relationship of the asynchronous handler and > period_time. Does this make sense? Am I going about this all wrong? > > Thanks, > Tim > _______________________________________________ > Alsa-devel mailing list > Alsa-devel@alsa-project.org > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel >