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

[Question]: How do avoid generate keyframe when dynamic change encoder frame rate? #494

Closed
MemeTao opened this issue Aug 21, 2024 · 5 comments
Labels

Comments

@MemeTao
Copy link

MemeTao commented Aug 21, 2024

I want to decrease| increase frame rate dynamically, But every time i call 'SetProperty(FrameRate)' will generate key frame automatically.
Is there any method can avoid this like nvenc?

@MikhailAMD
Copy link
Collaborator

Which codec?

@MemeTao
Copy link
Author

MemeTao commented Aug 22, 2024

Which codec?

AMFVideoEncoderHW_HEVC.

Platform: AMD Radeon RX 7700 XT.
OS: Windows 11

@MemeTao
Copy link
Author

MemeTao commented Oct 15, 2024

Which codec?
AMFVideoEncoderHW_HEVC.

Platform: AMD Radeon RX 7700 XT.
OS: Windows 11

Is there any api to avoid generate key frame when dynamic change frame rate (set_property(FRAMERATE, fps))?@MikhailAMD

@MikhailAMD
Copy link
Collaborator

Currently every change in framerate property causes insertion of IDR frame. This is done to have ability to insert SPS with VUI header with timing information containing the new framerate. If you want to change framerate just to manage bitrate control, you can use bitrate instead. The effect would be the same.

@MemeTao
Copy link
Author

MemeTao commented Oct 17, 2024

Currently every change in framerate property causes insertion of IDR frame. This is done to have ability to insert SPS with VUI header with timing information containing the new framerate. If you want to change framerate just to manage bitrate control, you can use bitrate instead. The effect would be the same.

Thanks. You are right. I just want to control the bitrate. I will try the method you said.

@MemeTao MemeTao closed this as completed Oct 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants