You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 1, 2022. It is now read-only.
This might be better than a a few-size-fits-all approach. You're already using ffmpeg to convert, so it would be cool if the program just generated a text string that got passed to ffmpeg. It would expose commands like this and allow for user editing.
Some video compression tools already use this approach. It is great for power users, because they can customize the command as much as they want. It also gives the tool more forward-compatibility.
It would be even better if the tool loaded options from a config file for the ffmpeg path. Something like:
Yes, I'll look into a way to achieve something like this, it seems useful 👍
Perhaps as an advanced setting/option, since I don't want to take away from the usability of the program!
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This might be better than a a few-size-fits-all approach. You're already using ffmpeg to convert, so it would be cool if the program just generated a text string that got passed to ffmpeg. It would expose commands like this and allow for user editing.
Some video compression tools already use this approach. It is great for power users, because they can customize the command as much as they want. It also gives the tool more forward-compatibility.
It would be even better if the tool loaded options from a config file for the ffmpeg path. Something like:
Then I could add Opus recipes at different bitrates, for example. :)
The text was updated successfully, but these errors were encountered: