In v0.5, the pixel data encoder interface was adjusted so that encoding options could be specified by the consumer. There are still a few limitations:
There are attributes which should be added or updated in the event of pixel data re-encoding (such as Lossy Image Compression), and the encoder does not have a way for the current method signature to return these.
It is an all or nothing operation: the encoder will encode and push all encoded frames onto the destination, even though in practice they might have to be laid out in separate fragments.
Version 0.6 should bring changes to the PixelRWAdapter interface to fulfill these requirements.
Enet4
commented
1 year ago
In v0.5, the pixel data encoder interface was adjusted so that encoding options could be specified by the consumer. There are still a few limitations:
Version 0.6 should bring changes to the
PixelRWAdapterinterface to fulfill these requirements.