From: "Tom Browne" <tbrowne@tbrowne.demon.co.uk>
To: Jaroslav Kysela <perex@suse.cz>
Cc: Clemens Ladisch <clemens@ladisch.de>, alsa-devel@lists.sourceforge.net
Subject: Re: snd_pcm_writei not returning (?!?)
Date: Tue, 6 Apr 2004 10:58:19 +0100 [thread overview]
Message-ID: <021d01c41bbd$b0a8fc10$0100a8c0@burpxp> (raw)
In-Reply-To: Pine.LNX.4.58.0404061114560.3153@pnote.perex-int.cz
Jaroslav Kysela wrote:
>> alsa_buffer_size = snd_pcm_hw_params_get_buffer_size(params);
>> err = snd_pcm_hw_params_set_period_time_near(handle, params,
>> alsa_period_time, &dir);
>> alsa_period_size = snd_pcm_hw_params_get_period_size(params, &dir);
>> ...
>> err = snd_pcm_sw_params_set_start_threshold(handle, swparams,
>> alsa_buffer_size-1)
> It's not correct and it was never correct, but the pcm.c was buggy,
> too. Look to the latest version.
Running a file compare, I see only one line of significant difference
between the version in 0.9rc2 and 1.0.4 pcm.c...
err = snd_pcm_sw_params_set_start_threshold(handle, swparams, (buffer_size
/ period_size) * period_size);
Which gives threshold = 6552 from buffer=6553, period=3276... exactly the
same value as the code I was already using gives! What else am I missing
from the garish red and yellow blocks of WinDiff?
Why does changing to mmap writes make the blocking problem go away? And as
I said, the problem only has been made to occur at 88.2 and 96K sampling
rates...
- Tom.
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
next prev parent reply other threads:[~2004-04-06 9:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-31 11:59 No mixer elems found Vincenzo Di Salvo
2004-03-31 12:38 ` Paul Davis
2004-03-31 15:33 ` snd_pcm_writei not returning (?!?) Tom Browne
2004-04-05 14:25 ` Tom Browne
2004-04-05 15:49 ` Clemens Ladisch
2004-04-05 16:16 ` Tom Browne
2004-04-06 7:48 ` Clemens Ladisch
2004-04-06 9:07 ` Tom Browne
2004-04-06 9:15 ` Jaroslav Kysela
2004-04-06 9:58 ` Tom Browne [this message]
2004-04-06 10:15 ` Jaroslav Kysela
2004-04-06 10:44 ` Tom Browne
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='021d01c41bbd$b0a8fc10$0100a8c0@burpxp' \
--to=tbrowne@tbrowne.demon.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
--cc=clemens@ladisch.de \
--cc=perex@suse.cz \
/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