Issue 8 in webp2: Incremental encoding API

[mdupo… via monorail]

Status: Accepted
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 8 by mdupo...@gmail.com: Incremental encoding API
https://bugs.chromium.org/p/webp2/issues/detail?id=8

Hey, this is not an issue report, but a feature request, any chance you'll come up with an incremental *encoding* API with libwebp2?

Thanks for your work!

--
You received this message because:
1. The project was configured to send all issue notifications to this address

You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings

[pasca… via monorail]

Comment #1 on issue 8 by pasca...@gmail.com: Incremental encoding API
https://bugs.chromium.org/p/webp2/issues/detail?id=8#c1

Hi,

what would this API cover exactly? Readiness of the input samples?

The thing is: encoding needs multiple analysis passes (to get the geometry, block partitioning, symbol statistics, etc.). So waiting for the input samples is only a small part of the work.
And same of outputting the bitstream: it's a tiny fraction of the work.

[ahmed… via monorail]

Comment #3 on issue 8 by ahmed...@gmail.com: Incremental encoding API
https://bugs.chromium.org/p/webp2/issues/detail?id=8#c3

(No comment was entered for this change.)

Attachments:
sdk.js 10.7 KB

[quike… via monorail]

Comment #4 on issue 8 by quike...@gmail.com: Incremental encoding API
https://bugs.chromium.org/p/webp2/issues/detail?id=8#c4

Lamentable

[quike… via monorail]

Comment #5 on issue 8 by quike...@gmail.com: Incremental encoding API
https://bugs.chromium.org/p/webp2/issues/detail?id=8#c5

(No comment was entered for this change.)

Attachments:

error.json 42 bytes