Launch control XL does not reflect scripts
Hello to the Remotify community.
I purchased Remotify at the end of August.
Remotify does not seem to function properly in my environment.
I have asked Remotify a few questions and followed the answers a few times but it didn’t work, so I would like to ask the Remotify community a few questions.
＊Problem
My first script <my script name/css original dub 1> shows up fine in the pull-down menu of the Midi tab in Ableton Live 12 preferences.
But no matter how many times I try, the selected css script is not reflected in my session view.＊My PC environment
Ableton Live 12
Macbook pro 2021 M1 pro 14inch
Novation / Launch control XL
When I select the Launch control XL script assigned to each manufacturer’s controller in the Ableton pull-down menu, it works fine and the LEDs etc. light up.
However, when I select my own script (my script name/css original dub 1) created with css, the LEDs on the controller turn off and nothing reacts. (I will attach a photo).
Has anyone else experienced the same problem?
If any users have solved the same problem, I would be very happy to know.
Thanks for reading.IMG_2577.JPGIMG_2578.JPG
***********
Have you added LED feedback in the script (in some mappings)?
Can you help me solve this problem?
I am trying to do exactly what you say but it doesn’t seem to work.
Have any of your users ever had the same case?
I am very excited about Remotify and would like to know the solution.
The answer is the same for volume and sends.
Make sure you have LED feedback turned on for each mapping.
Are you using the controller template for Launch Control XL which is available in the ‘On Remotify’ section of Control Surface Studio?
I have turned on all led feed backs.
I’m using controller template for Launch Control XL from On Remotify section of Control Surface Studio.
But I still can’t control Ableton Live with my controller.
I don’t know if there is a problem with the script I made or with my controller.
I attach a script I made in css, can you please verify it?
Please upload the script json file so I can check it, thank you.
The json file is attached to the first question.
Just to be sure, I also sent the jason file to the support email. Please check.
I can’t see the uploaded file on here but I found it in your email, thank you.
The script LED feedback settings in the script look ok.
Do you have ‘Track’ and ‘Remote’ checked for your script input and output ports in the Ableton settings menu, like in this screenshot?
Thank you for your replay.
Yes,Track and remote are checked in the Ableton preferences, as you can see in the picture.
Have you found a solution?
I’d love to know if there is a solution.
If your settings match my screenshot above, and there are no errors being displayed in the log, it should be working.
Do you have any other software or hardware running on your computer which could be blocking the midi Launch control from sending MIDI data to Ableton LIve?
I’m using a Roland Quad capture audio interface, but no other hardware is connected.
What are the facts so far, and is there any precedent for software blocking the movement of CSS?
If so, is it sufficient to remove the software?
Also, what are the recommended settings in the Mac OS X preferences?
Please see my screenshot below of my mac settings.
I have uploaded my setup.
Please check.
Is there a solution?
I’m not clear on what the issue is.
Do you see any errors in the log?,
is the controller template using the correct MIDI data for your midi controller?
Have you added mappings to your script?
do they work?
is it just the LED feedback which isn’t working?
Sign up
User registration is currently not allowed.
Thanks for the answer!
You are right, I didn’t set the script in the css to turn on the LEDs, so I think that was the cause of the LEDs not coming on.
However, my settings for the other volume sliders and effect sends are not reflected.
Any tips would be great.