@David-Healey Backdating made it work, and I’m not one to argue with a good thing. Consider me resolved, good sir. Love your YouTube tutorials, by the way.

I've added a SourceBPM property alongside NumQuarters so now I can just specify the BPM the sample was recorded at which seems more logical to me. I also fixed a bug that was causing clicks at certain BPMs. PR

@Jeetender said in How to display jpanner node values in labels/panel:

the one in the red circle, i want to display its value from -100% to a 100%
Untitled.png

@David-Healey said in How to display jpanner node values in labels/panel:

@Jeetender So what you show on your UI is the value of Left, since that is controlling the parameter.

For example

const ScriptFX1 = Synth.getEffect("Script FX1"); Console.print(ScriptFX1.getAttribute(ScriptFX1.Left)); API call with undefined parameter 0

But I'm guessing you have a knob on your UI that is connected to Left already?

@duma You open it in Projucer, like when you build HISE

@ustk That's the input value which is between 0 and 127 for a MIDI mod.

@David-Healey Sorry, I didn't describe it clear enough

@Christoph-Hart said in Instant crash when loading any faust dsp to the module:

@Lindon damn, alright then. macOS or windows?
macOS arm 64 bit

Personally I use panels in most cases as well.

In your case, I know all of my components begin with a prefix indicating their type.
Examples:

knb: knobs btn: buttons lbl: labels

I do this to be able to assign LAFs. control callbacks, etc. as I want.
Assuming you did something similar, it would be simple enough at the outset of your project to format all the labels as you want:

const var labels = Content.getAllComponents("lbl"); for (l in labels) l.set("editable", false);

Editing the HISE source code is a quicker, more permanent recommendation.

@duma Yes should do

@David-Healey Thanks! I ended up figuring it out from an old post you advised on as well. lol. Attached the callback to a slider with 'save in preset' loaded that triggers the callback on preset load.

@David-Healey @DanH In fact it's not something that problematic because it can be LAFed easily.
It's just the annoying message "Not Assigned" that I can't get rid of, so I just make it transparent, but I feel like it's a hack and it should be cleaner...

@RedFireTF2 You need to compile from source, but the VST3 SDK will only come into play when you compile your project as a plugin (or if you're compiling HISE as a plugin).

Yes, this functionality is broken when you try to run Tools>Convert all samplemaps to monolith + samplemap

@Sifres I just went and looked... That looks SO great.

@pcs800 And strangely enough, today I can compile to the network drive again without issue.
The server must have been low on bluetooth fluid

@pratitghosh if you run the HISE project in Xcode or visual studio and build in debug it’s a lot faster. Then you can use the audio plugin host template from JUCE to launch and test it quicker.

@David-Healey thank you very much. Yes, it was a bug. I have compiled HISE from the github following your excellent tutorial and everything is fine. Strange, nobody had the issue as well.