-
Notifications
You must be signed in to change notification settings - Fork 261
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 FPS setting on FFmpeg 4 #520
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #520 +/- ##
========================================
Coverage 48.33% 48.33%
========================================
Files 128 128
Lines 9962 9962
========================================
Hits 4815 4815
Misses 5147 5147
Continue to review full report at Codecov.
|
@ferdnyc Travis is having trouble with finding our FFmpeg PPA: https://launchpad.net/~jon-hedgerows/+archive/ubuntu/ffmpeg-backports. This all of a sudden does not seem to exist anymore. Ughhh.... 😉 |
Oy, not again. I'm beginning to understand why some people say they won't ever use community PPAs in production builds. |
I'll just set the 3.2 build as allowed-to-fail, for now, like I did with FFmpeg 4 during the "walkout". But it looks like that PPA was made private, I doubt it's coming back. And there was no Ubuntu LTS release that included FFmpeg 3.2, it got skipped over. We may just have to drop that version from our build matrix. |
I suppose we could always setup our own PPA builds, but that sounds like a huge amount of time to get things all automated and building constantly, and then we'll have the same problem that Jon has, a ton of other projects will see our PPA and start incorporating it into their production builds. |
Fixed in your branch, and I'll open a PR for develop. |
Thanks, that makes sense! |
OK, let's try that again. |
There we go, now I see it's marked "allowed to fail'. I tried to mask it by environment variable like I did last time, but that didn't work. I think to do that I'd have to mask the entire environment config, and we have three variables now. So I masked it by name insead. |
Co-authored-by: Frank Dana <ferdnyc@gmail.com>
This should include description of the problem. The fix itself is incorrect. And someone told me that will use the |
Fix FPS setting on FFmpeg 4, which currently is not setting a valid FPS. This causes all sorts of strange behavior on videos produced with libopenshot using FFmpeg 4. This patch does require a depreciated approach, and I'm not sure how we are supposed to be correctly setting the FPS parameter, so I'm open to suggestions.
Also, thanks to PeterM for troubleshooting this issue and finding a solution! Nice work!