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-git Releases (Code Base v1.4.x) (Read 49709 times) previous topic - next topic
0 Members and 3 Guests are viewing this topic.

Re: FLAC-git Releases (Code Base v1.4.x)

Reply #151 –
Quote from: darkalex on
Quote from: Replica9000 on
I'll post some builds...

FLAC git-a7d69df6 2024-10-28
- Windows 32-bit & 64-bit - Static binaries built with GCC 12.2.0 (MinGW)  -  [ZIP File]
- Linux amd64 & i686 - Static binaries built with GCC 14.1.0 / LIBC 2.29+  -  [TGZ File]
 

Can you try something like this for the latest flac version?

https://hydrogenaud.io/index.php/topic,123234.msg1018713.html#msg1018713

I would really like a new binary that is as fast or faster than this one

For the 64-bit compiles, I included a generic version and a version built with no asm optimizations that will speed up encoding for 16-bit files on AVX2 capable processors.  Other than that, performance advantages come down to the compiler/flags used.

For multithreading, use the -j option

Re: FLAC-git Releases (Code Base v1.4.x)

Reply #152 –
Quote from: MrRom92 on
Is there a guide someone can link to that can help explain to the noobs here (me included) in the simplest terms possible, exactly how to go from GitHub to a working executable much like the ones many of you have provided here?
I've added a task to github to provide automated builds after every change to the code. It is not too obvious where to get them, so I'll explain.

Go to https://github.com/xiph/flac/actions/workflows/msys2.yml?query=branch%3Amaster You'll see a bunch of tasks there, click on the topmost one with a green check mark in front of it, to get the newest one that is finished. On the next page, look for a box with the title Artifacts and download the flac-win64-static zip file. The zip file contains the latest win64 GCC builds, and the newest documentation.

@Porcus: through there, the changes discussed in https://github.com/xiph/flac/issues/699 (providing html docs for windows builds) are finally available for review  :))
Music: sounds arranged such that they construct feelings.

Re: FLAC-git Releases (Code Base v1.4.x)

Reply #153 –
Quote from: ktf on
Quote from: MrRom92 on
Is there a guide someone can link to that can help explain to the noobs here (me included) in the simplest terms possible, exactly how to go from GitHub to a working executable much like the ones many of you have provided here?
I've added a task to github to provide automated builds after every change to the code. It is not too obvious where to get them, so I'll explain.

Go to https://github.com/xiph/flac/actions/workflows/msys2.yml?query=branch%3Amaster You'll see a bunch of tasks there, click on the topmost one with a green check mark in front of it, to get the newest one that is finished. On the next page, look for a box with the title Artifacts and download the flac-win64-static zip file. The zip file contains the latest win64 GCC builds, and the newest documentation.

@Porcus: through there, the changes discussed in https://github.com/xiph/flac/issues/699 (providing html docs for windows builds) are finally available for review  :))

Seriously awesome! Thank you for all your work on this KTF, you rule 🙏

Re: FLAC-git Releases (Code Base v1.4.x)

Reply #154 –
Quote from: ktf on
@Porcus: through there, the changes discussed in https://github.com/xiph/flac/issues/699 (providing html docs for windows builds) are finally available for review  :))
Oof, I should have had the brain capacity to contribute more. Thanks for keeping up.

Re: FLAC-git Releases (Code Base v1.4.x)

Reply #156 –
Would it be possible to add the Code Base Number to the ID of newer builds?

I think it would better to identify the used FLAC git version by "reference libFLAC 1.4.3 git-5152c6c 20241030" OR "reference libFLAC 1.4.3 (git-5152c6c) 20241030" OR "reference libFLAC 1.4.3 20241030 git-5152c6c" OR "reference libFLAC 1.4.3 20241030 (git-5152c6c)" for example.

Especially the last two proposed identifiers would be as similar as possible to the ID of the latest official release (which is "reference libFLAC 1.4.3 20230623").