Someone was posting recently how it cost him tens of dollars of LLM Agent time to reverse engineer Linux Davinci and add codec he wanted back in.
Someone was posting recently how it cost him tens of dollars of LLM Agent time to reverse engineer Linux Davinci and add codec he wanted back in.
This is one of the the cases where “the language model won't necessarily respect IP law” is really relevant. Individual users may be able to get away with this because they're too scattershot to sue, and users in some jurisdictions may actually be fine regardless, but broadly, the patent licensing around things like H.264 is not something BMD can afford to ignore. AFAIK the biggest reason Google was pushing WebM in the first place was because they, a huge corporation, were balking at being under the thumb of the MPEG LA!
I appreciate that it can be confusing for users that patents can still apply to techniques where implementations exist that are both libre and gratis from a copyright perspective, but this has been an issue for Linux-adjacent software distribution for ages—like, see how Debian used to put certain stuff that was encumbered by patents in the US but not in other jurisdictions in special “non-US” repository sections, that sort of thing. It's not Black Magic's doing that the codec space is like this. I wish people wouldn't make so many mocking assumptions sometimes.
Linux Vivaldi builds use libffmpeg.so from chromium-ffmpeg, which includes decoders for most codecs used on the web (no h265/mpeg2 tho), and VA-API which will handle all hardware accelerated codecs on particular platform.
This looks similar to using Microsoft provided Media Foundation codecs. No idea why Black Magic doesnt do it like Linux Chromium browsers.
Do you have any information on how the actual patent licensing is set up for Vivaldi? I wasn't able to find much on it, though I see the note in https://wiki.archlinux.org/title/Vivaldi that it “automatically downloads” the relevant files, which is at least suggestive that they can't just redistribute the binaries normally. The other closest thing I was able to find was https://github.com/chromiumembedded/cef/issues/3559 which describes a specific proprietary_codecs option in CEF, which is not quite the same thing but ought in some sense to be related… the way they describe having to set ffmpeg_brand=Chrome normally for that to be available doesn't sound promising?
I would be moderately surprised if whatever arrangement is going on there allows full use of the codecs for video editing software and not just for consumer decode of Web resources.