Remove slate generator and renderer #47
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changelog Description
Removes Selenium-based slate generation functionality to improve LabLib stability and reduce complexity. The slate generator and renderer components relied on Selenium WebDriver, which introduced significant environmental compatibility issues and maintenance overhead. This update eliminates these problematic dependencies, streamlining the codebase while maintaining core VFX dailies processing capabilities. The removal addresses widespread deployment failures and reduces the attack surface for dependency-related issues in production environments.
Building on OCIO generator improvements from PR #46, this change focuses LabLib on its core strengths: reliable video processing using OIIO and FFMPEG with enhanced OpenColorIO integration. The elimination of browser automation components reduces installation complexity and improves cross-platform compatibility.
Additional info
Technical Removals:
Impact on Codebase:
The slate generation functionality was identified as a source of frequent deployment failures and maintenance burden, particularly in headless server environments and containerized deployments where browser automation is problematic.
Testing notes: