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
A few people mentioned that it would be far more convenient for the automation stuff to be a separate package; mostly to avoid a Vapoursynth dependency.
This will also bring at least a minor refactor of the entire automation suite.
I'm not quite sure yet when or if I'll do this but this is how I envisioned it:
Move all automation code that doesn't need Vapoursynth to a new package
Restore Vapoursynth related functionality in this package by extending existing classes from the new package
Passthrough imports from the new package to this one to avoid major breakage in existing scripts using vodesfunc
Activity
Vodes commentedon Feb 11, 2023
A few people mentioned that it would be far more convenient for the automation stuff to be a separate package; mostly to avoid a Vapoursynth dependency.
This will also bring at least a minor refactor of the entire automation suite.
I'm not quite sure yet when or if I'll do this but this is how I envisioned it:
Vodes commentedon Oct 3, 2023
All of this is essentially implemented or improved at vs-muxtools and muxtools.