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

@d-healey wow...I unchecked that and it removed the expansion error...but I had to delete the Vel Table script and then it worked fine...thank you David!!!

@ericchesek I think the only solution would be to put single mic samples in separate samples and manage the multi-mic stuff manually (just like in Kontakt)

@Christoph-Hart

Thanks for clearing it all up.

@kameron When no expansion is selected it should show the presets of the main project (or at least I thought that's what it does)

@d-healey You're right. I auto-piloted the first step.

Create a typed Audio Sample Script Reference with right click

I used the generic reference option.

Thanks, David. For responding so quickly on a Sunday evening, too 🍻

@Christoph-Hart Is it possible to upload an image through a server and then convert it to an svg and paint it?

The UI height/width is fixed.

@Christoph-Hart

Alright, so you're assigning it in the Property Editor. How to do it with scripts that allows for clearer code instead of relying on definition order? I saw there was a commit the other day, 555cd89 - - added virtual method to get the parameter index by ID . Does it address this?

Btw. I noticed a strange behavior of the Property Editor and widget selection when working with two scripts. This can be replicated in your snippet.

I opened an issue on GitHub, the forum won't let me upload the gif here (too big).

https://github.com/christophhart/HISE/issues/420

@Lumi283 You can use the "Global Animator" to this

const var ScriptPanel1 = Content.getComponent("ScriptPanel1"); // USING THE GLOBAL ANIMATOR inline function onFadeInOutControl(component, value) { ScriptPanel1.fadeComponent(value, 1000); }; Content.getComponent("FadeInOut").setControlCallback(onFadeInOutControl);

Solved. Just had to use the artificial system and got everything working.