Basvlk

Hi all - I've been struggling with this, it's been hard to find why this patcher (and many variations of it) keep crashing live. It seems to work OK _until_ i create an abstraction, after which a save or change of argument crashes Max and often Live as well.

I suspicions are that it is related to 1) the use of patcherargs or 2) the use of a switch that switches between live.remote and live.object (see further down)

*on an incoming LIVE path, it builds some strings to send to my Ipad (parameter values, label names)

*it assigns a TouchOSC fader on my Ipad to a Macro of a live device

One thing which I"m not sure about is that I build a switch in it which allows you to switch how you control a LIVE rotary: either through live.remote or through live.object. I've been very careful to make it all happen in the right sequence, like sending an 'id 0' to live.remote before switching to live.object. It works really well on its own but I wonder if having a few of these buried in abstractions is causing problems. Here's the patcher:

Hope this makes some kind of sense. As a general rule... is there a way to troubleshoot why Max crashes?

Here's what the patcher does:
*on an incoming LIVE path, it builds some strings to send to my Ipad (parameter values, label names)
*it assigns a TouchOSC fader on my Ipad to a Macro of a live device

Can you see why this patch crashes Max and Live?