Alsa-Devel Archive on 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: Problem with aloop
Date: Fri, 09 May 2008 09:56:09 -0300	[thread overview]
Message-ID: <482449E9.3000405@tet.com.br> (raw)
In-Reply-To: <d5eabee70805090546t5219e9e3v63df15b5d64fd7dd@mail.gmail.com>

Benjamin van den Hout escreveu:
> Gustavo da Silva Serra wrote:
>
>   
>>    I am developing an application that captures sound and send it
>> through a network, just like a sound server. To test it I am using
>> kaffeine with alsa output plugin. After some time playing continuously,
>> or if I keep moving the position slider backward and forward, I get
>> choppy sound. If I close and reopen the capture stream opened by my
>> sound server, the sound is restored to good quality. Sometimes I have to
>> reopen many times before I get a good sound. When I use kaffeine oss
>> output plugin I don't have this issue. I don't have an audio sound card,
>> so I don't know if this is an *aloop* issue.
>>     
>
>   
>> Here are some details:
>> - RedHat EL 4 kernel 2.6.9.55-ELsmp 64bit
>> - Alsa 1.0.16
>> - Xinelib 1.1.12
>>     
>
> Hi all,
>
> I'm experiencing the same problem as Gustavo. In my case I have a SIP
> client calling to another PC and I'm injecting audio with aplay (or
> amarok, no difference there) into that SIP call. About 8/10 times
> everything goes well, the other two times the audio that comes out at
> the other PC sounds really choppy. Both PC's are on the same local
> network so that is probably not the problem.
>
> What I found out is that if I patch aloop-kernel.c in the 'static
> struct snd_pcm_hardware snd_card_loopback_info' to have ".formats =
>  (SNDRV_PCM_FMTBIT_S8 )," this problem goes away. But then I'm stuck
> with 8 bit audio. It sounds a bit like the aloop device sometimes
> doesn't properly synchronise the 16 bit (or 32bit, tried that as well)
> samples on both PCM devices and things get mis-aligned. I'm quite new
> to ALSA so please don't laugh too hard if I'm missing something here
> :)
>
> Any input is greatly appreciated!
>
> Kind regards,
> Benjamin van den Hout
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>
> __________ NOD32 3088 (20080509) Information __________
>
> This message was checked by NOD32 antivirus system.
> http://www.eset.com
>
>   

Well, I discovered that only xinelib has this problem. Xmms and 
alsaplayer, for example, don't have this issue. I am testing VLC and it 
seems to work fine. I am not surprised, since the xine source code that 
deals with alsa is huge and ugly, it must be very hard to mantain that.

  reply	other threads:[~2008-05-09 12:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-09 12:46 Problem with aloop Benjamin van den Hout
2008-05-09 12:56 ` Gustavo da Silva Serra [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-05-13 13:27 Benjamin van den Hout
2008-05-13 13:45 ` Gustavo da Silva Serra
2008-05-14  8:35 ` Benjamin van den Hout
2008-05-13  7:43 Benjamin van den Hout
2008-05-13 11:51 ` Gustavo da Silva Serra
2008-04-30 20:27 Gustavo da Silva Serra
2008-02-20 14:19 [PATCH] improved snd-aloop quality when using certain samplerates and kernel HZ Ahmet İnan
2008-02-20 16:08 ` Takashi Iwai
2008-02-21  0:06   ` Ahmet İnan
2008-02-21  6:54     ` Takashi Iwai
2008-02-22 18:05       ` Ahmet İnan
2008-02-28 11:48         ` Takashi Iwai
2008-03-01 11:55           ` Ahmet İnan
2008-03-01 15:22             ` Takashi Iwai
2008-03-01 23:35               ` Ahmet İnan
2008-03-06 15:51                 ` Takashi Iwai
2008-05-31 20:00                   ` Problem with aloop Ahmet İnan
2008-06-01 16:15                     ` Benjamin van den Hout
2008-06-02  8:08                       ` Ahmet İnan

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=482449E9.3000405@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox