Basvlk

Hi - my previous post was a bit lengthy, I think I have narrowed down the problem.

when you have the above patcher as an abstraction inside a M4L device, it crashes when you add an argument at the end of the patcher name. It seems only to happen when Preview is ON though... anyone an idea what may be going on?

Hi - my previous post was a bit lengthy, I think I have narrowed down the problem. 

when you have the above patcher as an abstraction inside a M4L device, it crashes when you add an argument at the end of the patcher name. It seems only to happen when Preview is ON though... anyone an idea what may be going on?


adding-an-argument-causes-crash-hmm-bug

I can't reproduce the crash, but I think your abstraction is problematic since the switching between live.object and live.remote~ mapping may cause conflicts due to overlapping disable/enable operations.

yeah - I did feel it would be somewhat risky to change method within a subpatcher, but it's oh-so-handy: both methods have pros and cons and it is great to be able to build a patch without committing to either, at least during development.

I did take care to have an 'id 0' sent to the one before the other is activated: as far as I can see, sending an 'id 0' switches off the live.observer / live.remote. I submitted the patcher to support, let's see what happens

adding an argument causes crash. Hmm. bug?