Pvsfunc

Latest version: v4.3.0

Safety actively analyzes 622344 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 2

4.3.0

Override the behaviour of d2v_source's _ColorRange set approach in PD2V. Instead, PD2V will try to obtain the color
range of the original input video of the D2V file. This would be the demuxed MPEG stream since the input file path
might not be a video container, but may be a D2V file instead.

If no color range is found in the MPEG stream, then limited/TV range will be assumed as there's more of a chance
that MPEG media will be limited/TV ranger over full/PC range.

For more information on this, see https://github.com/dwbuiten/d2vsource/pull/41

4.2.1

- Fix regressions from v4.2.0 in PD2Vs `deinterlace()` causing runtime errors if `recover()` was not used first.

4.2.0

- Add new `recover()` method to PD2V for recovering progressive frames with VFM optimally
- Support VFM recovered input clips in PD2V `deinterlace()`

4.1.0

- Update pyd2v to 1.3.0, remove PD2V._get_d2v
- Remove explicit VapourSynth dependency (prevents annoying conflicts between vs users who are on non-pip-installs vs. those on pip-installs)
- Rework release-packager workflow for releases

4.0.3

- Fix pathlib usage in `PD2V._get_d2v` and `PLWI._fps_reset`, stem and suffix was mixed up.

4.0.2

- Fix `__ALL__` imports in `__init__`, was using old PLS name after it was renamed to PLWI.

PLWI

- State "Progressive" instead of "Deinterlaced (Progressive)" in deinterlace()'s verbose info.

Page 1 of 2

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.