Parameters that read as the same concept use very different ranges, and out-of-range values are clamped with no warning, so a mistyped value looks like a broken effect rather than a bad input.
Steps to reproduce
1. Set neonGlow pathIntensity to 1.6 (reasonable if you assume a 0-3 scale, as runningGlow glowLevel uses)
2. Render
Expected
Either the value is honoured, or a warning says it was clamped and to what.
Actual
pathIntensity and linesDraw ldIntensity are 10-400 (default 100), while runningGlow glowLevel is 0-3. A value of 1.6 clamps to 10 and renders as though the effect is switched off. Nothing reports the clamp, so the natural conclusion is that the effect is broken.
Context
Cost us a render cycle chasing an effect that was working exactly as told. Suggestion: expose min/max per parameter in /api/video-editor/capabilities, or warn on clamp.
Environment
App version: 8.8.0
Platform: Windows 11 Pro 10.0.26200
Post a Reply