@d-healey

Interesting.
Okay I've never done this before I didn't know set attribute could be used that way.
I'll have a go

@griffinboy Thank you! 👍

@Christoph-Hart

Good to know that it wasn't anything bad. It didn't seem to be breaking anything.

Is it okay for me to use this function then? It says that I shouldn't here unless I'm rendering. But I couldn't really see why, so I've been using it

@griffinboy

edit* Rephrased into a more answerable question hopefully!

@griffinboy bump to top : p ; 3

@Christoph-Hart

Thanks I'll look into it!

@griffinboy i suspect that implementation will just be a stretching of the path across a different area, haha.

For multiple channels, you'll probably find it easier to do using the new Rectangle() object.

@griffinboy said in Get Modwheel value? (Callback):

if(Message.getControllerNumber() == 128) // Pitchwheel

There's also a constant for this Message.PITCH_BEND_CC

@d-healey

Lol, thanks. I'm definitely still not used to it!

@griffinboy I digress.

@d-healey

Worked!
Great, thanks David.

Answer:

const var ScriptnodeSynthesiser1 = Synth.getAudioSampleProcessor("Scriptnode Synthesiser1"); inline function onButton1Control(component, value) { if (!value) return; FileSystem.browse(FileSystem.getFolder(FileSystem.Downloads), false, "*.wav", function(file) { if (!isDefined(file) || !file.isFile()) return; ScriptnodeSynthesiser1.setFile(file.toString(file.FullPath)); }); }; Content.getComponent("Button1").setControlCallback(onButton1Control);

@griffinboy For what I understand, it's not Hise to support latency, be it variable or not. Hise just reports what you want, so if you want it to be variable, technically, you should be able to do it.
But the DAW might not like it... It doesn't seem to be something "normal" to report a continuously changing value, but I can't refer to anything else than my own perfectible thoughts...

Thank you!!!

@griffinboy I am using the DLL export at this very moment with the latest version successfully
Have you tried to run Export -> Setup Export Wizard ?

So you are saying it's the old version that doesn't have the new export window,
and you are trying to build the last version of Hise to get this new window but the build fails?

@griffinboy you should set your fictional voice count, assign ids to array indexes and remove them when releasing notes. Then you can check along the array to fill the first empty index with a new od and set event data based on the index.

Your event data for individual voices is in another array, obviously, all ordered by voice order.

@Allen said in Please Increase parameter limit on Scriptnode custom nodes!:

I just found out one of my node with about 100 parameters won't update the internal value and ready to increase this limit to 256

Haven't tested all the params but just wanna comfirm so far it works in both script fx and compiled fx with max 256 params limit! :)

I found there's also a similar param number limit in the rnbo node so don't forget to change that one as well if you're using a rnbo node

@mmprod Yep! We haven't announced it yet, so…well, if you know who I am, you probably know who it is. HISE will be on it! 👻