fix(fancy-audiovisualizer): prevent content clipping at widget border#272
Merged
ItsLemmy merged 1 commit intonoctalia-dev:mainfrom Feb 17, 2026
Merged
Conversation
…clipped at widget border The visualizer content (bars, waves, bloom glow) could extend beyond the widget boundary and get hard-clipped at the rounded corners, especially at high sensitivity and bloom intensity settings. Fix by dynamically scaling the UV coordinate space based on the maximum possible content extent derived from the current sensitivity and bloom intensity settings, and adding a smooth radial edge fade that catches bloom tails before they reach the border. The content scale is calculated as: maxContentRadius = 0.35 + sensitivity * 0.5 maxBloomReach = bloomIntensity * 1.0 (from exp decay analysis) contentScale = (maxContentRadius + maxBloomReach) * 1.05 This guarantees no clipping at any combination of user-configurable settings while keeping the visualization as large as possible.
Contributor
|
@ItsLemmy - this PR modifies your plugin. Please review when you have a chance. |
e5c6818 to
6a1b606
Compare
Contributor
|
@ItsLemmy - this PR modifies your plugin. Please review when you have a chance. |
Contributor
|
Thanks! |
Author
|
Glad to help, was getting annoyed by the bloom clipping creating a moving border around my otherwise transparent visualization, looks flawless now :) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
sensitivityandbloomIntensitysettings, shrinking the visualization to always fit within the widgetHow it works
The content scale is calculated per-frame from uniforms:
The edge fade uses
smoothstepfrommaxContentRadius/contentScaleto1.0in widget space, so it only attenuates bloom glow and never affects the main visualization geometry.At default settings (sensitivity=1.5, bloom=0.5)
contentScale ≈ 1.68. At max settings (sensitivity=3.0, bloom=1.0)contentScale ≈ 2.99. It auto-adapts to whatever the user configures.Test plan