[Fluxus] Fluxa issues

[Kassen]

Ok, so back to Fluxa :¬)

I had a series of issues;

* the internal help for "seq" is actually just a part of the help for
(clock-map) and won't run on it's own as a variable "nt" is undeclared. It
also shares the next issue.

* the internal help for clockstep is this;

 (seq (lambda (time clock)
    (clock-map
      (lambda (nt cutoff)
        (play time (mul (adsr 0 0.1 0 0)
          (mooglp (saw (note nt)) cutoff 0.4))))
      clock
      (list 39 28 3)
      (list 0.1 0.1 0.4 0.9))))

And should likely read;

 (seq (lambda (time clock)
    (clock-map
      (lambda (nt cutoff)
        (play time (mul (adsr 0 0.1 0 0)
          (mooglp (saw (note nt)) cutoff 0.4))))
      clock
      (list 39 28 3)
      (list 0.1 0.1 0.4 0.9)) *.15* ))

...or something like it.

* To make matters worse, if we *do* run the example as is, we get this;


Error in Task 'fluxa-update-task - Task removed.
+: expects type <number> as 2nd argument, given: #<void>; other arguments
were:
 1290416223.224918
call stack:
go-flux line 976 in /usr/local/lib/fluxus-017/fluxa.ss
#f line 174 in /usr/local/lib/fluxus-017/tasks.ss
call-with-exception-handler line 274 in
/usr/local/lib/racket/collects/racket/p
rivate/more-scheme.rkt
for-each line 45 in /usr/local/lib/racket/collects/racket/private/map.rkt
run-tasks line 161 in /usr/local/lib/fluxus-017/tasks.ss
default-fluxus-frame-callback line 373 in
/usr/local/lib/fluxus-017/scratchpad.
ss

.......we get that to the terminal if that's what we started from and I get
it on my "dramatic debug-printing" but it doesn't seem to show up in the
plain repl. I think it should. This means losing the fluxa task and I don't
think I've been able to get that task back up without re-starting Fluxus. I
don't think that's proper behaviour as this is a easy typo to make (clearly!
:¬) ) and additionally there is the "fluxa error handler" that I imagine is
meant to prevent exactly that sort of thing from happening in catching stuff
like this before it causes that big a problem.


Aside from this series of issues I should note that jamming in Fluxa is
unexpectedly large amounts of fun for how simple it all is. Some of the
weirdness (what is the unit of cutoff frequencies of the filter?) make
surprising amounts of sense once you adapt to them. Nice.

Yours,
Kas.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pawfal.org/pipermail/fluxus-pawfal.org/attachments/20101122/70c7bce5/attachment.htm>