sox-users@lists.sourceforge.net unofficial mirror
 help / color / mirror / code / Atom feed
From: "Dr. Mark Bugeja MD" <marcusfb@gmail.com>
To: sox-users@lists.sourceforge.net
Subject: Re: merging mono files
Date: Thu, 8 Dec 2016 21:37:02 +0100	[thread overview]
Message-ID: <16188a83-dfaf-a400-7333-43cb29a8982a@gmail.com> (raw)
In-Reply-To: <5849BB51.9030200@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 3567 bytes --]

I cannot give any more information on where the loops and markers are. 
They are created using audio software.

It does not matter if SoX would not include features like these. I 
thought I'd make my perfectly legitimate request.... I tried.

I'll just have to be patient and do the job manually.

Thanks everyone for your interaction in trying to solve my difficulty. 
SoX was recommended to me by a friend with whom I create samplesets. I 
took up that recommendation but clearly this is not the software I need,

Apologies for any inconvenience caused. 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.

Best wishes to all,

Mark


On 08/12/2016 20:58, fmiser wrote:
>>>> Dr. Mark Bugeja wrote:
>>>>
>>>> If Sox does not preserve loops and cues yet.... then please
>>>> add that to the wish list. It would be very handy for several
>>>> people doing serious digital sound processing. :-)
> Keep in mind, SoX is used by a lot of us for a lot of
> different tasks.  The one task you are wanting to us it for
> (joint two mono files into a stereo file) is a very tiny piece
> of what SoX can do.
>>>   Peter wrote:
>>>
>>> I was thinking about the problem of markers in the file
>>> headers when mixing files together, as Dr. Mark is trying to
>>> do. What if the markers in the left channel and the right
>>> channel are not completely identical? I think this is a more
>>> complicated task than just copying input file markers to the
>>> output file when mixing.
>> Dr. wrote:
>> They are *identical*...
> In _your_ case, they are identical.  But a SoX effect or
> function can't be added just for _your_ case.  At least, not
> if it doesn't behave well for other cases.
>
>> ... and most probably created
> So what should SoX do if it happens to be something other than
> "most probably"?  SoX is good partly because it does work so
> predictably even when doing odd or unusual things.
>> The separation must have been done after to accommodate
>> for Hauptwerk software's special features.
> Again - in your case.  There is no guarantee, or even a high
> probability,  that other people and other files would be the
> same situation.
>
> Something like "preserving loops and cues" has the potential for
> being tricky for the reasons Peter wrote.  Then, as Jeremy pointed
> out, they may be in a sidecar file and not in the audio file
> itself.
>
> Have you tested the stereo file you made using SoX?  Are the
> markers intact?  If so, your situation is resolved.  If not -
> maybe there is a way to copy the info from one of the mono
> files to the stereo file.
>
> But so far, I haven't seen from you what these "loops and
> cues" are.  You described how you use them - but is it in the
> header?  If so, where?  If not the header, then where is it?
> Is it in a sidecar file like Jeremy described?
>
>
> ------------------------------------------------------------------------------
> 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
>



---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

[-- Attachment #1.2: Type: text/html, Size: 5841 bytes --]

[-- Attachment #2: Type: text/plain, Size: 322 bytes --]

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

[-- Attachment #3: Type: text/plain, Size: 158 bytes --]

_______________________________________________
Sox-users mailing list
Sox-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-users

  reply	other threads:[~2016-12-08 20:37 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 [this message]
2016-12-08 22:23                       ` Jeremy Nicoll - ml sox users
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=16188a83-dfaf-a400-7333-43cb29a8982a@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).