@Christoph-Hart I thought I'd have a go at this fft thing. Following your instructions above and the docs I load a sample from the sampler into a buffer. If I uncomment the process line in this script HISE will just crash.

const var Sampler1 = Synth.getSampler("Sampler1"); reg sound = Sampler1.createSelection(".*")[0]; const buf = sound.loadIntoBufferArray(); const fft = Engine.createFFT(); fft.setEnableSpectrum2D(true); fft.setWindowType(fft.BlackmanHarris); fft.setMagnitudeFunction(function(data, offset) { var max = 0.0; for(s in data) { max = Math.max(max, s); } Console.print("The max value at " + offset + " is " + Engine.getDecibelsForGainFactor(max)); }, true); fft.prepare(1024, 2); //fft.process(buf);

@d-healey Actually I just remembered I made a script for this exact purpose, and it's public domain so you can use it in your project - https://codeberg.org/LibreWave/RhapsodyBoilerplate/src/branch/main/modules/AhdsrController.js

@d-healey The panel can also save an array.

The linking is a good point.

@aaronventure the reference. I believe it is reset each time a file is loaded.

@ulrik Thank thats exactly what i am looking for here's the example

HiseSnippet 1061.3ocsV01ahaDDdMA2Vb6o1H0e.t4CsNRtHamP.TUUuDBTgZSNT45oS5T0oM1K3UYYWK6kvgpx+49OncFaH1z3DUg5wG.OyyLCO6ryKdRpJjkkoRIFsd85DFw3KLmtVpiGDS4Rx3KIFGZNhKiFJD7jL14oLJ4h0IzrLVDwv3feFMynUSR9m+5mtfJnxPVoJB4MJdH6W4K35RsSd4uvEhQzH1q4KpX8oubbnRNPITKAJcfoGIgFdKcN6ZJZVCShwmLLhqUoS0TMKiXz7BUz5owpUxB6eCOieifgB9joPfJTORIhPFiZICh4hnIaO5YDHJSJSDGTjH9Zyq3Q7GzWlP9pb.6ROplOLZrK8NXG54WkddUnWMTxnBkZVPoCMmFlxSzkHHe9bywRMKcFER6UoRgsjFlMMGn.Kj51Kn2xFkBBO3giuWvot1m44c7OXAlkoDr1gBFM0ATXYA2FYZ66no1SjB6ezdajlyzCTKRTRPv4H.6Hz7RqSpXaHTznYSn5XLlIsEJZDvhEWR0Tm246645602E9Nnm6Y8cOqm6IAtc7c86Bxcc62aGrNAtAAcc86zAACB.rNf1NHVPPG2.uSc8OoKBV31I8pABBZO29f+9Ooece7+VEfcnnuWumg+8Abe.26OfiOjpZmwzSfpI8uoVp4RlyrkxPMWIcler0eZ0ZNZPQOfSwOYsWEy0Lvc.LJktJOYl3ZmfWDWnVJixb7O101GMwpEelsiNlm0NBRws4YikY7H1wVsfn+7gGPmAcl0Gezf6stGuo2bLtRsLiMfJD2.sokmC1cv8d9Y4wr.JLRZCEJZHCj47tbSa+AW6hGVi4Hf+Eg.pD4g2xhr+V6ZNN3gYaIaRJGKD45uKylmCeT9wAIbMg6adp3Ua.gqoxHBgDiYt+orD7dDKqyyJVVaSA1J40JM6URm7zf08V1+anYypEC6ZRUBAKsVXbdY5y4nib4haXotPanXI6ACggH6NYx7omLUcvYXQSbECUxwRt9UIL4SMNkroyGd52Gic433rM5.6RXoZNRAiKY2A6FJFt0x7RV1sZURtsaFsPL9TcN5K1N5iJYBBGFvYZB0fjOTcSy5pBq3Q5XvLCMnJlwmGqQo21fPf5U0psUs.O9RyyEB6REjGO5EF5qhVJn5c2Dfq+1..WB6L9EGwB0U50UWO9+15g+qT7PyIbcXb8brQMbDtp9XvwMKUeg4vYyXg5RB1zbza+3rAkTLdc9UTcJGpSLud4hovztPF7uKgxHrIvnAVtVH6gxXFXJSFkK72vmMf9nrwFP+sfjEzvT06CKZ8v01eVtFfSx72Xok4UnrsOIucDKa8Z6QV.uAw6CCwi+2CcP06Svd3yI6gOmtG9zYO74r8vmt6gO8dVevWd67kZ0hh1APwjg4ynLLFJoPkUdUH4efRtCTE

@Christoph-Hart bump

@Christoph-Hart said in Script panel label keyboard entry?:

Ok, but what do you do? I load up the snippet and can click on the button, then it will open a popup.

Yes that's what I'm doing too.

Where's the UI - in the interface designer or another window. Do you have another floating window with the interface open?

Aha mystery solved. I was just in the interface designer. If I open the floating interface preview it works!

@d-healey said in All Control Callbacks Get Triggered On Init?:

Another solution is to put a button at the end of your component tree and put your code in its callback, this will be called after all the other components. Or instead of adding a dummy button, use the actual last component in your tree if suitable.

That's a good one. Kontakt has on persistence_changed which executes after on init, meaning that on init has to pass first, which does not happen if the track is muted in the DAW or the VEPro instance isn't connected. So my instruments there always load up with the "loading" image which says exactly that, and all the UI controls get their visibility set only in persistence_changed.

But if in HISE the controls get executed after the init callback passes, then simply adding a dummy control at the end is not a big deal. Much like the PersistentData thing, or the colorPalette, or my dummy DAW automation controls. or my dummy switcheroo volume sliders. Hey, we need a dummy component list!

@d-healey said in Disabling Default Modifier (CTRL/SHIFT/ALT/DoubleClick) Behavior for Sliders, Buttons, Tables:

Yes, I use basically the same UI for all my instruments

Yeah this is all part of setting up my design language within the HISE environment. I'm also exploring all the new cool shit I can do here and seeing how much eye candy I can stuff in this baby before it starts to cry.

The idea is that once I set it up, I can forget about it, just change the colors as needed and single-line-add any sort of control I want now or in the future.

@aaronventure this did the trick ! many thanks!

//button const var Buttonx = Content.getComponent("Buttonx"); inline function onButtonxControl(component, value) { if (value) { // Button pressed, start animation p.startTimer(1000.0 / object.frameRate); } else { // Button released, stop the animation p.stopTimer(); } } Content.getComponent("Buttonx").setControlCallback(onButtonxControl);

@aaronventure said in deferCallbacks and Its Effect on MIDI-Mapped Controls:

Should I even use deferCallbacks in my interface script

I always add it by default. That way if I add something to one of the realtime callbacks that shouldn't be there I'll get a warning message.

@ulrik That worked like a charm, thank you so much! The array is what I've been missing. many thanks

@Christoph-Hart

You can fetch the content of any sample as HiseScript Buffer and draw it yourself

This is where I had got up to. But I don't get the playback data from the sampler so I can't draw the playback cursor. Given the performance issues you mentioned I think I will abandon this road :)

My main goal was to be able to update the waveform when the gain level is changed (like in the waveform editor) and have horizontal and vertical zoom.

@virtuscapeaudio said in Rhapsody Boiler Plate "LookAndFeel.js" file not found:

No expansions needed so I just deleted the settings cogwheel for the plug in version of the build

So you're not making a library to run in Rhapsody?

The cog wheel is unrelated to expansions, it's there to allow users to access the Settings panel.

@virtuscapeaudio said in Rhapsody Boiler Plate "LookAndFeel.js" file not found:

and just redesigning as needed since it has everything there

If you don't need the design stuff then just remove the look and feel and paths files and replace them with your own. But if you are depending on the boilerplate for styling things like the preset browser or settings panel then you probably want to keep the boilerplate files and also add your own files that style other elements.

Those early posts of mine were from when I was fresh off the KSP boat. Since then I haven't needed any KSP style variable persistence.

With your multiple modes example just have a hidden knob on the UI that stores the selected mode. Slider packs are also a great option if you have a lot of data to store/restore.

I made a lucky guess

Console.print(Math.from0To1(0.5, {"min": 0, "max":100}));

@d-healey Hey, there's an idea for your next video. HISE museum! For April Fools or whenever.