Storing data in widgets

[d.healey]

@toxonic

does "preset" in this case mean: preset via the presetbrowser?

Yes, whenever I talk about presets this is what I mean, unless I specifically say otherwise. :)

so you can control the selection of presets via keystrokes

No. User selects the preset from the preset browser. Do you want different keyswitches for different presets?

[toxonic]

@d-healey

Yes, whenever I talk about presets this is what I mean, unless I specifically say otherwise.

okay, do not mind me, i wasn't sure! ;-) and if i'm honest, i don't really know what you mean with that sentence

If you want different key switches for different presets then you can use a combination of scripting and widgets.

since this somehow contradicts with

No. User selects the preset from the preset browser.

or did i misunderstand that?
but yes, i want to different presets with different keyswitches on my midi keyboard. ;-)

[d.healey]

The user selects a preset from the preset browser with the mouse - not the keyboard.

i want to different presets with different keyswitches on my midi keyboard

I don't quite understand what you want. You said this previously:

C4 on my keybord to play range from sample 0-40000 of the loop,
C#4 on my keybord to play range from sample 50000-60000 of the loop and so on?

Will those keyswitches, C4 and C#4, be used for all presets or do you need each preset to have totally different keyswitches?

[toxonic]

@d-healey
uhh, i really seem to express myself very awkward, i'm sorry for that. :-/
i want to store different loopranges (AudioWaveForm) to different presets. by pressing a key on my midi keyboard i want to select a specific preset and play the looprange saved within that preset.
C4 -> looprange a (saved in preset 1)
C#4 -> looprange b (saved in preset 2)
D4 -> looprange c (saved in preset 3)
....and so on
got me now? thanks for your patience with me, my english is quite poor and my HISE knowledge as well.... :-/

[d.healey]

What do you want the combobox to do?

Will you need to change the loopranges from the interface?

[toxonic]

@d-healey
okay, my first problem was storing data (start and endpoints and maybe other values) persistenly and recalling it. the combo box was just to select the.... how should i call it..... snapshots? it was only for experimenting purposes, it seemed quite handy to me for that task.

[toxonic]

@d-healey said in Storing data in widgets:

What do you want the combobox to do?

Will you need to change the loopranges from the interface?

later i wanted change this to control via midi keyboard

[d.healey]

We're going around in circles. But we'll get there! :)

Why do you need to store data at all? Why can't you just hardcode the values?

[toxonic]

@d-healey

hardcode the values? you mean, they are not changeable anymore? this instrument should become something like a loop-slicer, where you can load sampleloops in, and then rearrange them in a DAW. When the values are hardcoded, the enduser would only be able to use the one sampleloop, the hardcoded ranges fit to.

[d.healey]

How many loops will be loaded at one time?