Closed GoogleCodeExporter closed 9 years ago
attached screenshot: image is an upsampled frame of a (282,231) size decoded
output from libvpx. seems like the problem is webrtc libyuv wrapper does not
support odd size frames.
Original comment by marpan@google.com
on 1 Jun 2012 at 9:58
Attachments:
notice red blob next to face
Original comment by marpan@google.com
on 1 Jun 2012 at 9:59
This appears to be a problem in the webrtc chroma plane size calculation.
The address of the Y and U are right but the V is miscalculated when the size
of image is odd.
Original comment by fbarch...@google.com
on 2 Jun 2012 at 12:22
fix for this is here: https://webrtc-codereview.appspot.com/633004/
will update the unittests.
Original comment by marpan@google.com
on 2 Jun 2012 at 12:59
[deleted comment]
fix is verified. can close the issue.
Original comment by mar...@webrtc.org
on 4 Jun 2012 at 10:07
Fix was on webrtc side, allocating enough memory for odd sized images,
computing size of each plane correctly, and passing correct stride values for
rows.
No libyuv changes needed.
Original comment by fbarch...@google.com
on 4 Jun 2012 at 10:20
Original issue reported on code.google.com by
fbarch...@google.com
on 1 Jun 2012 at 6:51