Post by André G. Mendes on Mar 1, 2018 7:44:05 GMT -5
Ok so I was testing yesterday and I noticed something awesome that I didn't knew.
So I used to have the top slot of the control surfaces area reserved for Clyphx Pro. But yesterday while testing I removed Clyphx Pro from that slot and I notied that it was still loaded in Ableton.
I then realised that because I'm using Arsenal (NLC A) on another slot that the Clyphx is somehow loaded into Arsenal so I don't need to have one Slot dedicated to Clyphx Pro anymore, which is great because now I can have all 6 slots for Midi controllers.
I wasn't aware of this so it kinda made my day
Regarding your previous answer, I will try NativeKontrol's bcr/bcf scripts and see how it goes because I'm having some strange issues with Isotoniks when Arsenal is connected. Somehow after a while the Launch Control stops responding.
Anyway I just got a Midi Fighter Twister and I find the default 9.6 script not very user friendly... Are you thinking of making a proper script for this controller? I'm asking because I'm really impressed with the options on this controller. Because of the led feedback on the knobs and the on/off options this has a great potential if armed with a script Arsenal powered!
Yes, Arsenal scripts automatically load ClyphX Pro if it isn't already selected as a control surface. FYI, this is covered in Arsenal user manuals.
As far as the Launch Control ceasing to respond, other scripts should have no bearing on that. If it should happen again, post on the Arsenal board with some more details and make sure to attach your Log.txt file. On a related note, we don't currently offer any products for the BCF. As far as the Twister, there's a request for that here. Please give it a vote.
There's a couple of issues here. The first is that you should be renaming __init__.pyc to __original_init__.pyc.
The second is that if you're going to use the standalone ClyphX_Pro script with retrofitted scripts, it needs to be selected in a Control Surface slot above all retrofitted scripts. So, in this case, it would need to be selected in slot 1 or 2, above the SL script.
Hi Stray, if those underscores before 'original' are significant, you should edit you're second (tutorial) post.
I encountered something puzzling, I tried retrofitting my livid base using the youtube video and this thread (I have Arsenal working so I was just interested in creating an X-controls folder for base mode 4), but the only result was that it made the folder invisible in the ableton control surface list, then I tried my APC40mk2 just to check, with the same result.
No real big deal for me, I can do the same things on my arsenal launchpad setup, but still thought it worth mentioning,, cheers, sal
The video on YouTube is slightly out of date. The info in the first few posts of this thread are correct. In short, since the video was done, the naming was simplified as the underscores were causing confusion.
Locate the folder of the script to retrofit in Live's MIDI Remote Scripts directory.
In the script's folder, find the file named __init__.pyc and rename it to original__init__.pyc. So you're just adding the word original to the beginning of the file's name.
Paste the following file into the script's folder and restart Live.
Undoing the retrofit:
Delete the files named __init__.py and __init__pyc.
Rename original__init__.pyc back to __init__.pyc. So you're just removing the word original from the beginning of the file's name.
Notes: At present, the Push and Push2 Control Surface scripts cannot be retrofitted. Additionally, the following legacy scripts cannot be retrofitted: Axiom, FireOne, LV1_LX1, LV2_LX2_LC2_LD2, MackieControl, MackieControlXT, MackieControl_Classic, MasterControl, Nocturn, ProjectMixIO, RemoteSL, RemoteSL_Classic and Tranzport.
I'm very confused, please help.
after renaming to "original__init__" the folder XTAPC40_MkII is created and now I should add my actions in the X-controls inside that folder. but when I do nothing happens.
I tried the same process with my Midifighter twister as well.
I'm using the original X-control files for nanokontrol.
What you're trying to do here wouldn't work since the APC40_MkII script uses all of the MIDI messages sent from the controller and so those MIDI messages cannot be used for X-Controls. FWIW, the X-Controls section of the manual covers this.
Can't Midi Fighter Twister be retrofitted? I tried the steps above but when I restarted live and go to the Midi settings, the Control surface for MFT is set to none and the Twister script is no longer in the list