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 Re: Setting encoder properties after usage #301

Open
idhland opened this issue Mar 24, 2022 · 6 comments
Open

Question Re: Setting encoder properties after usage #301

idhland opened this issue Mar 24, 2022 · 6 comments
Labels

Comments

@idhland
Copy link

idhland commented Mar 24, 2022

Hello! Are we supposed to be able to set encoder properties after setting "Usage" ( and before Init ). Different OS SKUs for Windows are giving my team different results. I was curious about any insight that could be provided. Thanks!

@rhutsAMD
Copy link
Collaborator

Hi! Yes, the different "Usages" are meant to provide a set of default values, after which you may further modify and set properties based on different categories.

Static Properties:

  • Should be set before encoder initialization

Dynamic Properties:

  • Can be set at any time

Per-Submission Properties:

  • Can be set on the AMFSurface being provided as input with SubmitInput()
  • Applies only once

@idhland
Copy link
Author

idhland commented Mar 24, 2022

Hey Roman, thanks for getting back to me so quickly! I thought that was the intention of the API. We're running into issues with this on a cloud VM SKU so I wanted to check first before going back to them. Basically we're unable to set properties after choosing a "Usage". Thanks again.

@rhutsAMD
Copy link
Collaborator

Could you please share which usage you are using as well as which properties are unable to be set afterwards? Additionally, could you please provide the OS, GPU, and driver version?

Properties set before Init() are stored inside AMF and will be passed to the HW in the Init() call. So it is unlikely that the VM is the issue.

Please also provide the debug output log and return codes.

@idhland
Copy link
Author

idhland commented Mar 24, 2022

That makes sense. Let me ping them first to see if this is on their radar or if there's a reason for it. I'll get back to you.

@idhland
Copy link
Author

idhland commented Apr 20, 2022

Hey Roman, I think we found our issue. It looks like AMF_VIDEO_ENCODER_RATE_CONTROL_METHOD (and possibly other rate control parameters) cannot be set if the usage mode is set to AMF_VIDEO_ENCODER_USAGE_ULTRA_LOW_LATENCY. This only happens on GCN cards though. RDNA seems to be fine. Could you provide more context on the this subject? I didn't see anything in the documentation about this but I could have missed it.

@bisher13
Copy link

bisher13 commented May 11, 2022

I agree while i am using my rx580 via FFmpeg encoder if i used the ultra latency mode (usage mode )the most settings ignored

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

3 participants