From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: Jaroslav Kysela <perex@suse.cz>
Cc: Alsa-devel@lists.sourceforge.net
Subject: Re: status pointer's problem with dmix.
Date: Thu, 18 Sep 2003 17:20:28 +0100 [thread overview]
Message-ID: <3F69DB4C.8070401@superbug.demon.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.53.0309181459440.5983@pnote.perex-int.cz>
Jaroslav Kysela wrote:
>
>
> I'm asking again, what is your problem in your application? Yes, avail in
> driver is negative, because appl_ptr is NOT updated from the dmix clients
> (and it is not possible - it is a shared thing), but the dmix plugin
> should pass the right value (non-negative) to application. Please, don't
> look to /proc tree with the dmix plugin. Appearently, you're confused,
> because the dmix uses some tricks to let things working.
>
> Jaroslav
>
> -----
> Jaroslav Kysela <perex@suse.cz>
> Linux Kernel Sound Maintainer
> ALSA Project, SuSE Labs
>
>
You are correct, my application does in fact get correct "delay" values,
but the /proc/asound/card0/pcm0p/sub0/status does not show these when
using dmix.
The sound output from my application is very broken up when using
"dmix", but sounds fine when using "front".
The break up sounds like one period sound, one period mute, one period
sound, one period mute.
It must be something in my application, because aplay does not break up.
I suspect it is my application trying to do xrun recovery or something
like that, but dmix runs freewheel even on xruns, so I might have to
change some of my code. My reasoning behind this, is that with "front",
I can do xrun recovery by stopping and then restarting the pcm, so the
recovery is very quick, but with dmix, I have to wait a whole period
before sound output starts again.
Cheers
James
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2003-09-18 16:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-17 18:33 status pointer's problem with dmix James Courtier-Dutton
2003-09-17 18:52 ` Takashi Iwai
2003-09-17 19:01 ` James Courtier-Dutton
2003-09-17 19:10 ` Takashi Iwai
2003-09-17 20:46 ` James Courtier-Dutton
2003-09-18 8:28 ` Takashi Iwai
2003-09-19 2:17 ` AthlonRob
2003-09-20 11:07 ` Clemens Ladisch
2003-09-21 11:43 ` Jaroslav Kysela
2003-09-21 17:06 ` AthlonRob
2003-09-27 21:13 ` AthlonRob
2003-09-18 9:50 ` Jaroslav Kysela
2003-09-18 12:48 ` James Courtier-Dutton
2003-09-18 13:03 ` Jaroslav Kysela
2003-09-18 16:20 ` James Courtier-Dutton [this message]
2003-09-18 17:28 ` Jaroslav Kysela
2003-09-18 14:10 ` Paul Davis
2003-09-18 15:02 ` Jaroslav Kysela
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=3F69DB4C.8070401@superbug.demon.co.uk \
--to=james@superbug.demon.co.uk \
--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.