hi all
it's for me currently not possible to test nova on my box, so i cannot
contribute with bug reports and such. however, what i probably still
could do is addressing some issues that i have with pd, so these could
be avoided in nova beforehand. probably what i have in mind is already
addressed by tim (or other devs), but anyway i think it would be nice to
have some kind of an idea pool (wikipage?) where people could post their
ideas (if that is desired). what do you think?
a short list of general issues, that spontaneously come to my mind (i
don't know if probably some of them are already addressed in nova):
- errors:
in pd many objects print their errors to the console, which makes it
impossible to take them into account within a patch. i think this is a
big flaw (if it pd is considered to be a programming language [and that
is how i use pd])
- reporting:
many objects are able to print their current state (connection, on/off,
whatsoever) to the console, but not to an outlet. others don't report
their state at all, while reporting would be helpful.
- networking
actually the problem described above (reporting): all network objects in
pd use a standard buffer of 4kB. if the buffer is full, processing is
stopped, which causes audio drop outs. i think it would make sense for
all objects that establish a connection and buffer messages, if they
would report their actual buffer state. in case of the network objects,
it would aready be sufficient, if they would send a 'bang' or whatever,
whenever the buffer is emptied. with that information, patches could be
built, that send only the next message, if the buffer is empty, but at
the same time use the maximum bandwidth available.
- reading~ from tables
pd's abilities to deal with samples are quite limited. if reading
directly from disk, you can only play at actual samplerate, that pd is
running. not only that, but you also cannot start playback from an
arbitrary point within the file (you can use some hacks, but they only
work, if you set headersize, bytes per sample, channels, endianess etc
yourself -> not a clean solution). if non-standard speed is needed,
samples need to be loaded into tables. however this is limited by ram,
which isn't that much an issue anymore nowadays. but there is also a
problem with floating point precision. depeding on your quality needs,
you are very limited in sample size, since above a certain index the
floating point representation is not precise enough anymore to set the
index accurately. actually, i don't know how this could be solved, but
if it would be solved, it would be a big PLUS for nova.
my 2¢ (still CAD)
roman
___________________________________________________________
Der fr�he Vogel f�ngt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail:
http://mail.yahoo.de
_______________________________________________
nova-dev mailing list
[email protected]
http://klingt.org/cgi-bin/mailman/listinfo/nova-dev
http://tim.klingt.org/nova
