I can't think of a situation where someone would want this issue to be
ignored, so we should treat it as any other encoder error and perform 3
retries, then exit if it continues to fail. This probably indicates some
kind of issue with decoding or applying filters to that chunk.
* Add zones support
Currently implemented:
- Overriding the selected encoder & number of passes
- Overriding or adding video params
- Overriding photon noise setting
- Overriding min/max scene length
Closes#267
* Error if zoned encoder does not support output pixel format
* Fix crash if zones change number of passes
* Set passes to 1 for zones with rt mode
* Action: Add rust caching to test
* Actions: Use github action to cache docker
* Optimize Dockerfile to allow for caching
* Docker: Use cargo chef for caching
Co-authored-by: Luigi311 <luigi311.lg@gmail.com>
* Add command line arg for sc-only
* added arg to settings.rs
* Add check and kill after split_routine()
Deletes the temporary directory, it would be better if it was never created in the first place.
* Initialize sc_only in EncodeArgs
* cargo fmt
* Integration test
* Make -s a requirement
* cargo fmt
* Add -s as requirement to sc-only via clap
* revert f7688ca
* Fix me not reading errors
* revert db4fb3b
* Cargo fmt
* Added --scenes as a requirement for --sc-only with clap
* Update wording
* Trying to fix the weird integration bug
* Revert 393b380
* Condition on test failure
* Github actions again
* Filename in actions
* 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>