1) List SC package symbols and import them all into the :om package - so I can use them just like OM symbols. Biggest drawback, possible symbol name confiicts and needing to ensure all SC symbols are in the list used

2) Create new :om package functions/macros with clean names that callsc: functions internally. Eliminates symbol conflicts, but wrappers need maintenance and possible processing implications.

Which - if any - would be preferable - or should I just continue to be bothered by having to use the sc: prefix all the time for UGens (or, more likely, forgetting to use it and getting errors!)

bw

Andrew

Here's a really useful way to create massive clusters of sound with samples using a simple file-player Synth-Def inside a function that creates multiple instances of a synth within pitch ranges defined when calling the function. Number of instances only limited by your CPU. I've used this with 1000+instances without trouble. It's particularly effective with pitched metallic material but works well with anything as long as the 'rate' variable is kept within a range that doesn't go too low or too high. It works better within a smaller range for complex overlaps of sound file play rate in multiple instances.

This is basically a translation of the SC lang code into cl-Collider so formatting still retains some SC peculiarities but it's simple enough to understand:

Synth Def code:

(sc:defsynth playfile-sus 
           ((note 40)(out 0)(buf 0)(start 0)(end 0) (gate 1) (atk 1)(dec 1)(sus 0)(rel 1.5)(lp 0)(amp 0.5))
  (let* 
      ((rate (sc:midiratio (- note 60)))
       (env (sc:env-gen.kr (sc:adsr atk dec sus rel)
                             :gate gate
                             :level-scale amp
                             :act :free))
       (pointer (sc:line.ar start (- (sc:buf-frames.kr buf) 1) (/ (sc:buf-dur.kr buf) rate) :act :free))
       (sig (sc:buf-rd.ar 2 buf pointer)))
    (sc:out.ar out (* sig env))))

Player function code:

(defun multi-synth (file bank low high repeats)
  (dotimes (n repeats)
  (sc:synth 'playfile-sus 
                :buf (nth file bank) 
                :note (rnd repeats :low low :high high) 
                :start 1
                :end 0 
                :atk (rnd repeats :low 0.1 :high 50)
                :dec 1
                :sus 1
                :rel 1
                :lp 0)))

Load files into a buffer to be read by the Synth and then call the function with arguments:

(multi-synth 1 bank 20 100 50)

where the arguments are = file number within bank of files, name of bank of files, min rate speed, max rate speed, number of synths

This call above plays 50 instances of the synth with random choice of rate between 20 to 100 (based on original file rate of 60 so within -/+ 40 of original rate - which I've found is usually really good). Try with 100s of instances with the right material and it's great to play with.  Highly dependent on what sound file you feed into the buffer, of course! 

On starting OM, I get the following error message pop-up:

Error: While loading file Users/acr/Opusmodus/User Source/Extensions/Load CL-Collider.lisp

Package CL-PATTERNS not found

If I try to evaluate (load cl-collider) directly from the file I get the same error in the Listener initially, but then if I use the debugger to trace I get the following error:

Error: compile-file-error while compiling #<asdf/lisp-action:cl-source-file "cl-patterns" "backend">

I have previously managed to load cl-collider successfully and connect to SC Server without any problems -  so not sure why this is now happening? Advice and suggestions?

I am running most recent updated OM Version 3.0.29319 

bw

Andrew

I have a synthdef for a sampler that plays from a buffer based on the list of all files in a folder. It's working fine in SuperCollider:

 

(
SynthDef(\play, {
    var sig, buf, e;
    e = PathName.new("/directory_path/*").files.scramble.copyFromStart(20);
    buf = \buf.ir(0);
    sig = PlayBuf.ar(1!2, buf, BufRateScale.ir(buf) * \rate.ir(1), doneAction: 2);
    sig = sig * \amp.ir(0.5);
    Out.ar(\out.ir(0), sig);
}).add;
)

Synth(\play, [buf: b, rate: 0.midiratio]);

I'm not sure how to build this in OM's sc:synthdef as the examples seem to be focused on oscillator-based sound sources.

My first attempt at an OpusModus sc:synthdef sampler (based on the above example) is:
 

(sc:defsynth sampler ((freq 200) (dur 2.0))
   (let* (e = PathName.new("/directory_path/*").files.scramble.copyFromStart(20))
         (buf = \buf.ir(0))
         (sig = PlayBuf.ar(1!2, buf, BufRateScale.ir(buf) * \rate.ir(1), doneAction: 2))
         (sig = sig * \amp.ir(0.5))
    (sc:out.ar 0 out)))

Which evaluates with a bug. I'm sure there are syntax problems but I'm also wondering if there are conceptual switches I could make to understand synthbuilding in OM rather than supercollider.

Thanks!

THT

Hello,

Working with SC in OM and wondering how I can route my audio on a mac? In SC there are settings like:

Server.default.options.inDevice_("Built-in Microph");
Server.default.options.outDevice_("Built-in Output");

Not sure how to make these device specifications in the OM SC library.

Thanks,

THT

I need a bit of help.

I would love to use cl-patterns which is a wonderful real time tool for live coding with cl-collider.

I've tried that example but doesn't works in fact works but no audio output.

If somebody more experienced than me could help here, it would be nice !

(sc:defsynth sine-kick ((freq 440) (time 0.25) (amp 0.5) (out 0))
    (let* ((env (sc:env-gen.kr 
                 (sc:env (list 0 1 1 0) 
                         (list 0.001 time 0.3)) :act :free))
           (fenv (sc:env-gen.kr
                  (sc:env (list 1 0)
                          (list time)) :level-scale freq))
           (sig (sc:sin-osc.ar fenv 0 (* env 0.2))))
      (sc:out.ar out (sc:pan2.ar sig 0 amp))))


(cl-patterns:pb :kick
  :embed (cl-patterns:pcycles "o-o-------oo----")
  :instrument :sine-kick
  :dur 1/4
  :quant 4)

 (cl-patterns:play :kick)

Best salutations to the always growing Opusmodus users community !

S.