@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

Link Preview Image HISE | Docs

favicon

(docs.hise.audio)

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

@d-healey it works, thank you

I'm not sure why but for this to work you have to set the intensity via scripting from the knob's callback.

Constant1.setIntensity(value);

It is - on the Project Tab in the node loader. Done!!!

@d-healey said in feedback needed :):

As you get higher the notes (even though they're the same) sound brighter.

Yeah this is something I wrestled with for a while, I tried using a single note and spanning it with Loris and catching the harsh frequencies with a dynamic EQ but it just didn't sound the same as sampling the higher string/fret

And obviously there is a huge difference between playing the open strings and playing the same note fretted.

A caveat with this is that (at least in my experience) bright strings are sought after in aggressive music as they help cut through dense mixes, open strings are a lot brighter so I've intentionally used the lower open samples as the "main samples" that take up most of the keyrange

finding a balance between brightness without it being too harsh on the higher notes was key

@orange said

You can use more user friendly general terms rather than using Waveguides and Residue.

Yeah this is definitely something I'm still battling with, I heard Alex Hormozi mention that the average american reads at a 3rd grade level so the writecopy should be fed to a literacy test algorithm. that being said, I think the average VI enthusiast isn't your typical customer, and they're generally more curious about the "story" of an instrument or piece of software, so I'm trying to find a copy that's easy enough to read, while still having some of that technical aspect

Plus "digital waveguide" sounds way cooler than "wavetable synth" 😎

They can download it after Newsletter Subscription.

There's a free tier for the Patreon which can essentially serve as a mailing list, the website needs to be Static to work with github pages, and there's a button inside the plugin to open the store page instantly so I'm trying to avoid "gatekeeping" the download behind a signup, I personally hate the friction and I'm trying to keep it as few steps as possible between discovering the instrument, and having it on the users HDD

I really appreciate the feedback guys! It's all going on the blackboard (btw I bought sticky blackboard paper for like $4 and it's the best investment I've ever made)

@CyberGen This is what I needed to see. It all makes sense now. I think I may be able to work it out from here. Thank you!!!