From: Vinod Koul <vinod.koul@intel.com>
To: Richard Fitzgerald <rf@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] tinycompress: add gapless meta data APIs
Date: Fri, 22 Feb 2013 23:45:00 +0530 [thread overview]
Message-ID: <20130222181500.GB23711@intel.com> (raw)
In-Reply-To: <20130222162410.GA21630@opensource.wolfsonmicro.com>
On Fri, Feb 22, 2013 at 04:24:10PM +0000, Richard Fitzgerald wrote:
> I'd prefer that we don't require that a next track has been set in order to be
> able to call a partial_drain. It would be awkward to implement in Android
> because the decision to append the next track to the end of the current stream
> and pass down metadata is made in a higher level of code than the part which
> handles issuing drain control and there's no actual synchronization between
> these two operations or knowledge in the lower (drain-handling) level of any
> notion of gapless playback.
>
> A partial drain just drains to the end of the current track... it doesn't really
> matter whether that happens to be the last track.
If you are in gapless mode (yes it may be last track), you can signal next track
and then call partial drain. But later if you find that if you are the last
track, you can call drain or stop.
Now why normal drain wont work... the reason being drain will return when
complete track is rendered, we don't want that here, so we drain partially to
allow DSP to switch to next track if required.
--
~Vinod
next prev parent reply other threads:[~2013-02-22 18:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 9:52 [PATCH] tinycompress: add gapless meta data APIs Vinod Koul
2013-02-22 16:24 ` Richard Fitzgerald
2013-02-22 18:15 ` Vinod Koul [this message]
2013-02-24 14:19 ` Vinod Koul
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=20130222181500.GB23711@intel.com \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=rf@opensource.wolfsonmicro.com \
/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).