@Orvillain Ah yes I meant to revisit that. I did figure it out but the solution was admittedly more AI-influenced than I care to admit, so I was waiting until I have a more proper understanding of it to share.

@DanH if you need context

Link Preview Image HasTail

no, as you're not using polyphonic FX, which can only be used inside a processor anyway Not so fast, the effect you describe is how this flag is working wit...

favicon

Forum (forum.hise.audio)

@Christoph-Hart Thanks for the detailed response, the future looks bright! Global envelopes (and compilable cables) were a huge improvement, especially for more complex projects.

@Orvillain
Oh ok, my bad then. Maybe it’s your sample that’s below 0dB, so it goes up and then drops back down. Anyway, glad it’s working for you now! 😊

@vyexx
Crystallizer is a real time granular delay.
You may not be able to do that in pure scriptnode I think you'll need to code c++

@Lindon
@Christoph-Hart

Ahhhh ! Amazing guys. Thank you so much !

+1 here too 😀

@griffinboy This was it! For some reason I never even noticed the drop down on the wet/dry gain! Thanks as always :)

@obolig usually there is not too much overhead of running inside HISE, except for the debugging tools that might cause some UI lags - the audio rendering path is almost identical between HISE and the compiled plugin - unless you do something weird.

@Christoph-Hart Haha that's not at all what that requirement says.

The requirement says that if I input MIDI or audio into HISE and it spits something out, then pressing export should result in that same plugin.

Faust nodes need the compilation step before they can work? Alright ,throw a warning and tell me to enable Allow Compilation. If I didn't ask again on export. But then it should compile to a plugin that works. Because it works in the HISE IDE.

I can, in HISE, have a single .dsp file that I use in 10 different networks at 30 different places in Fasut nodes and it'll work in the IDE. I can make changes and it'll work. But just pressing export wont.

So what, I should now first compile that faust dsp file in a lone network that exists just for compiling lone faust files, replace all existing faust nodes that are used for development because I cannot just branch, as the nodes cannot be in there when exporting, connect all the cables for 30 instances across 10 networks and then compile? And then when I have to make a change, what then? Git discard all the changes to the networks, make changes, and then replace and reconnect 30 nodes again just to run pluginval?

Come on, man 😄

@xander my guess is your faust code works with a fix expected samplerate so that when you‘re oversampling it shifts the normalised frequency ratio.

@Christoph-Hart said in Scriptnode Synth Crackling with Chords:

What might be possible at some point is to use the routing.send / routing.receive nodes WITHIN a polyphonic network to implement polyphonic feedback delay lines (for stuff like resonators etc).

yes, exactly.

At least for me this was the expected behavior. I kept flipping on and off the polyphonic setting for the chain, expecting that to be a fix, or the number of channels, but nothing solved it.

For the time being I will try out using Faust for my comb filter / physical modeling elements and see what I can do.