sox-users@lists.sourceforge.net unofficial mirror
 help / color / mirror / code / Atom feed
From: "Peter P." <peterparker@fastmail.com>
To: sox-users@lists.sourceforge.net
Subject: Re: too many open files
Date: Fri, 11 Nov 2016 14:12:41 +0100	[thread overview]
Message-ID: <20161111131241.r46ao53w3nijql2g@fastmail.com> (raw)
In-Reply-To: <3f07afeb-9961-097f-dda5-f1e8947066aa@eckner.net>

* Erich Eckner <erich@eckner.net> [2016-11-09 11:20]:
> Hi Peter,
> 
> I would suggest to transform all files to a raw format (e.g. without
> header) - with identical sample rate, bit rate and number of channels -
> and concatenate them via bash and afterwards encode them in your desired
> format (e.g. wav). Like so:
> 
> for file in inputs/*.wav
> do
>   sox $file -t raw -
> done |
>   sox -t raw - output.wav
> 
> As mentioned, you might need to specify bit and sample rate and number
> of channels manually, though.

Thank you for this nice solution Erich, and thank you Eric for your
comments on ulimit. 

I managed to get things to work this way. Nevertheless Eric, if you have
a moment to peek into the code and see why sox is keeping files open, it
would be fantastic and could prevent similar questions coming up again.

In order to provide sox with the information necessary to write its
output file from raw data, I query the input file for its properties
using soxi or sox --i .I discovered that sox --i -e yields 
	Signed Integer PCM
while the -e flag for setting the encoding expects a different
wording (from manpage):
	signed-integer

I wonder if the encoding reported by soxi should be made identical to
the one required by sox in order to ease setting it in scripts?

Thank you both again,
best, Peter

------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi

  reply	other threads:[~2016-11-11 13:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-09  9:50 too many open files Peter P.
2016-11-09 10:02 ` Erich Eckner
2016-11-11 13:12   ` Peter P. [this message]
2016-11-16  9:38     ` Eric Wong
2016-11-09 11:18 ` Eric Wong
2016-11-10  0:01 ` fmiser

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=20161111131241.r46ao53w3nijql2g@fastmail.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).