New versions of free software used in the GUI's

[seagate]

Repack – Visual C++ redistributable runtimes v.0.83.0 (https://github.com/abbodi1406/vcredist/releases/tag/v0.83.0/)

[Jamaika]

ffmpeg version 7.1.0-66c05dc0 Copyright (c) 2000-2024 the FFmpeg developers
built with GCC: (GNU) 11.5.0 (SIMD) AVX
configuration: -std=gnu++11 -march=x86-64-v2 -ftree-vectorize -g0 -O3 -fPIC -mavx -mxsave -mpclmul -maes -o lib/ffmpeg.exe fftools/ffmpeg.o fftools/ffmpeg_dec.o fftools/ffmpeg_demux.o fftools/ffmpeg_enc.o fftools/ffmpeg_filter.o fftools/ffmpeg_hw.o fftools/ffmpeg_mux.o fftools/ffmpeg_mux_init.o fftools/ffmpeg_opt.o fftools/cmdutils.o fftools/objpool.o fftools/opt_common.o fftools/sync_queue.o fftools/thread_queue.o -Llib -lavdevice_x64 -lavfilter_x64 -lavformat_x64 -lavcodec_x64 -lswresample_x64 -lswscale_x64 -lavutil_x64 -lpostproc_x64 -lwebp_x64 -lopenjpeg_x64 -lsvtjxs_x64 -ljxl_x64 -lcodec2_x64 -lgsm_x64 -logg_x64 -lvorbis_x64 -ltheora_x64 -llc3_x64 -lsnappy_x64 -lxavs_x64 -ldavs2_x64 -lxavs2_x64 -luavs3d_x64 -luavs3e_x64 -ltwolame_x64 -lspeex_x64 -lshine_x64 -lmp3lame_x64 -lxvid_x64 -lfdk-aac_x64 -lopenh264_x64 -lx264_opencl_0810bit_x64 -lkvazaar_x64 -lx265_081012bit_x64 -luvg266_x64 -lxevd_x64 -lxeve_x64 -lcelt_opus_silk_x64 -lvpx_x64 -ldav1d_x64 -laom_x64 -lass_x64 -lrsvgdec_x64 -lcairo_pixman_x64 -l:fribidi_x64.a -l:freetype_harfbuzz_x64.a -lxml2_x64 -llcms2_x64 -l:zlib_x64.a -l:bzip2_x64.a -l:lzma_x64.a -lvmaf_x64 -l: opencv2_opencl_x64.a -l: opencl_x64.a -l:quirc_x64.a -lqrencode_x64 -lpthread_x64 -L. -lcfgmgr32 -ldnsapi -ldwrite -lbcrypt -liphlpapi -lgdi32 -lopengl32 -lole32 -loleaut32 -lsecurity -lshlwapi -lstrmiids -luuid -lvfw32 -lws2_32

https://github.com/netwide-assembler/nasm/commit/6ad3bab7fe6cfec52308c90c5e7d97b9ef81c3c6

Video Codec
https://bitbucket.org/multicoreware/x265_git/commits/1cb70f6b44247a069163ab79c213620bfc3b1bf6
https://github.com/cisco/openh264/commit/fa6d0994964d423ebad020d0f5c36f98b6532117
https://github.com/mpeg5/xeve/commit/f269812ebbb2214b35ac28c4aff2a603e4ed52ac
https://github.com/mpeg5/xevd/commit/be6c2049074a68967cf2da660ee1866fd9658de6
https://github.com/webmproject/libvpx/commit/fcd1f39e569eeb8d9956ab6f44193c55a7337e76
https://github.com/jbeich/aom/commit/f6b976de024e998f19d3f8c3ed045e3273fcc288
https://github.com/webmproject/libwebp/commit/f9a480f7c3fdaf921d9366aeb9c37e64e551995d
https://github.com/ultravideo/kvazaar/commit/2f9a21423a1ef666c93f15e2068bcde979d20f7e

https://gitlab.freedesktop.org/cairo/cairo/-/commit/bbf385d35c5b3913cf7dce369d2e363a460aafcc
https://gitlab.freedesktop.org/freetype/freetype/-/commit/c4e6791f8286128714a9bd9d2be5b3a53ed8f89e
https://gitlab.freedesktop.org/pixman/pixman/-/commit/b753a6f49b9b0ec5df84aff10e174601545bdf79
https://gitlab.gnome.org/GNOME/glib/-/commit/02ffe6a7794de5fe70276e8fa816ef2110109f3f
https://gitlab.gnome.org/GNOME/pango/-/commit/01547b2678bae3efdd9e62f1bdcc89d95f1aea01
https://gitlab.gnome.org/GNOME/libxml2/-/commit/f2c48847fa58fcd1ffda4863295cd7e486657e68
https://github.com/PCRE2Project/pcre2/commit/bfca266959547a5133aaf6faeba56d335e059fd0
https://github.com/harfbuzz/harfbuzz/commit/a411de2b3ee3ebc3e52fc4704451fdb581e97154
https://github.com/libass/libass/commit/1774117b8048d6296c79425cfbb1086bcd2ac2fa

https://github.com/mm2/Little-CMS/commit/0eb5c4d1a827225d923dc8458e6241428f40daf5
https://github.com/Netflix/vmaf/commit/d95b69e03d9401ad9f3532eaab14066427761c35

AVSX codecs have numerous warnings Wshift-negative-value.
https://www.sendspace.com/file/k5c3pi

[LigH]

M-AB-S now included support for libvvenc in ffmpeg (which was already possible before if you knew you could enable it manually).

[Selur]

nice, so with some luck the synth source filters will support it too in a not to distant future :)

[LigH]

nice, so with some luck the synth source filters will support it too in a not to distant future :)

Source filters would use vvdec, not vvenc.

Plus, there is an issue with the pkg-config (https://github.com/m-ab-s/media-autobuild_suite/issues/2756).

[Selur]

damn,...

[guest]

x265 v3.6+76
Built on August 16, 2024, GCC 14.1.0

https://bitbucket.org/multicoreware/x265_git/commits/branch/master

DL :
https://www.mediafire.com/file/1u616cvvbh8ufwx

FYI, I cannot use any of these new "generation" builds with RipBot264 :(

""\\RYZEN-9-7950X\Ripbot264temp\Tools\ffmpeg\bin\ffmpeg.exe" -loglevel panic -i "\\RYZEN-9-7950X\RipBot264temp\job3\Chunks\1.avs" -strict -1 -f yuv4mpegpipe - | "\\RYZEN-9-7950X\Ripbot264temp\tools\x265\x265_x64.exe" --seek 0 --colorprim bt2020 --transfer smpte2084 --colormatrix bt2020nc
--master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(40000000,50)" --crf 16 --fps 24000/1001 --min-keyint 24 --keyint 240 --frames 3610 --sar 1:1 --level 5.2 --profile main10
--output-depth 10 --ctu 64 --high-tier --vbv-bufsize 240000 --vbv-maxrate 240000 --y4m --pools "32" --output "\\RYZEN-9-7950X\RipBot264temp\job3\Chunks\1.265" -"

x265 [WARN]: extra unused command arguments given <->

[LigH]

That's because recent x265 encoders may support multiple sources now (e.g. for MVC encoding) and had to change the CLI parsing rules; RipBot264 needs to add "--input" before the "-" now.

[guest]

That's because recent x265 encoders may support multiple sources now (e.g. for MVC encoding) and had to change the CLI parsing rules; RipBot264 needs to add "--input" before the "-" now.

I just wanted to let Barough know directly...

I am aware of the change, and the dev of RipBot264 has been informed...just not sure whether he'll bother to update anything :(

http://msystem.waw.pl/x265/ haven't update yet, Patman hasn't, but Jpsdr has, with his recent release.

I guess it will effect most apps.

[Guest]

x265 v3.6+103
Built on August 30, 2024, GCC 14.1.0

https://bitbucket.org/multicoreware/x265_git/commits/branch/master

DL :
https://www.mediafire.com/file/0wor4kj4ox7mjz6

Not that it probably matters anymore, but I'm still getting this error:-

x265 [warning]: extra unused command arguments given <->

[LigH]

I really expected this complaint from you...

Nobody reported yet that the suggested patch to fix this bug was already committed.

Patience. We will tell you when it's available.

Or maybe someone applies it manually, they it will be announced next to their release.

[Guest]

I really expected this complaint from you...

Nobody reported yet that the suggested patch to fix this bug was already committed.

Patience. We will tell you when it's available.

Or maybe someone applies it manually, they it will be announced next to their release.

Well, I didn't disappoint you then....

And that's why I comment after every new release I find..

I'm just not sure why Barough keeps wasting his time (and ours) releasing new builds that don't work.

You say manually, CAN this be added to the x265 command line ??

[LigH]

I am just trying to build a patched version. Patience...

[LigH]

New upload: x265 3.6+103-85f1e34+pipefix (https://www.mediafire.com/file/oei7rjjxiilvaur/x265_3.6+103-85f1e34+pipefix.7z/file)

[Windows][GCC 14.2.0][32/32XP/64 bit] 8bit+10bit+12bit

No serious changes in intel x86[-64] code. Added the patch to fix Y4M pipe handling prior to its commit.

[Selur]

Added the patch to fix Y4M pipe handling prior to its commit.
Thanks, did a quick test, seems to fix the pipe problem, so let's hope they commit this soon to the main branch.

Cu Selur

[Guest]

New upload: x265 3.6+103-85f1e34+pipefix (https://www.mediafire.com/file/oei7rjjxiilvaur/x265_3.6+103-85f1e34+pipefix.7z/file)

[Windows][GCC 14.2.0][32/32XP/64 bit] 8bit+10bit+12bit

No serious changes in intel x86[-64] code. Added the patch to fix Y4M pipe handling prior to its commit.

I'm still getting this:-

x265 [warning]: extra unused command arguments given <->

So clearly there's more than one issue going on here, and/or, despite the "pipefix" it's something that the dev needs to address.

[Selur]

So clearly there's more than one issue going on here, and/or, despite the "pipefix" it's something that the dev needs to address.
Yes, the pipe issue and the 'extra unused command arguments' issue that appear depending on the way x265 cli is called, are different things.
(I only ran into the pipe issue, since the calls Hybrid generates for x265 do not triggered the pipe issue. :))

Cu Selur

[LigH]

@FTLOY:

Did RipBot264 already fix the x265 calling command line?

If not, then blame Atak_Snajpera, not MultiCoreWare or even me. Or, better don't. I uploaded my patched build just yesterday, and I don't expect him to use mine immediately, preferred over an official build.

Patience.
Patience.
Patience.
...

Until confirmedly fixed, use the last working builds. Newer builds don't contain any changes relevant for better quality or efficiency on x86* CPUs, anyway.

[Guest]

@FTLOY:

Did RipBot264 already fix the x265 calling command line?

If not, then blame Atak_Snajpera, not MultiCoreWare or even me. Or, better don't. I uploaded my patched build just yesterday, and I don't expect him to use mine immediately, preferred over an official build.

Patience.
Patience.
Patience.
...

Until confirmedly fixed, use the last working builds. Newer builds don't contain any changes relevant for better quality or efficiency on x86* CPUs, anyway.

No, RipBot has not been updated, and I'm not holding my breath, either, it would take someone more "important / influential" than me to get him to do anything, he doesn't even like me using Patman or JPSDR builds !!!

One things for sure, eventually it will have to be updated.

So "official" builds get posted here ???

http://msystem.waw.pl/x265/

[seagate]

DGDecNV 255 (06.09.2024) (https://www.rationalqm.us/dgdecnv/binaries/)

[LigH]

New uploads (MSYS2, MinGW32 / MinGW64, GCC 14.2.0):

MP4Box 2.5-DEV-rev503-g25797108-ab-suite (https://www.mediafire.com/file/x2v56tvk079dotd/MP4Box_2.5-DEV-rev503-g25797108-ab-suite.7z/file)

MediaInfo CLI 24.06 (https://www.mediafire.com/file/ghguvym5op6zysf/MediaInfo_CLI_24.06.7z/file)

[tormento]

DGDecNV 255 (06.09.2024)
Sometimes, having strange CUDA errors when aborting/launching an encode.

Unfortunately I can't find the previous hotfix release, anyone?

[tebasuna51]

Unfortunately I can't find the previous hotfix release, anyone?
This is from 22/07/2024: https://www.mediafire.com/file/q38ubmviu0jmvmk/dgdecnv_255.zip/file

[tormento]

This is from 22/07/2024
:thanks:

[seagate]

DGDemux v.1.0.0.75 (28.09.2024) (https://www.rationalqm.us/dgdemux/binaries/)

[Wishbringer]

x264 0.164.3192 c24e06c
GCC v14.2.0 / Win32/64
...
DL :
https://www.mediafire.com/file/gra4vvgg329xbkw

Link not working...
x265 works, but x264 not.

[Wishbringer]

x264 link works just fine

Not here
Quote from MediaFire:
„Well, looks like we can‘t go any further
The file you requested has been blocked for a violation of our Terms of Service“

[LigH]

Something similar happened for me when I uploaded binaries of Xvid there. Seems that they may blacklist words in filenames which are common in pirated moviez.

[tebasuna51]

ffmpeg version 7.1.0-9d3cdf8f with avisynthplus 3.7.3-2b55ba4

ffmpeg 7.1-1 still without support avs+ 3.7.3 audio channelmask

[Jamaika]

ffmpeg 7.1-1 still without support avs+ 3.7.3 audio channelmask
Maybe. I'm not an avisynth expert. The codecs must be installed under Windows (vfw) to work. Provide examples of channel mask plugins.

[LigH]

I need an experienced author of AviSynth plugins to help me develop an audio plugin ... no replies until today.

[seagate]

x264-r3193-3a8b5be (06.10.2024) (https://artifacts.videolan.org/x264/release-win64/)

[tebasuna51]

I need an experienced author of AviSynth plugins to help me develop an audio plugin ... no replies until today.
I make the last versions of NicAudio.dll (32 bits) but it's a decoder with a external input file and with a old avisynth.h.

Maybe you need see the last soxfilter.dll sources from pinterf
(https://github.com/pinterf/SoxFilter/releases)

[Arx1meD]

When I use X265 with Patman Mods, errors appear:
x265 [WARN]: extra unused command arguments given <->
[vost#0:0/wrapped_avframe @ 000001e81f0e8240] [error] Error submitting a packet to the muxer: Invalid argument
[vost#0:0/wrapped_avframe @ 000001e81f0e8240] [error] Error submitting a packet to the muxer: Invalid argument
[out#0/yuv4mpegpipe @ 000001e81f0e5300] [error] Error muxing a packet
[out#0/yuv4mpegpipe @ 000001e81f0e5300] [error] Task finished with error code: -22 (Invalid argument)
[out#0/yuv4mpegpipe @ 000001e81f0e5300] [error] Terminating thread with return code -22 (Invalid argument)
[out#0/yuv4mpegpipe @ 000001e81f0e5300] [error] Error writing trailer: Invalid argument
[out#0/yuv4mpegpipe @ 000001e81f0e5300] [error] Error closing file: Invalid argument
Redistribuable Package Visual Studio 2015-2022 installed. Other builds X265 work normal.
Does anyone know why errors appear?

[Wishbringer]

@Arx1meD

x265 [WARN]: extra unused command arguments given <->
Maybe because newer builds need explizit "--input inputfilename" instead of just "-"

See here:
https://forum.doom9.org/showthread.php?p=2006886#post2006886

[LigH]

Maybe you need see the last soxfilter.dll sources from pinterf
(https://github.com/pinterf/SoxFilter/releases)

I can also read the source of Shibatch SSRC which is shipped with the AviSynthPlus package used in M-AB-S.

But that does not help me. I have no active experience in C++ development. I don't know how to edit all files required by GCC to compile a whole project.

All I can provide is the idea, the algorithm, the documentation for the AviSynth Wiki.

[Arx1meD]

Wishbringer, Thank you! It helped.

[LigH]

Mildly interesting, Jamaika, but does not concern me at all.

[seagate]

Repack – Visual C++ redistributable runtimes v.0.84.0 (https://github.com/abbodi1406/vcredist/releases/tag/v0.84.0/)

[seagate]

x264-r3194-1243d9f (16.10.2024) (https://artifacts.videolan.org/x264/release-win64/)

[seagate]

x264-r3196-3a21e97 (23.10.2024) (https://artifacts.videolan.org/x264/release-win64/)

[seagate]

DGDemux v.1.0.0.76 (28.10.2024) (https://www.rationalqm.us/dgdemux/binaries/)

[seagate]

DGDemux v.1.0.0.77 (29.10.2024) (https://www.rationalqm.us/dgdemux/binaries/)

[LigH]

It took me a while to understand, but I guess now I got it ... you are linking Avisynth and plugins statically into your build of ffmpeg? :scared:

[Jamaika]

Yes, but I won't answer whether it makes sense. I haven't tested plugins. I'm wondering more whether to remove the ability to add plugins in avisynth, for example to avoid adding a virus.
I post my inept suggestions on github with .7z files.
https://github.com/Jamaika1/plugins_ffmpeg701_mingw1150

[seagate]

Repack – Visual C++ redistributable runtimes v.0.85.0 (https://github.com/abbodi1406/vcredist/releases/tag/v0.85.0/)

[Xuqiwu]

MediaInfo v24.11
https://mediaarea.net/en/MediaInfo/Download

[seagate]

DGDemux v.1.0.0.77 (07.11.2024) (https://www.rationalqm.us/dgdemux/binaries/)

[LigH]

New upload (MSYS2; MinGW32 / MinGW64: GCC 14.2.0):

kvazaar v2.3.1-25-ga71354e (https://www.mediafire.com/file/z3kylbq50yy6t77/kvazaar_v2.3.1-25-ga71354e.7z/file)

[tormento]

kvazaar v2.3.1-25-ga71354e
You made me curious. How does it compare to x265?