New versions of free software used in the GUI's

[guest]

x264-r3155-9c3c716 (https://artifacts.videolan.org/x264/release-win64/)

[StainlessS]

LAV Filters 0.78 just updated a few moments ago.
https://forum.doom9.org/showthread.php?p=1992856#post1992856

[StainlessS]

DGDecNV 250
https://www.rationalqm.us/dgdecnv/binaries/

DGDecNV 250 (2023-10-14)
https://www.rationalqm.us/dgdecnv/binaries/

DGDecNV 250 (2023-10-22)
https://www.rationalqm.us/dgdecnv/binaries/

That's the spirit kedautinh12, make sure that nobody forgets :)

[kedautinh12]

That's spirit of sharer :D

[seagate]

x264-r3156-d46938d (https://artifacts.videolan.org/x264/release-win64/)

[guest]

new eac3to_mod 3.37

Info:-
https://forum.doom9.org/showthread.php?p=1992999#post1992999

Use the DLLs etc. from the eac3to 3.36 release. Easiest is to just put eac3to_mod.exe in the same directory as your eac3to 3.36 installation.

Download link:-
https://rationalqm.us/misc/eac3to_mod.rar

[kedautinh12]

MKVToolNix v80.0
https://mkvtoolnix.download/windows/releases/80.0/
https://mkvtoolnix.download/doc/NEWS.md

[StainlessS]

Not sure if this should be posted here, perhaps UT_Video used in some pre-rendered lossless file (eg MEGUI does that I think),
UT_Video Codec, [updated April 2023]:- https://www.videohelp.com/software/Ut-Video-Codec-Suite
Updated back in April, but never seen update posted anywhere on D9 [version I was using was from 2021].

[kedautinh12]

x264_tmod_r3156
https://github.com/jpsdr/x264/releases

[StainlessS]

kedautinh12, whos compile is that x264 ?

[guest]

kedautinh12, whos compile is that x264 ?

I would think it's from here :-

https://artifacts.videolan.org/x264/release-win64/

https://artifacts.videolan.org/x264/release-win64/x264-r3156-d46938d.exe

[StainlessS]

Thanks TDS.

[LeXXuz]

x264_tmod_r3156
https://github.com/jpsdr/x264/releases

What kind of mod is that?

[guest]

What kind of mod is that?

Jpsdr drops a lot of tweaked & optimised builds, compared to the "standard" releases.

Follow the link for more detail.

[kedautinh12]

kedautinh12, whos compile is that x264 ?

It's from Barough, he is forget post to here

[seagate]

L-SMASH-works 20231106 1147.0.0.0 (https://github.com/HomeOfAviSynthPlusEvolution/L-SMASH-Works/releases/tag/1147.0.0.0)

[LeXXuz]

Jpsdr drops a lot of tweaked & optimised builds, compared to the "standard" releases.

Follow the link for more detail.

I know. But I couldn't really find a readme to what that tmod for x264 is and what it does.

[kedautinh12]

x265 r3.50.111 with Patman mods
https://github.com/jpsdr/x265/releases/tag/r3.50.111

[seagate]

VisualCppRedist AIO v.0.77.0 (Visual C++ 2022 redistributable - v.14.38.33130.0) (https://github.com/abbodi1406/vcredist/releases/tag/v0.77.0/)

[guest]

Apparently FFMPEG is now @ 6.1...

Found it @ https://www.videohelp.com/software/ffmpeg & https://www.gyan.dev/ffmpeg/builds/, but not here (yet), https://github.com/BtbN/FFmpeg-Builds

[kedautinh12]

DGDemux_1.0.0.72 (2023-11-14)
https://www.rationalqm.us/dgdemux/binaries/

[kedautinh12]

Apparently FFMPEG is now @ 6.1...

Found it @ https://www.videohelp.com/software/ffmpeg & https://www.gyan.dev/ffmpeg/builds/, but not here (yet), https://github.com/BtbN/FFmpeg-Builds

BtbN already had 6.1 in win64 latest

[guest]

BtbN already had 6.1 in win64 latest

OK, good to know, I was just going off that there wasn't 6.1 in the files name, it's still only 6.0.

[kedautinh12]

That's ffmpeg-n6.0-latest-win64 not ffmpeg-master-latest. In ffmpeg-master-latest-win64 is 6.1. You can download ffmpeg-master-latest-win64-gpl-shared.zip and check version of library from here:
https://www.ffmpeg.org/download.html#release_6.1

[kedautinh12]

What kind of mod is that?

You can check some tweak here:
https://github.com/jpsdr/x264/commits/t_mod_New

[seagate]

L-SMASH-works 20231117 1156.0.0.0 (https://github.com/HomeOfAviSynthPlusEvolution/L-SMASH-Works/releases/tag/1156.0.0.0)

[seagate]

ffms2 r1387 (https://codeberg.org/StvG/ffms2/releases/tag/r1387)

[eac3to_mod]

Please don't link the test versions of eac3to_mod! It is still changing rapidly. Please wait for a formal release. Thank you.

[kedautinh12]

Ok, welcome to doom9 forum :D

[guest]

Please don't link the test versions of eac3to_mod! It is still changing rapidly. Please wait for a formal release. Thank you.

But a lot of the software that's shown on this thread changes rapidly, so the more that hear about what your great work is doing, the more feedback you'll get and help with development.

[eac3to_mod]

But a lot of the software that's shown on this thread changes rapidly, so the more that hear about what your great work is doing, the more feedback you'll get and help with development. It's not quite ready for prime time, though getting close. And people can follow eac3to_mod development at the DG Tools website if they are so inclined.

[kedautinh12]

Please don't link the test versions of eac3to_mod! It is still changing rapidly. Please wait for a formal release. Thank you.

Your file don't "_test" in name, maybe it's formal ver?

[eac3to_mod]

Yes, that's correct.

[kedautinh12]

MediaInfo 23.11.1
https://mediaarea.net/en/MediaInfo/Download/Windows

[guest]

MKVToolNix v81.0
https://mkvtoolnix.download/windows/releases/81.0/

[kedautinh12]

DGMPGDec 2.0.0.9
https://www.rationalqm.us/dgmpgdec/

[kedautinh12]

Avisynth+ 3.7.3post test 10 (20231202 - r4035)
https://forum.doom9.org/showthread.php?p=1994584#post1994584

[kedautinh12]

AviSynthPlus Builds r4035 with IntelLLVM and Clang build by Asd-g, fix this error (https://forum.doom9.org/showthread.php?p=1994621#post1994621) too
https://drive.google.com/file/d/1OcPJNK_qEuYPTsL6yXvy-FV3XATUx9Io/view?usp=drive_link

[tebasuna51]

AviSynthPlus Builds r4035 with IntelLLVM and Clang build by Asd-g, fix this error (https://forum.doom9.org/showthread.php?p=1994621#post1994621) too
https://drive.google.com/file/d/1OcPJNK_qEuYPTsL6yXvy-FV3XATUx9Io/view?usp=drive_link

Can you explain the differences with the previous r4035 post 10, the change log is identical.

Also explain the differences between IntelLLVM and Clang versions and for what a user can select one or other.

Please remember my first post:

Please link only official, tested and legal versions with the inprovements or bug fixes (or changelog), than justify the download and replace the new version in at last in one GUI of this sub-forum.

because your builds aren't official (https://forum.doom9.org/showthread.php?p=1994774#post1994774)

Put your builds in that thread to test purposes but not here.

[kedautinh12]

Why other people post not official build you don't said to them, just tag me?? Double standard. And this build from Asd-g not me.

[kedautinh12]

FDK-AAC v1.0.5 (2023-12-05)
https://www.mediafire.com/file/sw7ncdv2pc3vtqe

As @tebasuna51 said, don't post mp4box, fdk-aac, x264 personal build here. This post only accept official build

[tebasuna51]

As @tebasuna51 said, don't post mp4box, fdk-aac, x264 personal build here. This post only accept official build

It is not a problem with you, but this forum have a dedicated sub-forum to AviSynth+, and put here other versions without explain well the differences to the official ones can be a problem. At least for me these versions are worse than official ones.

Other software don't have dedicated threads here, but of course there are differents builds, for instance with x264/x265, than I like must be better explained to help the users use them or not.

[Wishbringer]

I am a bit surprised about the last two posts.
@Barough did the 2nd post in this thread, with personal builds in Jan 2023.
And now, around 11 months later you demand, not to post personal builds...
A little bit late!

I can understand your intention to not confuse users, but this is a tech forum, where ppl try to optimize their encoding.
There are tmod builds here, compiles with gcc, intel, ms,
builds with included libs like libswscale, libavformat, ffmpegsource, lsmash and so on.

As long someone wrote down his "additions" to the build like "(libswscale 7.6.100)(libavformat 60.18.100)(ffmpegsource 3.1.1.0)(lsmash 2.16.1)"
or "built with GCC 13.2.0" all should be fine

This thread was for me a source of new releases (and builds) and a chance to not search several sites, forums and threads around the net.

[kedautinh12]

It is not a problem with you, but this forum have a dedicated sub-forum to AviSynth+, and put here other versions without explain well the differences to the official ones can be a problem. At least for me these versions are worse than official ones.

Other software don't have dedicated threads here, but of course there are differents builds, for instance with x264/x265, than I like must be better explained to help the users use them or not.

In my post have IntelLLVM and Clang build and "r4035" that mean same commits with official build. Why i need explain when it had in my post link?? And "At least for me these versions are worse than official ones." that your personal. Don't use your standard to put to other people. For me IntelLLVM faster in my test

[kedautinh12]

I am a bit surprised about the last two posts.
@Barough did the 2nd post in this thread, with personal builds in Jan 2023.
And now, around 11 months later you demand, not to post personal builds...
A little bit late!

I can understand your intention to not confuse users, but this is a tech forum, where ppl try to optimize their encoding.
There are tmod builds here, compiles with gcc, intel, ms,
builds with included libs like libswscale, libavformat, ffmpegsource, lsmash and so on.

As long someone wrote down his "additions" to the build like "(libswscale 7.6.100)(libavformat 60.18.100)(ffmpegsource 3.1.1.0)(lsmash 2.16.1)"
or "built with GCC 13.2.0" all should be fine

This thread was for me a source of new releases (and builds) and a chance to not search several sites, forums and threads around the net.

He can't mention Barough that because "Barough excellent updated recopilation" in his first post. When Barough just post built with GCC 13.2.0 it's fine. But i post r4035 build with IntelLLVM and clang it confused. That show double standard guy. And here have some people like that, example: R.D. I post only "thanks", he said i spam the post. But Selur just post "thanks" more than me, he said it's fine :D

Additional: fdk-aac not legal but he don't mention Barough:D

[guest]

He can't mention Barough that because "Barough excellent updated recopilation" in his first post. When Barough just post built with GCC 13.2.0 it's fine. But i post r4035 build with IntelLLVM and clang it confused. That show double standard guy. And here have some people like that, example: R.D. I post only "thanks", he said i spam the post. But Selur just post "thanks" more than me, he said it's fine :D

Additional: fdk-aac not legal but he don't mention Barough:D

It's clearly "who you know, NOT, what you know"....sad really :(

[tebasuna51]

This thread was for me a source of new releases (and builds) and a chance to not search several sites, forums and threads around the net.

Ok, that was the purpose of this thread, y only demand to be clear about the differences between builds.
If I read Avs+ r4035 from 2023/12/02 and after another from 2023/12/05 I suppose the second one is better or solve some bug. And, for me, that is not true.

I'm not the owner of this forum and you can link anything under your responsibility.

I don't know if fdk-aac is not legal in all the countries, it is illegal in the mine but I don't use it because qaac is free and better, for me of course, and I don't need fdk-aac at all.

I am a old man, and I don't speak/write english very well, but argue preferences over a user or other is a children argument far of my intenttions.

[kedautinh12]

Yeah, old man with double standard. Why it's solve some bug when it's same commit (r4035). That your standard not other people. And i'm not said it's better than pinterf's build. It's from your thinking too. On internet not talk about ages, it's base equal relationship. When you treated double standard with me, that show you don't respect me so why i must respect you?
https://forum.doom9.org/showthread.php?p=1994786#post1994786

[kedautinh12]

So, if you don't use it, it'll legal. Wow, "very good" standard. Talk about Barough's x264 personal build. He just post "x264-0.164.3172_c1c9931_Win_GCC132", c1c9931 show that same commit from Videolan (https://artifacts.videolan.org/x264/) so why you think it solved bugs and GCC132 show that better build than videolan??? Are you sure all people use x264 will faster with GCC132??? If not, why you don't mention Barough need explain clearly than just "x264-0.164.3172_c1c9931_Win_GCC132", double standard old man?

[Barough]

Let's stop bitching about this and that.
I think that stable compiles made from the official source is fine to post since it's untouched and many places dont offer official builds/releases neither on odd encoders and such.
The only thing im against in here is test/trial builds since they can contain a lot of bugs and such.
Now i said what i had on my mind.

And this thread is really in need of a cleanup....... some really old and outdated stuff. Everyone that have made posts in here can maybe cleanup their old/outdated stuff.