knob tooltips

[Nubeat7]

maybe it works better with a ruby based solution for the "if mouse is in area" boolean..

[aombk]

anyways if you set mousemove to false my info panel still works but only if you move the controller

interesting

btw. 448 controllers without any direct or intuitive info in one tab is just a pita for any new user, also if you have your info panel you always would need to search for the right controller, for me this would be a reason to abandon the best synth ever..

i understand. i have a feeling this would be the case with this synth for many people. but i am building it according to my taste and i have abandoned synths for the exact opposite reason. for having multilayered guis and important but hard to find options in menus and submenus etc.

great, i am going to look into a ruby based solution mouse in area boolean. thanks.

[aombk]

btw here is the reaktor version.

it has tooltips for everything like the one on top left, if you can see it, and it also features visual info for all the envelopes and lfos and of the math calculations between them (those thin blue lines if you can see them)

its extremely optimized but that was a lot of work, i admit.

[aombk]

nubeat7, i think it might actually work, using the isInMousePoint ruby method. i am close but i have to go now. i will post results later. thanks.

[Spogg]

On a few occasions I've had controls that are "sticky" in Flowstone but work as smooth as silk in the exported VST(i).
I assume this is a trigger avalanche in FS but why doesn't this happen equally in the exported VST? Is this optimised during compilation by FS for example?

It does happen in the exported VSTi, you just don't notice it anymore. That's because within Flowstone you work in edittime. Flowstone hooks in to everything you create to keep control. That's a lot to do for Flowstone. However, in an exported plugin there is no need for any Flowstone control. So this overhead code is not part of the export, which gives the plugin more cpu time to work with - and therefore a way to deal with the trigger avalanche better than in Flowstone.

Thanks for the explanation tulamide and I do understand. My conclusion is that the trigger avalanche can still have an effect on the performance of an export then, although much less than in FS. I guess that in a situation where the DAW and plugins are close to the limit then this trigger issue becomes critical.

Cheers

Spogg

[aombk]

success!
it now works like before, but without any visual performance hit
thanks Nubeat7 for the hint

[Nubeat7]

well, i just did a fix too, then i saw you already got it..

anyways here is mine, its basically the same as yours, just one thing, you should put a "change" primitive on the mOver output, like this it sends a trigger only when changing true or false, otherwise it sends triggers everytime the mouseposition is moved!

just put a triggercounter on the mOver output on your version to see the amount of triggers...

[aombk]

great help, thanks

[aombk]

ok here is a simplified version of my knobs.

with this new optimized ruby isInMousePoint method, when the mouse movement between the knobs is fast, some descriptions stay on.

can this be fixed?

also, the knobs module shape is this way to help me add both the knob and its description easily and move them together. but this way it is easy for knobs to overlap and that makes it hard to arrange (hope these sentences make sense)

can this be done any better way?

[Nubeat7]

how about this..