IssueTracker

This is a continuation of https://issuetracker.google.com/issues/304123366 since it was closed.

Please find below & attached the information requested in the linked issue.

• We have only begun using this product recently, but we have never experienced the expected behavior. As far as we can tell, this problem is not new;
• This behavior is consistent in our experience, however our sample size has been small. All videos we have used with rotation metadata +90 or -90 have the wrong resolution in the manifest;
• To reproduce, please follow the below steps:

1. Submit an interactive job with an ad-hoc configuration from the Node.js Transcoder Client. The configuration species the elementary stream height. (Sample config and input video file are attached)
2. After job completes, inspect the produced HLS manifest file and observe that the width and height are reversed. The width should have the value of the height and vice-versa. This can be confirmed by using Apple's HLS Report tool, which indicates that the resolution listed in the manifest does not match the actual video resolution.

In this example case, the input video is encoded in landscape orientation with a resolution of 1280x720, but with a rotation=-90 flag to be presented in portrait orientation as intended. The Transcoder API correctly picks up on this and generates the properly rotated output (720x1280), but lists the incorrect, original resolution (1280x720) in the HLS manifest file. The manifest should list the resolution as 720x1280.

You can use ffprobe to find the true input and output video file properties.

I have no idea if this issue also affects DASH outputs or not, we have only tried HLS to this point.