Root note in SuperClean

Questions
1

When using SuperClean (i.e. //type clean) changing the root does not have any effect.
It is also not documented in the SuperClean parameter file (SuperClean/superclean-parameters.scd at main · danielmkarlsson/SuperClean · GitHub)

When commenting //cln however it works. I could simply write degree: Pseq([0,1,3,5]+4, inf), Is this the method of choice?

)
(
Pdef(\test,
    Pbind(*[
        //type: \cln,
        snd: \sin,
        //num: Prand([1], inf),
        dur: Prand([1/4, 1/4], inf),
        amp:0.8,
	    scale: Scale.minor.degrees,
		root: 15,
        degree: Pseq([0,1,3,5], inf),
        octave: 4,
    ])
).play;
)
2

from your link:

There are some notable exceptions in this list of keys that provide convenient calculation of frequency when compared to the equivalent list in SuperCollider. This is because these keys have been reconstructed inside the custom event type that is SuperClean. There are some workarounds. You can use ctranspose as a dropin replacement for root. If you add 60 to a midinote value you get the equivalent to note. If you add a fraction like for example 0.5 at the end of a midinote calculation you get the equivalent of detune.

1 Like
3

Thanks, I play with this to figure it out.

4

A bit of context: the Event class itself doesn’t define any parameters at all. It’s completely agnostic as to names and values. So, for events in general, there isn’t any \root or \degree. (There’s perhaps one exception, where anEvent.delta is hardcoded to \dur and \stretch.)

What we usually think of as “event parameters” are really defined in the default event prototype.

A new event type function, like \cln, does not have any obligation to follow the parameter design used by the normal \note function. If \cln’s pitch model is different from the default one, and it documents that it’s different, then the right answer is to follow what SuperClean documents (because the \note event type parameters are not rules that must be maintained – they are just one scheme among many possible approaches).

(It’s also possible to define completely different prototype events, which don’t implement any of the default parameters.)

hjh

1 Like
5

I think my confusion came from this section:

The parameters below aren’t actually part of SuperClean, but are very useful to know about,
and, because SuperClean is running inside SuperCollider, we can use them.

dur: The duration between events, range is a float above zero to infity, zero is infinitely fast, so, never do that.
midinote: 0 to 127. 60 is default. Interestingly accepts floats which allows for microtonality.
freq: When we want to work with frequencies instead of midi note numbers as above, accepts integers 20 to 20000.
scale: Choose scale, for example: Scale.harmonicMinor, add a tuning there like this: Scale.harmonicMinor(\sept1)
degree: Negative infinity to infinity really but often, in the west, there will be seven degrees in scale.
octave: Choose the octave. Range is zero to infinity really but a reasonable range is more like 1 to 6. Accepts floats!
ctranspose: Chromatic transpositon. All the keys on a piano. Range is something like integers between -63 and 64 but depends.
mtranspose: Modal transposition of degree within a scale. Works in combination with other keys like degree and scale.

Especially because of “because SuperClean is running inside SuperCollider, we can use them.” I thought that maybe “root” will also work.