From: Keith Chew <keith.chew@gmail.com>
To: alsa-devel@alsa-project.org
Subject: Re: PCM multi A/V Sync bug on SMP system
Date: Wed, 28 Apr 2010 07:28:59 +1200 [thread overview]
Message-ID: <m2z20f65d531004271228gc2ab0716na68845e9b262a839@mail.gmail.com> (raw)
In-Reply-To: <n2i20f65d531004242207zde83c421gac35d243420dcaff@mail.gmail.com>
>
> Please advise how can I track down this problem in code, happy to make
> changes and test.
>
After further investigation on the soucecode, it appears that the
default surround51 for the driver ca0106, uses "multi" to the 3
devices/outputs on the card. So "multi" does work fine on an SMP
system. The timing problems are only introduced when "multi" is
combined with "dmix" for 5.1 channels.
I would like to help out in fixing this, but need a little bit of
guidance from the experts here. Have I identified the problem
correctly? Ie interaction between "multi" and "dmix" on a 5.1 channel
card giving timing issues on an SMP system? If it is unlikely, I will
investigate other areas.
Regards
Keith
next prev parent reply other threads:[~2010-04-27 19:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-25 5:07 PCM multi A/V Sync bug on SMP system Keith Chew
2010-04-27 19:28 ` Keith Chew [this message]
2010-04-28 20:12 ` Keith Chew
2010-04-30 11:09 ` 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=m2z20f65d531004271228gc2ab0716na68845e9b262a839@mail.gmail.com \
--to=keith.chew@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).