* Display chunk index instead of worker index in verbose mode
The chunk index would be much more useful for users who are using
verbose mode. Worker index is easily derived from counting the lines,
and is not particularly useful.
* Pass padding around instead of recalculating it
* Add assert and comment
Co-authored-by: Redzic <yusufredzic@gmail.com>
The way we have been doing releases does not coincide well with how we
have been utilizing our stable branch. Given that we release from
master, and that many people in the community use master on a daily
basis, it makes more sense for stable to always match the latest
released version, and for master to include unreleased changes which are
considered "stable".
For experiments, we should instead use a feature branch per experiment
until we are confident that it is ready to be merged into master.
- Update log levels so that the log file contains more verbose
information by default, while leaving the stderr progress indicator
relatively uncluttered
- Explicitly set the log level to `error` for all dependencies
- rav1e scenechange info has been moved to `--log-level trace`
- Avoid outputting colors if stderr is not a tty
- Fix a crash when using `--quiet`
* Fixed mkvmerge on windows by allowing for commands over 32767 characters to be executed.
* Fix formatting
* Fix errors
* Fix clippy warnings
Co-authored-by: Kesava Viswanadha <kviswanadha@berkeley.edu>
Co-authored-by: Redzic <yusufredzic@gmail.com>
* Use latest indicatif release
* Fix some clippy lints
* Also validate formatting and warnings in CI
* Minor dependency updates
* Do not show '/0' frames if we haven't computed frame count yet
People have been requesting this because the default chunk order tends
to skew toward underestimating the final filesize. Longest first is kept
as the default because it provides the best performance.
This commit mainly changes the behavior in 2 ways:
1. We now get the frame count and do scene detection in parallel. Initially, only the number of processed frames are shown, and the percentage stays at 100%, and the total frame count is 0. When the actual frame count is available, the progress bar is updated to reflect that. This can help I/O bound situations where the source is very large and the frame count takes a long time to calculate.
2. We also generate the vapoursynth cache in parallel with the scene detection and calculating the frame count. This eliminates the pause between scene detection and actual encoding (if vspipe finishes generating the cache in time, which will be the case 99% of the time, and it will still reduce the overhead in the very unlikely case that it hasn't finished yet).
Also fixes bug where vapoursynth input wouldn't work if you specified anything other than lsmash or ffms2 for the chunk method.
