When I use FLAC frontend to convert my tracked waves to FLAC, I get the warning message
"WARNING: skipping unknown sub-chunk 'id3'"
I use CDWave to track the original wave file from my JB3. Is this something I should concerned about? Is my JB3 adding some type of tag to my recording?
My FLAC settings are set for:
Level 6 encoding
Verify
Align on sector boundaries
Delete input files
Thanks
Mark
I get the same type error with any file I try to FLAC that I resampled in wavelab (going from 24bit to 16bit)...doesn't seem to do anything though
same here....even if I transfer from DAT. don't think that has anything to do with it though
Tommy
FLAC FAQ:
http://wiki.etree.org/index.php?page=FlacFrontend
ADDITIONAL NOTE: Your .wav editing software (Sound Forge, Cool Edit, CD Wave, WaveLab, etc.) may have added extra unnecessary data in the header of the .wav file. If this is the case, the FLAC encoding DOS box warning will be displayed:
WARNING: skipping unknown sub-chunk 'LIST'
Don't worry about it... the FLAC encoder is just telling you that there's extra, unnecessary junk in your .wav file, and because FLAC is so cool, it's just skipping it.
Quote from: deadhoarse on July 08, 2005, 02:29:16 PM
FLAC FAQ:
http://wiki.etree.org/index.php?page=FlacFrontend
ADDITIONAL NOTE: Your .wav editing software (Sound Forge, Cool Edit, CD Wave, WaveLab, etc.) may have added extra unnecessary data in the header of the .wav file. If this is the case, the FLAC encoding DOS box warning will be displayed:
WARNING: skipping unknown sub-chunk 'LIST'
Don't worry about it... the FLAC encoder is just telling you that there's extra, unnecessary junk in your .wav file, and because FLAC is so cool, it's just skipping it.
thanks for the info, I never seen a problem with it, but never knew 100% if it was problem..or not +T
Thanks
+T when I can
there's an extensive explanation of this in the archive too. Basically, its metadata the program doesn't know or need to know how to handle, from what I can discern.
a little metadata never hurt anybody 8)
cool thread, I've always wondered about that error.