@Straticah I’ve noticed that communicating MIDI information in FL Studio is particularly frustrating (actually I find most things about that DAW frustrating but that’s beside the point). Does this solve the issue in your particular case?

Typing keyboard not working on plugins

(support.image-line.com)

@pcs800 You're referencing the panel like this:

const var displayPanel1  = Content.getComponent("Panel1");

But you are assigning it incorrectly:

Panel1.setPaintRoutine(function(g)

And then later you have a second paint routine which would just overwrite it anyways

displayPanel1.setPaintRoutine(function(g) {

Also you have a bunch of timers set to the panels to repaint them which isn't really the most efficient. It would be better to use the knob's control callback to repaint them like I do in my example.

Probably worth looking into the examples here a bit:
https://docs.hise.dev/scripting/scripting-in-hise/scriptpanel.html#the-paint-routine

@pcs800 Actually I think you were touching on the solution in the video already. Typically what you would do is map the value to a new set of values. In this case though it looks like the function is already built into the Engine API as Engine.getTempoName();

Here's an example:

HiseSnippet 1039.3ocsV08aaaCDmxIJnwaoXEn+AH3mTFLBjcRlWPvvbi+XyXMoFydAa6k.ZRZahPQJPQ0XuhBz+j6a6wsiRxVJ0YooFX5AAce+i2w6NMTqHr3XkF4Tc7xHFx4qcGsTZl2YNlKQC5hbdt6k3XCS6kw5hkQ33XFE43ryOYY3r+tnzmO9iWfEXIgUvBgtVwIrWyC4lBtCa+KbgnOlxFyCKo8IsGPTxNJgJAvyNtAnHL4V7L1UXqZUbQ+LNdNx4acCXSlPmN43yXMazn4YmFbZqIMAVGyH3lSacRifVm1p4Y.H2qGkaT5QFrgECN8BEc4n4p6jYA3ZdLehfYIZfFAQNiMpybtfNbUxIFgb1cXQpZmrT0KcujS4q4Wjx9lTAdEVTNo4T4wfTiu.H4TBR6lAoW3Nhn4QlBIV77UtCjPEbJFpMkgRltnJ+cE2NJPCo4nP7sr9ZfXsE9GGDT2Cdc34UqB0mXi2awZuakStYLKLR48CdqLdFyzQArj.ges0ZTCrrvvHo3lt73HAd4+ookzwZb0pZ1LORhVCRSc4.Iks.LO.DxkBtj4MMQRLbkzSIWGYq20JgOYkqqCPPjvNr56p5AOOjKSU37TwkfwQZVDTdM9.bde0pqivQwVfmFkNXgXBbg0eS.XOCkcFXzPq29UUhAvt+Jr6OaExrYJLfFybdrM47ZEAKtPkHow91JwJcL1nX6O.c6ImANyp83Ub823Dlaa5qYYn21u4Grne9StFoB6qrkiov6Z08ZFrVDUiu6UB9LIiNlsv3uFF08v08pQfPpYTas68GddoJyUJC6MRe6obeHO58ohlN8AkkmFEL8CJ1NFQ+XF5KSBmvzkp9oJBsM2uWbumVuHI6RaIEUxARt4MQrb59JA01iY+dyNWT9sdaObNBAUMocvOOuCdjfSYZDmZaeWeeBkd.JFY9x1neaPWrAuxUfWgHEwzFt8.4zk8VX.b1vg8c6xhu0nhfYoqa1PNO6IE3EEAcb6kED+Q6PNkJXCUwbaRuPRs1vZinQ7+hUdGQHtjmZ1NTQY1.kFDXyCwlbVCs8xf1AqlpgkLQJxNvsT6TIr8gqKgsOLs8cbpA1X35r.nmy3ylarT+Y5ZnMldBysUzDA1b+g410b4BrGvxSPsSIkvAeY4i3WvD9fGcB+SEhuvcH2Pl+vXrxCfQ31x+GXLeu3At8lNkQLE.bW29+91tD7yD9rQnytDazb3df6UIgif4YDFDcIbcI1VuqX64xnCrz1LvHljlR7OvStvFVZmbgMVIDEhIZ0MjrNU6l2mkxAvjL8OS1G9EIf1qwm1dhPPyA+FB49tZCCatsFd71Z3IaqgmtsF9caqgs1VC+9Oug1+S6UIFUXVaCBc4vdoiScb5IwvMvzaqn+E2LpIuB

Content.makeFrontInterface(300, 300);

const var knb_Tempo = Content.getComponent("knb_Tempo");
const var pnl_Display = Content.getComponent("pnl_Display");


reg currentTempoIndex = 0;

inline function onknb_TempoControl(component, value)
{
    currentTempoIndex = value;
    pnl_Display.repaint();
}

knb_Tempo.setControlCallback(onknb_TempoControl);

pnl_Display.setPaintRoutine(function(g)
{
    var a = this.getLocalBounds(0);
    var tempoName = Engine.getTempoName(currentTempoIndex);
    
    g.setColour(0xFFFFFFFF);
    g.setFont("font", 20);
    g.drawAlignedText(tempoName, a, "centred");
});

@d-healey @Oli-Ullmann haha yes that's why I will leave it up. I think I learned about this before (watching David's video) and just sort of forgot about what the boolean was for.

@HISEnberg Lol I think this is one of my dumbest posts to date

@Oli-Ullmann

Ahh true it's right there in the docs!

HISE | Scripting | Engine

An API class for accessing global properties.

(docs.hise.dev)

@HISEnberg Actually I just tried this and it works but it is kind of buggy! Sometimes I need to click the button twice and sometimes it still cycles through the same folder, other times it will actually change the folder

    inline function onbtn_PresetNextControl(component, value)
    {
        Engine.loadNextUserPreset(value);
    }

    inline function onbtn_PresetPrevControl(component, value)
    {
        Engine.loadPreviousUserPreset(value);
    }

The current method is fine for navigating within the current folder:

	// Control Callbacks
	inline function onbtn_PresetNextControl(component, value)
	{
	    if (value) 
			Engine.loadNextUserPreset(true);
	}

	inline function onbtn_PresetPrevControl(component, value)
	{
	    if (value) 
			Engine.loadPreviousUserPreset(true);
	}

	btn_PresetNext.setControlCallback(onbtn_PresetNextControl);
	btn_PresetPrev.setControlCallback(onbtn_PresetPrevControl);

However, does anyone know of a method of cycling through the different folders/banks? So say I reach the end of the presets in this specific folder, then hit next, the first preset in the second folder will load? I can't find anything in the Engine API/File API (other than maybe getting the List with Engine.getUserPresetList and manipulating that somehow). Just wondering if there isn't an easy solution here that someone has discovered.

@Christoph-Hart I gave this a shot but this wasn't the solution. It's my mistake.

@d-healey you are exactly right.

Basically for anyone who ends up here I recommend looking at and comparing the Info.plist that is part of the .component bundle. In my case I had changed the company code and this is why the plugin wasn't being recognized properly. Strange I couldn't find this in my Github commits but my issue had nothing to do with the version number.

Thanks both for your responses!

@d-healey thanks that makes a lot of sense, I’ll try adding that to my installer scripts.

Is that how you release updates of your plugins?

Have you seen this issue before? I’m noticing in my ProTools sessions that the new version of my plugin is launching fine so it seems specific to Logic. I’m going through my GitHub repository and I’m not seeing any other changes in the project settings other than this and one other flag (force mono to stereo). Am I correct in thinking that all the DAW ought to care about in this case is the Plugin ID?

My assumption about the Project Version (so the version you assign in the project settings, typically formatted as 1.0.0) is that different "versions" of the same plugin (so same plugin code) should load just fine. So if I distribute an updated version of the plugin (1.0.1), the user should be able to replace their existing version of the plugin with it and it should open in any previous projects they were using the plugin with.

However, I'm getting some users saying it isn't being properly recognized specifically in Logic. It's being seen as a "new" plugin. I notice there is a warning in the project settings (but this is almost the opposite issue):

Be aware that some hosts (e.g. Logic) are very picky when they detect different plugin binaries with the same plugin version.

I'm wondering if I am missing something here or why the plugin isn't being detected properly, I always assumed it was the Plugin code that mattered not really the version number. What's the proper procedure here? Do you instruct your users to remove older versions of the plugin? Anyone else have this issue?

@Chazrox Check out the mid/side node for doing that. The pan node is basically just two gains applied to each channel and it will just make the left or right channel quieter/louder. It doesn't actually send the signal from left to right.

@theovintagesynth there exists some issues with the analyzers and how they operate in the DAW. I've posted a lot about this topic, the best answer I can give you is resize the display buffer so it is a bit smaller. This will definitely increase performance. The script here can be adapted to apply to the oscilloscope:

FFT Analyser Path - Need help drawing the magnitude to height

I made some progress towards solving the UI lag from the FFT. @Consint & @oskarsh @Oli-Ullmann this may be of some interest to you. Basically I found that if...

Forum (forum.hise.audio)

After that, there are a lot of smaller improvements you can try (reduce drawing points, slower timers, etc.) which can help reduce CPU usage. I've talked about them before here (specifically about the oscilloscope):

Oscilloscope Script

@HISEnberg siiick

Forum (forum.hise.audio)

@ally do you have the AllowCompilation flag set and you have compiled the scriptnode network?

This is a good place to start:

@ustk Yes big bump on this one, it can be quite frustrating particularly the first time you find out!

@Christoph-Hart yes you are right.

I don't think there is a justification for removing them on the unscaled parameters, you can figure out pretty quick if the parameter linking is broken using your ears in most cases, plus it's a good reminder to just try to make the ranges match (even if it doesn't always work).

@ustk I ignore them too and don't have any issues.

@Christoph-Hart For sure I'll give it a try and report back. I had my eye on those. I noticed by reducing the FFT buffer sizes (and all the buffers I was using for that matter) seemed to free up more resources, so I'll definitely give these fixes a chance and see if it helps. Thanks for the response!

@Christoph-Hart I'm kind of curious how this works between DAWs, for me the UI locking behaviour happens with ProTools on my Mac. How is the data transmitted between the plugin, the SDK and the DAW. How is the behaviour so markedly different across the different DAW and OS setups? I.e. do you know where I can look to learn more about this topic?

@Orvillain Are you using the FFT or any other audio analyzer?