Softcut~

[andrew]

it slews record level not output level

Norns: update 190930

2.2.0 use SYSTEM > UPDATE while connected via wifi. changelog NEW crow support FIX vu polls now use dbfs scaling @catfact FIX (BREAKING) audio.file_info now uses absolute path NEW system_cmd async os call function NEW softcut.level_slew_time slews level (not rec/pre level) FIX softcut.level_slew_time -> softcut.recpre_slew_time NEW softcut.pan_slew_time FIX softcut pan flip channels, scale from -1.0 (left) to 1.0 (right) FIX softcut.level_cut_cut arg order @license FIX softcut equal power…

^ see this update on norns - this was ported before that change. in max ya might as well just run the output into a *~ and slew the control signal

(in a lot of ways this port doesn’t feel purpose built for max and that’s a future project I want to work on)

[Anfim]

Interesting! from a performance/ui perspective, what’s the purpose of slewing output level? I can understand slewing rec level - you’ll get swells when recording rather than abrupt chops. would slewing the output affect anything apart from starting and stopping playback?