Hi, back in the world of Live 8 and Max 5/6.0, c74 informed me that this property was not safe to observe in js due to it being flooded with data – i’ve tried this in L9/6.1 and it seems better, but still causing crashes. Would be greatful if anyone or c74 can comment on whether this is still a no-no or not.
Please to post or send a frozen device which exhibits the problem. Thanks, Jeremy
Ok, give me a day or so to isolate an example – just fyi, I’ve done a bit more testing and it seems to be no problem if I’m not outputting to the max windows – currently, my devices output a load of trace, maybe 10 msgs per update per clip for 4 clips – if i turn off the trace to the max window it seems to be ok – also, when running in live and not in the editor it’s fine also, so maybe it’s an issue with so much data going to the max window??
That doesn’t seem likely, but we often see memory corruption problems which lead to crashes during posts to the Max window. That is, it’s the effect and not the cause. Thanks for taking the time to isolate an example — hopefully we can quickly identify the problem.
ok, will do… where should I send the device to?
If you don’t want to post it here, you can send it to my first name at cycling74 dot com.
C74 RSS Feed | © Copyright Cycling '74