I tried rendering patterns for the first time last night. It's
really cool, but seems to have a nasty memory leak. The following
code leaks about 30 meg on my system:
---------
// make a big score
a = { Pbind(
\dur, Pseq(({ rrand(0.125, 8.0) } ! 1024).normalizeSum * 30, 1),
\freq, Pseq({ rrand(50.0, 4000.0) } ! 1024, 1),
\amp, Pseq({ rrand(-48.dbamp, -12.dbamp) } ! 1024, 1),
\attack, Pseq({ exprand(0.001, 0.2) } ! 1024, 1),
\release, Pseq({ exprand(0.001, 0.2) } ! 1024, 1),
\legato, Pseq({ [exprand(0.1, 1.0), exprand(1.0, 2.0)].choose } !
1024, 1)
)} ! 8;
// render it
Ppar(a).render("foo.aif", 30);
---------
Since the whole reason I'm rendering is to quickly evolve, compare,
and mutate large patterns in a long batch job overnight, this makes
it somewhat useless for me. Am I doing something wrong, or is this a
bug?
It seems to be dependent on the size of the score rather than the
size of the rendered file.
--
Tim Walters | The Doubtful Palace | http://doubtfulpalace.com
_______________________________________________
sc-users mailing list
info (subscription, etc.): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: https://listarc.bham.ac.uk/marchives/sc-users/
search: https://listarc.bham.ac.uk/lists/sc-users/search/