From: Ben Dooks <ben@trinity.fluff.org>
To: Markus Rechberger <mrechberger@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: struct snd_pcm_hardware_t values
Date: Sun, 6 Aug 2006 20:56:14 +0000 [thread overview]
Message-ID: <20060806205614.GB2929@trinity.fluff.org> (raw)
In-Reply-To: <d9def9db0608061138o100b5b78yead3623f655ec60b@mail.gmail.com>
On Sun, Aug 06, 2006 at 08:38:53PM +0200, Markus Rechberger wrote:
> I did some more investigation uppon this
> > .buffer_bytes_max = (32*1024),
> this one seems to be clear now, I set it to the max
> transfer_buffer_size of 1 URB
> > .period_bytes_min = 64,
> this one not .. in my case I set it to transfer_buffer_size/2
> > .period_bytes_max = 2048,
> this one is again transfer_buffer
> > .periods_min = 1,
> I set this one to 2 (people in IRC cleared me up about this one)
> > .periods_max = 255,
> no idea again..
>
> So what I get now is:
> http://lost-souls.mercuryserver.de/files/data/test.wav.mp3
>
> and a buffer underrun regarding aplay
> aplay -D hw:2,1 5_5_2006__07_00_59.wav
> Playing WAVE '5_5_2006__07_00_59.wav' : Signed 16 bit Little Endian,
> Rate 9600 Hz, Mono
> underrun!!! (at least 0,307 ms long)
> underrun!!! (at least 0,285 ms long)
> underrun!!! (at least 0,295 ms long)
> underrun!!! (at least 0,279 ms long)
> underrun!!! (at least 0,298 ms long)
> underrun!!! (at least 0,287 ms long)
>
> the strange thing here is the DTMF tones in the background sound fine,
> so I don't really recognize an underrun when playing the file just
> that strange noise which is constant all the time..
>
> following is what my debug prints in dmesg:
> I'm sure the PCM PLAYBACK TRIGGER STOP! are caused by the buffer
> underrun which is reported by aplay..
> The outgoing dataformat is 9600hz, S16_LE, mono ..
I'm having trouble with ALSA intermittently getting into a state
where the trigger is being repeatedly called for start then stop
and can only sometimes get out of it. I will post a seperate report
on this later.
--
Ben
Q: What's a light-year?
A: One-third less calories than a regular year.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
prev parent reply other threads:[~2006-08-06 20:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-05 13:09 struct snd_pcm_hardware_t values Markus Rechberger
2006-08-06 18:38 ` Markus Rechberger
2006-08-06 20:56 ` Ben Dooks [this message]
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=20060806205614.GB2929@trinity.fluff.org \
--to=ben@trinity.fluff.org \
--cc=alsa-devel@alsa-project.org \
--cc=mrechberger@gmail.com \
/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