So is it correct that one cannot get the heap down to below the starting heap value without changing it and recompiling s7?
I've had quite a striking change in GC time when the heap is bigger, so am curious to give a smaller heap size a try. In other news though, locking it out for the duration of a song works like a charm and allows me to run real time s4m sequencers inside Ableton Live with even very low latency values. Though for that matter, doing absolutely nothing to the GC also works fine for pretty standard Ableton Live latency settings. A large heap resize does give me an underrun but seems like I have to deliberately abuse it to make that happen, normally the gc does it's thing in time without issue. iain On Fri, Sep 10, 2021 at 9:59 AM Iain Duncan <[email protected]> wrote: > Ah, great, thanks Bill. > > When I feel like I have got somewhere decent I will document up what I've > learned and if it's useful to have up on a non-Scheme-for-Max specific > cookbook page or something, I'd be happy to make that. > > iain > > On Fri, Sep 10, 2021 at 8:40 AM <[email protected]> wrote: > >> To see heap and gc stats, set gc-stats to 3 -- I should >> dream up names for these bits. >> >>
_______________________________________________ Cmdist mailing list [email protected] https://cm-mail.stanford.edu/mailman/listinfo/cmdist
