From: Vinod Koul <vkoul@kernel.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: Daniel Baluta <daniel.baluta@gmail.com>,
Takashi Iwai <tiwai@suse.de>, Patrick Lai <plai@codeaurora.org>,
alsa-devel@alsa-project.org,
Liam Girdwood <liam.r.girdwood@linux.intel.com>,
Curtis Malainey <cujomalainey@google.com>,
Mark Brown <broonie@kernel.org>
Subject: Re: [alsa-devel] [ANNOUNCE] 2019 Linux Audio miniconference
Date: Fri, 25 Oct 2019 15:15:16 +0530 [thread overview]
Message-ID: <20191025094516.GG2620@vkoul-mobl> (raw)
In-Reply-To: <36d84c86-50d0-487b-181a-9238e11d7fce@linux.intel.com>
On 24-10-19, 09:31, Pierre-Louis Bossart wrote:
> On 10/24/19 9:20 AM, Patrick Lai wrote:
> > On 10/22/19 11:59 AM, Mark Brown wrote:
> > > Hi,
> >
> > >
> > > As with previous years let's pull together an agenda through a mailing
> > > list discussion - if people could reply to this mail with any topics
> > > they'd like to discuss we can take it from there. Of course if we can
> > > sort things out more quickly via the mailing list that's even better!
> >
> > 1. Gapless playback handling between two playbacks with different format
>
> did you mean compressed formats?
Yes this is for compressed formats. So, we do not allow users to set
parameters for gapless playback as the assumption is that we are in
album with same parameters for the subsequent tracks to be played.
But in case of some codecs like wma (and flac iirc) there can be changes
to next track using different wma formats which warrants change in
params.
Question is if this should be allowed and if so we need to propose a
change in API for this
> > 2. Passing timestamp along with buffer for both playback and capture
> > 3. PCM device volume control
> > 4. Unified audio graph building across multiple subsystems
> >
> > Thanks
> > Patrick
> >
>
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
--
~Vinod
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2019-10-25 9:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 18:13 [alsa-devel] [ANNOUNCE] 2019 Linux Audio miniconference Mark Brown
2019-10-09 18:48 ` Daniel Baluta
2019-10-10 15:57 ` Mark Brown
2019-10-10 16:43 ` Pierre-Louis Bossart
2019-10-10 19:43 ` Daniel Baluta
2019-10-09 19:16 ` Pierre-Louis Bossart
2019-10-25 10:05 ` Vinod Koul
2019-10-14 19:47 ` Liam Girdwood
2019-10-14 20:16 ` Curtis Malainey
2019-10-15 20:11 ` Mark Brown
2019-10-15 20:11 ` Mark Brown
2019-10-22 18:59 ` Mark Brown
2019-10-23 9:20 ` Jerome Brunet
2019-10-23 16:53 ` Mark Brown
2019-10-24 14:20 ` Patrick Lai
2019-10-24 14:31 ` Pierre-Louis Bossart
2019-10-25 9:45 ` Vinod Koul [this message]
2019-10-25 14:27 ` Pierre-Louis Bossart
2019-10-25 17:26 ` Patrick Lai
2019-10-24 19:15 ` 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=20191025094516.GG2620@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=cujomalainey@google.com \
--cc=daniel.baluta@gmail.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=plai@codeaurora.org \
--cc=tiwai@suse.de \
/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