Summary
I built a VFX plugin (scope-vfx) with GPU-accelerated chromatic aberration + VHS/retro CRT effects using pure PyTorch ops. It registers via pluggy like any other pipeline and has 8 custom parameters (toggles + sliders) using ui_field_config.
When I register it as a main pipeline (no usage set), everything works great. The dynamic parameter sliders show up in the settings panel and I can tweak all the effects live. Screenshot for reference:
Then I switched it to usage = [UsageType.POSTPROCESSOR] so I could chain it after generative models like LongLive and apply the VFX on top of AI-generated video instead of raw camera input. The effects apply correctly in the chain, but the parameter sliders don't show up for post-processors.
The post-processor dropdown selects the pipeline, but there's no settings panel that expands for it.
Workaround I found: select VFX Pack as the main pipeline first, dial in the settings, then switch back to the generative model with VFX Pack as post-processor. The parameter values persist and get applied. Works, but not exactly discoverable.
I think the gap is that the frontend renders dynamic parameters for the main pipeline slot but doesn't have an equivalent section for pre/post-processor slots. The backend side is fine, schemas are served correctly and parameters flow through the chain. It's just the UI that doesn't expose them.
Platform
Win 11, 64GB RAM
Nvidia GPU
NVIDIA GeForce RTX 5090, 32607 MiB
Scope Version
daydream-scope: 0.1.0b3 git commit: 0febd6a
uv Version
uv 0.9.8 (85c5d3228 2025-11-07)
node Version
v24.11.0
Summary
I built a VFX plugin (scope-vfx) with GPU-accelerated chromatic aberration + VHS/retro CRT effects using pure PyTorch ops. It registers via pluggy like any other pipeline and has 8 custom parameters (toggles + sliders) using ui_field_config.
When I register it as a main pipeline (no usage set), everything works great. The dynamic parameter sliders show up in the settings panel and I can tweak all the effects live. Screenshot for reference:
Then I switched it to usage = [UsageType.POSTPROCESSOR] so I could chain it after generative models like LongLive and apply the VFX on top of AI-generated video instead of raw camera input. The effects apply correctly in the chain, but the parameter sliders don't show up for post-processors.
The post-processor dropdown selects the pipeline, but there's no settings panel that expands for it.
Workaround I found: select VFX Pack as the main pipeline first, dial in the settings, then switch back to the generative model with VFX Pack as post-processor. The parameter values persist and get applied. Works, but not exactly discoverable.
I think the gap is that the frontend renders dynamic parameters for the main pipeline slot but doesn't have an equivalent section for pre/post-processor slots. The backend side is fine, schemas are served correctly and parameters flow through the chain. It's just the UI that doesn't expose them.
Platform
Win 11, 64GB RAM
Nvidia GPU
NVIDIA GeForce RTX 5090, 32607 MiB
Scope Version
daydream-scope: 0.1.0b3 git commit: 0febd6a
uv Version
uv 0.9.8 (85c5d3228 2025-11-07)
node Version
v24.11.0