Design concept question [selectable GUI]

[RJHollins]

ooo ... the NuBeat multi-function slider ...

it is a favorite over here !! This is a really nice function you put together, and probably holds the secret formula to handle all the knobs, sliders, button values.

I might be jumping the gun ... but it seems this 'multi-function' routine could be defined by the 'slot number', and thereby, have discreet values regardless of how many may be in use.

It's late evening [morning] here, and just getting back from my gig ... but I think this could be a good solution.

If so .... you guys are great !!! and if not .... ya still R

[RJHollins]

Hi GANG,

Well ... I've put together a proto-type of a 'multi' module. This as a test to see it in its most basic form.

What we're working with ... again the EQ example.

I have 4 basic eq bands that are grouped by their 'Q-factor'. This would be Narrow, Medium, Wide, and a Shelf. Each are discreet in how they work ... and, more importantly, this is what I'm givin to work with.

Basically, I made a GUI for each EQ, and then using the 'multi-tab' concept, I choose a Radio button array to switch to a specific GUI.

It works as expected ... not really a problem as to function.

The bigger issue is the 'size' of the file.

I have 9 of these selectable modules, each containing the 4 individual GUI's ... so that means some 36 GUI's. And of course, each of these GUI modules are fully functioning within themselves.

Basically ... there is an obvious mucho duplication of every internal function and graphics.

Like I said ... this was the basic, crude design to see what I would be facing.

Even though the entire proto-type works fine ... I did notice that the VST takes a long time to load, and clocks in at about 10 megs

Not sure ... but I'm trying to think of ways to streamline this.

[tester]

If your guis have the same content, you could use single gui and arrays to drive different selections.

I'm rebuilding one of my apps too. Right now I just stuck with too many triggers to make one thing work correctly with presets. :-] But it's doable. Trog was going to help me a little bit, but he disappeared then suddenly (yet judging by the stats - he is visiting here?).

[RJHollins]

If your guis have the same content, you could use single gui and arrays to drive different selections.

Hi tester,
yes ... each of the 4 group modules are currently being replicated 9 times.

The single GUI /arrays sounds an interesting concept that I'd like to learn more about.

[tester]

Just play with "preset parameter array" primitive. It has singular input/output and whole array management. Rather easy to wire, just check where you need to retrig values on change the index.

Having said this - you can use the same indexes to drive colors and items on the singular gui (in some cases, for switching - it's better to use selectors instead of multiplexers).

[RJHollins]

Just play with "preset parameter array" primitive. It has singular input/output and whole array management. Rather easy to wire, just check where you need to retrig values on change the index.

Having said this - you can use the same indexes to drive colors and items on the singular gui (in some cases, for switching - it's better to use selectors instead of multiplexers).

ahhh ... sounds good what I'm reading from you.

I've not really played much with the "preset parameter array" primitive ... I should start by re-reading that section in the manual.

I know the work that NuBeat did on the 'Multi' slider [really nice] ... that I've been looking over to glimpse some ideas from.

I know this is not usually found in examples or forum discussion, but I'm still searching to help understand this better.

I hope that if I can get a basic concept to work, that I can then build from there. Got some study/experimenting to do.

All insights most welcomed and appreciated !

[tester]

There is nothing to understand. If you use the array preset prim, then your preset manager (loading) should work faster a little bit, because you will have less single parameters to handle. All array elements can be automated anyway.

Just wire whatever basic setup, I don't know - with editbox, button or so - and see what works and what isn't working. If something isn't working, then you will know what question to ask. But as I said - you should be able to wire it within 5-10 minutes, without manual, just trial and error method.

Even if your gui elements have different positions on the schematic - it should be not a problem, because you can switch "area" coordinates from one place to another.

[Nubeat7]

hey, i dont exactly understand how you need your it but here s a little example of how to use the presetarray parameters

the preset module inside the knobs is taken from the multifunctional slider just use any knob you want and use the wireless 'set' to set the knob on presetchanges..

there are different ways to extract the individual parameters from the array, you will find 2 in the example..

hope it helps

[RJHollins]

You are something Mr NuBeat !!

I just dL'd the schematic you posted, and getting my first look inside.

I recognize, you now 'classic', multi-preset module

Obviously I need to study this ... but thankfully your layouts are clean ... I need to understand/ get familiar, with how this all interacts.

One point of confusion ... the ruby selector that lets us select 'Low Pass, High Pass, Band Pass, Band Reject,Peaking', is not updating after the selection ... however, the PresetManager is registering the selection. When I change preset [1-3], THEN the ruby selection is updated.

back to study !

BIG THANKS Mr. NuBeat

[Nubeat7]

oh thanks RJ, yes the selector needs a after change trigger to update the label, i reuploaded it - should work fine now..

the reason is that the selectors label and selection is updated by the check input and not by interaction with the selector (like it works with knobs or faders)