FFmpeg vs x265 + AVS/VPY ?

[Nico8583]

Hi,
I would like to know if there is an interest to use x265 + AVS/VPY instead of FFmpeg ?
Any speed gain ? Any quality gain ? With the same parameters of course.
Thank you.

[MeteorRain]

I've never used ffmpeg to do x265 encoding. Always AVS/VPY piped to x265. I'm not seeing any benefits using ffmpeg in my use case.

[Nico8583]

Thank you. FFmpeg is easier to use than create a script and pipe to x265 when the script is very basic. What do you use to pipe for each ?

[MeteorRain]

avs4x264mod if I understand your question correctly.

[Nico8583]

Thank you

[Nico8583]

Two years later, I'm getting up this topic to get new tips if anyone has it
Is there a difference (quality, speed) between FFmpeg as decoder+encoder versus AviSynth/VapourSynth (with plugins ?) as decoder + x265 as encoder ? Without any filters, just serve the source as it.
Thanks !

[FranceBB]

Originally Posted by Nico8583

Two years later, I'm getting up this topic to get new tips if anyone has it
Is there a difference (quality, speed) between FFmpeg as decoder+encoder versus AviSynth/VapourSynth (with plugins ?) as decoder + x265 as encoder ? Without any filters, just serve the source as it.
Thanks !

Yes.
Technically, using FFMpeg would allow you to skip the indexing part and serve the decoded frames on the fly.
That being said, I've never used FFMpeg to decode and encode anything directly.
Also you would have no control over which build of libx265 is being used and which assembly optimizations have been used in the build (SSE, SSE2, SSSE3, SSE4.1, SSE4.2, AVX, AVX2, AVX512). On top of that, I don't trust FFMpeg 'cause I don't know if it's actually turning on some filters under the hood, so my suggestion is to stick with Avisynth + x265

[kolak]

Originally Posted by FranceBB

Yes.
Technically, using FFMpeg would allow you to skip the indexing part and serve the decoded frames on the fly.
That being said, I've never used FFMpeg to decode and encode anything directly.
Also you would have no control over which build of libx265 is being used and which assembly optimizations have been used in the build (SSE, SSE2, SSSE3, SSE4.1, SSE4.2, AVX, AVX2, AVX512). On top of that, I don't trust FFMpeg 'cause I don't know if it's actually turning on some filters under the hood, so my suggestion is to stick with Avisynth + x265

ffmpeg is fine. It doesn't turn on any filters just like that. You have full control. Also if at the end you need to mux elementary streams with ffmpeg your can actually have more problem when you use already existing streams.
Avisynth/vs has other more important benefits than this compared to ffmpeg. If you need a lot of filters then nothing can beat avs/vs.

ffmpge allows you to control builds- it always says which x264/5 build it's using and you can aways build ffmpeg with specific x264/5 version if needed.

If anything I'm not that confident with avs/vs input filters, except avi (plenty issues with frame accuracy, missing frames etc). For me it's avs/vs weakest part (ffms2 is far from been very reliable).

[Nico8583]

Thanks !
Which AviSynth version and which plugin (to serve H264/H265, FHD/UHD, HDR10/HDR10+/DoVi streams) would you recommend ? I'm using Windows 10 x64 and Ryzen 7 3700X.
Thanks.

[videoh]

Originally Posted by Nico8583

Thanks !
Which AviSynth version and which plugin (to serve H264/H265, FHD/UHD, HDR10/HDR10+/DoVi streams) would you recommend ? I'm using Windows 10 x64 and Ryzen 7 3700X.
Thanks.

Latest Avisynth+ together with DGSource (if you have an nVidia GPU).

[Nico8583]

Thanks kolak !
Which version/build of FFmpeg do you use ? And are you on Windows or Linux ?

[kolak]

It doesn't matter much which you use.
Use latest stable build.
I use own build as I needed more AAC encoding options.

[Nico8583]

Thanks !
I don't have an nVidia GPU, just an Intel GPU