-
-
Notifications
You must be signed in to change notification settings - Fork 241
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]: -vcodec copy HLS #396
Comments
Thanks for opening this issue, a maintainer will get back to you shortly! In the meantime:
|
@juniorcines Thank you for the suggestion. Adding an option to copy the existing video codec ( |
Thanks to you, and if when we only want to use the default quality to pass it to HLS, if it is already in H264, using copy is good to pass it quickly without consuming a lot of resources. I use it in Nodejs, but I would like to have this in Python with your library. |
💬 When the output codec is set to "copy" (stream copy mode), certain video processing parameters like "-vf" (video filters) and "-aspect" (aspect ratio) are not supported and can lead to errors and invalid output files. ♻️ This commit refactors the internal `PreProcess` method in StreamGear API to handle the stream copy mode correctly: - 🥅 Moved the existing code for setting "-vf" and "-aspect" inside conditional block that checks if the output stream codec is not "copy". - 🔊 Added an else block to log warnings and discard "-vf" and "-aspect" in stream copy mode.
Issue guidelines
Issue Checklist
Describe your Idea
Hello, I would like the option that if the original quality is used, one can specify if they want to do:
-vcodec: copy
I say this because most of us could have the video in H264 and we just want to use the original quality and have it in HLS.
So with this option it would be faster to convert the videos to HLS.
Use Cases
-vcodec: copy
transfer the video to HLS faster if the original quality is used without the option of multiple qualities
Any other Relevant Information?
No response
The text was updated successfully, but these errors were encountered: