From: Vinod Koul <vinod.koul@intel.com>
To: Richard Fitzgerald <rf@opensource.wolfsonmicro.com>
Cc: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>,
patches@opensource.wolfsonmicro.com, alsa-devel@alsa-project.org
Subject: Re: [PATCH] crec: Add option to specify codec ID
Date: Fri, 18 Nov 2016 09:23:33 +0530 [thread overview]
Message-ID: <20161118035333.GG2698@localhost> (raw)
In-Reply-To: <1479308001.18450.25.camel@rf-debian.wolfsonmicro.main>
On Wed, Nov 16, 2016 at 02:53:21PM +0000, Richard Fitzgerald wrote:
> On Wed, 2016-11-16 at 13:48 +0000, Charles Keepax wrote:
> > On Wed, Nov 16, 2016 at 01:07:55PM +0000, Richard Fitzgerald wrote:
> > > On Wed, 2016-11-16 at 18:35 +0530, Vinod Koul wrote:
> > > > On Wed, Nov 16, 2016 at 11:44:09AM +0000, Richard Fitzgerald wrote:
> > > > > This patch adds a -I command line option to set the codec ID,
> > > > > either from a defined set of string values or as a number.
> > > >
> > > > Can you explain why you want to add this? The utility cant really record a
> > > > mp3 file!
> > >
> > > You need to be able to pass a codec ID that the driver supports, and to
> > > indicate which codec you're trying to use. It's not useful to only be
> > > able to open the "PCM" codec. It doesn't really matter whether crec
> > > understands the content of the data, we're just pulling raw data, most
> > > likely for test/debug.
> > >
> > > The wm_adsp driver on Wolfson/Cirrus codecs uses the new BESPOKE stream
> > > ID so we need a way to pass that. And we'd also need it for any drivers
> > > that had streams using other codec IDs.
Ah that was my guess too.
I am okay to be able to add bespoke format and use that to dump raw data.
But I am not okay to add codec formats which we dont support..
> > Is the objection here not that crec is wrapping the data with
> > a WAV file? Should we perhaps just expand this so that if you
> > request a different format it uses the raw data mode that it uses
> > when you let the output go to stdout.
> >
>
> Funny I thought we'd already added a flag for saving to the file raw.
> It's raw when you pipe it to stdout.
--
~Vinod
next prev parent reply other threads:[~2016-11-18 3:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 11:44 [PATCH] crec: Add option to specify codec ID Richard Fitzgerald
2016-11-16 13:05 ` Vinod Koul
2016-11-16 13:07 ` Richard Fitzgerald
2016-11-16 13:48 ` Charles Keepax
2016-11-16 14:53 ` Richard Fitzgerald
2016-11-18 3:53 ` Vinod Koul [this message]
2016-11-18 10:11 ` Richard Fitzgerald
2016-11-18 10:29 ` Vinod Koul
2016-11-18 14:39 ` Pierre-Louis Bossart
2016-11-18 16:17 ` Charles Keepax
2016-11-23 3:41 ` Vinod Koul
2016-11-23 10:21 ` Richard Fitzgerald
2016-11-23 10:38 ` Vinod Koul
2016-11-27 17:52 ` Pierre-Louis Bossart
2016-11-28 9:47 ` Richard Fitzgerald
2016-11-28 15:54 ` 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=20161118035333.GG2698@localhost \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=patches@opensource.wolfsonmicro.com \
--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).