All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo da Silva Serra <gustavo.serra@tet.com.br>
To: alsa-devel@alsa-project.org
Subject: Re: Still have choppy audio using 1.0.17
Date: Fri, 04 Jul 2008 09:40:06 -0300	[thread overview]
Message-ID: <486E1A26.1030802@tet.com.br> (raw)
In-Reply-To: <486A7757.4060907@tet.com.br>

I forgot a very important detail, when I can choose the output plugin 
(alsa or oss in Kaffeine, for example), only alsa has choppy audio. oss 
plugin works perfectly, only using kernel module emulation.

Gustavo da Silva Serra escreveu:
> I have tried to implement the solution you proposed. However I still 
> get choppy audio, just like before, otherwise the sound is clear.
>
> Basically I moved the timer to the cable struct, and updated the timer 
> function to update both playback and capture.
> I am sending the code attached so you can see if I implemented what 
> you suggested. The code is not very clean, nor completely functional, 
> as I never programmed to kernel before, and might cause kernel panic 
> when closing a stream.
>
> Any other suggestions?
> Thanks for the help and the attention.
>
> Takashi Iwai escreveu:
>> At Wed, 25 Jun 2008 08:24:33 -0300,
>> Gustavo da Silva Serra wrote:
>>  
>>> If I keep the difference between the playback and capture pointers 
>>> at one period, no choppy audio occurs. If the difference is 0, 2 or 
>>> 5 periods for example, choppy audio will always occur. Any ideas why?
>>>     
>>
>> Through a quick look at the code, it's likely the problem of the
>> timing of timer handlers for playback/capture streams.  In the current
>> code, the timer handlers are invoked individually.
>>
>> One possible fix would be to force to synchronize the updates of both
>> directions instead of individual timers.  That is, share the same
>> timer for the connected streams so that the update order is
>> guaranteed.
>>
>>
>> Just my $0.02.
>>
>> Takashi
>> _______________________________________________
>> Alsa-devel mailing list
>> Alsa-devel@alsa-project.org
>> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2008-07-04 12:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-16 20:04 Still have choppy audio using 1.0.17 Gustavo da Silva Serra
2008-06-18 18:24 ` Gustavo da Silva Serra
2008-06-18 19:44   ` Gustavo da Silva Serra
2008-06-19 13:01     ` Gustavo da Silva Serra
2008-06-20 19:07       ` Gustavo da Silva Serra
2008-06-25 11:24       ` Gustavo da Silva Serra
2008-06-25 16:06         ` Takashi Iwai
2008-06-25 18:34           ` Gustavo da Silva Serra
2008-07-01 18:28           ` Gustavo da Silva Serra
2008-07-04 12:40             ` Gustavo da Silva Serra [this message]
2008-07-14 17:57               ` Gustavo da Silva Serra
2008-07-15  0:50                 ` stan
2008-07-15 11:56                   ` Gustavo da Silva Serra
2008-07-15 18:40                     ` Gustavo da Silva Serra
2008-07-15 21:31                       ` stan
2008-07-16 14:19                         ` Gustavo da Silva Serra
2008-07-16 15:30                           ` Takashi Iwai
2008-07-16 15:43                             ` Gustavo da Silva Serra

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=486E1A26.1030802@tet.com.br \
    --to=gustavo.serra@tet.com.br \
    --cc=alsa-devel@alsa-project.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.