Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: FLAC 1.1.3 released (Read 206975 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

FLAC 1.1.3 released

Reply #25

I thought most people are using tools like EAC, AutoFLAC, frontend, etc where the command string is only specified once, and it is easier to do the workaround.
Josh


That's me.

Josh, I want the absolute best compression (ripping from CD via EAC), and I do not care about encode time.  So what combination of flags do I need to set? Currently I'm using -8.  It looks like now I need to specify -m --best -e ?

if you want the maximum compression available, then you should use a few -A functions. it increases the encode time with little to no improvement to the compression. also, you can use -A more than once.

FLAC 1.1.3 released

Reply #26
Josh, I want the absolute best compression (ripping from CD via EAC), and I do not care about encode time.  So what combination of flags do I need to set? Currently I'm using -8.  It looks like now I need to specify -m --best -e ?

it's still -8 (same as --best) both of which turn on -m and -e.  if you're affected by the locale bug you have to specify -A "tukey(0,5)" manually.  then if you really don't care about the encoding time you can add more and different -A options but this is unlikely to ever get you more than .25% increased compression and they really slow things down.

I have some more ideas for compression improvements that I will be testing now that 1.1.3 is out.

Josh

FLAC 1.1.3 released

Reply #27
Will there be a separate P4 specific build like the previous version?  Or will we just have to wait and see if John33 compiles this?
"The way we see our world is better than yours."

FLAC 1.1.3 released

Reply #28
Thanks for the great work Josh. Looks like it's back to FLAC for me.



FLAC 1.1.3 released

Reply #31
Considering that a LOT of countries are affected by the -A bug (almost every country in fact !), and that this can cause IMHO potential problems with AccurateRip for instance (different file sizes, so no matches found) and lead to lots of wrong data being uploaded to AccurateRip's database, can we expect the "-A bug free version" to be available quite soon ?

Josh, what can be the estimated delay for the next bug-correcting version ? Are we talking about days ? weeks ? months ? years ? 

Thanks in advance. I hope everybody will soon be able to fully enjoy all of 1.1.3's great improvements.


FLAC 1.1.3 released

Reply #33
I will also wait for the version which fixes the localization bug. I don't know which one (',' or '.') is set at my computer, so I'll be safe and use 1.1.2 untill a bugfix is released.


FLAC 1.1.3 released

Reply #35
An estimate of a bigfix would be appreciated. Weeks? A month? Months? Year?

Doesn't have to be that precise, but for now I will just wait for the fix (since I don't expect to encode much until after my christmas gifts  )

FLAC 1.1.3 released

Reply #36
I don't think FLAC chooses the window depending on any criteria.  It always uses tukey(0.5).

Edit: Hmm... I see you are quoting the documentation and it does give the impression that the window is chosen dynamically.  I guess I must be wrong.

You're right, currently it is always "tukey(0.5)":

Quote
The encoder chooses suitable defaults in the absence of any -A options; any -A option specified replaces the default(s).

How does it choose? Is it always tukey(0.5)?

right now, yes  but it may get smarter.

FLAC 1.1.3 released

Reply #37
Thanks for the confirmation, and quotes, Egor.

I did wonder whether this referred to potential changes in the future, rather than current practise.
I'm on a horse.

FLAC 1.1.3 released

Reply #38
I uploaded a hack-fixed version for Windows here. It treats both comma and dot with apodization functions in the same way.


FLAC 1.1.3 released

Reply #40
So it has the same behaviour as 1.1.2?
No.  If tukey(0.5) and tukey(0,5) are working as they should then this release will do what 1.1.3 intended to do.

Unless of course Case means that now tukey(0.5) is fubar'd as well. 

Edit: Also, may I say in my best Brian Blessed voice, "Gordon's alive!".
I'm on a horse.

FLAC 1.1.3 released

Reply #41
Is the new version of FLAC OK to use with FLACFrontend? I'd use the surely marvellous Foobar but it makes my tiny brain hurt.

Thanks for treating me gently!!



FLAC 1.1.3 released

Reply #44
I uploaded a hack-fixed version for Windows here. It treats both comma and dot with apodization functions in the same way.

Thanks for the fix Case.

When creating a flac file with both beta 2 and the final fixed version there is one byte difference in the file size.
I assume this is normal behavior.

FLAC 1.1.3 released

Reply #45
Thanks for all your work Josh 
foobar2000 + EAC + Burrrn = Happiness

FLAC 1.1.3 released

Reply #46
To clear things up: The command line fix completely solves the issue, right? Flac does not set the switch dynamically like posted before?

FLAC 1.1.3 released

Reply #47
I believe that is the idea, yes.

The easiest way to test (assuming that you use the comma as the decimal separator) is to run the following two command lines, and ensure that the results are identical :

Code: [Select]
FLAC.EXE -o one.flac source.wav 
FLAC.EXE -A tukey(0,5) -o two.flac source.wav

Edit: In fact, on testing, this appears to work even if you use a full stop as the decimal separator.  I assume that Case is simply replacing any occurrence of "," with "." or something:

Code: [Select]
C:\Documents and Settings\Neil\Desktop>FLAC.EXE -o one.flac source.wav && FLAC.E
XE -A tukey(0,5) -o two.flac source.wav && FLAC.EXE -A tukey(0.5) -o three.flac
source.wav

flac 1.1.3, Copyright (C) 2000,2001,2002,2003,2004,2005,2006  Josh Coalson
flac comes with ABSOLUTELY NO WARRANTY.  This is free software, and you are
welcome to redistribute it under certain conditions.  Type `flac' for details.

source.wav: wrote 24487047 bytes, ratio=0.723

flac 1.1.3, Copyright (C) 2000,2001,2002,2003,2004,2005,2006  Josh Coalson
flac comes with ABSOLUTELY NO WARRANTY.  This is free software, and you are
welcome to redistribute it under certain conditions.  Type `flac' for details.

source.wav: wrote 24487047 bytes, ratio=0.723

flac 1.1.3, Copyright (C) 2000,2001,2002,2003,2004,2005,2006  Josh Coalson
flac comes with ABSOLUTELY NO WARRANTY.  This is free software, and you are
welcome to redistribute it under certain conditions.  Type `flac' for details.

source.wav: wrote 24487047 bytes, ratio=0.723
I'm on a horse.

FLAC 1.1.3 released

Reply #48
Discussion regarding decimal separator moved here.
I'm on a horse.

FLAC 1.1.3 released

Reply #49
first, to save time I'll say the answers by synthetic soul and doubleXP are correct.

as for when the next release will be out, please understand first that the full release cycle for flac is actually quite a lot of work, which I am hesitant to do for a bug which has such a simple workaround (adding an option).  the alternative is just specific fixed binaries, and I think case's handles that nicely for windows.  the fix in CVS on the trunk will be checked in probably tonight.

I don't have a schedule for 1.1.4, but the next full release will not be 2 years away again.  flac releases tend to ping-pong between major releases which take a lot of time, and shorter minor releases which are mostly fixes.

Josh