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

SetvideoEncoderconfiguration #331

Open
momoAmch opened this issue Aug 30, 2024 · 3 comments
Open

SetvideoEncoderconfiguration #331

momoAmch opened this issue Aug 30, 2024 · 3 comments

Comments

@momoAmch
Copy link
Contributor

Hi

The setVideoEncoderConfiguration function appears to have a bug in how it parses and accesses the properties for H264 and MJPEG encoders. Specifically, it tries to access the profile property, but the actual property name is H264Profile for the H264 encoder. Similarly, there is a mismatch for the MJPEG encoder properties.

( options.H264.profile ? '' + options.H264.profile + '' : '' ) +

#148

@RogerHardiman
Copy link
Collaborator

RogerHardiman commented Oct 3, 2024

Thank you for the Issue Report.
It makes a lot of sense to allow the output of GetVideoEncoderConfiguation to feed directly into SetVideoEncoderConfiguration.

I cannot apply PR #148 as it breaks backwards compatibility. (PR 148 already warns about this)

If you can do a new PR that takes PR 148 as the starting point but continues to support the existing ".profile" API as well as adding in the better API (.H264Profile) then I can review and merge it.

Thanks for helping improve the library with better property names.
And thanks too to @bl0ggy for the old PR that I forgot to review 4.5 years ago

Roger

@RogerHardiman
Copy link
Collaborator

actually, I'll just do it now

@RogerHardiman
Copy link
Collaborator

There is a new branch with this fix.
Please can you test it.

Roger

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants