Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
View issue level access limits(Press Alt + Right arrow for more information)
Unintended behavior
View staffing
Description
This will create a public issue which anybody can view and comment on.
Please provide as much information as possible. At least, this should include a description of your issue and steps to reproduce the problem. If possible please provide a summary of what steps or workarounds you have already tried, and any docs or articles you found (un)helpful.
Problem you have encountered: Currently the pixels width and height gets processed only if they're of even integer and within accepted size based on this documentation:https://cloud.google.com/transcoder/docs/reference/rest/v1/JobConfig#h264codecsettings
When the inputs pixels width and height are not in above recommended values then the process fails.
What you expected to happen: We expect that if the given value is not in recommended values, then automatically round down to the nearest accepted value so that the job can complete.
Steps to reproduce: Give JobConfig with an odd pixel height and width to see it fail. The job also fails if the JobConfig has a larger non standard image pixel width and height.
Other information (workarounds you have tried, documentation consulted, etc): Workaround: Currently, the workaround is to manually set the pixel width and height to an accepted value.
Documentation:https://cloud.google.com/transcoder/docs/reference/rest/v1/JobConfig#h264codecsettings