I finally succeeded, thank you for your help.

@d-healey & @Lindon Thank you very much, both of your responses have really helped me explore the possibilities here. I am pleased to know I can use the text property in this way, and will definitley explore this more in future projects. A lot of this particularly UI is already laid out so I am settling for bypassing any text that is not the exception cases, and employing it for any cases that call for customized value displays.

Example based on Lindon's edits:

const tempos = ["1/1", "1/2D", "1/2", "1/2T", "1/4D", "1/4", "1/4T", "1/8D", "1/8", "1/8T", "1/16D", "1/16", "1/16T", "1/32D", "1/32", "1/32T", "1/64D", "1/64", "1/64T"]; const filterModeLabels = ["Lowpass", "Highpass", "Bandpass"]; const LAF_StandardKnob = Content.createLocalLookAndFeel(); LAF_StandardKnob.registerFunction("drawRotarySlider", function(Style,Widget) //... if (Widget.text.contains("FilterType")) { // For FilterType knob, display the corresponding label displayLabel = filterModeLabels[parseInt(Widget.value)]; //For TempoSync, display tempo sync values }else if (Widget.text.contains("TempoSync")){ displayLabel = tempos[parseInt(Widget.value)]; } else { // For all other knobs, display the value displayLabel = Engine.doubleToString(KnobValue, 2) + Widget.suffix; } Style.drawAlignedText(displayLabel, [Area[STARTX] + LabelOffset, Area[HEIGHT]-Area [HEIGHT] +6, Area [HEIGHT]+LabelOffset, Area[HEIGHT]], "left"); //...

@d-healey Honestly, Now I can't remember why I made that choice. 😕

Thank you for reminding me that option existed. I'll make the change.

@d-healey said in Filter Freq popping on CC Control:

@Lindon Try using a CC mod and connecting the knob to that and see if the issues goes away, if it does then it is almost certainly a lack of smoothing that's the problem - although I would have expected it to work the way you have it...

Well -- I asked him to try changing the audio card buffer size - as that's a classic pops and clicks source, and it fixed it.. so I will save the "add a global MIDI modulator or two.." for another day I think.. thanks tho. it prompted me to go back to think about adding these again - at the same time I will a dd the new global envelope modulators too, so the user gets user-drawn tables...

@Sounddiy Thank you very much, it actually worked.
i guess that's a bug then, hope it gets fixed soon.

@d-healey double Thankyou!

@Lindon actually I don't remember, I guess isPlaying and something?

@Natan having said that if the sample map is actually mono the AudioWaveform will only display one channel

@d-healey this works for me to now, thank you!!!

@DabDab said in How to use RSA License:

@Lindon Hmmm.. but How ? is there a minimal snippet ?

no - you have to build your own apps and plugins.

@clevername27 Thank you, I solved it

@d-healey Resolved, thank you. The work you're doing is beyond expectations.

@yall

https://docs.hise.audio/glossary/custom_lookandfeel.html

https://www.youtube.com/playlist?list=PLynv7CujPCfYYI4yvr8gqfIu_m_FgBACm

@darealchanax

Are you following the steps here? https://github.com/christophhart/HISE?tab=readme-ov-file#osx

Which one do you get stuck at? This might just be a case that the documentation needs improving.

@capygeneral said in VST3 plugin error in DAW:

@d-healey I exported as both (the VST3 + AU option). Should I try VST3 and AU individually?

start with a VST3 - its a bit more forgiving on macOs usually

@ALBERTODELRIO I remember having this issue when first learning HISE…as @d-healey stated samples and presets aren’t a directly connected system….if I had to guess you’re probably loading up a set of samples and then creating a preset based on that sample…then loading up another sample map then creating a preset based on that…the samplemap system works in an alphabetical order…so if I create a sample map and call it “beta” then create a preset called “preset 1”…then I create another sample map and call it “alpha” and then create a preset called “preset 2” when I click on the preset 1 the “alpha” samplemap will probably load cause of the hierarchical structure…it’s a bit offsetting when you are just getting going…but I’ve found it a best practice to load up all of your samplemaps first for your project and then create presets based off of those…

@d-healey

It’s achieved; I’m loading samples based on their tokens and creating a module structure. Right now I’m only loading one mic (OH_M) and there are 6 other mic positions to load later with multimic. I should probably investigate doing it manually and exporting the sample map to see how it is represented there, if it is.

const var dataObj = Engine.loadFromJSON("../ArticulationData.json"); include("UI.js"); function createModule(type, name, parent) { if (type.toLowerCase() == "sampler") { var type = builder.SoundGenerators.StreamingSampler; } else { var type = builder.SoundGenerators.SynthChain; } var module = builder.create(type, name, parent, builder.ChainIndexes.Direct); return module; } function createSampleObj(fName, note1, note2, loVel, hiVel, RRGroup /*(j+1)*/ , Duplicate /*0*/ ) { var obj = { FileName: fName, Root: note1, LoKey: note1, HiKey: note1, LoVel: loVel, HiVel: hiVel, RRGroup: RRGroup, Duplicate: Duplicate }; return obj } var builder = Synth.createBuilder(); builder.clear(); var sampleMap = []; var stopper = 0; for (group in dataObj) { stopper++; var groupSampler = createModule("Sampler", group, 0); include("SetSamplerAttributes.js"); sampleMap = []; for (hit in dataObj[group]) { var rrGroups = dataObj[group][hit].RRGroups; var rrSize = dataObj[group][hit].RRSize; var Layers = dataObj[group][hit].Layers; var note1 = dataObj[group][hit].Note1; var note2 = dataObj[group][hit].Note2; var count = 0; for (i = 0; i < rrGroups; i++) { // for each rrGroup for (j = 0; j < rrSize && count < Layers; j++) { count++; include("SampleSortConsolePrint.js"); var fName = "{PROJECT_FOLDER}" + group + "-" + hit + "-OH_M-" + count + ".wav"; include("VelocityMath.js"); var obj = createSampleObj(fName, note1, note2, loVel, hiVel, (j+1), 0); sampleMap.push(obj); if (count == Layers) { // only saves complete sample sets until overflow logic is complete //Console.print("test"); Engine.dumpAsJSON(sampleMap, group + ".json"); } } Synth.getSampler(group).loadSampleMapFromJSON(sampleMap); } } if (stopper > 4) break // Let's take it slow } builder.flush();

Working good!

@pgaudioworks

Lots of info on the forum.

There's a 101 guide in the docs:
https://docs.hise.audio/scriptnode/101/dsp_network.html

And some examples in the tutorial repo - https://github.com/christophhart/hise_tutorial/tree/master/ScriptnodeHiseModules

drawFilterGridLines seems to do it

@Lindon Hi Lindon. I used this now and its working as expected.

inline function onSampleViewer1Control(component, value) { if (value > 0) { local id = Sampler1.getSampleMapList()[value - 1]; Sampler1.loadSampleMap(list[value]); SampleName1.setValue(list[value]); Sampler1.loadSampleMap(id); } }; Content.getComponent("SampleViewer1").setControlCallback(onSampleViewer1Control);

If I take out the part you said was incorrect, then it stops working again.

Is there a different way I should go about this now?