OpenJPEG Plugin

Sebastian Dröge sebastian at centricular.com
Thu May 12 05:27:18 UTC 2016


On Mi, 2016-05-11 at 13:55 -0400, Aaron Boxer wrote:
> 
> 
> On Wed, May 11, 2016 at 2:06 AM, Sebastian Dröge  wrote:
> > On Di, 2016-05-10 at 13:19 -0400, Aaron Boxer wrote:
> > > 
> > > Sebastian, can you please elaborate on how the API change made it
> > > less efficient?
> > > I contribute to the project, so if you can advise on improving the
> > > API, I can try to get this implemented.
> > 
> > I can't remember details unfortunately, but it somehow related to the
> > new file-style API with read/write functions. And after the porting,
> > the encoder/decoder were both considerably slower, but I didn't look
> > closer back then.
> > 
> > Sorry for not having a more useful answer, I would have to look in more
> > detail again.
> Thanks. I will look into this when I have  time.

It was also about requiring to copy more data than before.

Ideally openjpeg would directly work on our input data without copying,
and we could pass its output data directly onwards without copying. But
that was also not the case before IIRC.

-- 
Sebastian Dröge, Centricular Ltd · http://www.centricular.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 949 bytes
Desc: This is a digitally signed message part
URL: <https://lists.freedesktop.org/archives/gstreamer-devel/attachments/20160512/3311a998/attachment.sig>


More information about the gstreamer-devel mailing list