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: Sox marker handling Was: Re: merging mono files
Date: Fri, 9 Dec 2016 15:20:14 +0100	[thread overview]
Message-ID: <f4c17334-1ce9-c3bb-64e1-c1c3e4392ff4@gmail.com> (raw)
In-Reply-To: <20161209140510.GM62092@www.stare.cz>


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

Yes. The person who was processing these files died 14 months ago so 
there is no way we can get the files he was working on. We're luck to 
have the rest of the instrument where most of the ranks are in combined 
stereo. It's just these few folders that were different but between them 
there are 4000+ mono files that must be processed to produce the 2000+ 
stereo files we need.

I must add that the mono samples are really stereo.... one channel 
having been deleted and therefore blank and saved as the other channel 
in a separate stereo file with the opposite channel being blank.


On 09/12/2016 15:05, Jan Stary wrote:
> On Dec 08 15:08:40, marcusfb@gmail.com wrote:
>> If loops are not identical they would be useless.
> Well, I can imagine instruments where the left and right channel
> behave differently even in respect to attack and release etc.
> Think Pat Metheny's Orchestrion and other weirdnesses?
>
> But this mostly points to how strange it is what you need to do:
> there was an original "stereo version" of what you have
> on your hands now, right?
>
> 	Jan
>
>
> ------------------------------------------------------------------------------
> 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: 3244 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-09 14:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-08 13:47 Sox marker handling Was: Re: merging mono files Peter P.
2016-12-08 13:59 ` Dr. Mark Bugeja MD
2016-12-08 14:45   ` RT
2016-12-08 17:56     ` Dr. Mark Bugeja MD
2016-12-08 22:30       ` Jeremy Nicoll - ml sox users
2016-12-09 14:01     ` Jan Stary
2016-12-09 13:58   ` Jan Stary
2016-12-09 14:14     ` Dr. Mark Bugeja MD
2016-12-09 15:38       ` Stuart Bruce
2016-12-09 16:06         ` Dr. Mark Bugeja MD
2016-12-09 17:01         ` Dr. Mark Bugeja MD
2016-12-08 14:08 ` Dr. Mark Bugeja MD
2016-12-09 14:05   ` Jan Stary
2016-12-09 14:20     ` Dr. Mark Bugeja MD [this message]
2016-12-09 13:56 ` Jan Stary
2016-12-09 14:53   ` Måns Rullgård

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=f4c17334-1ce9-c3bb-64e1-c1c3e4392ff4@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).