@DanH soon as I find out how to do it ;) nothing in the docs

@Morphoice The PMA outputs a modulation value like this:

PMA Output Mod Value == param(Value) * param(Mul) + param(Add).
It's useful when you want to control how much of a value you want to apply to something (among other things...)

IIRC now you can have more than 16 parameters in a network, but yes you could have your synth in a network and the filter in another. It makes sense.

@Matt_SF that's quite ingenious, but if I change the frequency knob during a held note, the sustain level shifts with it, I'm looking to just shift the end and start point, the sustain level in between should not be affected... that's what gives me the major headache

@Morphoice Hey just to make sure try not to duplicate a node, instead always use a fresh new node. Sometimes when duplicating a node it leads to issues like that since some internal state is not being cleared.

Also I place the modchain on top of the network.

@Morphoice because the midi number node output is 0-1, as it's essentially giving you noteNumber/127. So you multiply by 127 to get it back.

I have no idea why the faust node parameter rounds it erroneously between C2 and E2.

PMA takes the value, multiplies it with the multiplier and then adds whatever you plug into add. The base PMA node aims to output 0-1, while the unscaled outputs anything.

@Consint Thanks for the detailed explanation, it's much appreciated!

@griffinboy I have read a couple of papers about getting alias free waveforms, it's hard to do. Hence me hoping anyone some day lends their expertise to HISE to get a couple of new waveforms we all could use. Then again, the the wavetable synth already does it with random waveforms, so it might not be super complicated to use that tech and simply let the user draw a wave instead of importing it from external wav files...

@bendurso no

@Matt_SF Cheers mate!

@Matt_SF Very cool! I'll check it out…

@Mors Code tags

65ae8408-4b0b-49ff-8924-94afa2a4f0d2-image.png

@Christoph-Hart

As always, thanks for the response: )

@aaronventure said in Is it Possible to Deactivate Nodes by Name Inside a Compiled ScriptNode?:

What do you mean by compiled nodes? This targets a node inside of a network. It's unlikely to work if you compile the network and replace it with a hardcoded network, because it's expecting a reference. The point of that whole API is to eventually be able to create and operate fully dynamic scriptnode networks at runtime, but it's unfinished as of today.

I meant "Nodes that are compiled as part of a Network." Are you talking about compiling a version of a plugin, but not compiling the ScriptNode networks? (I get an instant crash if I try to do that.)

@ustk Thank you, as well. I rebuilt it a few times, but was never able to narrow it down.

@Morphoice it's always the current buffer size unless you tell it otherwise. Use the dynamic blocksize node to compare.

If you have any time-based processing like oscillators or ramps or compression, you will notice a difference. For filters, it's not necessary.

@JulesV Try to use online faust editor and let's see if it does the same error or not