obs-StreamFX VS FFmpeg

Are you using the blur plugin from here, because there are different types of mask modes https://github.com/Xaymar/obs-StreamFX/wiki/Filter-Blur

StreamFX is not paywalled off, they had an issue with non-GPL code in the repo with the GPL-licensed code. They just updated the Wiki with build instructions. I have to get this built today, it's messing everything up not to have StreamFX in OBS 29. https://github.com/Xaymar/obs-StreamFX/wiki/Building

Yes, it's this one: https://github.com/Xaymar/obs-StreamFX/wiki/Filter-Dynamic-Mask

https://www.xaymar.com/guides/obs/high-quality-recording/ https://www.xaymar.com/guides/obs/high-quality-recording/nvenc/ https://github.com/Xaymar/obs-StreamFX/wiki/Encoder-FFmpeg-NVENC

I downloaded the newest beta of StreamFX for OBS, installed it exactly as they said on my Windows 10 machine, and OBS refuses to recognize the plugin when I open it. No additional filters, no StreamFX tab in the top toolbar, nothing. I've tried downloading for all users and just me. I've tried manually moving the installed plugin from /ProgramData/ to /Program Files(x86). OBS just does not acknowledge that any plugin is present. Using OBS 29.0 and the beta that's supposed to run on 29.0.

If you're technically adept enough to know what NVENC and HEVC are, then it's not too difficult to understand and setup OBS with StreamFX and follow the guide.

for obs 28 you'll need the beta: https://github.com/Xaymar/obs-StreamFX/releases

FFmpeg (https://ffmpeg.org/)

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.