Author Topic: 24-bit FLAC encoding (Read 6884 times)

keepongoin · « **on:** February 02, 2005, 11:07:35 AM »

What version of FLAC frontend do I need?

I have 1.1.1 and it says that my 24/96 wave files are not a known format.

WTF?

MattD · « **Reply #1 on:** February 02, 2005, 12:30:03 PM »

1.1.1 is the latest version, AFAIK. What editor/program did you use to create those files? Odds are it's doing something to the wave formate when saving. They *are* wav files, right? (Not SDII or AIFF or something else.)

John Kelly · « **Reply #2 on:** February 03, 2005, 09:55:19 AM »

You could also try using shntool with SOX, it may be able to read the format to pass it on to flac.

keepongoin · « **Reply #3 on:** February 03, 2005, 12:50:57 PM »

i used sourdforge to edit and CdWave to track them.

flac just doesn't seem to want to work.

i dithered the original wav to 16/44.1 and have circulated the show that way.

i would like to archive these old analog tapes in 24bit/96khz. i must figure out what is wrong. I am going to start using wavelab instead of soundforge.

dnsacks · « **Reply #4 on:** February 03, 2005, 12:56:59 PM »

cdwave can save directly to flac (at least with 16/44.1 files) -- have you tried saving directly to flac with the 24/96 files in cdwave?

MattD · « **Reply #5 on:** February 03, 2005, 01:17:53 PM »

some versions of CD wave have a funky thing for 24-bit wave format. Check the preferences for "alternate 24-bit format" and either check it or uncheck it depending on what it's set to now and try FLAC-ing that.

JasonSobel · « **Reply #6 on:** February 03, 2005, 01:49:15 PM »

when I use CD Wave to cut up 24 bit files, I always check the "use alternate 24-bit format"

It's something about Microsoft trying to redefine the way header info is used in .wav files (I forget exactly what they were trying to change and why). but in my experience, a file saved from CD Wave, WITHOUT using the "alternate" 24-bit format, will NOT open in Cool Edit 2000. However, when I use the "alternate" 24-bit format, Cool Edit opens it just fine, and I've had no problems compressed to FLAC.

Tall Adam · « **Reply #7 on:** February 03, 2005, 02:12:48 PM »

correct. saving with out the "Alternate" format does something to the headers and makes it an Unknown file type in flac. try that, or really just output directly to flac. no reason to run frontend if your saving from cdwave

Dr.FOB · « **Reply #8 on:** February 04, 2005, 08:16:26 AM »

The purpose of flac, like shorten, is to convert a wav file to a compressed data file for transport and storage. CDWave has not proven, to me, to be effective in compressing 24 bit files in flac format, regardless of the compression setting. The flacs are valid, but no smaller than the wav files. Stick with flac frontend.

creekfreak · « **Reply #9 on:** February 04, 2005, 07:37:23 PM »

Quote from: JasonSobel on February 03, 2005, 01:49:15 PM

when I use CD Wave to cut up 24 bit files, I always check the "use alternate 24-bit format"

It's something about Microsoft trying to redefine the way header info is used in .wav files (I forget exactly what they were trying to change and why). but in my experience, a file saved from CD Wave, WITHOUT using the "alternate" 24-bit format, will NOT open in Cool Edit 2000. However, when I use the "alternate" 24-bit format, Cool Edit opens it just fine, and I've had no problems compressed to FLAC.

I do the same, have to use it also if you plan to burn your 24bit files onto DVD for listening in a dvd-v player using DVD audio creator, if you don't, audio creator won't recognize the files

The Kilted Taper · « **Reply #10 on:** April 15, 2005, 01:26:39 PM »

Similar situation here, but Frontend is telling me they are not WAVE files, and that I must specify a value for endian, sign, channels, bps and sample-rate.

I've gone from the master .w64 file, broke it up in SF 6.0 and saved the tracks as .wav's. Any thoughts?

MattD · « **Reply #11 on:** April 15, 2005, 01:36:28 PM »

Hmm ... maybe the w64 hearder info is still there?

The Kilted Taper · « **Reply #12 on:** April 15, 2005, 02:04:42 PM »

Here's another question, Soundforge doesn't even ask in what format I want to save the regions, put does give it the .wav tag. Nothing (real player, winamp, etc) will open/play the file EXCEPT SF6.0. Am I missing something?

The Kilted Taper · « **Reply #13 on:** April 15, 2005, 02:19:36 PM »

Maybe it's my FLAC Frontend. I can't even Decode any flacs I have on my laptop right now. It's saying:

Quote

ERROR while decoding metadata
state = FLAC_STREAM_DECODER_END_OF_STREAM

MattD · « **Reply #14 on:** April 15, 2005, 03:21:16 PM »

Are you nearly out of disk space?

The Kilted Taper · « **Reply #15 on:** April 15, 2005, 03:59:26 PM »

Quote from: MattD on April 15, 2005, 03:21:16 PM

Are you nearly out of disk space?

Do you consider 7.31 GB nearly out?

That's actually a lot less than I thought I had. I'll try cleaning it up a bit.

F.O.Bean · « **Reply #16 on:** April 16, 2005, 12:58:54 AM »

and restart your comp, its amazing what a good ole restart can do

momule · « **Reply #17 on:** April 18, 2005, 02:07:19 PM »

Q: As I drag and drop files, everything is fine. When I hit decode, it says: Got error code 0: Flac stream decoder error status lost sync. Error while decoding metadata state =4 end of stream. What does this mean and how can I decode without getting this error message?

A: Error codes generally mean your file is corrupt. Try performing flac -t (Test in FlacFrontend). Get a fresh copy if there is a problem.

Quote from: BornAgainTaper on April 15, 2005, 02:19:36 PM

Maybe it's my FLAC Frontend. I can't even Decode any flacs I have on my laptop right now. It's saying:

Quote
ERROR while decoding metadata
state = FLAC_STREAM_DECODER_END_OF_STREAM

momule · « **Reply #18 on:** April 18, 2005, 02:10:11 PM »

get a much newer version of frontend.
Im running 1.7.1
then uncheck the box that says "align on sector boundaries"

you should have no problems this route .

Quote from: keepongoin' on February 02, 2005, 11:07:35 AM

What version of FLAC frontend do I need?

I have 1.1.1 and it says that my 24/96 wave files are not a known format.

WTF?

F.O.Bean · « **Reply #19 on:** April 18, 2005, 05:31:15 PM »

Quote from: Momule (AKA powerboatman) on April 18, 2005, 02:10:11 PM

first off get a much newer version of frontend.
Im running 1.7.1
then uncheck the box that says "align on sector boundaries"

you should have no problems this route .

Quote from: keepongoin' on February 02, 2005, 11:07:35 AM
What version of FLAC frontend do I need?

I have 1.1.1 and it says that my 24/96 wave files are not a known format.

WTF?

the newest versions of frontend have the sector boundary fixed, this is how ive been fixing SBE's lately, even mike wren chimed in and said its been working flawlessly in the newer ones

so when encoding 44.1k, make sure the box IS CHECKED unless running and older version

F.O.Bean · « **Reply #20 on:** April 18, 2005, 05:32:03 PM »

nevermind, keep the box UNCHECKED, i forgot this is for stricly 24-bit, no SBE'sto fix there, hell, they wont even encode if its checked

The Kilted Taper · « **Reply #21 on:** April 18, 2005, 09:36:08 PM »

I don't know why, guessing it's a header problem, but when I cut the show into smaller bits to save as a .wav instead of .w64, then split in cd wav, saved using "alternative 24 bit options" Frontend seems to work fine.

One odd thing, Frontend is saying:

Quote

Encoded by FLAC v1.1.2a with FLAC Frontend v1.7.1 FLAC tag written

What's that?

momule · « **Reply #22 on:** April 18, 2005, 09:53:44 PM »

Quote from: BornAgainTaper on April 18, 2005, 09:36:08 PM

I don't know why, guessing it's a header problem, but when I cut the show into smaller bits to save as a .wav instead of .w64, then split in cd wav, saved using "alternative 24 bit options" Frontend seems to work fine.

One odd thing, Frontend is saying:

Quote
Encoded by FLAC v1.1.2a with FLAC Frontend v1.7.1 FLAC tag written

What's that?

are you letting cdwave encode the files?
maybe cdwave recognizes Version 1.1.2 . and frontend recognizes that you have 1.71

The Kilted Taper · « **Reply #23 on:** April 18, 2005, 10:18:20 PM »

Quote from: Momule on April 18, 2005, 09:53:44 PM

are you letting cdwave encode the files?
maybe cdwave recognizes Version 1.1.2 . and frontend recognizes that you have 1.71

Sorry, should have clarified. NO, I am only using CD Wave to track. Frontend to encode.