From: "Måns Rullgård" <mans@mansr.com>
To: sox-users@lists.sourceforge.net
Subject: Re: specifying format of RAW files
Date: Fri, 10 Nov 2017 14:18:11 +0000 [thread overview]
Message-ID: <yw1xlgje5iak.fsf@mansr.com> (raw)
In-Reply-To: <yw1xvaii5iy7.fsf@mansr.com> ("Måns Rullgård"'s message of "Fri, 10 Nov 2017 14:04:00 +0000")
Måns Rullgård <mans@mansr.com> writes:
> Jan Stary <hans@stare.cz> writes:
>
>> When playing RAW audio files, the specified format seems to
>> only take effect for the first file. Subsequent files fail
>> to play because of unspecified rate etc.
>>
>> $ play -c 1 -r 48000 -e float -b 32 pcm1.raw # OK
>> $ play -c 1 -r 48000 -e float -b 32 pcm2.raw # OK
>> $ play -c 1 -r 48000 -e float -b 32 pcm*.raw
>> play FAIL formats: bad input format for file `pcm2.raw':
>> sampling rate was not specified
>>
>> Is this intended, or should the specified format be used
>> for the subsequent files as well?
>
> This is intentional. Format options apply to the following file only.
> Having them apply to a sequence of raw files could of course be useful,
> but I'm afraid this would require quite some work. Remember that these
> same options will also override parameters in the file headers.
Oh, and something like this should work in your case:
$ play $(printf '-c 1 -r 48000 -e float -b 32 %s ' pcm*.raw)
--
Måns Rullgård
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Sox-users mailing list
Sox-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-users
prev parent reply other threads:[~2017-11-10 14:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-10 13:30 specifying format of RAW files Jan Stary
2017-11-10 14:04 ` Måns Rullgård
2017-11-10 14:18 ` Måns Rullgård [this message]
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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.sourceforge.net/lists/listinfo/sox-users
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yw1xlgje5iak.fsf@mansr.com \
--to=sox-users@lists.sourceforge.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/sox.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).