Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VST Effects GUI Windows Stay On Top In A Strange Way #6270

Open
sound8 opened this issue Jan 11, 2022 · 6 comments
Open

VST Effects GUI Windows Stay On Top In A Strange Way #6270

sound8 opened this issue Jan 11, 2022 · 6 comments
Labels

Comments

@sound8
Copy link

sound8 commented Jan 11, 2022

Windows7 64Bit
LMMS 1.3.0 Alpha 64Bit

VST Effects GUI Windows Stay On Top In A Strange Way

Best way to test this is to load up an empty fresh LMMS instance.
Then immediately open up a VST Effect
Then load up any LMMS or LADSPA effect.
With the VST Effect GUI Window open,
Drag the LMMS/LADSPA effect window across the VST Effect GUI Window as if you were trying to put its window on top of the VST Effect window.
You will notice that the VST Effect GUI will stay on top and that the LMMS/LADPSA window will actually show up under the VST Effect GUI yet on top of the VST Effect Window edge, like a slice of LADSPA cheese in between two slices of VST Effect bread.

Odd thing is, is that if you load a VST Instrument (VeSTige) before or after this process, it actually fixes the glitch.
So it appears as if the VST Instrument is providing LMMS with something that is missing from VST Effect.

Hope this helps, any questions let me know.

@sound8 sound8 added the bug label Jan 11, 2022
@Spekular
Copy link
Member

Can you provide a screenshot of the issue and list your LMMS version?

@Monospace-V
Copy link
Contributor

Monospace-V commented Jan 12, 2022

Duplicate of #6115? Caused specifically with QtAPI embedding. Moving an LMMS window over a non-LMMS plugin has unusual results. "Stay on top" disabled.

@sound8
Copy link
Author

sound8 commented Jan 12, 2022

Windows 7 64Bit
LMMS 1.3.0 Alpha 64Bit

Not sure if my issue is exactly like this, although very similar.
The video shown in that post shows a VST Instrument and VeSTige generating this glitch.

As mentioned the issue I found only occurs with VST Effects.
Also mentioned that loading VST Instruments with VeSTige before or after loading VST Effects in my case ends up fixing the glitch.

I don't think I have ever had it happen with a VST Instrument.

Edit:
I will try version 1.2.2 and report back

@Spekular Spekular reopened this Jan 12, 2022
@Monospace-V
Copy link
Contributor

Cannot replicate 1.2.0, but 1.3 alpha VSTfx shows same behaviour. Both QtAPI and Win32API break them, but in slightly different ways. As opposed to issue 6115, where unusual behaviour occurs only on QtAPI. Note, cannot replicate this or 6115 on 1.2.0.
But it looks a lot like a duplicate. The way both break on QtAPI is similar. See:

VSTi:
image

VSTfx:
image

Whereas on Win32 API, VSTfx breaks as:
image

@sound8
Copy link
Author

sound8 commented Jan 14, 2022

@Monospace-V
Thank you for testing / verifying this.
I tested it out in 1.2.2 64Bit also and it does not have this glitch.
So that confirms that this was generated in 1.3.0 Alpha version.
I cannot speak about the code itself, if the issues are the same.

I cannot seem to generate this with VST Instruments like the other users post did.

When you replicate this using VST Effect did you try loading a VST Instrument as I mentioned which fixes the issue.
If not if you have some time give it a try.
Thank You again for verifying

@Monospace-V
Copy link
Contributor

Sound8 check plugin embed API. Instruments issue shows up with QtAPI, and given the nature of your issue (VST cheese between LMMS bread) I think you were using Win32API.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants