-
Notifications
You must be signed in to change notification settings - Fork 187
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
Use MonotonicTimelineInterpolator
in video transcoder
#4257
base: develop
Are you sure you want to change the base?
Use MonotonicTimelineInterpolator
in video transcoder
#4257
Conversation
This should ensure timestamps are motononically increasing, as the transcoder library needs.
📱 Scan the QR code below to install the build (arm64 only) for this PR. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #4257 +/- ##
===========================================
- Coverage 80.07% 80.03% -0.05%
===========================================
Files 2048 2048
Lines 54357 54385 +28
Branches 6633 6646 +13
===========================================
Hits 43525 43525
- Misses 8555 8583 +28
Partials 2277 2277 ☔ View full report in Codecov by Sentry. |
Allow uploading the original file if it can't be transcoded.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a first comment, I do not see any MonotonicTimelineInterpolator
in the changes. What am I missing?
The title is a bit outdated, this PR was just added so we could test solutions to fix an issue when trying to transcode videos before sending them (the linked one above) in some Android versions (MIUI for Android 12?). The original error said:
So I tried to fix that by using an interpolator that ensures the video timestamps always go forward, to see if that could solve the issue (it doesn't). This is either a problem with the codecs in the OS shipped by problematic vendors or an issue with the lib we're using to simplify the transcoding process. So I guess our options are either allowing videos to be sent as is if transcoding fails (either as a file or as the actual media) or using a different lib or transcoder for this. I'm waiting for a decision from @mxandreas , but the latest commit tries to implement the first solution. |
If "as is" means that the video size/quality will not be affected, but we can still remove the sensitive pieces (like geolocation tags), then I think that's fine. However, I would send them as "file" to have some indication that the transcoding was not applied. |
Content
This should ensure timestamps are monotonically increasing, as the transcoder library needs.
Motivation and context
Screenshots / GIFs
Tests
Tested devices
Checklist