From: Jan Stary <hans@stare.cz>
To: sox-users@lists.sourceforge.net
Subject: Re: Fwd: Re: merging mono files
Date: Sat, 10 Dec 2016 22:53:00 +0100 [thread overview]
Message-ID: <20161210215259.GB98254@www.stare.cz> (raw)
In-Reply-To: <6533c36b-631b-cc83-0980-17bed81ee74c@gmail.com>
On Dec 10 11:18:05, marcusfb@gmail.com wrote:
> Hi all,
>
> What you are saying is right. I did find one pair of files that have
> different lengths of audio. This surprised me somewhat. Generally, the files
> are identical in length and carry the loop marks in exactly the same place.
>
> Irrespective of any differences, I would still like to merge all the pairs
> of files into stereo. It should not be such a difficult task recreating
> loops again and inserting pitch tuning data. LoopAuditioneer does all that
> quite fast and what is left is to check that the loops do not present
> clicks.... again.... I can do pretty well and efficiently having done the
> job so often.
>
> So, forget loops and marks and other data as the issue is complicating
> itself unnecessarily.
It seems to me that this is the gist of your problem.
Merging the mono files int ocorresponding stereo files
is a triviality. Losing the loops and marks means
you will _not_ have what you want anyway.
Do you intend to process each and every of the 2000 resulting
files manually in LoopAuditioner to recreate the loops?
------------------------------------------------------------------------------
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
next prev parent reply other threads:[~2016-12-10 21:53 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a4f1ff10-c573-a233-916f-3f92c66bf9ce@gmail.com>
2016-12-08 13:36 ` Fwd: Re: merging mono files Dr. Mark Bugeja MD
2016-12-09 13:51 ` Jan Stary
2016-12-09 14:10 ` Dr. Mark Bugeja MD
2016-12-09 17:48 ` Erich Eckner
2016-12-09 18:58 ` Dr. Mark Bugeja MD
2016-12-09 22:55 ` Jan Stary
2016-12-10 6:42 ` Dr. Mark Bugeja MD
2016-12-10 21:49 ` Jan Stary
2016-12-09 23:41 ` Jeremy Nicoll - ml sox users
2016-12-10 6:44 ` Dr. Mark Bugeja MD
2016-12-10 9:23 ` Jeremy Nicoll - ml sox users
2016-12-10 10:18 ` Dr. Mark Bugeja MD
2016-12-10 21:53 ` Jan Stary [this message]
2016-12-10 22:28 ` Dr. Mark Bugeja MD
2016-12-11 6:43 ` Erich Eckner
2016-12-11 7:44 ` Kevin Conder
2016-12-11 8:59 ` Jeremy Nicoll - ml sox users
2016-12-11 9:38 ` Dr. Mark Bugeja MD
2016-12-11 10:31 ` Erich Eckner
2016-12-11 11:16 ` Jeremy Nicoll - ml sox users
2016-12-11 20:39 ` Dr. Mark Bugeja MD
2016-12-11 21:48 ` Jeremy Nicoll - ml sox users
2016-12-12 10:41 ` Dr. Mark Bugeja MD
2016-12-12 12:12 ` Dr. Mark Bugeja MD
2016-12-12 18:00 ` Jeremy Nicoll - ml sox users
2016-12-12 18:15 ` Dr. Mark Bugeja MD
2016-12-12 18:51 ` Jeremy Nicoll - ml sox users
2016-12-12 17:46 ` Jeremy Nicoll - ml sox users
2016-12-12 11:31 ` Dr. Mark Bugeja MD
2016-12-12 18:06 ` Jeremy Nicoll - ml sox users
2016-12-12 18:35 ` Dr. Mark Bugeja MD
2016-12-12 19:02 ` Jeremy Nicoll - ml sox users
2016-12-12 20:06 ` Dr. Mark Bugeja MD
2016-12-11 19:08 ` 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=20161210215259.GB98254@www.stare.cz \
--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).