vst window as a float
Hi,
Is there a way to make the interface for a vst plugin display as a floating window (always in the front)?
Thanks,
Greg
bump
I am wondering the same thing - using Max/MSP 4.6. Looking at the list of arguments for plugconfig in the MSP reference manual, I saw nothing that would make the VST window float.
The patcher window can be made to float with the messages "window flags float" & "window exec" to a [thispatcher] object, but it doesn't seem to translate when you save as a plug-in.
Anybody?
On 17 oct. 08, at 14:26, Jesse wrote:
>
> bump
>
> I am wondering the same thing - using Max/MSP 4.6. Looking at the
> list of arguments for plugconfig in the MSP reference manual, I saw
> nothing that would make the VST window float.
>
> The patcher window can be made to float with the messages "window
> flags float" & "window exec" to a [thispatcher] object, but it
> doesn't seem to translate when you save as a plug-in.
>
> Anybody?
This is not possible as far as I know.
Best,
ej
Bump. Nearly 18 years later and still not possible. As for [vst~], I'd also like to see an unload plugin option, ability for direct parameter map/automation with Ableton, and a way to get the name of the currently loaded plugin.
The VST window as a floating window is one of those things that should be a no-brainer and super easy to implement. In Max's preferences it could be reverted, for anyone that would prefer the current method, but I don't see any reason to. Some DAWs let you choose if you want it or not, but most alyaws put the plugin on top.
how can a window not be on top after it´s beeing opened?
ah, i see 11olsens explanation about live as host in the other thread.
well, just use the mouse-up event to trigger the "open" action and you should be fine.
that is a good practice for many other GUI releated things anyway.
I could also have a metro banging the message "open" every millisecond, it would still be a workaround (a heavy one, I admit ;-)). And workarounds are not "good practice", they exist purely because the needed resources don't exist or are not available.
you can as well bang open 100 100 (sreen coordinates)
using metro or other means to keep vst winow on top.
How about that inline view which can be put into bpatcher
and controlled with thispatcher ?
But in any case in Max having such windows floating, steals key stroke focus which is very annoying, imagine having 4 vst winows open
imagine having 4 vst winows open
spat windows all have a float option
I made custom floating subpatcher windows with float option - I added spacebar = close all
shouldn't be a problem for C74 adding float option to vst
or~
you can stick this code inside any patcher and bang it open to float (@EATMOREART)
then design your own custom vst controls
(maybe send them over to Juice to pretty up a bit - I never used Juice)
or maybe put the inline view (@Source Audio) inside patcher window
(I know nothing about Ableton)
I thought I prepare a little xmas cheer and wrote a little external to solve some [vst~] issues. It extends the original [vst~] object with some features:
- open floating plugin window
- temporary show/hide without pulling focus
- report plugin name
- report plugin latency
- unload plugin
I added a m4l device to the zip (not frozen, the external needs to be in the search path to make it work)
It shows solutions for:
- autohide plugin window when track is not selected
- recall plugin window state when loading Liveset
- report latency to Live
This is a beta version, only tested on my systems. Also there's lot of debug output to the Max window which I will remove in next version if it proofs to be stable enough. Another fact is that the external might stop working if C74 is changing the code of the original [vst~] object family.
🎅 is early! Thanks 11OLSEN, this is very cool -- your window management external expertise strikes yet again.
WOMM (works on my machine - M1 MacBook Air, macOS Ventura 13.6.1 Live 11.3.something and latest Max) in a pretty trivial test.
Behavior AFAIC is slightly different than the "standard" float window in that if Ableton is backgrounded (e.g. not the front app) but not hidden, the window remains floating on top as opposed to hiding the float window when Ableton is in the background. But it does hide as expected if Ableton is hidden.
Also the title bar is standard height rather than "thin" on macOS.
But I'm guessing you probably knew both these things already :-p. Really cool work, and I'm sure many folks here will find this helpful!
I'm not sure what's the better solution if I make them "hide when Live goes to background" you can't tweak a plugin if you have another app in the front? Or is this rare case?
Small title bar is possible.
🎄
Honestly, I only mentioned the "hide when Live goes to background" for the sake of consistency with how other plugin windows are treated in Live. I think very valid cases can be made both for hiding and not hiding it.