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
Video file transcoded unnecessarily before sending; inflates a 12MB video to almost 90MB! #13511
Comments
I am able to experience the delay in upload , but my file size is not inflating , can you upload screenshots |
I experienced a similar issue from uploading a video file from iCloud to Signal (on iOS), it got from ca. 49MB inflated to ca. 101MB |
Hi @cousinit99 , can you also upload the debug log |
It's in the OP. |
Screencast from 19-04-24 10:07:53 PM IST.webm |
The video is mostly audio in terms of content. The visual is essentially a static picture with subtitles. Very little changes from one frame to the next. The subtitles are all that change visually. There's a great deal of temporal redundancy. My guess is that the encoder is removing the motion vector compression from the original file. |
Bug description
Sending videos takes forever because Signal Android performs some kind of processing prior to sending. This processing inexplicably takes a 12MB H.264 640x360 video with a 167kbps total bitrate, and somehow inflates it to almost 90MB.
Steps to reproduce
Actual result: The video takes roughly 5 minutes to process before even starting to upload. The upload then begins for an 88MB file.
Expected result: No processing or transcoding delay occurs, the video is uploaded at a size no larger than the source, and the upload is virtually instantaneous. The Signal desktop app behaves exactly this way for the same video file using the same internet connection.
Device info
Device: OnePlus Open
Android version: 13
Signal version: 7.3.1
Link to debug log
https://debuglogs.org/android/7.3.1/28a1ea63cbc652c60d2300faaa566648894a66f2f102d751e0d80a25e03d3c37)
Video file meta
The text was updated successfully, but these errors were encountered: