-
Notifications
You must be signed in to change notification settings - Fork 9
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
fix: Fixed pub_multi_track.sh frame rate #21
base: main
Are you sure you want to change the base?
fix: Fixed pub_multi_track.sh frame rate #21
Conversation
Before I merge this, @TilsonJoji, I'm wondering if this may have been intentional to try to align IDs between tracks? |
Either way, it seems like it probably is some kind of bug to say we have different framerates, but then end up producing all the same framerate. |
Re: starting from a 60fps source - I wouldn't mind replacing the bunny with something different if we have a reliable source... 🦾 🚀 |
Thank you for reporting the issue with constant fps for all o/p tracks @Manuel-Barrabino Thank you @englishm for bringing this thread to my attention. I had used Theoretically for all the o/p streams , I had a look at the reported issue Here the problem does not lie with the usage of Ideal fix would be to place After placing
Since the input file
I second the idea of using a 60-fps input file as it gives more flexibility to downscale/manipulate the frame rate for different output streams, and I would recommend using |
Understood, I'll add the -r before the input and try to add a new 60fps reliable source |
In
dev/pub_multi_track.sh
: The-r
flag was deleted from theffmpeg
command to stream the video because it fixed the frame rate for every video output. Instead of having 3 tracks with 60, 30, and 25 fps we had all of them with 25.