Re: Fwd: Re: Fwd: Re: merging mono files

Would it help to provide 2 samples, one from an instrument known to work 
and another, a file merged with the script? I have no idea how to 
compare them other than opening them up in a software like soundforge 
and seeing what the properties of each show? It seems there is some kind 
of information within these files (?header) that is relied upon by 
GrandOrgue and needs to be somehow corrected. Otherwise the merged files 
are what they ought to be - stereo, 24bit and 48kHz.

If this can help before I go through with anything else then here is the 
link:

https://mega.nz/#!IZQwFByQ!oZCDk6Qh_xSq_DvC3mKBJCVRO726cvAFCULMHWFNhNY

The files are clearly labelled as to which is which.

If there is something in them, can it be corrected manually or (less 
preferably) by re-doing the merger using a modified script to preserve 
as much of the properties of the original (source) files?

Mark

______________________________________________
On 14/12/2016 00:48, Jeremy Nicoll - ml sox users wrote:
> On 2016-12-13 18:39, Dr. Mark Bugeja MD wrote:
>> I have tested the wav samples. They won't load in the software
>> GrandOrgue and give a PCM format error. Could this have something to
>> do with the merging process we have just done?
> Who knows?
>
> I had the impression you earlier tested a merge and decided the
> resulting file
> was ok (either it sounded ok, or it looked ok in some other program)?
> Was that
> so?
>
> If so, do the files merged by the script also sound ok to you, or look
> ok, doing
> whatever it was that you did before to check a file?
>
>
>
> Take one example (ie a left file, a right file and file that was merged
> from them),
> and for each of those files issue in a command window this command
> (though use the
> paths that make sense on your computer):
>
>    "C:\path\to\sox\soxi.exe" "C:\path\to\audio-files\some.wav"
>
> Note that this runs "soxi.exe" not "sox.exe".  Make sure that you have a
> soxi.exe
> (in the same place as you have sox.exe).
>
> Paste the command you issued and whatever the result was, for each file,
> in your
> next reply.
>
> Also issue, for each file, this command:
>
>    "C:\path\to\sox\sox.exe" "C:\path\to\audio-files\some.wav" -n stat
> stats
>
> and paste those commands and results into your reply too.  Note that
> this command
> called 'sox' not 'soxi', and the 'stat stats' part runs two separate
> effects which
> will list details about the audio data in the file concerned.
>
>
> So, that's three separate commands to be issued, against three separate
> files.
> Hopefully something in the details the three commands list will give
> someone here a
> clue as to what might be wrong.
>
>
> Do you remember earlier in the discussion someone pointed out that,
> really, scripts
> should check things?  The script you've been running checks nothing.
>



---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

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

_______________________________________________
Sox-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sox-users