MuShoo

I've got a project I'm working on using Beat~ (I've tried beatitude and the others, beat~ works best for my purposes.)

It works fine in Max 5.1.7 (OSX 10.6.6, 8-core mac pro 5gb RAM), but when I run it in a standalone it will inevitably die after a few minutes - the app itself doesn't crash, JUST Beat~ stops actually functioning. Cycling DSP status, changing vector sizes, restarting the scheduler, nothing works to revive it except restarting the app.

Any thoughts on ways to fix this? Or at the very least, a way to reload an object into memory via a standalone (in Max what I'd normally do is add a space at the end of the object name so it reloads... can't do that in a standalone!)

It works fine in Max 5.1.7 (OSX 10.6.6, 8-core mac pro 5gb RAM), but when I run it in a standalone it will inevitably die after a few minutes - the app itself doesn't crash, JUST Beat~ stops actually functioning.  Cycling DSP status, changing vector sizes, restarting the scheduler, nothing works to revive it except restarting the app.

Any thoughts on ways to fix this?  Or at the very least, a way to reload an object into memory via a standalone (in Max what I'd normally do is add a space at the end of the object name so it reloads... can't do that in a standalone!)

Beat~ 'mild' crash in standalone.