Ruby component bug

[TrojakEW]

Look like more ruby comonents means more closing time for application. I have done simple test. I have added 256 slider controls made only from green primitives to fsm. After closing this fsm, flowstone respond immediately. I created another project but with sliders made with ruby - same number 256. After closing, flowstone doesn't respond a few seconds. Normally I wouldn't care if this was only after closing project in flowstone but this happen in exported vst too. Not problem for small plugins with just few controls but big problem for bigger project.

I have noticed this only because I have started replacing all green primitives with ruby in my plugin. Version with green primitves works fine even with multiple instances. Closing project in daw is instant. New version with ruby components cause daw not to respond or even crash on close.

Everything else works fine, not a single problem. Only closing is problem. My new plugin use ruby for GUI, thanks to this there are much less components, less links, file is smaller and it is also easier to adjust properties if needed but the cost is high. Hope this can be fixed since returning back too green is not an options for me.

[Nubeat7]

what slider do you use?

maybe there is some programming issue? i also only use ruby components for all gui stuff and never recognised something like this....

some test schematic would be interesting

[Nubeat7]

just tested it with the stock slider no issues here...

[TrojakEW]

Well if you have fast computer i7 you may need more then 250. I have old athlon x2 and I can see difference. If I use about 700 these slider flowstone not respond for about 9 second after colsing. This not happen with green version.

[TrojakEW]

Well There is no need for a code in ruby. I just added 4096 empty ruby modules in schematic. This take about 25 sec to respond after close on my computer. Don't close flowstone just project in flowstone.

My plugin use 935 ruby modules for now. It takes about 4-5 sec to delete plugin from a channel. After use 6 instances of plugin it daw stopeed to respond at all (if I try tu close or create new project in daw). Works like charm without ruby modules.

Standalone version work fine too.

[Nubeat7]

well you are right, this is an interesting test i did the same test using green float nodes and it has the same effect!

maybe its just too much modules? you could try to reduce the ruby modules merging some into bigger ones also try not to work into very deep levels, i think there is no need to get deeper than 6 or 7 levels when the schematic is well structured

[TrojakEW]

Well that gren test work for me like charm. After close no wait.

As for the plugin well I can't reduce that number. Ruby components are at different places doing diferent stuff. I have already reduced that number as I can. This plugin/project is quite big synth with many controls and features. Well may by it is possible to put all controls/create whle GUI with one ruby module but it is impossible for me, don't have that much ruby programing skills that's why I choose flowstone.

[Nubeat7]

ha, funny thing, yes the greentest works like it should be, the waiting time was just when i deleted the rubyparts and included the green ones, then it freezes on closing!

when you use pages with controls you also can use one controller for more functions

viewtopic.php?f=3&t=1802

[TrojakEW]

It is good idea, but I use ruby not just for knobs, sliders and controls.

This ruby "bug" thing needs to be fixed.

[billv]

crash on close.

I had that issue throughtout the X11 re-build....
Don't know what cause's it to happen...but its gone now...
i did manage to get rid of it somehow....got no idea 'how' though...