MUX problem with some vst/i's preset browser

Official support for: mutools.com
RELATED
PRODUCTS

Post

valhallasound wrote:
mutools wrote:I also suspect some issue in a commonly used UI framework. Yes it might be Juce, judging on the striped background of the menus. Please do email the relevant plugin developers, they need to set a breakpoint in their code and lookup the very reason. I'm open to help to narrow this down and fixed, wherever the bug is located.
I use Juce for my plugin code. The classes in question would be the PopUp Menu, if that is helpful. Is this with 32-bit or 64-bit VST? OSX, or Windows?

Sean Costello
32/64 bit all hosts.

Post

valhallasound wrote:No idea, as it works in most other Windows VST hosts (I haven't tried every VST host, but I haven't heard this complaint from any other Windows users). You can take a look at the Juce source code, and see how this would interact with your code.
It works fine in MuLab as well, so it must be something specific to the VST environment, i think. I assume it's much easier for you to set a breakpoint in existing code than for me to install a totally new framework, start studying it from scratch and then try to find out what's happening. And even then, chance is real that i'm debugging someone else's code, no? I mean the Juce Popup Menu is not part of the MUX code. Can't you please give it a quick look at your/Juce side?

Post

mutools wrote:
valhallasound wrote:No idea, as it works in most other Windows VST hosts (I haven't tried every VST host, but I haven't heard this complaint from any other Windows users). You can take a look at the Juce source code, and see how this would interact with your code.
It works fine in MuLab as well, so it must be something specific to the VST environment, i think. I assume it's much easier for you to set a breakpoint in existing code than for me to install a totally new framework, start studying it from scratch and then try to find out what's happening. And even then, chance is real that i'm debugging someone else's code, no? I mean the Juce Popup Menu is not part of the MUX code. Can't you please give it a quick look at your/Juce side?
I'm up to my neck in Audio Unit parameter warping issues this week, so won't have time to get onto the PC and look at this for awhile.

My guess is that it has something to do with having the plugin running in another VST's window, and the focus of the PopupMenu versus the VST window that MUX is running in. This is just a guess, as I really don't mess with the Juce framework - I just use it.

The best way of debugging this issue would be to compile the Juce Demo Plugin, add a popup window to it, and see if you can trace down what is going on inside of MUX when the demo plugin is running.

Sean Costello

Locked

Return to “MuTools”