From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: "Dr. Mark Bugeja MD" Newsgroups: gmane.comp.audio.sox Subject: Re: Fwd: Re: Fwd: Re: merging mono files Date: Thu, 15 Dec 2016 17:46:01 +0100 Message-ID: References: <3e4b090a-ae51-e069-f6b9-1cd35c23f8a1@gmail.com> <4f577dcd268dff595974e1abe01d0afc@wingsandbeaks.org.uk> <6cbd02d9-9ff4-d93d-05d9-207c4c0df815@gmail.com> <8ce44c8d-f0a9-b243-3b49-1043fcf7f95c@gmail.com> Reply-To: sox-users@lists.sourceforge.net NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6491141163899866553==" X-Trace: blaine.gmane.org 1481820392 29336 195.159.176.226 (15 Dec 2016 16:46:32 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 15 Dec 2016 16:46:32 +0000 (UTC) User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 To: sox-users@lists.sourceforge.net Original-X-From: sox-users-bounces@lists.sourceforge.net Thu Dec 15 17:46:23 2016 Return-path: Envelope-to: gcas-sox-users@gmane.org Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.51 as permitted sender) client-ip=74.125.82.51; envelope-from=marcusfb@gmail.com; helo=mail-wm0-f51.google.com; X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to; bh=OId+J8sYo8fzhFCM6G8DefZl8TKtaVvxzlluuPcDDwk=; b=TVTXeUZstP+MpRP/OFOq49VIf1TGbi9ktgi96qflk3o8g5Em5FtwOdTr4iIoC237Xx SFYRVx4QswVd6EpU9o/hT9ejrZHNPhKHMpe/soERcaD4YydM2w52NhDcrTQIFoWhz0Oj FAzqBNZxp74SX6Zbl/GPWqyjOLAA/F0Go0gIrQJCR9S9+VAsZ8Wlv6kzqzI1YDygnG1t 9ZFnwEULAcLVdfrQBZdwwy9qgVWITaU0RVRzIMjkF980pHX2DaqWCugyIci35Q+RfV5i tsYVkKLIdTRdNwKssXRHCNiarOUQWY4w4Fv5ZGXO0pmLBdWjpqcwTQkm7BH6CrToh+XH 82hg== X-Gm-Message-State: AIkVDXJIC5T/LuFo/0kDUD38bIUz1c87/wA9JuuljrPh8Q2N7BtO+fcsvp7gLHY2KAjkgQ== X-Received: by 10.28.147.81 with SMTP id v78mr2438025wmd.60.1481820367566; Thu, 15 Dec 2016 08:46:07 -0800 (PST) In-Reply-To: <8ce44c8d-f0a9-b243-3b49-1043fcf7f95c@gmail.com> X-Antivirus: avast! (VPS 161215-0, 15/12/2016), Outbound message X-Antivirus-Status: Clean X-Headers-End: 1cHZAb-0005Xz-Uj X-BeenThere: sox-users@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: sox-users-bounces@lists.sourceforge.net Xref: news.gmane.org gmane.comp.audio.sox:6463 Archived-At: Received: from lists.sourceforge.net ([216.34.181.88]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cHZAk-0006L0-Nk for gcas-sox-users@gmane.org; Thu, 15 Dec 2016 17:46:23 +0100 Received: from localhost ([127.0.0.1] helo=sfs-ml-3.v29.ch3.sourceforge.com) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1cHZAf-0000Hf-3a; Thu, 15 Dec 2016 16:46:17 +0000 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1cHZAd-0000HI-Ek for sox-users@lists.sourceforge.net; Thu, 15 Dec 2016 16:46:15 +0000 Received: from mail-wm0-f51.google.com ([74.125.82.51]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.76) id 1cHZAb-0005Xz-Uj for sox-users@lists.sourceforge.net; Thu, 15 Dec 2016 16:46:15 +0000 Received: by mail-wm0-f51.google.com with SMTP id g23so172933231wme.1 for ; Thu, 15 Dec 2016 08:46:13 -0800 (PST) Received: from [127.0.0.1] ([195.158.99.83]) by smtp.gmail.com with ESMTPSA id bj1sm2823916wjc.17.2016.12.15.08.46.05 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 15 Dec 2016 08:46:06 -0800 (PST) This is a multi-part message in MIME format. --===============6491141163899866553== Content-Type: multipart/alternative; boundary="------------ADD451E7346C814C4ED39DA8" This is a multi-part message in MIME format. --------------ADD451E7346C814C4ED39DA8 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit It seems like what I did didn't work although I'm still waiting for a reply from my friend. I am looking for converters hoping to strike gold but instead I seem to find myself sinking deeper and deeper in thick mud. For instance.... there is this online converter. Ok. Select bit-resolution, done; sampling rate, done; audio channels, done. Then... show advanced options, PCM format: and a horrible list with such things as little-endian and big-endian crops up. What the.......! What are these? A new race? Aliens from outer space? http://audio.online-convert.com/convert-to-wav Mark On 15/12/2016 15:20, Dr. Mark Bugeja MD wrote: > > I don't recall exactly what I sent to this forum though I may have > sent only the main file because I suspect this was at fault. I sent my > GO colleague a whole batch of files including the releases I later > suspected to be the real issue and he confirmed they were. I now used > Sony's Soundforge to batch process one set of release files and sent > him a specimen to check if the issue has indeed been addressed by what > I did. > > How these files turned out so different I have no idea and the person > who would have been able to answer the question is no longer with us > to do so. So we've got to sort out what he left behind the best way > possible. If the batch process I chose ie bit-depth converter, > selecting 24 bit instead of the default 32 that shows up on the > window, works fine then the matter is solved and another lesson learnt. > > For all its worth, this is the link to sample problem file (one of the > releases that is being implicated and yet to be corrected): > > https://mega.nz/#!pNAUmAgD!I0sh9C29SpFF7iMnf-0P4FvkfhQdqyawK5a0XMxf3DI > > Regards > > Mark > > > On 15/12/2016 12:31, Jeremy Nicoll - ml sox users wrote: >> On 2016-12-15 10:18, Dr. Mark Bugeja MD wrote: >>> Hi, I have asked a GrandOrgue guru who has helped many times in the >>> past and himself a sampleset creator. I sent him my main files and >>> releases and he discovered that the issue lies in the fact with the >>> releases, in that, for some strange mysterious reason, are saved as >>> "Wave_ Format_Extensible (Wavex)" whilst the main files are in >>> "Wave_Format_PCM". The latter is the correct format. This is the first >>> time I ever came across this. I am still waiting for a reply as to how >>> he managed to extract this information! >>> >>> Now for the next step: it's not so much understanding what Wavex is >>> but what software sports and supports this feature. All software I >>> have used so far identify one type of wav format only. No choice. No >>> options to select other than other formats like aiff, aa3, ac3, vox, >>> wma, wmv, mp3, flac, ogg, etc etc! >> The .wav file format is what, in computing, is known as a 'container' >> file. There are many types of data that can appear inside one, defined >> by the initial few bytes in the header of the file. For a simple WAVE >> file there's just the header then the audio data, but - I believe - more >> complicated files can have non-audio data interleaved with audio data >> throughout the file. Each section of audio or other data is introduced >> by something saying what follows, so programs can skip over the parts >> they do not understand. >> >> For example, a Broadcast Wave file also has extension .wav, but contains >> extra non-audio data required by the BBC, EBU and so on. >> >> >> Sox does support reading and creation of files whose names end in .wav >> but have (as the sox manual says) non-standard internal headers; there >> are extra parameters for sox commands that will allow us to tell it what >> form an input file has and what form the output file needs to have. >> >> I'm curious though why soxi did not identify the difference. Maybe it's >> not aware of the difference, or, the example files you've looked at with >> soxi weren't different. Did you send to the guru the same files as >> those >> that you've been issuing commands against? >> >> Also, if this is the problem, what you wrote implies that the funny >> format >> is only for release files... which would imply that the sox merge of the >> main files should have worked. Did they? >> >> > --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus --------------ADD451E7346C814C4ED39DA8 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: 7bit

It seems like what I did didn't work although I'm still waiting for a reply from my friend.

I am looking for converters hoping to strike gold but instead I seem to find myself sinking deeper and deeper in thick mud.

For instance.... there is this online converter. Ok. Select bit-resolution, done; sampling rate, done; audio channels, done. Then... show advanced options, PCM format: and a horrible list with such things as little-endian and big-endian crops up. What the.......! What are these? A new race? Aliens from outer space?

http://audio.online-convert.com/convert-to-wav

Mark


On 15/12/2016 15:20, Dr. Mark Bugeja MD wrote:

I don't recall exactly what I sent to this forum though I may have sent only the main file because I suspect this was at fault. I sent my GO colleague a whole batch of files including the releases I later suspected to be the real issue and he confirmed they were. I now used Sony's Soundforge to batch process one set of release files and sent him a specimen to check if the issue has indeed been addressed by what I did.

How these files turned out so different I have no idea and the person who would have been able to answer the question is no longer with us to do so. So we've got to sort out what he left behind the best way possible. If the batch process I chose ie bit-depth converter, selecting 24 bit instead of the default 32 that shows up on the window, works fine then the matter is solved and another lesson learnt.

For all its worth, this is the link to sample problem file (one of the releases that is being implicated and yet to be corrected):

https://mega.nz/#!pNAUmAgD!I0sh9C29SpFF7iMnf-0P4FvkfhQdqyawK5a0XMxf3DI

Regards

Mark


On 15/12/2016 12:31, Jeremy Nicoll - ml sox users wrote:
On 2016-12-15 10:18, Dr. Mark Bugeja MD wrote:

Hi, I have asked a GrandOrgue guru who has helped many times in the
past and himself a sampleset creator. I sent him my main files and
releases and he discovered that the issue lies in the fact with the
releases, in that, for some strange mysterious reason, are saved as
"Wave_ Format_Extensible (Wavex)" whilst the main files are in
"Wave_Format_PCM". The latter is the correct format. This is the first
time I ever came across this. I am still waiting for a reply as to how
he managed to extract this information!

Now for the next step: it's not so much understanding what Wavex is
but what software sports and supports this feature. All software I
have used so far identify one type of wav format only. No choice. No
options to select other than other formats like aiff, aa3, ac3, vox,
wma, wmv, mp3, flac, ogg, etc etc!

The .wav file format is what, in computing, is known as a 'container'
file.  There are many types of data that can appear inside one, defined
by the initial few bytes in the header of the file.  For a simple WAVE
file there's just the header then the audio data, but - I believe - more
complicated files can have non-audio data interleaved with audio data
throughout the file.  Each section of audio or other data is introduced
by something saying what follows, so programs can skip over the parts
they do not understand.

For example, a Broadcast Wave file also has extension .wav, but contains
extra non-audio data required by the BBC, EBU and so on.


Sox does support reading and creation of files whose names end in .wav
but have (as the sox manual says) non-standard internal headers; there
are extra parameters for sox commands that will allow us to tell it what
form an input file has and what form the output file needs to have.

I'm curious though why soxi did not identify the difference.  Maybe it's
not aware of the difference, or, the example files you've looked at with
soxi weren't different.  Did you send to the guru the same files as 
those
that you've been issuing commands against?

Also, if this is the problem, what you wrote implies that the funny 
format
is only for release files... which would imply that the sox merge of the
main files should have worked.  Did they?




Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com


--------------ADD451E7346C814C4ED39DA8-- --===============6491141163899866553== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot --===============6491141163899866553== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Sox-users mailing list Sox-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sox-users --===============6491141163899866553==--