At 13:40 18/02/97 -0800, you wrote:
>> Nope, I increased the RAM on perf.ppc and it still choked on the 25  
>> MB score file.
>> 
>
>You may or will get a similar looking memory error if the density of
>events (number of instruments allocated) is too high.  This sometimes
>happens with matt's score generator, e.g.  I think the only way to
>adjust for this is for the programmer to make a fixed pool larger. If
>you make the instruments smaller and the program behaves differently,
>that may be the case.  The memory allocation scheme for instantiations
>of instruments, if I remember right, is not quite so forgiving or smart
>as that for score files.  Something to put on the list, I guess.
>

I think this could well be something to do with my original problem. The
score sorts just fine, but dies while rendering. Since the score is
basically just a collection of randomly distributed sine blips that gets
less and less dense over time, and since it's more or less at its densest
when it falls over, that could well be where the bug (feature?) lies.

I'd guess it's trying to start another instrument, runs out of its memory
allocation, starts overwriting stuff and then falls off the edge of the world.

Could be completely wrong of course...

John?

R.