Tdarr VS FFmpeg

You could also use tdarr to automate transcoding as soon as stuff enters your library so that it’s direct playable when you decide to watch it, but I’ve never needed to try it

The only place I can find mention of the script is Tdarr_Server is not closing exiftool.exe after use. #423 and tdarr_server.exe crashes often #412

I've had issues with my 11600k and now 11400 in unraid too. Though it's CPU encoding in my case. See https://github.com/HaveAGitGat/Tdarr/issues/777 .

So I read through this issue and I have a couple nodes setup, some with QSV and others with NVENC. The respective node capabilities are designated for exactly one of QSV or NVENC.

Have a look at Tdarr for distributed transcoding. I have it on a few nodes and it’s been pretty easy on the network.

I have created a feature request in the Tdarr GitHub page; https://github.com/HaveAGitGat/Tdarr/issues/772

You can also use tdarr if you have more than 1 file it can auto transcodes multiple files in a directory all at once. https://github.com/HaveAGitGat/Tdarr

or this: https://github.com/HaveAGitGat/Tdarr

GPL2

Since FFmpeg is GPL2, doesn’t that require CompressX to disclose its source code?

IANAL, apologies if I miss understand license requirements.

https://github.com/FFmpeg/FFmpeg?tab=License-1-ov-file

This turns out to be a lot of assembly macros to help write one x86 assembly. https://github.com/FFmpeg/FFmpeg/blob/master/libavutil/x86/x...

The sibling comment recommending compiler intrinsics is probably the best way to go for writing SIMD code. A mixture of `` style types and intrinsics to specify instructions is a solid 90% solution compared to assembly.

If you want that last 10%, I think macros are putting the emphasis in the wrong place. They're a somewhat easy way to build up a language abstraction which will work if held carefully, but I'm confident the dev experience using this abstraction when you write invalid code will be deeply confusing.

I would suggest to write a parser instead of the macros. That'll tell you clearly when the syntax is invalid (though possibly not with much precision) and it'll give you a place to put semantic analysis for where valid syntax encodes nonsense. Do the equivalent of the macro expansions on the parsed tree instead of on the text. Emit asm as the "back end".

You might have heard of FFMPEG or ImageMagick for image and video edition in a programmatic way. MoviePy is a Python module for video editing (Python wrapper for FFMPEG and ImageMagick). It provides functions for cutting, concatenations, title insertions, video compositing, video processing, and the creation of custom effects. It can read and write common video and audio formats and be run on any platform with Python 2.7 or 3+.

There are many cloud-based tools and websites that can convert your images, but the problem with these tools is that you usually have to upload the files for them to be processed, and some of their services are not free. In this article, I'd like to introduce a piece of software called FFmpeg, which allows you convert the images locally with one simple command.

To run the demo locally, be sure to have Python 3.11 and FFmpeg installed.