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 105182 times) previous topic - next topic
0 Members and 1 Guest 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").

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

Reply #157 –
Quote from: rennie on
Would it be possible to add the Code Base Number to the ID of newer builds?
Yes, but I specifically chose to not do that. These builds are not stable FLAC 1.4.3, they are builds of a work-in-progress. I think adding 1.4.3 to the version string would be confusing in that regard.

May I ask why you feel this would be a welcome addition?
Music: sounds arranged such that they construct feelings.

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

Reply #158 –
Quote from: ktf on
May I ask why you feel this would be a welcome addition?

I don't know, if should agree to your statement that your builds are not stable or at least less stable than FLAC 1.4.3!

Commits that make it to the official master source code are usually intended to correct code errors.

So, why should the correction of errors lead to a less stable code/application in general?

Thus, I wouldn't hesitate to mention the code base in the IDs of builds to come.

Furthermore, it would be easier to understand, which code base version was used.

Of course it's possible to look up the commit number and/or the its publication date, if the code base version doesn't show up in the file info, but it I'd prefer to able to see it directly.

And if your unsure about the stability you could call your builds "reference libFLAC 1.4.3 20241206 git-c786b1c (unstable)" for example.
 

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

Reply #159 –
Quote from: rennie on
Commits that make it to the official master source code are usually intended to correct code errors.
No, they are not. I've been busy implementing a few new complex features (multithreaded encoding, decoding of chained Ogg FLAC) and I am still not done squashing bugs. So, these builds are NOT intended for general use.

Quote
Thus, I wouldn't hesitate to mention the code base in the IDs of builds to come.
But I do. The current state of the code doesn't yet feel release-worthy to me, so I really don't want people to think that it is.

Quote
Furthermore, it would be easier to understand, which code base version was used.
Please explain why.

Quote
Of course it's possible to look up the commit number and/or the its publication date, if the code base version doesn't show up in the file info[...]
Please do NOT create files that are not instantly disposable with these development builds, or accept that hic sunt dracones.

Quote
[...] but it I'd prefer to able to see it directly.
Please explain why.

Quote
And if your unsure about the stability you could call your builds "reference libFLAC 1.4.3 20241206 git-c786b1c (unstable)" for example.
I could, but I haven't seen a compelling reason why I should. I keep hearing (from others in the past too) they'd like to see the number of the previous release somewhere, but never why, beyond "I'd like that" or "I don't want to look it up".
Music: sounds arranged such that they construct feelings.

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

Reply #160 –
Quote from: ktf on
I keep hearing (from others in the past too) they'd like to see the number of the previous release somewhere, but never why, beyond "I'd like that" or "I don't want to look it up".

I do not have a better explanation! Sorry!

I'd like that and I don't want to look it up later on.  ;)

...and I think it would be useful to be able to see code base version immediately.

If there are really so many new unstable features in the master source I'd rather remove the word "reference" and add "(unstable)" instead.

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

Reply #161 –
I could maybe see something like this...
"flac git-d34489c4 20240831 1.4.4_BETA-1"
"flac git-d34489c4 20240831 1.4.4_RC-2"

Stable releases don't get pushed out so often that you can't stop by the git once in a while to see where things are at.

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

Reply #162 –
If you are happy with this, then yes!

Would make things much clearer!

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

Reply #165 –
Quote from: Ozz on
FLAC git-c1ef75b 20241227

For some reason, your version is around 8 times slower than NetRanger's release while using mutithreading. Didn't use single threading to test the encoder. I have Ryzen 5 3600. I think it doesn't multithread at all, as I don't see it using all CPU cores in task manager at all.
TAPE LOADING ERROR

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

Reply #166 –
Microsoft Visual Studio (MSVC) doesn't provide a pthread.h implementation, so the multithreading code cannot be build and is disabled.

Apparently, there is a pthread.h implementation that works with MSVC available on vcpkg, but I've only ever tested multithreading on Windows through MinGW64 with winpthreads (which I think is a different implementation).
Music: sounds arranged such that they construct feelings.