@ulrik Ok I found what was causing Hise to freeze, it was my "node templates" that I made the other day, I removed them and now it seems to work again.

@ustk

Can you tell me what is different about jdelay from core.gain

Not sure what you are asking here. One is a delay and the other a gain, but you know this already ☺

Lol, I meant core.delay.

Hmmm… seems a bit technical for users, no? Many of them are not necessarily confident enough with interface buffers length, so understanding internal blocksize might be confusing… (not trying to be pedantic here)

Good point - I don't make commercial plugins with HISE; they're functional prototypes for other developers and research. Also, I can use the pop-ups myself to easily try different values, and then go back change the dynamic ones to fixed.

All good on everything else - cheers!

@ustk Got it - thanks!

@Morphoice

skew = hslider("[01]Curve", 1, 0.1, 10, 0.01); range = hslider("[02]Range", 1, 0, 1, 0.01);

There's also a bug where if you add another parameter to a faust node which already has it built, you have to manually rebuild the parameters by clicking the three dots (where you create a new Faust file) and you'll find the option there.

Well, I rebuilt the whole thing and haven't compiled the network and it's working again. Not exactly endlessly repeatable though. I'll have to pull the C++ apart when I get time......

@filipalex96 hmmmmm... not sure I can help here. Perhaps @Christoph-Hart can advise whether it's possible or not...

@ustk I just realized the pitch_mod node can't be used in a compiled network so it's off the table anyways ;-(

@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