Linking a preset Name to a Labels text - Any ideas?

[d.healey]

I'm uploading a video tutorial for this now....

[LeeC]

@d-healey
Ah true legend man

[LeeC]

@arminh Not yet.
Hopefully David can lead us through this tunnel :crossed_fingers:

[arminh]

This post is deleted!

[d.healey]

You'll have to wait 10 minutes or so for the high q version to finish processing.

https://youtu.be/ra5Wrmi_z2Y

[LeeC]

@d-healey
Wow that video was crystal clear.

Learnt a lot about how callbacks work in HISE and the 'Save in Preset' or not to 'Save in Preset' stuff was golden - definitely wouldn't have discovered this myself.

All working now so thanks.

Your tutorials are second to none
Truly appreciate the insight man!

[arminh]

Thank you! You're master!

Btw, im trying to push sampleMapList to label but now I have all samplemaps

const var sampleList = Sampler.getSampleMapList();
const var sampleArrayString = sampleList.join("\n")
Console.print(sampleArrayString);
const var Label1 = Content.getComponent("Label1");
Label1.set("text", sampleArrayString);

[d.healey]

@arminh .join() takes all the elements in an array and connects them in a string.

For example [1, 2, 3, 4, 5].join("/n"); would become "1/n2/n3/n4/n5/n"

[arminh]

@d-healey so there is some method to pick current sample map name?

[d.healey]

@arminh The sample maps are in an array. So just use the index of the sample map you want. sampleMapList[index];

[Christoph Hart]

so there is some method to pick current sample map name?

Yes, there is Sampler.getCurrentSampleMapId()

Great video, Dave - there is also another advantage of loading the user preset you show before saving and that is that it keeps the Git commit history as clean as possible (otherwise it would be scattered with meaningless value changes).

The only thing I'd like to add to this is that it's a weird design decision to make a knob responsible for displaying the user preset name - for the sake of demonstration in this video it's certainly sufficient, but if people try to replicate this in their real projects it gets a bit messy.

The cleanest solution is using a timer and query the name periodically:

const var presetUpdater = Engine.createTimerObject();

presetUpdater.setTimerCallback(function()
{
    var text = Label1.get("text");
    var preset = Engine.getCurrentUserPresetName();
    
    if(preset == "")
        preset = "Gerald");
        
    // Check if it has changed before updating the text
    // in order to save a bit CPU.
    if(text != preset)
        Label1.set("text", preset);
});

// Check this 5 times per second.
presetUpdater.startTimer(200);

Normally, polling is not the smartest way of communication - the cleanest solution would be a callback onUserPresetChange() that you can use, but for this simple use case it is fine.

[lalalandsynth]

@d-healey Going through this tutorial and I keep getting warning at the else line.
"Found 'else' when expecting a statement"

const var presetLabel = Content.getComponent("presetLabel");


inline function onsliderInputControl(component, value)
{ 
      
    if (Engine.getCurrentUserPresetName() == "");
          Content.getComponent("presetLabel").set("text", "Preset 1");
      else
          Content.getComponent("presetLabel").set("text", Engine.getCurrentUserPresetName());
      
};
    
Content.getComponent("sliderInput"),setControlCallback(onsliderInputControl);

[Christoph Hart]

The semicolon at the end of the if line will terminate the branch.

This is the pitfall of omitting braces for branches, but it reduces the clutter.

[lalalandsynth]

@Christoph-Hart Thanks !

But you would suggest using the timer right or has anything changed in Hise since that post ?

As for using that knob , is that then supposed to be hidden , not sure what its purpose is .