Scriptnode Synth Crackling with Chords

[Christoph Hart]

and the lack of category labeling

Passive aggressive red arrows incoming:

[d.healey]

@aaronventure said in Scriptnode Synth Crackling with Chords:

hah I meant that the location and the lack of category labeling could lead people to think these are node flags, and not network flags.

I actually thought they were per node :)

[A Former User]

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

I can look into making them polyphonic as there might be a few good use cases.

That would be awesome, thank you!

[tomekslesicki]

I definitely second that @Christoph-Hart !

[tomekslesicki]

Hey @Christoph-Hart I'm just quietly upvoting this, being able to send polyphonic stuff with the global sends would be huge for me. Thank you!

[Allen]

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

But yeah, sends / receives are currently not polyphonic, but I can look into making them polyphonic as there might be a few good use cases.

I'm making a fm matrix and i found i just ran into the same issue.
It'll be really helpful to have a poly global send/receive :)

[Christoph Hart]

global sends & receives will never be possible in a polyphonic context because the voice allocation system is not deterministic so you cannot expect that eg. voice number 13 is rendering the same note as voice number 13 of another sound generator - just add a script that adds an octave note on one of the sound generators (or even use an envelope with two different release times or sample lengths) and the voices will lose their index relation.

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

[DanH]

@Christoph-Hart I'm hoping to use the Global Send and Receive nodes to pipe the main signal of my instrument around several Script FX modules for an FX re-ordering system. Any issue with this? I mean it seems to work fine in testing so far....

[Christoph Hart]

@DanH if your effects are not polyphonic then you don't have anything to be afraid of. Note that you'll introduce one buffer of latency whenever you send a signal "back" (=upwards). in the module tree though.

[DanH]

@Christoph-Hart Thanks, should be ok then. Aware of the latency issue. What's a good method of checking my latency calculation is accurate?

[Christoph Hart]

@DanH there's a latency checker in the tools menu now.

[DanH]

@Christoph-Hart noice

[AxiomCrux]

@Christoph-Hart Currently, trying to have a tuned resonant comb filter with feedback is causing this distortion because of the need for send and receive to create the feedback.

As far as I can tell, this limits the ability to do any physical modeling synthesis, which is quite a powerful technique. I think it's worth finding a solution to this.

[AxiomCrux]

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