I've just been using some Mux's to start a new track. Getting a beat going first then adding a sequenced VST.
I'm still quite new to MuLab despite owning a license for nearly 2 years! I haven't had a lot of time to mess about with it. Anyway, When I try to bring the VST to the front, it doesn't do so by clicking the VST GUI. Well actually on occasion it does, but mostly not.
If I click the MuLab TaskBar, the VST appears on top of the Seq window, but then I go to click on the VST GUI to adjust something and it immediately brings the Seq window back to the top making it impossible to edit the VST. After clicking the VST on TaskBar it will again show. But the problem persists whilst using MuLab under normal circumstances.
MuLab v5.4.1 x86
Windows 7 HPx64
Core i52467M
4GB RAM
VST window underneath Sequence window
- KVRAF
- 3161 posts since 28 Mar, 2008 from a Galaxy S7 far far away
- KVRAF
- 13864 posts since 24 Jun, 2008 from Europe
Just tried what you describe, but don't see any problem here.
Is it with a specific VST or with all VSTs?
Anyone else who can repeat this behavior?
Is it with a specific VST or with all VSTs?
Anyone else who can repeat this behavior?
- KVRAF
- Topic Starter
- 3161 posts since 28 Mar, 2008 from a Galaxy S7 far far away
The VST causing the issue is Icecream.
I just added a new rack and inserted Dune CM into it.
I have the Sequence window still open from before, ie the sequence for the Icecream VST.
I then opened the Dune CM VST window, and now when the sequence window is focused and the mouse hovers over the Dune VST in the background, it instantly becomes focused. Yet when Dune is focused and I hover over the sequence window nothing happens?!
I have set the option in MuLab for hover to bring windows into focus, but there's a delay for that setting. Whereas hovering over Dune brings it to the front instantly the cursor touches it. It shouldn't do that.
I'll try some other VST's and create new sequences and test further.
Thanks Jo
EDIT: Tried some other VST's and no problems. Does this mean these two VST's are at fault? I find it strange that Synapse Audio would design and release a special CM version with bugs? But the two problem VST's are creating a similar effect, focus. The focus in MuLab seems the possible problem.
Would you be able to look at this please, unless you're certain it's a VST issue of course.
Thanks
I just added a new rack and inserted Dune CM into it.
I have the Sequence window still open from before, ie the sequence for the Icecream VST.
I then opened the Dune CM VST window, and now when the sequence window is focused and the mouse hovers over the Dune VST in the background, it instantly becomes focused. Yet when Dune is focused and I hover over the sequence window nothing happens?!
I have set the option in MuLab for hover to bring windows into focus, but there's a delay for that setting. Whereas hovering over Dune brings it to the front instantly the cursor touches it. It shouldn't do that.
I'll try some other VST's and create new sequences and test further.
Thanks Jo
EDIT: Tried some other VST's and no problems. Does this mean these two VST's are at fault? I find it strange that Synapse Audio would design and release a special CM version with bugs? But the two problem VST's are creating a similar effect, focus. The focus in MuLab seems the possible problem.
Would you be able to look at this please, unless you're certain it's a VST issue of course.
Thanks
- KVRAF
- 13864 posts since 24 Jun, 2008 from Europe
Yes it's a vst plugin issue. Please email Synapse etc. They're doing something special when the mouse is over the dune window.
