sox-users@lists.sourceforge.net unofficial mirror
 help / color / mirror / code / Atom feed
From: fmiser <fmiser@gmail.com>
To: sox-users@lists.sourceforge.net
Subject: Re: too many open files
Date: Thu, 10 Nov 2016 00:01:18 +0000	[thread overview]
Message-ID: <5823B8CE.3020904@gmail.com> (raw)
In-Reply-To: <20161109095014.5gelkcfhnjmnjy5t@fastmail.com>

> Peter wrote:

> sox FAIL formats: can’t open input file ‘whatever.wav’ : Too
> many open files

> I tried to work around this by recursively concatenating each
> input file to a common (growing) output file using a simple bash
> until loop. The performance penalty of this is enormous, as the
> same output file has to be opened, read and written each time
> again.
>
> I am curious what a possible workaround could be, other than
> dividing above task between multiple calls of sox, each with a
> reduced number of files.

I can't help with the SoX source.  But what I would try first if I
were facing that problem is to concatenate in bunches.

For example, take the first 1000 and concatenate them into 01.wav,
then the second 1000 into 02.wav, then finally concatenate 01.wav,
02.wav, etc.

Maybe put the initial groupings into subdirectories to be sure
each file is included only once.

$ mv -nv $(ls path/name/ | head -n 1000) subdir/


------------------------------------------------------------------------------
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
_______________________________________________
Sox-users mailing list
Sox-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-users

      parent reply	other threads:[~2016-11-10  0:02 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.
2016-11-16  9:38     ` Eric Wong
2016-11-09 11:18 ` Eric Wong
2016-11-10  0:01 ` fmiser [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=5823B8CE.3020904@gmail.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).