I have a .wav sample that caused my computer to reboot whenever played in Winamp. After rebooting had finished, the Microsoft error reporter directed me to a bug report page explaining that the problem could have been my drivers. But when I checked the file properties I noticed that all of the samples in that set had a bit rate of around 231-705kbps, but the file that rebooted my computer had a bit rate of 25kbps. Is this the cause of the error, or is it something else? And what exactly is a bit rate, and how do differant values effect things?
Any help would be greatly appreciated.
.wav Reboots Computer
-
- KVRer
- 15 posts since 8 Jul, 2005 from Australia
-
- KVRer
- Topic Starter
- 15 posts since 8 Jul, 2005 from Australia
I just took the files to a friends place to see if they worked there, and the same problem accured (and we used multiple players) unless he played them through FL Studio and... (never seen it before... think it was) Sonar, then they worked fine.
Oh, and I found that the differances between files that work and those that don't are not only bit rate, but sample rate as well, the files that don't work usually have a 'sample rate' of 1kHz, 14kHz etc. (lowkHz), when those that do work have 44kHz.
So I'm not sure what to do, and if sample rate and bit rate (still don't know what they are) should be certain levels. And how come they work in FL Studio and such?
Cheers.
Oh, and I found that the differances between files that work and those that don't are not only bit rate, but sample rate as well, the files that don't work usually have a 'sample rate' of 1kHz, 14kHz etc. (lowkHz), when those that do work have 44kHz.
So I'm not sure what to do, and if sample rate and bit rate (still don't know what they are) should be certain levels. And how come they work in FL Studio and such?
Cheers.
-
- KVRAF
- 6937 posts since 4 Jun, 2004 from Utrecht, Holland
My guess is the specific file has an odd header (there the info is stored about sampling rate, bit depth, nr of channels, loop points, version, author, etc)
Do you know what program was used to create these wav files? Maybe Fruity & Sonar have a different way of interpreting the header, and know how to handle it. WinAmp obviously does not, and chokes in it.
I'd suggest to use "File - Save as" in a program that can cope with the file, and then try it again in WinAmp. Maybe not use a production host like Fruity, but an audio editor like Audacity (which is free), or CoolEdit, or whatever you can get your hands on & works...
Do you know what program was used to create these wav files? Maybe Fruity & Sonar have a different way of interpreting the header, and know how to handle it. WinAmp obviously does not, and chokes in it.
I'd suggest to use "File - Save as" in a program that can cope with the file, and then try it again in WinAmp. Maybe not use a production host like Fruity, but an audio editor like Audacity (which is free), or CoolEdit, or whatever you can get your hands on & works...
-
- Skunk Mod
- 21249 posts since 10 Jun, 2004 from Pony Pasture
=@.o= What kind of sounds were these?
The last time I used a 1 kHz sample rate it was on an home-made RCA 1800 system, in the mid-1970s. The audio quality was similar to toy walkie-talkies or a cheap pocket AM radio, barely recognizable as voice. For musical sound that sample rate would have been unusable.
I agree with C00kie's opinion that the headers might've got munged somehow, but that Sonar and FL have another way of dealing with things rather than depending on the header chunks.
What kind of sound quality do you get in those two programs? If it's not terrible (for the apparently low sample rate files), the headers are probably bogus in some way.
The last time I used a 1 kHz sample rate it was on an home-made RCA 1800 system, in the mid-1970s. The audio quality was similar to toy walkie-talkies or a cheap pocket AM radio, barely recognizable as voice. For musical sound that sample rate would have been unusable.
I agree with C00kie's opinion that the headers might've got munged somehow, but that Sonar and FL have another way of dealing with things rather than depending on the header chunks.
What kind of sound quality do you get in those two programs? If it's not terrible (for the apparently low sample rate files), the headers are probably bogus in some way.
-
- KVRer
- Topic Starter
- 15 posts since 8 Jul, 2005 from Australia
Thanks, I guess it was just the header being muddled up, since the quality of the samples are quite godd. I have used an audio editor and saved them again, and they work fine, thanks again.
-
Stupid American Pig Stupid American Pig https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=4753 - KVRAF
- 7065 posts since 25 Nov, 2002 from not sure
naw it was probably a compressed ADPCM or wav file that yer PC either doesnt have the codec for, or the codec you have doesnt work, or yes, the wav file headers are corrupt. Either way it sound like its causing a BSOD and auto rebooting yer PC. right click My Computer, Properties/ Advanced/ Start up and Recovery/Advanced and uncheck automatically restart. Then you can catch the bluescreen when it happens. If you can get it to work in FL studio or sonar, I would import it into that app then export a normal PCM wav file out of it and delete the original.
-
- KVRer
- Topic Starter
- 15 posts since 8 Jul, 2005 from Australia
Unfortunatly I don't have FL Studio or Sonar, but I can use my wave editor if it happens some more.
How does the blue screen help? Accasionally the computer didn't restart, it went to the blue screen, and it was just numbers and letters I didn't understand, and said to restart my computer, lol.
Thanks guys.
How does the blue screen help? Accasionally the computer didn't restart, it went to the blue screen, and it was just numbers and letters I didn't understand, and said to restart my computer, lol.
Thanks guys.