settitle on VST~
I am quite proficient in graphical environments ususally,
but I’m stuck on something that is simple.
I want to send settitle on my VST~ object.
I am wondering what to type in the message box?
I have tried a few commands, but no dice.
The manual says it is simply
settitle followed by a symbol
Any help is much appreciated,
sorry for being a newb 8D
Thanks mate, have reported it
Can I get confirmation that I’m not doing something wrong?
I didn’t get a reply to my bug report.
I am really wanting this to work.
I desire this capability muchly
I didn’t recieve any reply to my bug report,
it might be my fault for not being clear-
but anyway, I want to make a VST host and I have to have this, otherwise it will be confusing.
Can anyone confirm the bug?
Or suggest another way to delineate one window from another?
I see the ~VST object has been updated twice since the OP,
any chance of getting a fix for this?
It would be far neater than me creating a name window on my VSTs.
Maybe I will make a Rebirth type creation anyway,
but yeah, really would like this seemingly trivial thing.
bump for a reply
Sorry about that. I can confirm and the report is now logged.
my bug report example might not have been openable,
so no worries.
Just wanted to mention and make a feature request-
could we possibly get a MIDI in pin on VSTi~?
I have made a hack that lets me do this using the MIDI parser,
but it is not ideal. Currently you have to declare- prepend midievent,
and get the data from the parser.
Also- velocity will not show with MIDI sequencers built in FlowStone.
I have hacked around these issues,
but a MIDI in pin would be nice, and why can’t I see velocity after the parser?
My Korg Nanokeys however is telling me the velocity,
weird incompatability with FS MIDI coming in.
However- I am so happy that the MIDI signal remains poly after the parser,
8D 8D –nice work
Heya- still waiting on this.
I will buy 7 if settitle is implemented
+1 – would be great to have this fixed!
it is still listed as a working command in the vst helpfile.
but then again, the helpfile also suggest to load audiounits with the windows version of the external.
btw – i dont want to argue against your request – but i think what would be far more intresting than renaming the window would be that you should be able to save the windows location. in maxmsp probably only through a workaround (the vst object could provide the window location coordinates as a mesage from the last outlet so that you n save it to disk in the way you like.)
Forums > MaxMSP