Skip to content

[BUG] >10MB output from 10MB preset #68

Description

@necroparade

Prerequisites

  • I have checked that there are no open issues that are the same or very similar to mine, and I understand that my issue will be closed if it is a duplicate
  • I have filled in all required fields to the best of my ability, and I understand that my issue will be closed if they are not
  • I have copied the device & app info to my clipboard and pasted it into the device info section where indicated, and I understand that my issue will be closed if it is not
  • I have uploaded appropriate screenshots and log files, and I understand that my issue may be closed or remain unresolved if not
  • My issue is written in English, and I understand that my issue will be closed if it is not
  • I understand that my issue will be closed if all 5 of these checkboxes are not checked

Issue Description (required)

When using the "10MB Discord - Github" preset, some source videos consistently produce an output slightly greater than 10MB. In this instance, the source video is 44 seconds long, 1080x1920, H.264 with AAC, 30fps, and visually complex (outdoors with lots of motion). Discord fails to send the output video.

Expected Behaviour (required)

Expected output filesize <10MB. Other source videos have produced outputs with expected filesize.

Device Info (required)

Device Manufacturer* (e.g. Samsung): Samsung

  • Device Model* (e.g. Galaxy S10): Galaxy A36 5G
  • Android Version* (e.g. 12): 16
  • Compressor Version* (e.g. 1.1.0): 1.5.5
  • Where did you get Compressor from?* (GitHub Releases, IzzyOnDroid/F-Droid, Google Play Store): Google Play Store
  • Device Chipset (e.g. Exynos 9820): Qualcomm SM6475-AB Snapdragon 6 Gen 3 (4 nm)
  • Device Model Number (e.g. SM-G973F): SM-A366U1

App Version: 1.5.5
Device: samsung SM-A366U1 (Android 16)
Supported Encoders: video/avc, video/hevc

Screenshots (required)

Image

Logcat

Activity

  1. added
    BugSomething isn't working
    TriageThis issue has not been reviewed yet
    on May 19, 2026
  2. moved this from Ready to Not Implementing in Compressor Roadmapon May 20, 2026
  3. added
    Media3This issue is related to Android's Media3 framework
    Won't FixThis will not be worked on
    OEM issueThis issue is caused by your device manufacturer, not Compressor
    and removed
    TriageThis issue has not been reviewed yet
    on May 20, 2026
  4. JoshAtticus commented on May 20, 2026

    @JoshAtticus
    Owner

    Hi @necroparade, as frustrating as this is (it happens to me too), it's really not possible to fix this specifically because Snapdragon exists. All I can think of to fix this is VBR, where the app can set the bitrate even lower for less active parts of the video to save more storage, but, with VBR, Snapdragon chips actually ignore target bitrate, which then makes it impossible to specify a specific file size. Even if I added this for everything but Snapdragon, it wouldn't fix your issue specifically as you have a Snapdragon chip.

  5. JoshAtticus commented on May 20, 2026

    @JoshAtticus
    Owner

    I would recommend lowering the target bitrate further in video options, and potentially the resolution too. That's what I do.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

BugSomething isn't workingMedia3This issue is related to Android's Media3 frameworkOEM issueThis issue is caused by your device manufacturer, not CompressorWon't FixThis will not be worked on

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions