Some cameras and media will immediately begin exposing orientation information. In uncommon cases this orientation may change. If orientation changes during encoding through VideoEncoder frames with different orientation than the first are currently encoded with incorrect size and orientation. However the operation completes without a hard error. During discussions in the media working group it was decided that these cases should instead throw a non-fatal exception during encode(). There is already precedent for exception handling during encode() so authors should already be handling this case.
Can you clarify if "uncommon" here means that some cameras are known to change the orientation and those cameras are typically rare, or that most cameras will change the orientation if say the user changes the orientation, but that user behavior is rare? :) This does seem to introduce a new exception reason that seems almost expected to happen in some cases. Can you comment on whether the other exceptions that the author should already be happening are likewise "common"? There's a bit of a concern that authors that don't handle these exceptions will start breaking on orientation changing cases where previously they did not. Thanks! Vlad -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/192327f4-aefb-4ef7-8a6b-eb676cc0765an%40chromium.org.
