OpenCL-AMD-Fedora VS FFmpeg

for me rocm-opencl doesn’t work. i have to use this: https://github.com/sukhmeetbawa/OpenCL-AMD-Fedora to use resolve. Although this package will give dependency issues with kernel-debug-devel-matched, but i’m not sure how much will it affect Fedora

I'm running Fedora 36 on my PC with a RX 6700 XT. I have installed OpenCL from the amdgpu-pro drivers using this script: https://github.com/sukhmeetbawa/OpenCL-AMD-Fedora. I've tested both Unity 2020.3.38f and 2021.3.9f1 and they both crash when trying to bake the light maps on the GPU. I installed Unity using the RHEL installation from this page https://docs.unity3d.com/hub/manual/InstallHub.html#install-hub-linux. Any help would be very much appreciated.

Current OS: Fedora Silverblue, therefore I would prefer a solution that's provided for this distro. However I've come to the understanding that commonly proposed solutions like sukhmeetbawa / OpenCL-AMD-Fedora don't seem to be suitable with Silverblue. Though I'd love to be corrected on this. But any and all distros will be considered as I'll manage with multi-boot.

I think DV may require the OpenCL driver userspace driver as provided by the proprietary amdgpu-pro driver. You could try the script from this repository to see if that solves your issue.

You can use this.

git clone https://github.com/sukhmeetbawa/OpenCL-AMD-Fedora.git

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.