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

["Dr. Mark Bugeja MD" <marcusfb@gmail.com>]

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

Hi,

I can only test the files in GrandOrgue when I build the organ in 
question. I cannot test individual files on the software. I did check 
files with iZotope and they look good visually, sound well when played, 
they are in 24 bit and 48kHz sample rate, they load up on 
LoopAuditioneer so I could add pitch information and loops.

The only other software that issued a warning was Sony's Soundforge... 
though I can't get this warning again for some reason. What I am 
noticing just now is that Soundforge gives a detail (property) when 
opening up a file, something that I did not observe before, not that it 
means anything to me:

  * Rgns/Play/Cmd: No/No/No

A file that is known to work with GrandOrgue gives _*
*_

  * Rgns/Play/Cmd:_*Yes*_/No/No.

Could my answer lie with this difference?

I'll try running the script as you recommended and generate the "logs".

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

[-- Attachment #1.2: Type: text/html, Size: 4630 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