Your shopping cart is empty.
🔥 Lifetime deal! Get Control Surface Studio for Just £67 👉 Click Here To Get It
Time left...
⚠️ Lifetime licenses are ending soon, get yours before they're gone ⚠️
CSS2.6.3 + Live 11.1.5 - can't get it to function
Submitted by William Blanes on Wed, 05/18/2022 - 14:04
Control Surface Studio User
Hi. I'm using CSS 2.6.3 with the current version of Live (11.1.5) and am not able to get my remote script to control Ableton as desired.
I've been working on the FCB1010 template and have assigned all the MIDI CCs and Notes to my buttons with Midi Learn On in the Controller Templates page. I've then created a simple script following the tutorials and installed it properly (shows up in Ableton).
The thing is only the metronome on/off function works, but volume change and track select don't do anything.
Is there a problem with CSS2.6.3 + Live 11.1.5, or must I be doing something wrong? I've tried and tested everything that comes to mind, but Ableton just does not respond to these commands.
Topic Category:
Comments
Hi,
It sounds like probably a configuration problem:
With regards to volume, the FCB doesn't have faders so how are you trying to change the volume? can you post a screenshot of your configuration for that mapping.
Also, incase there is an error with script, check the log in css for errors.
I am trying to change the volume with the expression pedal. I am attaching a screenshot.
Thing is, nothing else works.
None o f the normal function like play, stop etc. actually work in Ableton.
Can I get some help? Even your templates don't work for me. I am able to instal them as control scripts but then the buttons and knobs have no effect on Ableton whatsoever.
same error here.. pls help!
Hi William,
Is the MIDI data definitely setup correctly for each of your buttons, knobs, expression pedals in the controller template?
You can check this by opening the MIDI menu at the top. when you move/press a physical input on your controller, its data should display in here.
Make sure that the MIDI channel/type/value are correct for the input settings.
The 'velocity' shows you what to input for the 'first' 'last' / 'on' 'off' settings.
Please can you tell me what velocity values the expression pedal sends, when you press /release it.
Thanks
I'm going to ask for a full refund as I am getting no replies.
WIlliam, did you see my reply to you, above your last comment?
Hi John. I have tried every which way, with factory default settings as well as manually programmed ones. Remotify recognises Midi coming from the FCB1010, and the FCB1010 works very well when Midi Mapped directly in Ableton, and the problem I am having is not happening solely with my FCB1010, but with all my controllers, Maschine Jam, Twister, Midi Fighter etc. I can map and program functions for the buttons, knobs etc. in Remotify, and send the script without errors to Ableton Live, but then once in Ableton Live, the controls I have set up and mapped simply do nothing.
Same here. I have trouble getting my script running. I just got a new Mac M1 and reinstalled everything. I remade the remote script I made a while ago for my Launch Control that gave me instant access to all send fx on the active track. The script was working for me before but now I cannot get it to work. There are no error messages. And I didn't find any error message in the log.txt. The midi messages are received by live as well but nothing happens when I turn the knobs. Is there a known Issue on the M1 (running live through rosetta) or Ableton Live 11.1.5? Thanks.
I have a mac M1 as well and do not have any issues using Ableton Live on it. I think the issue may be with Remotify on the M1, but hopefully John can shed some light on that. The software is completely useless to me, and it is a shame as I was really looking forward to mapping my controllers in a way that fits my performance and production setups.
Hi guys,
Have you tried generating scripts with any previous versions of Live (pre 11.1.5) to see if your scripts work in there?
No, I was hoping it wouldn't come to that.
When are you anticipating a fix for Live 11.1.5? CSS is sold as being compatible but it is not working.
I don't see any reason why the template shouldn't work if Ableton is able to receive midi from your device, outside of the template. Not saying you're lying, but there should be hope.
Do you have any devices that have a premade standard template? Does that work? I have an FCB1010. I could try out your template if you share it.
I have tested ableton live 11.5.1 this evening and scripts built with Control Surface Studio are working as usual with it.
John C. have you tested with a Mac M1.
Read golden_child92's post (from Tue, 06/07/2022 - 19:06). He or she is having the exact same problem as me and is also on an M1.
I have tried just about everything and nothing works. I'll explain how I broke it down to the bear minimum so you.
I made a simple script using your Midi Twister premade standard template.
I assigned Knob 1 to turn metronome on/off on the switch and to speed up and down the tempo on the rotary encoder.
I assigned the switch on Button 2 to play the song. Installed into Ableton Live. Restarted Live, open up the Midi tab in the preferences and set my new script as a control surface. Pressed the button and nothing happens, no play, no metronome action, even though Live is recognising a midi input from the Twister.
The scripts may have compiled properly and could work on non M1 macs, but not on M1.
Are you considering addressing this issue or should I request a refund and get my money back?
If you're able to share your template here today, I'll test it on my M1. Tomorrow I'm going to Italy, so then it'll be a while until I'm back.
I am experiencing similar problems with the CSS scripts on my Launchkey MK3 25. Only two of the seven assigned actions work. I have used MIDI-OX and also the CSS MIDI Learn feature to insure that I'm set up properly.
We don't currently have a Mac M1 which we can test it on here sorry.
As I mentioned, CSS scripts work with Live 11.1.5 so that isn't the issue.
Sitrusfrukt appears to be using an M1 and successfully building scripts for it, so that doesn't appear to be the issue either.
With regards to the MF Twister template, this uses the factory default MIDI settings, so ensure that you set the midi controller back to factory defaults or edit the template to match your changes.
I would recommend just adding 1 mapping, something simple like a start playback, to test that the script works. Then build on it from there.
@Cliff, it some of your mappings are working then it is more likely to be an issue with either the MIDI settings or mapping settings.