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 v1.3.4 (Read 10294 times) previous topic - next topic - Topic derived from FLAC v1.3.3
0 Members and 1 Guest are viewing this topic.

Re: FLAC v1.3.4

Reply #75
Code: [Select]
Writing library                          : libFLAC 20220425 (UTC 2022-04-25)
Where from? I find a "reference libFLAC git-c157be0f 20220425" in the file.

From a WAV file I've just encoded using NetRanger's FLAC git-c157be0 20220425 x64 build he has posted. MediaInfo doesn't report the git info but you're right, I see the full string inside the file using an hex editor.
Anyway I think the base version number 1.3.4 is still needed:  "reference libFLAC 1.3.4 git-c157be0f 20220425"

Re: FLAC v1.3.4

Reply #76
OK, so this is MediaInfo that reports
reference libFLAC 1.3.4 20220220                          as           libFLAC 1.3.4 libFLAC (UTC 2022-02-20)
reference libFLAC git-c157be0f 20220425           as           libFLAC 20220425 (UTC 2022-04-25)
... in "Tree" view. Now select Debug -> Advanced Mode ... or "Text" view.

Looks like this is just a MediaInfo peculiarity? Any reason that other applications should make the same issue?
Last two months' worth of foobar2000.org ad revenue has been donated to support war refugees from Ukraine: https://www.foobar2000.org/

Re: FLAC v1.3.4

Reply #77
I don't yet see the advantage of this.

Facilitating both reproducibility and comparability. If someone wants to build FLAC for themselves, they can use the information provided there either to achieve a build that ought to be identical to another one (could be useful for testing), or to compare the effect of different compile options or compilers.
Having had some time to ponder this, I've reconsidered: not a bad idea to add. Probably best to copy the approach ffmpeg has on what to output. Note that I don't consider this high-priority though, so it might take a while. Anyone is welcome to contribute a PR though.

This build doesn't show the base version number anymore, neither in the -version switch nor in the writing library info of the FLAC [...]
I think this is a bad idea, we should always know the base version number in any case like before.
Please elaborate why you think this is a bad idea.

I thought it a bad idea to leave any version number in. In my opinion version numbers belong a certain release, and these compiles are no releases, they are compiles straight from git, i.e. inbetween releases. ffmpeg uses the same approach: only specific releases have a version number, others a revision number. If you want to compare versions, I believe using the date provides a nice alternative.
Music: sounds arranged such that they construct feelings.

Re: FLAC v1.3.4

Reply #78
I thought it a bad idea to leave any version number in. In my opinion version numbers belong a certain release, and these compiles are no releases, they are compiles straight from git, i.e. inbetween releases. ffmpeg uses the same approach: only specific releases have a version number, others a revision number. If you want to compare versions, I believe using the date provides a nice alternative.
Because I want to know at first sight which base version has been used.
For instance, in ten years time from now I won't have to waste time searching for the commit number or the date and the base version it refers to.

Re: FLAC v1.3.4

Reply #79
Because I want to know at first sight which base version has been used.
For instance, in ten years time from now I won't have to waste time searching for the commit number or the date and the base version it refers to.

I agree with ya also. It must not say 1.3.4 (for example) at the beginning but the code base should be there even if it's a git compile.

Example :
FLAC git-c157be0 20220425 (Code base : 1.3,4)

The git releases is still based on the previous stable release.

Re: FLAC v1.3.4

Reply #80
Shouldn't in the very least the YYYYMMDD go at the end? Like
reference libFLAC 1.3.4git-c157be0 20220425

1.3.4git-something means that it is based on 1.3.4 and blah blah blah

Last two months' worth of foobar2000.org ad revenue has been donated to support war refugees from Ukraine: https://www.foobar2000.org/

Re: FLAC v1.3.4

Reply #81
Thanks very much. 
I'm still in love with FLAC. 
Gotta love FLAC. 


Re: FLAC v1.3.4

Reply #83
Thank you very much for the update.


 

Re: FLAC v1.3.4

Reply #85
FLAC git-1bec35e3 20220511
Built on May 11, 2022, GCC 11.3.0
Note that development is currently mainly focused on improving fuzzing to find security related bugs and as some sort of quality assurance for next releases, so there are few (if any) changes that affect end-users in these releases.
Music: sounds arranged such that they construct feelings.

Re: FLAC v1.3.4

Reply #86
FLAC git-1bec35e3 20220511
Built on May 11, 2022, GCC 11.3.0
Note that development is currently mainly focused on improving fuzzing to find security related bugs and as some sort of quality assurance for next releases, so there are few (if any) changes that affect end-users in these releases.

Thnx for the info :)