listener

[AM]

is there a possibilty to ONLY show INSIDE the LISTENER what i like to: some (print ....)-stuff

...and not all the "function-calls" like 

 

.....

ratio-to-msec
rnd-pick :seed 990096
rnd1 :seed 858709
compress
rnd1 :seed 223329
compress
list-to-string
ratio-to-msec
ratio-to-msec
ratio-to-msec
prob :seed 115209
prob :seed 40751
stop-score-player
score-player
....

 

thanx for a hint

andré

[opmo]

No possible.

[torstenanders]

Actually, it is possible to leave out those logging messages. Execute the following. (Unfortunately, this does not work when defined in an ~/Opusmodus/Extensions/*.lisp file. My guess is that it is overwritten by the system afterwards. However, you can execute it after the  startup, e.g., by hand, and it cleans up your listener.)

 

(defparameter *do-verbose* nil
  "Enable or disable traces printed by do-verbose.")

 

For details see

Best,

Torsten

[torstenanders]

Anyway, thanks to Janusz again for adding that after such a feature request! 

[AM]

dear torsten,

that works perfect!

so i can display what my algo is doing in each loop...

thx

 

 

 

[torstenanders]

Thanks for sharing your screen. Is sleep precise enough for realtime scheduling? 

[AM]

the LOOP-cycles produces data-sequences with lengths about 5 to 20 sec 

for this... stop and wait via SLEEP is oaky....

 

inside the loop: i send the datas (the sequences) to screens (generative score + conducting for the musicians / polytempo) and MAXMSP (sound/modsynth) ... this is via OSC for accuracy/coordination

 

so it works fine like that... but: LISP is not exactly suitable for REALTIME processing  

[opmo]

Soon I will release the documentation for the SCORE-PLAYER and STOP-SCORE-PLAYER function.