ssbothwell

hi. i am using bpatcher to create VST modules for a signal processing chain. i know that i can set values in the VST plugin using max messages and that i can use the 'open' message to load the VST's GUI in a new window. however, both methods are a little inconvenient and i was hoping i could simply embed the VST's GUI inside the bpatcher frame.

embed-vst-plugin-interfaces-inside-a-bpatcher

no unfortunately. I requested this feature but I think it is a tricky one to implement to be honest...

Endless Series v3 out now - A unique synthesis and effect plugin based on the Shepard Tone auditory illusion.

----
Endless Series v3 out now - A unique synthesis and effect plugin based on the Shepard Tone auditory illusion.

oh thats too bad. i guess i have to deal with them being in seperate windows.

you could create a custom interface and control the VST from there

quote Roman "you could create a custom interface and control the VST from there"

This is fine and easy to implement if you are happy dealing with 0. - 1. parameter values and not the 'real parameter value' (as I call them :-)

Otherwise you could end up spending alot of time building tables to convert to 'real' parameter values.

Many parameters don't translate easily from 0. - 1., for example I have done this for Lexicon VSTs, and there are many non standard exponential conversions that were most easily resolved with lookup tables, and one parameter comparison in particular where the changing 'room size' changes the 'reverb time' in 'real parameter value' but not 0. - 1. value.

Good luck I say if you take this approach!

This is fine and easy to implement if you are happy dealing with 0. - 1. parameter values and not the 'real parameter value'  (as I call them :-) 

Otherwise you could end up spending alot of time building tables to convert to 'real' parameter values. 

Many parameters don't translate easily from 0. - 1., for example I have done this for Lexicon VSTs, and there are many non standard exponential conversions that were most easily resolved with lookup tables, and one parameter comparison in particular where the changing 'room size' changes the 'reverb time' in 'real parameter value' but not 0. - 1. value.
Good luck I say if you take this approach!
Regards,
Leigh


i am aware that i can recreate the interfaces in max. as a general policy i try not to reinvent the wheel. :)

i'll just deal with the interfaces being in separate windows. thanks!

i am aware that i can recreate the interfaces in max. as a general policy i try not to reinvent the wheel. :)
i'll just deal with the interfaces being in separate windows. thanks!


Would also be keen to know if this is possible yet?

i think this might involve getting every single VST maker in the world to create a way to encode their interfaces in the max text-based format(that allows you to copy/paste/embed anything in the first place... the VST makers would then have to standardize their interface to utilize UI objects specifically available to Max, or pass their proprietary graphics to Cycling74)... that's not up to Cycling74, so it's most likely this will never happen(probably better for all of us they focus on developing other features of Max, anyways).

it sounds so simple: displaying a window and its content in another window. but in practice it is almost impossible.

embed VST plugin interfaces inside a bpatcher?