From: "Dr. Mark Bugeja MD" <marcusfb@gmail.com>
To: sox-users@lists.sourceforge.net
Subject: Re: merging mono files
Date: Fri, 9 Dec 2016 00:23:21 +0100 [thread overview]
Message-ID: <ef088e84-5f6a-30f2-4ce9-66f6613dc00f@gmail.com> (raw)
In-Reply-To: <0a0b8a7433b23f52d85880e703bd0fec@wingsandbeaks.org.uk>
[-- Attachment #1.1: Type: text/plain, Size: 4256 bytes --]
I have already alluded to the audio software I use, in previous posts.
However there is one other I have not mentioned.
I create markers using /*iZotope RX3 Advanced*/. It allows me also to
clean up samples from noise, cut pieces out, and do all sort of editing,
like eliminating artefacts, change frequency of a good sample to say
create missing/ unplayable or discordant notes when sampling a real
instrument like an old pipe organ.
Loops are then generated. I use /*L*//*oop*//*A*//*uditioneer*/
(https://sourceforge.net/projects/loopauditioneer/) created by Lars
Palo, a small but marvellous piece of software. It also sports other
features eg generating pitch information to wav files vital when
selecting to play the virtual instrument set to a different temperament
to that which it was created from.
Some software if used may not show the loops/ markers and if I recall
may even ignore and delete them upon saving any changes. I think, but I
may be wrong, Audacity would do that but /*Sony Soundforge*/ doesn't. I
stand to be corrected. I don't use Audacity that much.
Just for those who are interested, I have a website about my project in
creating digital samplesets of instruments from recorded samples of real
instruments:
* http://maltesepipeorgans.webs.com
One may listen to these virtual instruments, as they are played by
remote musicians in their homes, in my other website:
* http://maltesepipeorgans2.webs.com
I cannot add more than this since I am in no way technically minded to
be able to answer certain questions. I am capable of using some pieces
of software in so far as what I have been taught to do by others in the
know and, like a monkey, I just copy the steps I was shown to accomplish
specific, routine and repetitive tasks in the process of creating
digital wav files. Some processes are carried out by others eg noise
reduction which can prove quite challenging at times considering that
recording are made in churches where chairs are dragged across, doors
banged, people talk in the background, cars, buses, trucks and motor
bikes zooming past and hooting their horn in the busy streets outside,
church bells ringing half way through a session, birds chirping, etc etc
etc. Most frustrating. But the end results of hundreds or even thousands
of hours of hard work are the clear and crisp wav files that can do
justice to the instrument being replicated digitally.
The task I am now performing is basically reversing part of the process
that was done to these files after loops and markers were created....
that of recombining the L and R channels back into single stereo samples
preserving the processing done before the separation. Loops and markers
are created in positions that apply to both channels in a stereo file so
they are bound to match exactly when recombining them again.
Mark
On 08/12/2016 23:23, Jeremy Nicoll - ml sox users wrote:
> 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?
>
>
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
[-- Attachment #1.2: Type: text/html, Size: 6471 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
next prev parent reply other threads:[~2016-12-08 23:23 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
2016-12-08 23:23 ` Dr. Mark Bugeja MD [this message]
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=ef088e84-5f6a-30f2-4ce9-66f6613dc00f@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).