DSP Robotics Support

Thanks for the update ! Seems to work as you intended

I'm flipping back and forth between this, and the original you posted ... searching for what change you made.

?question? Was the 'change/fix' made in the RUBY code ?? Just trying to learn.

the change was in the presetmodule, the wireless 'set' sender needed an afterchange trigger to update the selector,

the thing is that the selector (label and current selection) doesn`t update itself when interacting (like knobs or faders do)so they need the updated information via the check input to get the label and the actual selection flag updated

OK ...

been playing and experimenting with the latest NuBeat example. Still at the 'trying things out' point, as I'm trying to learn this new way [for me].

I'm focusing mostly on the GUI stuff ... in fact, the actual EQ modules I've placed outside the example module .... as I mentioned, the EQ was a visual example of sorts. Most important is getting the GUI to respond correctly.

I've been able to do a couple of simple mods.

A 'radio' button selector has temp replaced the pull-down for the moment [although both select methods desired].

I've been able to trigger active updates of each 'status' to post actual values when switching.

Then the playing .... Again ... new ideas for me.

I use NuBeats GUAGE to display available knob values around the knob. I just learned that I can use a 'selector' tied to the radio INDEX that will switch different array values that feed the GUAGE display. This works perfect ... gonna have to consider using this idea more !

The same idea is also being used to load a 'pull-down' menu [again, another NuBeat refinement]. I still have to work this out a little more ... need the specific selection in the pull-down to be recalled when switching ... this probably needs to tie into this special 'multi-preset' module.

I'm needing to replace the example knobs [as I prefer either bitmaps - with [CNTRL-Click] to return to default, with the [SHIFT-mouse] for fine control. But I'm also looking into the VECTOR design.

The VECTOR knobs might hold the key to allow different STEPS to be used all from the same knob. The bitmap design seems to have difficulty if the render steps don't match .... even if doing 128 step rendering.

I would like the flexibility in this entire GUI concept to set STEP values in real-time, in other words, switching from one 'band' to another might have different number of values available, so the STEPing might need to change.

I know that I'm not describing this whole thing as clearly as I should ... it would be easier to see a picture of the concept. But NuBeat is pretty close on the general concept.

To maybe help ... if you are familiar with what are called 500 series Racks ... they hold small module EQ's, Preamps, etc .... they are all self contain modules that share the rack power supply and audio routing.

For an EQ, these modules might come as a HI/LOW filter, a parametric, or even different 'flavors' of sonic design.
The overall 'rack' may be able to hold 8 separate modules.

The 'concept' I'm looking at is similar, in that the user can select WHAT specific module they want in the rack. In any order, and in any combination .... heck, they can all be the same or any mixture.

What I'm trying to break away from is a predetermined design layout and function. We've all seen the typical 4-band EQ that has a LOW, MID, HIGH peaking filters and a Shelf. What I'm looking at is letting the user configure what type of bands they want/need. Maybe they need 2 MID bands ... or maybe 3 ?!?!

This may sound crazy to some .... or maybe not .... but this is the goal of the design to let the actual user configure the layout as a more 'modular' concept.

The challenge is to make this work flawless and efficient. I would like each module to 'remember' it's settings within it's rack space. As I think this through, it may be important that each 'slot' in the rack have an ID type number that would be used for the global preset manager.

The original proto-type I did on this works .... but it is a basic design that relies on 'video' switching of GUI modules [exactly like the Multi-tabbed windows]. My crude way needed each module to contain everything, and this means duplication upon duplication. It works ... but it is not elegant. Going in and making an change or adding a feature means 4 or 5 times the changes [non-synchronized modules ].

Still much experimenting to do .... but this initial concept from NuBeat provides a doorway to a different approach that could be much more efficient to accomplish this design goal.

Thanks for helping me to learn new things !!!

made some progress

Starting to get this multi-function GUI design working with some of the planned options.

I've substituted in a VECTOR knob that needed to be modified to handle the multi-preset module. Seems like its behaving well, as it recalls settings and values when switching both from the radio button selector and the Preset Manager.

I've added 'LIVE' setting of the STEP function for the knob, along with a dynamic change of the GUAGE. We also now have switching color enhancement of the knobs to aid visual navigation.

Next up is adding a different pull-down menu. What needs to happen is, each selected 'band' can have various EQ characters [so to speak]. I would like each selection to be recalled when changing through the combination of bands. This to insure that each setting resorts to what the user had selected. Again this probably just entails proper PM assignment. [i hope] That, and dynamically loading the pull-down menu. Again, I'm looking to NuBeats pull-down menu to handle that role.

The schematic is still in a 'bread-board' layout, but once I don't need to see everything at once, I'll start organizing things into modules.

This is getting interesting to put together now.

NuBeat's example really help open my thinking with a whole new approach. The things that I've modded or added were really simple to do [looking back]. The KEY is the special 'Multi-Preset' module that handles the arrays. Most everything after that is rather straightforward FS.

The cool part is now I'm doing things in quite a new and different way [for me], and this has again opened my thinking to new strategies and solutions. It's like the first time I used the BUS primitive That was a great piece that helped turn a complex problem into a manageable solution.

I am still humbled when I see how the GURUs design a schematic. I have nowhere near some of that sophistication ... but I have improved over this past year since starting SM/FS. With each project I'm trying to advance the design and function, as well as simplify the schematic.

Big THANKS to everyone that shares their insight and knowledge here on the forum. It may not get mentioned often enough ... but it is certainly appreciated.

Still wrestling with the pull-downs

Come back to it when brain is less mush

OK ... making some more progress

I've got the pull-down menus working in the multi-GUI design. I did 2 different designs.

One using NuBeats 'box' menu, and then a modified FS menu. Both can be loaded with choices dynamically, and each of the selected [checked] entries are properly recalled when switching modules.

I've also added some switches in the graphics display that can blank the display when the 'empty' selection is made. Basically wanting a plain background when no 'eq' module is selected [these are the empty slots].

I've 2 more GUI parts that need to be retrofitted into this multi design. One is a button for switching things on and off in the module, the other is the multi-function sliders that NuBeat designed. These 2 are proving to be somewhat difficult to do the modification too Hopefully I can solve these.

hmmm ... I'm stuck .... trying to adapt the NuBeat, 'multi-function' sliders into this new multi-GUI design logic.

I've gone back to the basic example that was posted in order to simplify the troubleshoot and implementation.
Here's the example screen shot


The slider is a dual function one that uses the same slider with a button selector to choose S1 or S2 [or more].

The main PreSetManager captures all the preset settings, and already works, using NuBeats special 'preset' module.

What I'm trying to do ...

At the fop of the schematic is a 'FLT' menu, that dynamically switches the GUI and values. The complication is how to tie the multi-slider into this design that would maintain both values in each selected 'FLT' independently. In other words, just as the knobs retain their value, so must the multi-slider.

Trying to figure out the logic of this

All my attempts have failed ... so this is why I post the most simple example.
Here's the schematic .... hope someone can figure how to do this

well .... I kinda got something working .... but, boy ... it seems a lame solution .... even for me

I switched out the select button with another that was easier to modify [its amazing how many different button designs [internal] there are [from various SM/FS posts].

As to the dual-function sliders ... the 'lame' solution was monitoring 2 'indexes' .... 1 for the button, which has 2 states [0,1] ... and then the 5 positions of the main INDEX.

The NuBeat preset module was assigned 10 entries .... I'm still not sure what to do with the preset 'names', if I should use a string name with an added index number !??!

On the main INDEX, I fed that to a SELECTOR PRIM, and used INT strings for each choice [0,2,4,6,8].

On the SELECTOR output, I fed an ADD prim to combine values of the button index and the main index ... this then was fed to the preset 'select' input.

Monitoring the array output, I can see each array being addressed .... but this is really a rookie looking solution it seems

Also ... still not sure how to NAME the presets. Should I use a index number suffix to a function name ? or just a name ... i don't know yet.

Anyway ... just trying an idea that's starting to work .... but really hope for a better way.

RJHollins wrote:I'm still not sure what to do with the preset 'names', if I should use a string name with an added index number !??

each preset array prim can only have one unique name and gets numbered with the indexes automatically like :
presetname 1
presetname 2
presetname 3
.
.
.
what you try to do is a nested preset array - i think your solution is pretty smart - but you need to live with the same presetname and if you want to automate it, parameters will be shown in daw as above,

not sure what this switch is used for? it is meant as switching between 2 snapshots of one parameter or?

Nubeat7 wrote:

RJHollins wrote:I'm still not sure what to do with the preset 'names', if I should use a string name with an added index number !??

each preset array prim can only have one unique name and gets numbered with the indexes automatically like :
presetname 1
presetname 2
presetname 3
.
.
.
what you try to do is a nested preset array - i think your solution is pretty smart - but you need to live with the same presetname and if you want to automate it, parameters will be shown in daw as above,

not sure what this switch is used for? it is meant as switching between 2 snapshots of one parameter or?

ahh ... OK on the preset names. The more I thought about, it does make better sense.

The button that switches the 'dual-fader'. The function I had in mind was to use this as a [CC] Continuous Controller that could be alternated between 2 different controllers. [or as you originally designed, as many controllers as needed]. This was to maximize use of GUI space. I have been using this idea, and it works great.

The way I have it in my 'complex' schematic is having BOTH values displayed, so that the numerics are always visible. The button switches to activate the desired [CC}. The 'hidden' value is displayed too. What is really nice about this ... when the button switches, the slider SNAPS to the correct value.

I'm going to go back and check my preset naming. I think I had over-complicated that by tagging the index number onto the name, sending that to your preset module. I think that was working with the knob and pull-down elements ... but now seems I did this wrong [or at least, over did it]

mmm ... nested arrays. I need to think about that idea. I think I just stumbled onto that [not realizing], but I did get it to work [I need to be sure its solid].

Thanks again NuBeat for looking over my shoulder, and providing some great examples and concepts.

This 'multi-function' GUI has been something I've always wanted to have available ... so I'm trying to plan out/design all the type of components that I usually need to tackle a project ... knobs, buttons, sliders, menus. Doing something like this can get messy real fast, so I thought I'd best focus on building the pieces first, in a way that is as simple to customize and follow.

I should probably post what my design is coming together as.

Another cool feature, since building on the VECTOR knobs, is an easier way to go from STEPS to continuous control. [or at least 128 MIDI values] ... all with the same knob.

again THANK-YOU !