I'm using FLAC 1.2.1b to encode 24/96 .wav files made by a sound device 722. Originally I recived the following message "warning: skipping unknown sub-chunk LIST". I thought I was good after I burn a data dvd with verify. however, upon copying files form the dvd to my new pc's "c:" drive. I get an error "cyclic redundancy check". I tried to decode direct form the dvd getting "flac_stream decoder aborted". Do I have a corrupt flac file and need to start over? I never used the command line "--keep-foreign-metadata", is there another way to get these 24/96 files flac'd up properly? The .16/44 .wav files seemed to flac up and decode fine.
Thanks in Advance for your help.
BT
Full Version: 24/96 Cycli Redundancy Check
yep, sounds like the file is corrupted on the drive. wouldn't be a usb external drive by any chance would it?
but to know for sure you should post as much info as you have, like the exact commands and error messages.
but to know for sure you should post as much info as you have, like the exact commands and error messages.
Hi,
Thanks for your insight. I'm using the master .wav files off the sound device recorder's harddrive (no usb). In turn these same "masters"files were placed directly on the C: drive of the PC. Then I just used the flac frontend to encode (1.2.1b), I did notice the "decode through errors" button was on the flacfrontend when I done with my first encode. Not sure how to proceed, except to re-encode and wish for the best.
BT
yep, sounds like the file is corrupted on the drive. wouldn't be a usb external drive by any chance would it?
but to know for sure you should post as much info as you have, like the exact commands and error messages.
Thanks for your insight. I'm using the master .wav files off the sound device recorder's harddrive (no usb). In turn these same "masters"files were placed directly on the C: drive of the PC. Then I just used the flac frontend to encode (1.2.1b), I did notice the "decode through errors" button was on the flacfrontend when I done with my first encode. Not sure how to proceed, except to re-encode and wish for the best.
BT
QUOTE(jcoalson @ Jun 14 2008, 17:14) 
yep, sounds like the file is corrupted on the drive. wouldn't be a usb external drive by any chance would it?
but to know for sure you should post as much info as you have, like the exact commands and error messages.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.