Subject: | Re: Windows 10 and .wav files |
---|---|
From: | madl74 |
Date: | Sun Aug 16, 2015 5:26 pm ((PDT)) |
Peter Shute [naturerecordists] writes: > That's extremely serious. The wording suggests this affects any media, no= t just Sound Devices. I'm very suspicious of new Microsoft products and let them shake down for a= while - hence I'm still using W 7. I've had a search for Windows 10 problem= s and one theory is that a W 10 upgrade causes the problem rather than a clea= n down and reinstall of W 10. One correspondent found that Audacity could still read the corrupted .wav files. Check out: http://answers.microsoft.com/en-us/windows/forum/windows_10-files/transferr= i ng-wav-audio-files/50bbf42f-84a7-44b9-ab57-8784b5606d09?page=3D3 David Brinicombe (wishing I'd bought a Mac years ago) :-) |
<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, Bernie Krause |
Previous by Thread: | Re: Windows 10 and .wav files, Peter Shute |
Next by Thread: | Re: Windows 10 and .wav files, Bernie Krause |
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