Bryntes Knobman Pack Vol.1

[djbrynte]

what do you mean with button? i can easily make a button in this program.

[kortezzzz]

It seems knobman just generates a vertical strip

That's exactly the problem! knobman makes only vertical strips, while the stock knob uses horizontal method.
Found that out today after extracting the stock switch's bitmap, so that's why knobman knobs never worked for me with ruby controls.
and that's the actual fix that needed; the code should follow vertical strips.

Anyway, another strange behavior of FS: when combining a vast of ruby controls (knobs, switches) in big schematics,
you may end up with "out of memory" or "runtime error" message while saving the project. These messages allready ruined for me few hours of tweaking. Removed half of the ruby controls from my project and these messages stopped. Did anyone else experienced it?

[tulamide]

Did anyone else experienced it?

I didn't experience it yet, but have a pretty good guess. You probably just grab the knobs from the toolbox, maybe change the bitmap here and there?

Let's assume a knob with 100 steps at size 48x48 pixels. That's 48*48*4 bytes per frame, or 9216 bytes. 9216 * 100 = 921600 bytes, or 900 kB. That's just one bitmap. Assuming 20 knobs, you're already at 17.5 MB. Is there a bitmap sample and hold somewhere? Add 900 kB per s&h. Etc.

You can optimize it, given that you have a lot of knobs that just look the same. Then delete all bitmap loaders from them and instead place a wireless in. Make a module where you load a knob bitmap and give it a wireless module out. If both, in and out are named correctly, you now have dozens of knobs that only use one bitmap. So only one bitmap is saved with the schematic.

[RJHollins]

If both, in and out are named correctly, you now have dozens of knobs that only use one bitmap. So only one bitmap is saved with the schematic.

woooo .... thanks for that tip !!

[kortezzzz]

You can optimize it, given that you have a lot of knobs that just look the same. Then delete all bitmap loaders from them and instead place a wireless in. Make a module where you load a knob bitmap and give it a wireless module out. If both, in and out are named correctly, you now have dozens of knobs that only use one bitmap. So only one bitmap is saved with the schematic.

Thanks for the tip. I already use this approach for long time, but as you can see, seems like many of us not yet know about it, so well done with posting.

Anyway, I don't think that this problem is bitmap size related because the same schematic with the same knobs
and controls loaded into green knob circuits never crushed before, but somehow, when using ruby knob circuits,
they do crush. I suspect that ruby badly deals with the ram in FS behind the scenes and never clear the ram after changes has been done in the schematics nor even modules has been deleted from it. I just don't have any other explanation, considering the fact that while ruby controls in VSTs are away more cpu friendly, they use almost 500mb ram more in my schematic and on some daws, like ableton, they just come out of order (maybe because of 32bits ram limitation? I dunno) and I have a proof for that.

[Nubeat7]

i never had any troubles like this using ruby modules, Repeat x has over 130 ruby controls inside plus 16 stepsequencers, 8 snapshotselectors, an 8 channel fx on/off sequencer and a FX chainer all done in ruby.. and it loads and works like charme...

i also would suggest to use "multifunctional GUI elements" where possible -> watch this thread: viewtopic.php?f=3&t=1802

like this you can reduce similar tabbed GUI elements, for example if you have 3 oscs which are tabbed you only need the controls for one osc and use them for all 3...

[Loopeytunes]

You can export control knob designs from knobman in horizontal too, just click the "preferences" in the top left corner of knobman under where it says "add" and then about half way down on the gui that pops up select "horizontal" from the "orientation" section and when you export your design it will export in horizontal format.

Loopey

[kortezzzz]

i never had any troubles like this using ruby modules, Repeat x has over 130 ruby controls inside plus 16 stepsequencers, 8 snapshotselectors, an 8 channel fx on/off sequencer and a FX chainer all done in ruby.. and it loads and works like charme..

Well, the problem is my schematic is bigger. A lot bigger. I beleive you already know how big . maybe my expectations from this 32bit FS platform are way too overweening. I better learn how to keep the feature list reasonable or I may miss the "big picture" features per performance.

like this you can reduce similar tabbed GUI elements, for example if you have 3 oscs which are tabbed you only need the controls for one osc and use them for all 3...

That's great concept. I'll try that.

You can export control knob designs from knobman in horizontal too

great news! I'll try it when I comeback home and report. maybe its time to squint at ruby

[djbrynte]

Ah ok your making efgfects with big knobs?

[kortezzzz]

Ah ok your making efgfects with big knobs?

The knob size doesn't matterS. The problem was that i didn't
know that knobman can create horizontal strips as well. Checked this option today and it 100% works with stock knobs! all you have to do is export your buttons using horizontal method and load it into the stock knob. After loaded, fit the properties to the knob's size.

Thanks @loopey!