Re: Weirdness w/1st Control Bus

On Mon, Mar 8, 2021 at 7:19 AM <[email protected]> wrote:
> Ha, I would have never guessed this!

The reason why I'm aware of this is:

MixerChannel uses control buses for level, pan and any other fader
parameters ("any other" so that people can implement any multichannel
strategy they need).

Logically, one of the first things to do in the server when loading a
live setup is to create a MixerChannel representing the hardware
output: ~hwOut = MixerChannel(...). This allocates a control bus for
level, and another for pan.

If nothing else has happened yet, that means the hardware-output
mixer's level lives on control bus 0.

Sometime later, I'm modulating (say) a filter frequency, but forgot to
specify the output bus: ~ffreqAuto = { LFNoise3.kr(0.2).exprange(200,
9000) }.play( /* should put outbus in here but live-coding oopsy */ ).

Well, now my hardware output channel has up to about 80 dB gain. Live
set ruined.

So I found it essential, for safety, to start with `~reserved =
Bus.control(s, 2)` so that any control-rate synth accidents go to a
bus that nobody is listening to.

Once it bites you, then you never forget it -- but it hasn't bitten
you yet, then it's easy to overlook.

hjh

_______________________________________________
sc-users mailing list

info (subscription, etc.): http://www.birmingham.ac.uk/facilities/ea-studios/research/supercollider/mailinglist.aspx
archive: http://www.listarc.bham.ac.uk/marchives/sc-users/
search: http://www.listarc.bham.ac.uk/lists/sc-users/search/