So now it should be fixed - I haven't tested it because I was too lazy to make a node with parameters, but I'm fairly confident that I can no-look fix this :)

@Christoph-Hart

The core:extra mod node?
I haven't used this node before!

Thanks for your response, I agree, it's certainly a fiddly routing scenario.
Part of me wants to completely write the sampler and everything else in the project from scratch so that everything is custom c++ and can be routed by hand.

However, I'm working with Dan on a project where he needs to use the built in Hise sampler because he's made a ton of monolith and sample map files for the hise sampler...

So my task is to figure out how to play nice with the hise modules while supporting FM between the custom stuff and the hise stuff 😬

@Christoph-Hart said in Parallel Threaded Voices in Hise?:

If your synth is able to max out a single core it won‘t work in a musical context anyway

Maybe I phrased it a little wrong, I'm talking about SIMD.
Many synths for example use SIMD for batching unison voices, or voices in general, or left right channels even, and processing them in parallel. This is common, no?

I was talking about parallelism rather than just threading.

@griffinboy yes it copies the data so that it works across the DLL boundary of the network DLL (otherwise it would be very prone to crashes). Once it's in HISE it will be referenced (so if you attach multiple callbacks they will use the same data object).

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

@Christoph-Hart

08acaf42-bb5e-4882-9a57-48678a5a5f49-image.png

well, all hope is not lost lol

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