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

@d-healey got it - thanks David!

@d-healey that's what i'm looking for thanks ❤

@Lindon

Thank you, this is very helpful!

@clevername27 said in HISE Changes and additions...:

is that available as a Tile I can use in my plugin?

Sadly not... yet

Solved.

I didnt realize having the "note length" of the arp set to the highest setting would cause this but sure enough that was it. If anyone else comes across this, insure your Note Length is below maximum value.

@d-healey wow you just and only just beat me to it... 😊

@capygeneral also move the HISE source code to the Documents folder for some super weird reason it did not built from the Downloads folder on MacOS.

@d-healey thank you sir

@oskarsh The panel also has its own mouse callback so you can do it there, without creating another broadcaster, unless you have need of the broadcaster's modular function stacking.

Any other widget type and yeah, you need a broadcaster.

@Lindon

const var GC = Engine.getGlobalRoutingManager(); const var MAIN_Cable = GC.getCable(1); const var MAIN_Cable_2 = GC.getCable("or choose name"); /// Global Cable Functions // MAIN_Cable inline function setMAIN_FUNCTION(value) { dothing; } MAIN_Cable.registerCallback(setMAIN_FUNCTION, AsyncNotification);

@Natan said in Too many set attributes in an Instrument! Is it safe?:

@Lindon Thanks Mate, I also take your advice on other forum and put everything inside namespaces.

It performance very smoothly 🙏

All good then...