@d-healey Okay I understand what you mean and agree with what you're saying. I am currently watching your video again. Thank you for your help.

@d-healey Ok thank you for the reply.

I designed the plugins, how I want them to be etc, before joining HISE or learning anything about scripting. The idea is to create Sample Based Instruments from my own instruments that I have recorded & mixed through analog hardware that would have a tempo synced Attack, Decay & Release.

Whenever using other instrument plug-ins I always prefer to use the ones that have this option, like Omnisphere etc. I find having to calculate the ms with a reverb calculator very time consuming and was hoping it would just be simple to change the ADSR from ms to beats.

I don't really have the time at the minute to learn all about Scripting in Hise, what I have already learnt is from previously watching your video you have mentioned on YouTube. Most of what I need to do in order to complete the plugins is possible without scripting, it's just a few things like the Tempo Synced ADSR etc. So I may need to leave it in ms for now & come back to Tempo Syncing at a later date when I have time to learn scripting properly. Either that or it seems to be possible in Scriptnode which looks similar to MAX which I'm familiar with, so I will also look into that.

Thanks.

@d-healey I have read the link & opened the snippet but I just don't understand it. I know very little about scripting & I have been building most of the plug-in without it.

Again though, if the knobs are synced to the DAW, what happens when the user moves the knobs manually?

I'm not sure I understand what you mean by this question. I intend for the whole plug-in to be tempo synced to the DAW. If the User moves the knobs manually I want the tempo of the Attack, Decay & Release to change in beats, not ms?

@Chazrox Thanks, I've done something different for the Preset Browser now, but I'll definitely check this out.

Is there a way to change the maximum height of the ComboBox drop down so it becomes scrollable & doesn't cover the whole GUI.

@d-healey @Lindon

Great it works, cheers guys.

@d-healey

HiseSnippet 1315.3ocsW01aiTCD1aZ2x0b7xcRHw2Pqh3CoPUzlj1RuqBnMMsPzcsWTSuCjNfJmccRL0wNx1aaiP2W3WB+R32z8M9HLd2MYeIaeUvVolLdlG6mY1YFOoqT3QTJgDYU9zoSHHqOzt2Ttdz9ivTNpSaj0Sr6JIJh9rVRwkJhD0Z5DrRQ7QVVK88FqrVcYT3y6+tVXFl6QRVBgdif5QdIcLUmrZ2ceAkwND6SNkNNk0araGOAeeASD.LZIaWzDr243gjiwFyJYi9ArZDx5KsazXf21tta2r4ltXbSeLdi5jlOiLXqAda59LW+9a5B+sExZkC7oZgrmFqIJXSaI7m1aj3RdzA7Fph1mQLB0Q8fSNZYz9inL+tyBOJDxZ4tIAqkhBVep8QTe570SGzLJbRPjNnYU5lnT86AkrRQokinzSs64IoSzIZL74w1c3Zhb.Fd2jlJQ1hJ8YKYuu.rfqqMFeN4PIHLGQ0sbcW2A92Z6TtL79Qoct.KcxlV37MNy1ggD89hwSDbPnZkrlUwrGTNixINCB3dZpf6H3QF0ivHdZheUuYvWGNIV.Ysx+d4xNvCS3gYNyr6rHXvQOGf4v6nIiOkbktJbVFP.uTBFo1DIEHTNvw1PG3jWSMFgOTOx4acbWKzlC3CAZWiIv9uFbkHqJX+J+txky500TlPBWKEr8wLVeHotZdmtn.SvDeHEI4vdIUAdEDLRhEFkwGsBBDwbDhB4QUTrnhwn3Wjpm6Tw4qxre09MAkWsx5NUVascbbB2fEcrpUnP.WAlU.1elavFhzDVJ1g1IUlvwBM4U7PmbU.gSdUCFTnt3nKiHKTsoMi7l.VkGLtOQlJeKzPnrJas5J2sZUunRgTFJ3c3T8qlPhkOTv7M0fluuXkMJtVBpwKEyPvTcXE9ShqvgZr9hVhqPT+B5RG5GoaMixuOeb79ziQ8A.lc4CreAWzuddvvyq6zFqwlVNwLCX6DhTSMAEq1jKfl7QMfV0tMQctVLANn4sAPVO59P9qRN6uX2ooEtj5qgK.rsdOHNhPGNRaj9bPJLKzz.rMYrvwsd4nOafFiuxXSITXbcNidrNtGdDiNDpq0T9vSovqSCq9jXVcajpytwgjH+OOr9Cmce1pq.V+2nXplr5+.OYWsQrwgOgA9R+UIaSYeESJUO7EjVAZsfW44NZY.Y8YZN3pIXtBxrU6ofsJXrwhAXlJwjvDOYwvMUXpEPXp.hrWkFPxxPQI3vft5tyAsmuewmwIDNbYdw5ZC8B0WitdDrzaTKrbQOBegPBAOyrCYTdX.i0EqGMyfrtVrK0AhW9jVBIDUxn+3fwQgPCr5gKEI+ilbvSfjEAn3sg81bq0L2y52y0gk+kvyvzRbOIAOOnFeBqWzGyQEwrSDW1E66CYw2UbyipsDAbeim91HEGIjwuHxqII6KulYw4EzV9cn4EtsKktv8WsxVTtxs1a5ZJC+yoI8F9iL8FZDNw4BCJAinI7CXXc141LSzFq.JixLrjYfHHYQOMca07Cys70eAgapKHtk1+2Q59T6tTs2nh4aoB3q49j+m4a7nwej8ACF.C1jP1ksO7mtw4f+ugJmHBLswOBqkTSeenLtGzR0i.LgyIL0r6BhkcMxlHSOB2OTvzONVYcirUrx5yTB2n3IEm4EcgpYP7GEtBvId3OTYU6iLxNEbS5X32EblmW1sZAfMdn.a9PAtwCE3lOTfa8PA90OTfae6.M+rs8BzhwQkSHzQcOH7BXKqC3XHaLLyE8uYcgRBA

@Lindon with the code that I replied to @d-healey with, it says: API call with undefined parameter 0

@d-healey Is this right?

Content.makeFrontInterface(260, 50);

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

inline function onPresetSelected(component, value)
{

    local Selected_Preset = component.getItemText();
    Console.print(Selected_Preset);
    if (Selected_Preset.length > 0)
    Engine.loadUserPreset(Selected_Preset);

}

Preset_Browser.setControlCallback(onPresetSelected);

inline function updateUserPresetList()
{
    local User_Presets = Engine.getUserPresetList();
    Console.print("User Presets: " + User_Presets.join(", "));  
    Preset_Browser.set("items", User_Presets.join("\n"));
    
}

updateUserPresetList();

@Lindon Thanks for the reply.

When adding + ".preset"; It Crashes Hise?

@d-healey

Content.makeFrontInterface(260, 50);

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

inline function onPresetSelected(component, value)
{

    local Selected_Preset = component.getItemText();
    Console.print(Selected_Preset);
    Engine.loadUserPreset(Selected_Preset);

}

Preset_Browser.setControlCallback(onPresetSelected);

inline function updateUserPresetList()
{
    local User_Presets = Engine.getUserPresetList();
    Console.print("User Presets: " + User_Presets.join(", "));
    
}

updateUserPresetList();

@d-healey I have set this up, and the ComboBox shows the User Presets. But when you select a preset, it says it doesn't exist and doesn't load like it does in the PresetBrowser. Any idea why?

@d-healey Okay thanks.