It doesn't really matter even if there are, in the case of hardware implementations -- because hardware decoders/encoders are typically fixed-function hardware blocks with fixed functionality. They are not designed for flexibility or reuse between formats. They are designed for exactly 1 function and nothing else.
Even if AV1 and VP9 share structurally similar components, no VP9 decoder is going to work out of the box. It may mean that people who produce AV1-capable encoding/decoding hardware have a better starting point, though (provided they had VP9 hardware, beforehand)
AFAIK a lot of "hardware" codecs are DSPs with some extra instructions that are good for video (like sum of absolute differences). In theory maybe they could support new algorithms with a firmware update. In reality, such firmware may simply not be developed or the DSP may not be fast enough to run a new codec.
It doesn't really matter even if there are, in the case of hardware implementations -- because hardware decoders/encoders are typically fixed-function hardware blocks with fixed functionality. They are not designed for flexibility or reuse between formats. They are designed for exactly 1 function and nothing else.
Even if AV1 and VP9 share structurally similar components, no VP9 decoder is going to work out of the box. It may mean that people who produce AV1-capable encoding/decoding hardware have a better starting point, though (provided they had VP9 hardware, beforehand)
Right but I guess I’m asking if they COULD be or if you’d need like a FPGA for that.
AFAIK a lot of "hardware" codecs are DSPs with some extra instructions that are good for video (like sum of absolute differences). In theory maybe they could support new algorithms with a firmware update. In reality, such firmware may simply not be developed or the DSP may not be fast enough to run a new codec.
4 replies →
There are. That's the reason we got instruction set extensions like simd.