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



  • Hey guys,

    Slowly making progress with HISE and I'm loving the journey.

    However, I've just stumble across something that I thought would be easy, yet I've been failing to get anything to work in the last couple of hours.

    The challenge?

    Is there a simple bit of code that can get the selected preset name from the preset browser and use this to set the text of a label?

    Any code or snippets welcome.

    Cheers



  • I've tried by using the code below but the text label does not pull through the selected preset ☹

    const var Label1 = Content.addLabel("Label1", 10, 3);
    Content.setPropertiesFromJSON("Label1", {
    
      "width": 358,
      "height": 30,
      
    });
    
    Label1.set("text", Engine.getCurrentUserPresetName());
    


  • You're living in HISE v1 world 😛

    Rarely should you need the setPropertiesFromJSON() function. Just setup your GUI in the interface designer and right click on widgets in the widgets list to get a variable reference for them that you can paste into your code. None of this Content.addLabel() stuff is required on a main interface script.

    Now to the preset name thingy.

    HISE doesn't load any preset when the plugin is first initialized. So Engine.getCurrentUserPresetName(); isn't going to work in the init callback. It's also important that you set the label's saveInPreset property to false.

    Now to get the name of the current preset when changing presets.

    After the on init callback completes, the control callback of each GUI widget is triggered (assuming the widget isn't assigned to a control through the interface designer's property ID system). Inside a callback for one of your widgets (I use my hidden sample map drop down menu) you need to put some code that will change the label's text.

    Something like this

    if(Engine.getCurrentUserPresetName() == "")
        Content.getComponent("lblPreset").set("text", "My Super Preset");
    else
        Content.getComponent("lblPreset").set("text", Engine.getCurrentUserPresetName());
    

    What this code does is check if there is a preset name from Engine.getCurrentUserPresetName()- this is important because, remember, when the instrument first opens this function will return "" as no preset is loaded by default. So inside here we manually set the label's text to whatever we want the "default" preset to be. In my example I've set it to My Super Preset but you should set it to whatever you want the default preset to be.

    Then the else part will fire whenever a user selects a preset from the preset browser.

    Before you export your project as a plugin to give to the end user you need to load your default preset from the preset browser and resave the project.

    There are loads of forum posts on this subject already.



  • Thanks @d-healey.

    Ok so that all makes a lot of sense and the "You're living in HISE v1 world" quote made me chuckle.

    The only thing that I'm not 100% clear on is where to place the example code you've laid out.
    So can I place this inside any callback written in my code like the one below?

    inline function onhideShowControl(number, value)
    {
            panel1.showControl(value); 
    }
    
    hideShow.setControlCallback(onhideShowControl);
    

    If so how would this be placed & structured in order for it to work?

    Sorry for all the newbie questions.

    Appreciate all the patience and feedback man ☺



  • @LeeC

    Hey, you made it? 🙂 Because I looking for solution 😛



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



  • @d-healey
    Ah true legend man 🙌



  • @arminh Not yet.
    Hopefully David can lead us through this tunnel 🤞



  • This post is deleted!


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



  • @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!



  • 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);
    


  • @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"



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



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



  • 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.


Log in to reply
 

6
Online

506
Users

1.8k
Topics

13.8k
Posts