-
-
Notifications
You must be signed in to change notification settings - Fork 247
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
[Proposal]: Allow configuration of input parameters #335
Comments
Thanks for opening this issue, a maintainer will get back to you shortly! In the meantime:
|
@HeeebsInc That's what |
@HeeebsInc Also, |
good afternoon @abhiTronix - I got the pipeline working only by modifying the source code. Before modifying and pulling the most recent release I see the parsing logic for ffpreheaders is not working. When passing
I get the following output
Vid gear is passing pre-headers as a list in the ffmpeg argument when it should be parsing it and passing in each argument of the list. so should be the following
|
this is the command I was hoping for. In order to get -framerate to the left you need to modify the vidgear.py file and add or am I missing something? -ffpreheaders: ['-framerate', 1] does not work |
Issue guidelines
Issue Checklist
Describe your Idea
Like output params, allow configuration of input parameters when using WriteGear. I recently faced an issue where I needed to have
-framerate 1
in the input parameters and the only way to get that working with vidgear was to modify the source code and replace
input_parameters ={} --> input_parameters= {'framerate': 1}
inside of writegear.py
Use Cases
when creating a video that you instead of be encoded at 1 fps. Using h265, trying to do this without having the additional input parameter created a video that is not actually 1 fps.
Any other Relevant Information?
No response
The text was updated successfully, but these errors were encountered: