Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[regression] providers/aws: Setting MaxFrameRate on ElasticTranscoderPreset breaks fixed frame rate #695

Closed
hashibot opened this issue Jun 13, 2017 · 4 comments · Fixed by #7141
Labels
bug Addresses a defect in current functionality. regression Pertains to a degraded workflow resulting from an upstream patch or internal enhancement. stale Old or inactive issues managed by automation, if no further action taken these will get closed.

Comments

@hashibot
Copy link

This issue was originally opened by @svanzoest as hashicorp/terraform#13638. It was migrated here as part of the provider split. The original body of the issue is below.


@catsby hashicorp/terraform#13422 broke hashicorp/terraform#9847 and undid hashicorp/terraform#11340, I can no longer set a preset with a fixed frame rate in 0.9.3, this was the reason the default was removed in the first place.

I now get:

* aws_elastictranscoder_preset.proxy: Error creating Elastic Transcoder Preset: ValidationException: When you specify a value for MaxFrameRate, you must also specify 'FrameRate':'Auto'. Either change the value of FrameRate or remove the MaxFrameRate object, and resubmit the request.
    status code: 400, request id: 8cf3908f-207e-11e7-84a3-01d702018b22
@hashibot hashibot added bug Addresses a defect in current functionality. regression Pertains to a degraded workflow resulting from an upstream patch or internal enhancement. labels Jun 13, 2017
@polython
Copy link

Also encountered this when declaring a fixed frame rate and no max frame rate:

* aws_elastictranscoder_preset.olympics: Error creating Elastic Transcoder Preset: ValidationException: When you specify a value for MaxFrameRate, you must also specify 'FrameRate':'Auto'. Either change the value of FrameRate or remove the MaxFrameRate object, and resubmit the request. status code: 400, request id: 5570e180-5d05-11e7-8604-01f6ba4419fa

@svanzoest
Copy link
Contributor

Re-adding my reply to @catsby from hashicorp/terraform#13638 for background, as that got lost in the transfer of the repo.

Hopefully I understand your situation correct; you're setting frame_rate to something that is not auto, and you are omitting max_frame_rate, correct?

Correct. Just for reference I am setting the FrameRate to29.97 forcing a consistent FrameRate among all transcodings done using this preset regardless of the FrameRate of the input. Since the FrameRate is not auto, you should not set MaxFrameRate at all. The default of 30 only applies when you set the FrameRate to auto, but do not specify a MaxFrameRate.

So, MaxFrameRate only applies when you assume the frame rate from the media file, but want to make sure you do not have a high frame rate.

Exactly.

Terraform clearly isn't handling reading the default MaxFrameRate correctly, thus our test TestAccAWSElasticTranscoderPreset_basic was failing. I suppose I'm confused on when to set max_frame_rate, it seems you can only set this property if frame_rate is auto? I didn't feel that the AWS docs said that explicitly, but I feel like that' what we're getting.

Yes, that is it and if you read the docs carefully, it states that as well.

FrameRate: If you want to preserve the frame rate of the input file and use it for the output file, specify auto.
MaxFrameRate: If you specify auto for FrameRate, Elastic Transcoder uses the frame rate of the input video for the frame rate of the output video, up to the maximum frame rate. If you do not specify a MaxFrameRate, Elastic Transcoder will use a default of 30.

MaxFrameRate only applies to auto FrameRate.

@github-actions
Copy link

github-actions bot commented Apr 1, 2020

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

@github-actions github-actions bot added the stale Old or inactive issues managed by automation, if no further action taken these will get closed. label Apr 1, 2020
@github-actions github-actions bot closed this as completed May 1, 2020
@ghost
Copy link

ghost commented Jun 1, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!

@ghost ghost locked and limited conversation to collaborators Jun 1, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Addresses a defect in current functionality. regression Pertains to a degraded workflow resulting from an upstream patch or internal enhancement. stale Old or inactive issues managed by automation, if no further action taken these will get closed.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants