Sep 2
Jim says
OK, I see it.
The first thing it needs is enough context for me (or
an outside examiner looking at it) to know how to use it,
namely what else specifically needs to be running
(to send it the osc stream), and how to invoke it.
Unless there's some way to record & playback the osc
stream that this thing consumes (an example .wav
and a short python script to read it and output
as osc??), it looks like it's going to be difficult
for me (or others) to run it without expensive
dependencies.
The second thing I would suggest is a roadmap of
ideas of possible feature sets to add during
the semester.
And you also need a bibliograpy i.e. list of links
to resources & documentation for the pieces you're
using (or might use) and/or links to those similar
efforts you mentioned.
The function doc strings are a step in the right direction.
But the fact that your one python file doesn't have
any sort of header given all the conversations
we've had and the nagging you've heard about from me
about that sort of thing is discouraging.
