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: Fwd: Re: Fwd: Re: merging mono files
Date: Thu, 15 Dec 2016 15:20:45 +0100	[thread overview]
Message-ID: <8ce44c8d-f0a9-b243-3b49-1043fcf7f95c@gmail.com> (raw)
In-Reply-To: <eef11f69478fdba50b4e903f7e4043e3@wingsandbeaks.org.uk>


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

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

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

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

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot

[-- 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-15 14:21 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <c5ed1e52-d9ed-f3e9-3295-05d2e00549b5@gmail.com>
2016-12-12 20:07 ` Fwd: Re: Fwd: Re: merging mono files Dr. Mark Bugeja MD
2016-12-13  1:40   ` Jeremy Nicoll - ml sox users
2016-12-13 18:39     ` Dr. Mark Bugeja MD
2016-12-13 23:48       ` Jeremy Nicoll - ml sox users
2016-12-14  7:22         ` Dr. Mark Bugeja MD
2016-12-14 12:40           ` Jeremy Nicoll - ml sox users
2016-12-14  9:50         ` Dr. Mark Bugeja MD
2016-12-14 12:44           ` Jeremy Nicoll - ml sox users
2016-12-15  9:31           ` Jeremy Nicoll - ml sox users
2016-12-15 10:18             ` Dr. Mark Bugeja MD
2016-12-15 11:31               ` Jeremy Nicoll - ml sox users
2016-12-15 14:20                 ` Dr. Mark Bugeja MD [this message]
2016-12-15 16:46                   ` Dr. Mark Bugeja MD
2016-12-15 17:42                     ` Jeremy Nicoll - ml sox users
2016-12-15 17:59                       ` Dr. Mark Bugeja MD
2016-12-16  2:47                       ` Dr. Mark Bugeja MD
2016-12-16  9:46                         ` Jeremy Nicoll - ml sox users
2016-12-16 10:31                           ` Dr. Mark Bugeja MD
2016-12-14 13:02         ` Dr. Mark Bugeja MD
2016-12-14 13:29           ` Jeremy Nicoll - ml sox users
2016-12-14 14:05             ` Dr. Mark Bugeja MD
2016-12-14 14:50               ` Jeremy Nicoll - ml sox users
2016-12-14 13:58         ` Dr. Mark Bugeja MD
2016-12-14 14:56           ` Jeremy Nicoll - ml sox users
2016-12-14 17:03             ` Dr. Mark Bugeja MD
2016-12-14 19:21               ` fmiser
2016-12-14 14:21         ` Dr. Mark Bugeja MD
2016-12-14 14:53           ` Jeremy Nicoll - ml sox users
2016-12-14 15:27             ` Dr. Mark Bugeja MD
2016-12-15  8:56               ` Jeremy Nicoll - ml sox users
2016-12-15  8:48           ` Jeremy Nicoll - ml sox users
2016-12-15  8:32       ` Jeremy Nicoll - ml sox users

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=8ce44c8d-f0a9-b243-3b49-1043fcf7f95c@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).