Re:FFmpeg for browser and Node, powered by WebAssembly
by ksec on Saturday August 21, 2021 @07:05PM
(#28261360)
IANAL the patent are required only if your devices does not already have an H.264/H.265 license.
H.264 is fine as it is literally the MP3 of Video. H.265 is a lot more complicated.
Re:FFmpeg for browser and Node, powered by WebAssembly
by kkielhofner on Saturday August 21, 2021 @07:25PM
(#28261494)
That is true but if you’re using libx264/libx265 you’re not using hardware encode/decode blocks that include the patent license so MPEG-LA is back in the picture.
Re:FFmpeg for browser and Node, powered by WebAssembly
by ksec on Saturday August 21, 2021 @10:19PM
(#28262327)
Again IANAL but license are per devices and not per IP blocks so you dont double pay for each and every components ( Hardware Encode Decode in CPU and GPU ). And generally speaking that is up to the OEM and Devices Manufactures to have it done.
Re:FFmpeg for browser and Node, powered by WebAssembly
by kkielhofner on Monday August 23, 2021 @11:24AM
(#28277248)
IANAL disclaimer as well but each component (hardware block, x264/x265 instance) is (IIRC) considered a separate "unit" [0].
[0] Slide 10, bullet one https://www.mpegla.com/wp-content/uploads/avcweb.pdf
https://www.mpegla.com/
It trips people up: the commercial x264/x265 license provides alternate use terms on the implementation. The implementation, however, is still protected by various patents worldwide and MPEG-LA is who you go through for access to the patent pool which is (supposed to) include payment to all of the identified patent holders.