External segmentation maps not working (VP8E_SET_ROI_MAP)

Chen-tao / webm

Automatically exported from code.google.com/p/webm

0 stars 0 forks source link

External segmentation maps not working (VP8E_SET_ROI_MAP) #411

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

As reported here[1], the ROI map feature is currently broken.

* The user's segmentation map is not used on the initial keyframe
* Segmentation is enabled on subsequent frames, but the map data update isn't, 
so the decoder never gets a copy of the map the encoder is using.

[1] 
http://groups.google.com/a/webmproject.org/group/apps-devel/browse_thread/thread
/11818a66bc068508#

Original issue reported on code.google.com by jkoles...@google.com on 21 Mar 2012 at 6:19

GoogleCodeExporter commented 9 years ago

Original comment by albe...@google.com on 29 Mar 2012 at 6:08

Changed state: Available
Added labels: Mstone-10, Pri-3
Removed labels: Pri-2

GoogleCodeExporter commented 9 years ago

Moving to next milestone

Original comment by albe...@google.com on 12 Apr 2012 at 6:05

Added labels: Mstone-11, Pri-2
Removed labels: Mstone-10, Pri-3

GoogleCodeExporter commented 9 years ago

Original comment by jimbankoski@google.com on 24 May 2012 at 6:34

GoogleCodeExporter commented 9 years ago

There is a fix to this bug pending review.

However I also note that the documentation appears to be incorrect.
I believe that the valid range of input values for both delta_q and delta_lf
is [-63 to +63] not [-64 to +64] and [-32 to +32] as described in
http://www.webmproject.org/tools/vp8-sdk/structvpx__roi__map.html#_details

Original comment by paulwilk...@google.com on 19 Jun 2012 at 11:49

Changed state: Fixed