Steno:set >> `mix` and `through` behaviour

[LFSaw]

It seems that mix is a drywet control, whereas through has no effect at all.

Documentation says:

mix sound level default: 1 through for filters: pre vs. post level default: 0

s.boot
(
t = t ?? {Steno.push};
t.quelle(\q, { |in, controls|
    Pulse.ar(1000) * LFPulse.ar(3, width: 0.04)
});
t.filter(\f, { |in, controls|
    PinkNoise.ar(Decay.ar(Impulse.ar(10), 0.01))  * controls[\env]
})
)

-- qf

// mix reacts like a drywet control. sounds to me like what is described as `through` in Steno helpfile (method set)

t.set(\f, \mix, 1) // only filter (default)
t.set(\f, \mix, 0) // only quelle

// through

t.set(\f, \through, 1, \mix, 1) // with mix==1, has no effect
t.set(\f, \through, 0, \mix, 1)

t.set(\f, \through, 1, \mix, 0) // with mix==0, has no effect
t.set(\f, \through, 0, \mix, 0)

[LFSaw]

@telephon can I have an opinion in this?

[telephon]

Let's discuss this when i have the occasion to test and look at the code, in a month or so.

The confusion comes perhaps from a different meaning of the two parameters in quelle and filter, and perhaps in buggy behaviour.

Normally, through should make a synth increasingly transparent, but i have to have another look. what's your opinion ?

[LFSaw]

mix behaves differently in quelle and filter, whereas through doesn't do anything. Let's discuss whenever you have time :) If it'll take a month, I think I need to just go ahead and develop my own fork, though...

[telephon]

I can discuss but nothing much else. Remember to check how parentheses respond to these parameters.

The bus mapping is a little delicate.

[telephon]

the difference between mix and through is in the difference between dryIn and outBus in the StenoSignal class. This is where I'd look if I could

[LFSaw]

thanks for the pointer. I also started to understand what is wrong with thorugh: it is not possible to set it with Steno:set since it is excluded from that here (we should definitely make this list a static variable that resides in a more visible place...).

[telephon]

ah yes, maybe it is better to keep it internal? I don't remember what I was using it for.

[LFSaw]

I'm on it... :)

On 14. Aug 2017, at 21:05, Julian Rohrhuber notifications@github.com wrote:

ah yes, maybe it is better to keep it internal? I don't remember what I was using it for.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.