sox-users@lists.sourceforge.net unofficial mirror
 help / color / mirror / code / Atom feed
From: Jeremy Nicoll - ml sox users <jn.ml.sxu.88@wingsandbeaks.org.uk>
To: sox-users@lists.sourceforge.net
Subject: Re: concat problem
Date: Wed, 27 Sep 2017 12:38:33 +0100	[thread overview]
Message-ID: <3ba9f8b212c71e6df364cda41623d005@wingsandbeaks.org.uk> (raw)
In-Reply-To: <CAKS_MTuHo=swTBpATpU3e5TimjDcz=4KrKeEZZJGmBBNg0336w@mail.gmail.com>

On 2017-09-26 18:24, Glenn English wrote:
> On Sat, Sep 23, 2017 at 12:33 PM, Jan Stary <hans@stare.cz> wrote:
>> On Sep 22 16:36:39, ghe2001@gmail.com wrote:
>>> Debian Jessie, Supermicro box, SoX 14.4.1, SoX noob.
>> 
>> The current version is 14.4.2
> 
> Not on Debian Jessie it's not.
> 
>>> I ask SoX to concatenate AIFFs, and Mac Air stops at the end of first 
>>> file.
>>> I've written a Python script (first use of SoX)
>> 
>> If you are new to SoX, learn it by running SoX,
>> not by writing Python scripts.
> 
> In Python, you just create a list of the command and the options and
> stuff, and it's passed to the kernel.


The point is, if you post here asking for help with sox, but muddy the 
issue
by doing thing through pythin (or any other scripting language) no-one 
trying
to help you can be CERTAIN that the problem doesn't lie with your 
script.

If you issue the commands from a command prompt, anyone can exactly 
replicate
what you are doing (at least if we also had the source) and can rule out
scripts etc as a possible cause.


>> What happens if you play the file with SoX's own play(1)?
>> What does 'play --ignore-length output.aiff' do?
>> What does soxi(1) say about the file?
> 
> Dunno.

Why not?



>> What "subprocess"?
> 
> See Python dox. It's a class/module Python uses to interact with the 
> kernel.

If you're asking for help here telling us to read documentation for your 
scripting
language etc is not the way forward.

It'd be better if you spent time reading the sox documentation - so for 
example you
would then know about soxi.



-- 
Jeremy Nicoll - my opinions are my own

------------------------------------------------------------------------------
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

  reply	other threads:[~2017-09-27 11:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-22 16:36 concat problem Glenn English
2017-09-22 17:34 ` Eric Wong
2017-09-22 19:51   ` Glenn English
2017-09-23 12:33 ` Jan Stary
2017-09-23 20:39   ` Eric Wong
2017-09-26 17:24   ` Glenn English
2017-09-27 11:38     ` Jeremy Nicoll - ml sox users [this message]
     [not found]       ` <CAKS_MTsMDd+_1wt5UJYp0HEDPi8hy1oswUSNNEi=v2i+xMnEMw@mail.gmail.com>
2017-09-28 15:00         ` Glenn English
2017-09-27 14:42 ` Jan Stary

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=3ba9f8b212c71e6df364cda41623d005@wingsandbeaks.org.uk \
    --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).