2.9 KiB

Raw Blame History

Programming Music Journal

[2022-08-19 Fri]

[2022-08-19 Fri]

past friday I've done some basic setup (painfully) and had simplest examples running

setting up supercollider package - so this doesn't work for some reason

here simplest things seem to work

cl-collider-tutorial-getting-started

so, let's just go the site?

nope, continue with the file that had some promise the one about cl-collider turorial

also, let's make this a separate repo?

oh, no, the 'supercollider-example' which is about cl-patterns started to work?

how and why? maybe reinit of some shit, or what

so, new file to hopefully learn something about cl-patterns

what is it that I want o learn ideally?

setting up drum sequences?

doing chord things with synth?

what's this thing about "FAILURE IN SERVER /n_set Node 1539 not found "

this seems to be startup

(ql:quickload :cl-patterns/supercollider)
(cl-patterns:backend-start 'supercollider)

;; also launch QjackCTL and connect SuperCollider outputs 1 & 2 to headphones
;; to force restart, use killall scsynth



(in-package #:cl-patterns)

(start-clock-loop :tempo 136/60)

but what's most basic pattern that would play then?

ones in supercollider example seem to work

and example seem to require me to define synth, right? to set it into the :instrument key

wtf am I to do.

maybe let's try to do stuff inside of org file?

how do I clear things, it seems that cl-patterns seems to send things to server?

should I try a different backend?

so, when SC returned lots of errors on pb what helped - starting syn wave from "setting-up" file

;;; https://defaultxr.github.io/cl-collider-tutorial/03-make-a-sound.html (setf s (make-external-server "localhost" :port 4444)) (server-boot s) ; already in use

;;; https://defaultxr.github.io/cl-collider-tutorial/03-make-a-sound.html (proxy :foo (sin-osc.ar 440 0 0.2)) ; no error, but hear no sound ;; opened QjackCtl, connected Graph SuperCollider to Air by Aftershokz left (proxy :foo (sin-osc.ar 300 0 0.2)) (proxy :foo (saw.ar 300 0.2))

how do I make sounds better?

do I go to cl-collider package for explanation of synths and such?

to stopp things that run amok:

(cl-patterns:stop t)

ugh. why doesn't it produce sounds?

ok, what did I learn today?

some interaction with pseq having scales, root / ocave
intersecting with durations, also seq and not totally alighning
some combined sounds, which don't sound nice
maybe reliant startup procedure
and attempting to run chords hangs it all

2.9 KiB Raw Blame History