Is it possible to alter the frequency information sent to faust in a scriptnode synth or hardcoded fx in code before it is processed by faust or scriptnode in general? To apply glide or pitch bend info outside of the network. The stock pitch modifiers have no effect on faust

@griffinboy @sletz there are many bugs to be fixed and features to be added before this is ready for release but the core sound engine works. Also once everything is done I have to create a buttload of presets first. Long way to go.

This isn't an ad or a post to brag but I wanted to show you what I achieved using HISE and FAUST in a few weeks with the help of this awesome community!

So this is to say thanks to all who supported me in learning HISE in a ridiculously short time. This would never have been possible without HISE and all of you. I started with simple FX plugins like reverbs and delays, which are now included in this synthesizer. So all the sound you hear is 100% HISE/FAUST.

The Audio:
https://www.instagram.com/p/DFDtqa2s5Sp/

From the bottom of my heart, you guys are my heroes!!
@Christoph-Hart @d-healey @aaronventure @HISEnberg @griffinboy @Mighty23 @sletz
and many many more <3

I'm trying to figure out why releasing the sustain pedal stops notes even though they are still held with the key on the keyboard... shouldn't it just stop the notes no longer pressed and keep the gate signal at 1 for notes that are still held?

I'm using faust osc's and faust envelope with the freq/gain & gate info. It works fine with a HISE envelope, but that can't be used in this case.

@aaronventure that sounds super useful. Where to are those faust nodes compiled anyways? are they in the DLL or can they be easily moved to e.g. another project once compiled? that would open up new ways to build a whole assortment of nodes and tools and share them with each other without the need to share the source code and compile

@Christoph-Hart you gotta be kidding me. I didn't know there was an inbuilt one. How great is HISE?!

From a general standpoint, how hard, easy or impossible is it to include an arpeggiator in a polyphonic hardcoded scriptnode (silentsynth) synthesizer and where would I start to approach it?

I'm thinking of something like up and down runs of held chord notes as swell as using a slider table for step arpeggio +/- semitone and expression values...

I recon there isn't a @d-healey video for this :)

@Dominik-Mayer yay!!

@sletz fixed thanks

I figured out the following so far

velocity = 1-depth*(1-gain); // for modulation from 0-1
process = osc(freq) * velocity <: _,_;

this gives me a velocity according to the depth from gain (the midi velocity automatically captured in faust). So if depth is 1 there is full velocity modulation, if depth is 0 the notes are always maximum volume (velocity = 1)

similarly with signals from -1 to 1 this should work

modulation = 1-depth*(signal*0.5+0.5); // for modulation from -1 to +1
process = osc(freq) * modulation <: _,_;

someone please correct me if I'm wrong. This still looks like mush to me but it seems to work and I can't see an easier way to do it.

This happens a lot and I always get this wrong.

What is the best way to modulate a signal with e.g. a velocity dependent on a velocity-modulator intensity?

signal is obviously -1 to +1 or any value
modulator can be 0-1 (e.g. a velocity) or -1 to +1 (e.g. an lfo) (so I guess it's two seperate formulas)
and the intensity is 0-1 where with 0 the signal remains unchanged and with 1 it is modulated by the velocity.

what are the most simple formulas for this?
I reckon many people often need this and can't wrap their head around it.

I have figured this out many times before but whenever I look at it or try to reuse it on another occasion it somehow turns to mush by just looking at it... and a dry/wet node can't be the most optimal solution

Just a reminder for everyone just getting started with faust to read this

https://faustdoc.grame.fr/manual/optimizing/

and avoid unnecessary cpu calculations. Really makes a huge difference!.

@Christoph-Hart also please let us color all nodes and the main container aswell as having the background of them also tinted ever so slightly, it makes things so much more neat and clear :-p

@Christoph-Hart please do fix the silent_killer not being passed through multiple polyphonic scriptnodefx all the way to the synthesizer group ;)))

a simplification of the workflow would sure be nice, but I have somehow gotten used to it, there's probably a lot of smaller bugs and glitches that can be far more annoying and could use some love, before you revisit the entire scriptnode system/workflow ;)
e.g. adding a parameter in hise still messing up all the cables sometimes, even if you click "rebuild faust parameters"... often enough only loading another faust script into the node and reloading the original one helps. I would document them if I could accurately reproduce them but it seems like it happens at random. ;/

yesterday I had to create a Hardcoded Polyphonic ScriptFX node 8 times before it finally decided to remember the network I had assigned to it after saving and reopening the project ;)) I'm sure if we could get this a little more rock solid more people wouldn't be "I avoid compiling networks at all cost" ;))) I feel them lol

A couple of less alert popups after compilation, at the start of hise and during the save would be great though. By know I know I have to close and reopen HISE, still don't want to initialize the defaults on startup and am really sure I want to save the XML if I hit CMD+S and am even sure I want to overwrite it, though that question is probably legit although not standard on apps ;) I do this after every line I write, just out of fear HISE will crash on me when I hit compile and my line will be lost ;)) So that's a lot of confirmations a minute and I am such a lazy bastard as it is ;)))))

@aaronventure

subpar =)
I reckon most elements are made by white with various alpha levels so unless @Christoph-Hart reveals all the secrets, i'll never get it completely purple. I'd settle for an ability to tint ;)) but there are more pressing issues. like the disfunctional silent killer ;)))

@aaronventure i only managed to change a few elements, i cant figure out the rest lol it looks ugly
With some things being grey and some purple. i cannot work like this

@ustk that was my workaround. We just found out, though, that this works:

Knob1.set("stepSize", 0.001);

@HISEnberg this is super useful!
I just never got how you can crush something by fractions of bits instead full bits only
but every bitcrusher has this so I guess it's legit ;)

@HISEnberg confirmed. that seemed to work! brilliant!! my man!

@ustk the problem is just the knobs start jumping as we can't have smaller stepsize than 0.01
and most sliders are from 0-1 not really giving many steps to work with