Disabling Autoarm feature. Max for live or python.
Posted: Tue Jul 29, 2014 3:33 am
So i'm trying to find a way of disabling this push 'feature' that causes arming of tracks that push has focus of which is not so great when using other grid controllers such as launchpad or even another push. I'm not a max or python programmer so have no idea as to how complex such an undertaking is.
I'm using uncompyle2 in conjuction with Easy Python Decompiler v1.2. Comparing my decompiled scripts with julian bayles scripts using WinMerge and apart from a few carriage returns differences the files seem identical.
Also have wing IDE
Looking into the decompiled Push scripts I can see an AutoArmComponent.pyc. The the main Push.pyc has various calls for this (function?). I tried the brute force (lazy)approach of removing the AutoArmComponent.pyc (actually renamed file) but this breaks push functionality i.e. no push response (surprise,suprise)
Then I figured removing all references to the AutoArmComponent in the main Push.pyc might be the best method but I'm obviously causing errors in code elsewhere. So then tried commenting out all references (to keep line spacing/numbering the same) to auto_arm in main Push.pyc or AutoArmComponent. Again broken script. So no quick fix then. lol
So I appreciate I'm gonna need to learn some python and general programming techniques terminology.
Max for live as an option at this stage is even more baffling as the LOM while mentioning control surfaces and various components I'm not entirely sure how to find the paths I might need.
Is it possible to path to and observe a Framework Component?
For instance in the AutoArmComponent.pyc there is a mention of a notification message which I figured that if I could observe this it might be possible to set a condition with it. But there is no mention of notification components in the LOM.
Not giving up yet...
Any insights into this stuff please share!
I'm using uncompyle2 in conjuction with Easy Python Decompiler v1.2. Comparing my decompiled scripts with julian bayles scripts using WinMerge and apart from a few carriage returns differences the files seem identical.
Also have wing IDE
Looking into the decompiled Push scripts I can see an AutoArmComponent.pyc. The the main Push.pyc has various calls for this (function?). I tried the brute force (lazy)approach of removing the AutoArmComponent.pyc (actually renamed file) but this breaks push functionality i.e. no push response (surprise,suprise)
Then I figured removing all references to the AutoArmComponent in the main Push.pyc might be the best method but I'm obviously causing errors in code elsewhere. So then tried commenting out all references (to keep line spacing/numbering the same) to auto_arm in main Push.pyc or AutoArmComponent. Again broken script. So no quick fix then. lol
So I appreciate I'm gonna need to learn some python and general programming techniques terminology.
Max for live as an option at this stage is even more baffling as the LOM while mentioning control surfaces and various components I'm not entirely sure how to find the paths I might need.
Is it possible to path to and observe a Framework Component?
For instance in the AutoArmComponent.pyc there is a mention of a notification message which I figured that if I could observe this it might be possible to set a condition with it. But there is no mention of notification components in the LOM.
Not giving up yet...
Any insights into this stuff please share!