Automapping layers
Hello!:)
I’m an absolute noob and I would like to ask for assistance to set up layered macro automapping.
For instance, my controller would get automapped ( Xtouch mini / Midimix) to the first 8 macro on a device, then switch to the next set of 8 after a press of a button. Where do I need to start?
Thanks!
Nothing to worry about, we’re all learning as we go. Thanks to your comment about having to ask access to the Google Doc tutorial, I just learned that I forgot to make it accessible for anyone with the link. You should now be able to open the document from the link and read it.
I just re-downloaded the script that I had posted in comment #1 and it works on my computer. Let’s do some troubleshooting. Here’s a checklist of questions. If everything checks out, I think you should get the example working. You’re not obligated to answer the questions to me, the list is meant to get you on the same page as me. If you find something not working out as it should and need help, then give a shout and we’ll see where we get with it.
Before opening Ableton
– Did you clear your Log in CSS before opening Ableton? This might be the cause of the sluggishness of CSS.
– Do you know how to see your Log in CSS? In the right halve of CSS, where you can view your Template, you need to drag the Log up in order to see anything that’s written in it. (see first 2 included pictures)
– When the Log window is visible, do you see any errors? I don’t know which other scripts you’re using but the one time CSS was sluggish for me was when turning a knob produced an error for each change in velocity. Turning a knob can rapidly produce a lot of velocity changes and thus a lot of errors. I’m only wondering if you’re having the same problem. If so, you might want to check that out, or stop using the script that causes it, for the moment.
– Did you import the contents of my .json file into an empty script, or were there already other mappings inside? If there were, maybe they are conflicting with the ones from my script. To see how the example works, I would suggest importing it in a new script. The list of mappings should look like the one in picture 3.
– Are you using the same MIDIMIX template as I have? I used the one that you can download in the CSS app itself, made by Remotify. (picture 4 shows the location)
– Are you using the same MIDI Channels and values of all the buttons as they are set inside the template? To test this, just move a button while the template is open. If the same button on the template turns green, then you’re fine. If not, then you’ll need to either change the template to match up with your MIDIMIX, or you’ll need to use the MIDIMIX Editor app to change the channel and CC values of the MIDIMIX itself. Little personal anecdote: Before I bought CSS, I had foolishly changed all the settings on the MIDIMIX itself (because I didn’t know what I was doing and was just trying stuff out). Later, I bought Remotify’s Mixify template and I had to revert all those settings again. Which was a chore, but the Mixify script worked like a charm after that.
If all those questions check out, upload the new script with my mappings to Ableton, clear your Log (if not already) and then open Ableton.
With Ableton open and the MIDIMIX connected
– In Ableton’s settings, do you have your script selected as ‘Control Surface’ for the MIDIMIX? Also, are the Track and Remote buttons selected? (see picture 5, my Control Surface is called css_temp).
– In your currently selected track, do you have a device open with Macro Controls? If not, I’d suggest following the example in picture 6. You can also max out the number of Macro Controls visible with the + sign under the “Show/Hide Macro Controls” button.
– On the MIDIMIX, only one button should be lit on startup of the script and that’s the button above slider 2. This means the sliders are now controlling Macro Controllers 1 to 4 of the currently selected device. Try moving the sliders and see if it works now.
– If you push button 2 once now, button 1 will also light up, because you’ve gone up a set of 4 Macro Controls. Now you can control numbers 5 to 8. Also, if you go and look in the Log on CSS, you should see that the latest message says “m1=4” and the first message says “m1=0” because that’s how the script keeps count of which Macro Controls can be manipulated.
If you push button 2 twice more, button 2 should go dim. That’s because the range of Macro Controls being controlled now are 13 to 16, and there can’t be more than 16 Macro Controls on a Device Rack. In the Log m1 should be 12 now.
Sign up
User registration is currently not allowed.