LMMS
New Compressor plugin graph breaking when resizing after a certain point
System Information
Windows 11 64bit latest
LMMS Version(s)
1.3.0-alpha.1.822+32c427e (nightly build)
Most Recent Working Version
No response
Bug Summary
If you resize the plugin after a certain point (maybe FHD resolution?) on a 1440p display, the visualizerbreaks and stops working.
Expected Behaviour
It should resize no matter how big, or have a maximum window size limitations to avoid the user going into it.
Steps To Reproduce
Get on a high resolution display, like 1400p or 4k, and resize it until you notice the numbers on the right disappear.
Logs
No response
Screenshots / Minimum Reproducible Project
https://github.com/user-attachments/assets/f00af7db-ac26-4987-8d34-539e9a20961f
Please search the issue tracker for existing bug reports before submitting your own.
- [x] I have searched all existing issues and confirmed that this is not a duplicate.
Tested in 1.3.0-alpha.1.835+cb84fce, still persists.
Also, the plugin's display doesn't "break" per se, it's just not drawing the background (and possibly the number's clip area) outside of a certain width
https://github.com/user-attachments/assets/bdfaa4ed-8494-4d3f-af5e-32302dc24d0a
Tested in 1.3.0-alpha.1.835+cb84fce, still persists.
Also, the plugin's display doesn't "break" per se, it's just not drawing the background (and possibly the number's clip area) outside of a certain width
https://github.com/user-attachments/assets/bdfaa4ed-8494-4d3f-af5e-32302dc24d0a
Check out my video, I also play a sound; the visualizer correctly shows the sound input when normal size, once the compressor is resized after a certain size, it doesn't only stop drawing the background outside of it, the visualizer stops working and doesn't show the sound input anymore except on the knee/ratio indicator (maybe you're right and its just because it goes right to left tho)
I think it's because it tries to draw from the outermost edge, but the clip space is beyond the draw area, so nothing gets drawn.
Alas, I'm not the plugin dev nor do I know the codebase, we'll see if one of the primary maintainers pick up on this issue and give further clarification