• 0 Posts
  • 61 Comments
Joined 16 days ago
cake
Cake day: October 7th, 2024

help-circle




  • @reallyzen @N0x0n kdenlive uses ffmpeg so formats it has available depend upon what is compiled into your ffmpeg which for many linux distros is minimal. However, if you grab FFmeg from github, then configure it for every possible option and install all of the necessary libs (some of which you will also need to compile because most Linux distros do not include all of them), THEN kdenlive will have all possible output formats presently supported by opensource, but there are literally several hundred libraries and options needed, this and the configure file is a real piece of shit that rather than telling you every library that is missing so you can go chase them down all in one shot, instead tells you the first one missing and aborts, so you chase that down, run it again, and this literally takes about 300 iterations. But if you go through the trouble of doing all this and then put YOUR FFmpeg in the $PATH ahead of the system one, kdenlive will now show all the available formats for both input and output.
















  • @Mwa @wildbus8979 Yes, early on there was AT&T and Berkley, System-V became AT&T’s mainstream though there were off-shoots like CB-Unix for PDP11/70’s which only had 64k I+D space, and Berkeley had 4.2 and 4.3BSD, and now you have offshoots of those, such as FreeBSD and NETBSD, MacOS is a highly mutilated BSD sitting atop a Mach micro-kernel with the Mac finder sitting on top of the whole mess. The Mach microkernel provides a layer of hardware abstraction that makes it easy to jump between architectures as Mac has often done. What I do not like about MacOS is that they include only drivers necessary for their hardware and forbid the use on Non-Mac’s by license. This limits your selection of things like video cards to those they specifically chose to use.