#140 request for feature: handling file lists for input

closed
nobody
None
5
2009-07-29
2008-12-29
No

this is a suggested enhancement to sox.

i'd like to be able to provide, as a command line parameter, a file containing a file list to be operated on. for example, the command line syntax might be:

sox @book1ch2.lst chapter2.wav

where the file book1ch2.lst might contain:
disk1track05.wav
disk1track06.wav
disk1track07.wav
disk1track08.wav
disk1track09.wav

it would be intended that this join together the five files specified, in the order specified.

i'm assuming sox doesn't already have a feature to do this that i've missed!!

Discussion

  • robs

    robs - 2009-02-07

    This sort of functionality is usually provided by the `shell'. If you are using Windows, then you may want to look at `powershell' that comes with recent versions.

    Of course, with the particular example you've given, a simple shell wildcard '?' or '*' might be enough.

    HTH,
    Rob

     
  • robert rozee

    robert rozee - 2009-02-13

    the problem is that - in my specific application - i want to:
    (a) be able to specify the order that the files are to be operated on - somewhat important if joining together,
    (b) join together a very large number of files, a number whose total name lengths are likely to exceed the legal command line length under windows (the o/s i'm using),
    (c) NOT have to do multiple smaller join operations, so as to minimize multiple-handling of files. i'm needing to work with many hundreds of short files of only 2 or 3 minutes in length, that are assembled into large 'chapters' of up to an hour. as it is, an automated assembly operation of the collection is likely to take a great many hours.

    to fit in with the above, an addition to sox _seems_ to be the most effective solution.

     
  • robs

    robs - 2009-02-16

    Oops, should've thought of this earlier:
    try renaming book1ch2.lst to book1ch2.m3u then
    sox book1ch2.m3u chapter2.wav

     
  • robs

    robs - 2009-06-28
    • status: open --> pending
     
  • robs

    robs - 2009-06-28

    Assuming existing m3u support is adequate.

     
  • SourceForge Robot

    • status: pending --> closed
     
  • SourceForge Robot

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 30 days (the time period specified by
    the administrator of this Tracker).

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks