Page 1 of 2

Possible bug - Exported wav file corrupt

Posted: Tue Aug 23, 2011 6:51 pm
by Sprinterdriver
System:
Audacity ® 1.3.13-beta (Unicode)
Windows XP sp3

I have a relatively simple project. It have two tracks.
Track one consist of ten times the same sound with some modification between the sounds.
track two is just one single sound.
Both tracks is 32 bit mono.

When exporting this to a single wav file, windows tells me that the file isn't a valid sound file. When open the same exported file in Audacity, it's mostly just noise with some elements from the sound tracks.

The project file seems to be fully functionally. I'll upload a 7z* file containing both project file's and the exported wav file.

Thanks


*7z is a compressed file just like zip files, but has much greater compression rate than zip (smaller file size).

Re: Possible bug - Exported wav file corrupt

Posted: Tue Aug 23, 2011 9:08 pm
by kozikowski
The only problem with New and Improved compression formats is that all the forum elves all over the earth have to be able to open them on all three computer platforms. That's why MP3 hung around since 1990.

Koz

Re: Possible bug - Exported wav file corrupt

Posted: Tue Aug 23, 2011 9:47 pm
by Sprinterdriver
kozikowski wrote:The only problem with New and Improved compression formats is that all the forum elves all over the earth have to be able to open them on all three computer platforms. That's why MP3 hung around since 1990.
MP3 format isn't part of this problem.

If you're talking about 7z, then most of todays file compression software packages support unpacking from 7z files. This include winrar, winzip and of course 7-zip too.

I would be thankful if you could test the files (if you get an faulty wav file when export) and give feedback on the actual problem instead of discussing file formats ;)

All input files where wav and so is the output file.

Re: Possible bug - Exported wav file corrupt

Posted: Tue Aug 23, 2011 10:13 pm
by Gale Andrews
Thanks for the files. I had 7-Zip but had to update it before I could open the 7z. Koz is on a Mac so likely can't even open the file. Please use zips in future, for the reason Koz states.

I can replicate the problem on Windows 7 and find I can export correctly after following either of these set of steps:
  • open the project, then remove either or both of the metadata tags
  • open the project, export then import that corrupted file (which still has the metadata)

Mixing and rendering the project before export or changing the project rate before export doesn't help, so I suspect there is something in those metadata tags (written by SoundForge) that prevents Audacity exporting correctly. When it gets the metadata as exported by itself (in the imported but corrupt file), it can cope.

Can you supply the original WAV file from SoundForge that you imported into that project?



Gale

Re: Possible bug - Exported wav file corrupt

Posted: Wed Aug 24, 2011 2:05 pm
by Sprinterdriver
Hi.

Here's the original sound files.

Re: Possible bug - Exported wav file corrupt

Posted: Wed Aug 24, 2011 4:08 pm
by Edgar
It seemed to work fine for me when I used the original source files.

But, then again, so does the original "bad" project without any modification.

Re: Possible bug - Exported wav file corrupt

Posted: Sat Aug 27, 2011 1:11 am
by Gale Andrews
Sprinterdriver wrote:Here's the original sound files.
Thanks. Not sure why Edgar gets different results, but there is no problem with the "hit10x.wav" imported on its own - that exports normally.

The "TauntPack_2578.wav" is the one that causes the problem - imported on its own into a clean project then exported, it ends up as a low level file with a lot of noise mixed in with the signal, and which Windows Media Player won't play. The only way I found to fix this if only that file is in the project is to clear the metadata in Metadata Editor.

I assume that different results occur in the project because a "good" and "bad" file are together. The reason the "TauntPack_2578.wav" upsets Audacity seems to be that the metatdata has been placed at the very end of the file after the data, instead of before the data.

Do you know how the file got like that?


Gale

Re: Possible bug - Exported wav file corrupt

Posted: Sat Aug 27, 2011 1:54 am
by steve
There's something badly wrong with the "TauntPack_2578.wav" (source) file.
On Linux, Audacity handles it fine, but VLC just plays it as a short chirp and on the first time playing VLC froze for about a minute.

Re: Possible bug - Exported wav file corrupt

Posted: Sun Aug 28, 2011 6:02 pm
by Gale Andrews
steve wrote:There's something badly wrong with the "TauntPack_2578.wav" (source) file.
On Linux, Audacity handles it fine, but VLC just plays it as a short chirp and on the first time playing VLC froze for about a minute.
Created a bug report at:
http://bugzilla.audacityteam.org/show_bug.cgi?id=448

Most applications can play "TauntPack_2578.wav" OK although it's non-standard, including Windows Media Player and "Movie Player" on Ubuntu.


Gale

Still not working (october 2011 alpha version)

Posted: Wed Oct 19, 2011 5:54 pm
by Sprinterdriver
Tried with: Audacity ® 1.3.14-alpha-Oct 14 2011 (Unicode)

Same files. When exporting, the result is just a crippled wav file :(

Does somebody know any programs out there that can (batch) clean up corrupted wav files? I has a collection of almost four thousand files that is pretty much useless because of this.