From: "random.bits" <random.bits@rogers.com>
To: Jaroslav Kysela <perex@suse.cz>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Re: alsa driver, repeat playback of buffer contents
Date: Tue, 15 Mar 2005 16:34:28 -0500 [thread overview]
Message-ID: <200503151634.28911.random.bits@rogers.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0503151949320.21135@pnote.perex-int.cz>
Sorry, I replied to your earlier message before seeing
this message.
I worked my way through the documentation looking at
no-xrun mode and stop_threshold values.
When I read the stop_threshold after setting the buffer
to 471 frames (length of pcm stream I want to repeat
is 1884 bytes, 11025 sampling, the concept of periods
is confusing me at the moment, but I used 1), the
stop_threshold is also set to 471. I then read the
boundary value and its set to 1975517184.
If I understand correctly, if I set the stop_threshold
to this value, the sound should continue to repeat.
It does not repeat the sound. Here is my debug output,
it shows initial and final settings as the program is
set up. Then the data is sent to the buffer for
playback. Followed by a stream status output. I can
post the source code if you want, but I figure I made
a mistake with the setup.
<debug output from alsarepeat.c, for pcm device "hw">
On opening the device, the hw parameters are:
ACCESS: MMAP_INTERLEAVED RW_INTERLEAVED
FORMAT: S16_LE S32_LE
SUBFORMAT: STD
SAMPLE_BITS: [16 32]
FRAME_BITS: [32 64]
CHANNELS: 2
RATE: [8000 48000]
PERIOD_TIME: (83 2048000]
PERIOD_SIZE: [4 16384]
PERIOD_BYTES: [32 131072]
PERIODS: [1 1024]
BUFFER_TIME: (83 2048000]
BUFFER_SIZE: [4 16384]
BUFFER_BYTES: [32 65536]
TICK_TIME: 1000
HW parameters are now:
ACCESS: RW_INTERLEAVED
FORMAT: S16_LE
SUBFORMAT: STD
SAMPLE_BITS: 16
FRAME_BITS: 32
CHANNELS: 2
RATE: 11025
PERIOD_TIME: (42721 42722)
PERIOD_SIZE: 471
PERIOD_BYTES: 1884
PERIODS: 1
BUFFER_TIME: (42721 42722)
BUFFER_SIZE: 471
BUFFER_BYTES: 1884
TICK_TIME: 1000
The initial software parameters are:
start_mode: DATA
xrun_mode: STOP
tstamp_mode: NONE
period_step: 1
sleep_min: 0
avail_min: 471
xfer_align: 471
silence_threshold: 0
silence_size: 0
boundary: 1975517184
SW parameters are now set to:
start_mode: DATA
xrun_mode: NONE
tstamp_mode: NONE
period_step: 1
sleep_min: 0
avail_min: 471
xfer_align: 471
silence_threshold: 0
silence_size: 0
boundary: 1975517184
Stream status is
state : RUNNING
trigger_time: 1110922148.974638000
tstamp : 1110922149.272647000
delay : 470
avail : 1
avail_max : 472
On Tuesday 15 March 2005 13:49, Jaroslav Kysela wrote:
> On Tue, 15 Mar 2005, random.bits wrote:
> > How can I get the hardware to continue to play
> > using the data in the ring buffer?
>
> Use no-xrun mode (set stop_threshold to boundary).
>
> Jaroslav
>
> -----
> Jaroslav Kysela <perex@suse.cz>
> Linux Kernel Sound Maintainer
> ALSA Project, SUSE Labs
>
>
> ----------------------------------------------------
>--- SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT
> Products from real users. Discover which products
> truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=cl
>ick _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/alsa-de
>vel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-03-15 21:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-14 20:30 alsa driver, repeat playback of buffer contents random.bits
2005-03-14 21:45 ` Lee Revell
2005-03-14 22:20 ` Måns Rullgård
2005-03-15 0:20 ` Lee Revell
2005-03-15 1:14 ` Mark Cannon
2005-03-15 1:19 ` Lee Revell
2005-03-15 7:49 ` Jaroslav Kysela
2005-03-15 18:49 ` random.bits
2005-03-15 18:49 ` Jaroslav Kysela
2005-03-15 21:34 ` random.bits [this message]
2005-03-15 8:14 ` Clemens Ladisch
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=200503151634.28911.random.bits@rogers.com \
--to=random.bits@rogers.com \
--cc=alsa-devel@lists.sourceforge.net \
--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 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.