Skip to content
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

[Feature Request] Estimated file size output #1277

Open
mishmanners opened this issue Jan 16, 2024 · 1 comment
Open

[Feature Request] Estimated file size output #1277

mishmanners opened this issue Jan 16, 2024 · 1 comment
Assignees
Labels
🔷Enhancement Type • Improvements for the software. ⬜ Pending Status • This issue stills needs to be analyzed.

Comments

@mishmanners
Copy link

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when I have to create multiple exports of the same thing because I can't get the file size right.

Describe the solution you'd like
What would be great, when we go to encode the file, it'd be great if there was an estimated size based on the parameters set. Ie. like what Adobe does when you export an image.

Describe alternatives you've considered
At the moment, I export up to 20 different files to get the correct size. Ie. to upload something to a blog or GitHub, 10MB is the file limit.

@mishmanners mishmanners added ⬜ Pending Status • This issue stills needs to be analyzed. 🔷Enhancement Type • Improvements for the software. labels Jan 16, 2024
@tankorsmash
Copy link

This isn't directly related, but when you try to export a recording, and the disk doesn't have enough space, the output just generates a 48byte stub or fails with an Ffmpeg error. If there was an filesize estimate, it would be nice if the UI showed you a warning before trying to export as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🔷Enhancement Type • Improvements for the software. ⬜ Pending Status • This issue stills needs to be analyzed.
Projects
None yet
Development

No branches or pull requests

3 participants