That sounds like what I hear from the online-converted PCM file.
That is where you are going wrong. That makes FFmpeg think it’s a native G.729 file not wrapped in WAV. The output sounds exactly like the output I get from running your 80088.wav through my G.729 decoder, then importing its PCM raw output into Audacity using Import Raw Data.
Now I’ll be damned. That works!
I still can’t quite understand how but it actually works!
It’s not exactly how I wanted it to work (just load the file into audacity and be fine with it) but having it run on ffmpeg prior to editing under audacity is perfectly acceptable, given the singularities of these files.
Now…why does it work this way? I am basically telling ffmpeg that it’s a WAV file but in fact it is a G.729 file.
Here’s the output of ffmpeg 3.3.1:
“-i 80088.wav” just gives FFmpeg the input file name. It does not tell FFmpeg anything about what audio format is in the WAV. Later FFmpeg can figure that out for G.729 wrapped in WAV. Older FFmpeg can’t, even though it supports decoding of proper G.729 files.
As we have said, you can run Audacity on Linux in a virtual machine. If you get for example Ubuntu 16.04 you may not have to compile Audacity - the Ubuntu-supplied version of Audacity may have a late enough version of FFmpeg built in so that it recognises your G.729 embedded in a WAV file.
Can we close this topic now? Steve and I have spent hours supporting you on this. Would you like to make a donation to Audacity http://www.audacityteam.org/donate/?
Just to confirm, on Windows 10, FFmpeg 2.2.2 cannot read the file. The most recent nightly, ffmpeg-20170601, from the command line, can convert the file.
The command I used, from the location of ffmpeg.exe
./ffmpeg.exe -i "input file" "output file"
Where “input file” and “output file” were fully qualified file names and “output file” had a file extension “.wav”