[sc-users] The curse of the blowups

[Dan Stowell <danstowell@xxxxxxxxx>]

Hi,

I'm doing a lot of work on evolutionary synth generation (as
mentioned/linked before), and because the networks that are generated
are so unpredictable, occasionally I'll get a blowup. Please stop me
if I'm using the term incorrectly - but what I'm referring to is the
condition when all output completely stops, only solvable by rebooting
the server. In one case I found it could be caused by a UGen being
tricked into outputting "NaN" rather than a real number.

So I have some related questions:

* Is there any way at all to "catch" blowups or to recover from them
without having to kill the server?
* Does anyone know of specific conditions which might cause blowups?
I'm not using any particularly weird UGens...
* Should this kind of problem be treated as a bug (assuming I'm not
using anything like FSinOsc which comes with a blowup warning)? I
would hope that an SC user should be insulated from this kind of
thing, but perhaps the decision has been to sacrifice that kind of
insulation in favour of faster code...?

Thanks
Dan


--
http://www.mcld.co.uk