Bug in VST windows
- Thread starter GME
- Start date
konsolenritter
Active Member
Where exactly is the bug?
GME
New Member
You see all that white stuff??? That's a problem.
konsolenritter
Active Member
Proof in your display settings (windows) that scaling for this monitor regarding size of text, apps and others is set to "100%".
If there is another percentage set, it can be the cause for your issue: The plugin has a fixed size face to be drawn into the provided space. The plugins developer doesn't know about the scaling/resizing.
So the face of the plugin should fit exactly into the window area if the scaling is set to 100%.
If there is another percentage set, it can be the cause for your issue: The plugin has a fixed size face to be drawn into the provided space. The plugins developer doesn't know about the scaling/resizing.
So the face of the plugin should fit exactly into the window area if the scaling is set to 100%.
c3r1c3
Member
I don't think it's a bug in OBS. From what I recall of the code it just calls for the window to be drawn and handed to the plug-in for all the content in the window and the plug-in decides the size of the window.
I've seen this happen in DAWs as well, so I don't think it's a bug in OBS per se. That said, maybe some more code could be added to force a resize of the window to the viewable plug-in area after the plug-in initializes, but that then breaks other plug-ins (and technically the VST 2.x standard) and could lead to crashes, so the best thing is to just ignore it.
Thinking about it some more, it could also be coming from some type of minimum size window defined somewhere deep in the Qt/interface/C-wrapper of Qt code in OBS, but I wouldn't be able to find that without spending more time then I have to look for it...and I seriously doubt Jim did something like that in the code.
I've seen this happen in DAWs as well, so I don't think it's a bug in OBS per se. That said, maybe some more code could be added to force a resize of the window to the viewable plug-in area after the plug-in initializes, but that then breaks other plug-ins (and technically the VST 2.x standard) and could lead to crashes, so the best thing is to just ignore it.
Thinking about it some more, it could also be coming from some type of minimum size window defined somewhere deep in the Qt/interface/C-wrapper of Qt code in OBS, but I wouldn't be able to find that without spending more time then I have to look for it...and I seriously doubt Jim did something like that in the code.
GME
New Member
Ok thanks for your response. Scaling seems to make the frame larger but keep the VST at the same size...resizing the VST itself doesn't work. Should probably be fixed by disabling scaling for open windows inside the filter ad-ons such as the VST plugins.