3 ms·
Some honest questions: Does the caller of this API need a patent license to do so? Does the patent license of H.264 cover decoding of the format through OS API
by mmastrac 17y ago
Some honest questions:
Does the caller of this API need a patent license to do so? Does the patent license of H.264 cover decoding of the format through OS APIs, or does each caller need its own license?
- astrange 17y agoOf course you don't. That would be like having to get your own patent license to use iTunes. Although you do actually need a license to use the QuickTime AAC encoder in your own program, but only on Windows. Or so I remember from mailing list traffic, haven't tried it myself.
- Petter 17y agoYes you will need it, not for using quicktime, but this is a low level API where you will implement a lot of patent stuff yourself.
- astrange 17y agoOh, I forgot this reply existed. It isn't. An example of an API that does would be XvMC, which requires parsing and doing large parts of the video decode yourself. The most you'd have to to use this framework is parse a .mp4 file yourself. Such things are not patented.
- ZeroGravitas 17y agoI believe you pay per "branded decoder" in software, and you pay more for a "branded decoder" intended to be included in an operating system. You would hope that the extra fees would cover the downstream, but the "branded" language makes it sound like you'd have to be explicit that you're calling out to Quicktime or whatever. Obviously with hardware, as with OS decoders, you're expecting it to be called by others but again the "branded" language may confuse matters. Plus, you're almost certainly only covered for "personal and non-commercial" decoding in any of these cases.