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: merging mono files
Date: Thu, 08 Dec 2016 22:23:55 +0000	[thread overview]
Message-ID: <0a0b8a7433b23f52d85880e703bd0fec@wingsandbeaks.org.uk> (raw)
In-Reply-To: <16188a83-dfaf-a400-7333-43cb29a8982a@gmail.com>

On 2016-12-08 20:37, Dr. Mark Bugeja MD wrote:
> I cannot give any more information on where the loops and markers are.
> They are created using audio software.

Well, what software?


> Apologies for any inconvenience caused.

I'm sure no-one thinks you've caused any inconvenience.  We're all here
because we want to process audio files, and like the approach that sox
offers.

In my case, I use sox for things because it's easy to keep notes 
describing
what sox command I used to do something or other, whereas documenting 
how I
may have used a GUI-based application is far more difficult.  And, I 
worked
as a computer programmer so have little difficulty using sox (& other 
tools)
to find things out about portions of a set of audio files, and then use 
my
own programs to generate sox commands to manipulate those files.


> At least I got as far as
> merging two files using a bat process. Re-creating loops and markers
> and checking each is as much of a task as the process at hand so might
> as well just get on with it.

Does the audio tool within which you created these markers offer any 
options
for exporting marker definitions separate from audio data?


-- 
Jeremy Nicoll - my opinions are my own

------------------------------------------------------------------------------
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-12-08 22:24 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <f8656c10-854d-2f07-72bc-0b5016a5401b@gmail.com>
2016-12-07 19:52 ` merging mono files Dr. Mark Bugeja MD
2016-12-07 21:07   ` Peter P.
2016-12-07 21:07     ` Dr. Mark Bugeja MD
2016-12-08  0:07       ` Peter P.
2016-12-08  0:09         ` Peter P.
2016-12-08  0:34           ` Dr. Mark Bugeja MD
2016-12-08  1:01             ` Jeremy Nicoll - ml sox users
2016-12-08  1:36               ` Dr. Mark Bugeja MD
2016-12-08  7:06                 ` Jan Stary
2016-12-07 22:27     ` Dr. Mark Bugeja MD
2016-12-07 23:05       ` Jeremy Nicoll - ml sox users
2016-12-08  0:28         ` Dr. Mark Bugeja MD
2016-12-08  7:12         ` Jan Stary
2016-12-08 10:46           ` Jeremy Nicoll - ml sox users
2016-12-08 10:58             ` Dr. Mark Bugeja MD
2016-12-08 11:45               ` Peter P.
2016-12-08 12:06                 ` Erich Eckner
2016-12-08 13:19                 ` Dr. Mark Bugeja MD
2016-12-08 19:58                   ` fmiser
2016-12-08 20:37                     ` Dr. Mark Bugeja MD
2016-12-08 22:23                       ` Jeremy Nicoll - ml sox users [this message]
2016-12-08 23:23                         ` Dr. Mark Bugeja MD
2016-12-09  5:43                           ` Jeremy Nicoll - ml sox users
2016-12-09 12:37                             ` Dr. Mark Bugeja MD
2016-12-09 19:46                               ` Jeremy Nicoll - ml sox users
2016-12-09 20:50                                 ` Dr. Mark Bugeja MD
2016-12-09 13:21                           ` Jan Stary
2016-12-09 13:59                             ` Dr. Mark Bugeja MD
2016-12-09  9:08                       ` fmiser
2016-12-09 11:08                         ` René Bastian
2016-12-09 12:33                         ` Dr. Mark Bugeja MD
2016-12-09 13:36                           ` Jan Stary
2016-12-09 14:03                             ` Dr. Mark Bugeja MD
2016-12-09 12:41                         ` Dr. Mark Bugeja MD
2016-12-09 13:27                         ` Jan Stary
2016-12-09 13:17                       ` Jan Stary
2016-12-09 13:44                         ` Dr. Mark Bugeja MD
2016-12-09 22:48                           ` Jan Stary
2016-12-09 13:02                 ` Jan Stary
2016-12-09 13:38                   ` Jan Stary
2016-12-10  1:21             ` Jeremy Nicoll - ml sox users
2016-12-08 11:00           ` Dr. Mark Bugeja MD
2016-12-08 11:42             ` Peter P.
2016-12-08 13:16               ` Dr. Mark Bugeja MD
2016-12-08 13:47                 ` Doug Lee
2016-12-09 12:49                   ` Dr. Mark Bugeja MD
2016-12-09 13:39                 ` Jan Stary
2016-12-09 14:05                   ` Dr. Mark Bugeja MD
2016-12-08 12:28             ` Jeremy Nicoll - ml sox users
2016-12-08 13:43               ` Dr. Mark Bugeja MD
2016-12-09 13:40               ` Jan Stary
2016-12-09 14:06                 ` Dr. Mark Bugeja MD
2016-12-08  2:15   ` Kevin Conder
2016-12-08  4:29     ` Dr. Mark Bugeja MD
2016-12-08  4:34     ` Dr. Mark Bugeja MD

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=0a0b8a7433b23f52d85880e703bd0fec@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).