It looks like you're new here. If you want to get involved, click one of these buttons!
Cntrlr shows up under I/O but not Control SurfacesAbleton is finding the python scripts and compiling them, but they never show up in the Control Surfaces list. Cntrlr with latest firmwareAbleton Beta 9.5.1 b2 on Windows 10Thanks!
Sounds good! Thanks Mike.
Did you get this figured out? It should be working if you're using the most current build....
Using the latest download from the website in the latest beta of Live, no go, still.
How are you installing it, are you using our installer? If you have more than one copy of Live in your applications, it will only install to the first one it finds. Try moving any copies of the Live application that are present into a subfolder in your Applications folder and try the installer again. AFAIK there is no problem with the current version and 9.5.
Ableton is seeing the Cntrlr, the Input and Output ports show up but none of the scripts appear in the dropdown. When I push a button, Ableton indicates that it's receiving MIDI data. I'm using your installer from the page http://wiki.lividinstruments.com/wiki/CNTRLR_Ableton_Live_Remote_Script_v2The installation is into C:\ProgramData\Ableton\Live 9.5 Beta\Resources\MIDI Remote ScriptsI checked, the files are there and I see .pyc files that were generated on the first run. Looked in log.txt and found the following: (see http://pastebin.com/2LvbxEkD - too large to fit in message) excerpt follows:(snip)4283 ms. RemoteScriptError: Traceback (most recent call last):4286 ms. RemoteScriptError: File "<string>", line 1, in <module>4289 ms. RemoteScriptError: File "MIDI Remote Scripts\Codec__init__.py", line 3, in <module>4292 ms. RemoteScriptError: 4294 ms. RemoteScriptError: from Codec import Codec4297 ms. RemoteScriptError: File "MIDI Remote Scripts\Codec\Codec.py", line 38, in <module>4300 ms. RemoteScriptError: 4303 ms. RemoteScriptError: from _Mono_Framework.DeviceSelectorComponent import NewDeviceSelectorComponent as DeviceSelectorComponent4306 ms. RemoteScriptError: File "MIDI Remote Scripts_Mono_Framework\DeviceSelectorComponent.py", line 10, in <module>4309 ms. RemoteScriptError: 4312 ms. RemoteScriptError: from _Mono_Framework.MonoButtonElement import MonoButtonElement4315 ms. RemoteScriptError: File "MIDI Remote Scripts_Mono_Framework\MonoButtonElement.py", line 7, in <module>(snip)
Along the way I had also trying uninstalling and reinstalling, removing the Remote Scripts folders in between installs. Currently I am on 9.5.1b6
Tried the files from Github and interestingly some of them show up, such as Livid Alias8 M4LLivid Base M4lLivid Blockand a few others, but not Cntrlr, still the same errors in the log file.
Completely uninstalled and reinstalled Beta again - same result as above.Did a fresh install of 9.5 and I do see the scripts there.
So sorry, I missed that part where you mentioned you were using the beta. Scripts definitely won't work with beta yet, they've changed a lot of things (yet again) and I'm in the process of updating. Sorry for the trouble.
Likewise, Mike! We'll have something out very very soon.....there are already working versions of our scripts in our github repository.
Yes, the scripts in our github repository are working with the Live 9.6 release (AFAIK....if you find something that doesn't work, please let me know). We'll have new installers up very soon.
Hi there, I'm new here in the forum. I also work a lot with the CNTRL:R, also play live. I really really need that script for Live 9.6.. Also need the Drum-Stepper.. Thanks in advance..Markus
Yes yes yes!!!! THANKS LIVID!!!! Great Job, great support Thanks Mike!!!
There were still a lot of bugs I was finding, don't bother reporting them yet as I'm rewriting everything from (more or less) scratch.
Ok, looking forward to the updated script Amounra.
Just tested it but sometimes it seems like the script is loosing itself on the CNTRLR.. I'm also wondering how I can reach the STEPP:R that I use a lot. Until I couldn't find out how to open the template that I can use it like in Script 1. In the manual I can't find a description for that. Is it possible to use Script 1 for Live 9.6? Can somebody help me? Cheers.. Markus
I'll be pushing a new version of CNTRLRv2 to github tomorrow, it should fix some problems (although it's still a work in progress, I think it's about done now....I could use some bug reports if you find any).
There's a new version of CNTRLR named CNTRLR_v2 in our github repo, make sure to move aumhaa folder into your MIDI Remote Scripts folder as well or it won't work.
Thanks. Will try it this week.
Dear Amounra,just tested it.. ok. Nice, but.. I'm not using the Script functions like navigating and all those other tools. I just need the controller setup like in the pre-version for ableton 9.5., a naked CNTRLR and the Stepp:r (my TR-909).. that I can reach by toggling the first push encoder. How I can get these settings? In your description above you told me to add a ..@d:2.. to the stepper. Sure, I can select the stepper, but it doesn't work like before to select the 16 sounds and also to select a step in the TR-like sequencer. Also the 12 encoders are not corresponding to the Stepper's edit-knobs. Thank you.Markus
Perhaps you're also still using the OLD stepprs? You'll need to update them to the current ones or they won't work with the new script. There's no way I can continue to support the old-style scripts (and stepprs). I did my best to provide a way (with the device selector) to still be able to get directly to the steppr you need to access, but there's usually a price for progress :/
Well I think you're right. Seems like I'm really using the old ones..
No worries :) You shouldn't have to fuss with it much, but let me know if anything causes problems with your old presets.
Now I'm into it.. Some things sometimes need some time :-)One question about the Stepper and also the Accent: Normally when Steppr was started the 16 pads of the CNTRLR were showing the sounds that are playing. But now there's no reaction.. Any idea?