Subject: | Re: Windows 10 and .wav files |
---|---|
From: | madl74 |
Date: | Sun Aug 16, 2015 7:48 pm ((PDT)) |
> That's comforting. I wonder what it's changing in the files to still allo= w the data to be extracted. Maybe just damaging the headers? There are some= very pissed off people participating in that thread. Peter, I gathered from the link that the problem lies in corrupted headers. I don'= t know if Audacity will unscramble compressed files as well. I've played around with editing .wav files in a text editor and Audacity always seems t= o correct itself after a glitch. It will play a synthetically generated tone.= The message as ever is to backup everything. I'm a backup freak with Gigs o= f backups and it's all there if I can find it. :-) David Brinicombe |
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | Re: Windows 10 and .wav files, Peter Shute |
---|---|
Next by Date: | Re: Windows 10 and .wav files, oatcruncher |
Previous by Thread: | Re: Windows 10 and .wav files, Peter Shute |
Next by Thread: | Re: Windows 10 and .wav files, oatcruncher |
Indexes: | [Date] [Thread] [Top] [All Lists] |
The University of NSW School of Computer and Engineering takes no responsibility for the contents of this archive. It is purely a compilation of material sent by many people to the naturerecordists mailing list. It has not been checked for accuracy nor its content verified in any way. If you wish to get material removed from the archive or have other queries about the archive e-mail Andrew Taylor at this address: andrewt@cse.unsw.EDU.AU