Pan2 affecting other UGen's ability to change signal #464
-
It's the end of a long day right now, so I don't have a working example. Before I post one, I'm just wondering if Pan2 is known for affecting the ability of other UGens to modify the signal when they are all part of a in signal processing chain? For example, it seems like using either a Limiter or just a UGen where I modify the amplitude by multiplying the signal by some float doesn't work at all, or very little, while there is a Pan2 UGen further up the processing chain. Is this something you've run into? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 1 reply
-
No, I've never run into that. Suspect that if you're not hearing any modulation from Pan2, you might be summing things incorrectly. Try dumping out a visual graph of the SynthDef with |
Beta Was this translation helpful? Give feedback.
-
OK.
I have everything connected via buses, and in groups, and I'm quite sure
that the order of execution is correct. I'll take a look at it again later,
tho. Thanks!
…On Tue, Mar 4, 2025, 7:51 PM Joséphine Wolf Oberholtzer < ***@***.***> wrote:
No, I've never run into that.
Suspect that if you're not hearing any modulation from Pan2, you might be
summing things incorrectly. Try dumping out a visual graph of the SynthDef
with supriya.graph(my_synthdef) and read through the signal flow. You'll
need to make sure graphviz is installed to do this.
—
Reply to this email directly, view it on GitHub
<#464 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACVNNETP3IEUR7OHGUXIBVL2SXYZZAVCNFSM6AAAAABYKHJSSKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMZZGI2DOMY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
Ooh, OK. That's probably the issue.
…On Tue, Mar 4, 2025, 8:20 PM Joséphine Wolf Oberholtzer < ***@***.***> wrote:
Ah, if you're orchestrating multiple SynthDefs via buses, and one
SynthDef's responsibility is panning, also check that it's replacing the
contents of the bus it writes to rather than summing to it. Either
ReplaceOut or XOut instead of just Out.
—
Reply to this email directly, view it on GitHub
<#464 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACVNNETNBP5Y7Z4ZQRLBIMT2SX4GNAVCNFSM6AAAAABYKHJSSKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMZZGI3TKMQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
Ah, if you're orchestrating multiple SynthDefs via buses, and one SynthDef's responsibility is panning, also check that it's replacing the contents of the bus it writes to rather than summing to it. Either ReplaceOut or XOut instead of just Out.