From: Raymond Yau <superquad.vortex2@gmail.com>
To: ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Re: [RFC 0/4] FIFO caused playback delay (latency) handling in soc
Date: Fri, 5 Mar 2010 09:19:00 +0800 [thread overview]
Message-ID: <4f3252891003041719h3c492e5mbde9f1c0a5a11705@mail.gmail.com> (raw)
>> Do soc support snd_pcm_rewind() and snd_pcm_forward ?
>>No driver demand yet, though it'd be trivially implemented if anyone
>>wanted to do it.
if size of fifo is around 1x ~ 3x fames
How accucate do those media player need to allow A/V lip sync ,
Video is about 24 ~ 30 frames per seconds and audio is 48000Hz ?
next reply other threads:[~2010-03-05 1:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-05 1:19 Raymond Yau [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-03-02 13:39 [RFC 0/4] FIFO caused playback delay (latency) handling in soc Peter Ujfalusi
2010-03-02 13:53 ` Mark Brown
2010-03-02 23:29 ` Raymond Yau
2010-03-03 10:03 ` Mark Brown
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=4f3252891003041719h3c492e5mbde9f1c0a5a11705@mail.gmail.com \
--to=superquad.vortex2@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).