BrainModular

I am trying to set up a preset manager so that incoming value anywhere from 0-15 recalls preset 0, values anywhere from 16-31 recalls preset 1 etc.
These values are all being sent from a single listbox that has a range of 0-127
I think I need to filter value ranges, and then remap any value occuring within the desired range to a value of 1, and then connect this to a recall inlet on the preset manager, but I am having a heck of a time figuring out a way to make it work consistantly.
I have been trying mostly with Min,Max,<= and >= modules...
...anyone want to save me some pain?

maybe with: list box (0-127) goto AmodB, (B=16) , directly to preset recall nb?

or list box (0-127) , A/B (B=16),round, preset recall nb

If I make B=31 A/B (B=16),round works for selection of the first two presets (0-15, 16-31) . After that I get nothing. ..?
I am trying for splitting the ranges between a preset manager x8 (so 128/8)

AmodB just cycles through the presets per value input, restarting from 0 every eight values (or whichever value B= ).

It seems like it should be so simple....but my undestanding of the math modules is limited.

Hi,

Just try:

Fader (0-127) -> A/B (B=16) -> trunc -> pass if has changed -> preset manager num in

Hope it can help,

Rgds,


B.

Thanks bmoussay. Your solution works fine for me

Same patch different problem...
The purpose of this patch is to unify eight preset managers so that they behave as one large preset manager with 128 slots, while using minimal cpu.
The problem I am having with this patch is that when I select a preset from a different preset manager than the one that is current(via the listbox), more than one preset manager is recalling its preset.
I had the same results also when trying to use renaming busses as a method of selecting the active preset manager.

Here is the patch so far if anyone wants to have a look. Only the first three preset managers are integrated so far, preset selection 0-47 is made via the listbox:
http://www.sensomusic.com/forums/upload ... 20test.pat

[edit: I don't know why but this example patch needs to loaded as a sub patch or the values stored in the top PMx8 are lost]

uhh ok, I don't exactly know why or how it wasn't working but I have another solution...ps thanks 23fx23 for the A mod B suggestion.It''also ended up helping me in the end.
Preset Manager x128 to be uploaded to addons as soon as it has passed final QC.