[FEATURE REQUESTS] Universal Remote Script for Ableton Live

Thanks for trying out the Universal Remote Script for Ableton Live. This tool has been developed given the frequent necessity of our community to have the features they are used to in their regular controllers when using their custom ones. This is the first version of the tool. If you tried it and you find that there is a feature you miss, or you have improvements ideas, comment on this topic.

We can’t promise quick further development of this tool but we want to have a clear view of what’s needed when there is a chance to upgrade it.

Please Note:

  • Read the comments to check if your idea has been previously suggested by another community member.
  • For bug reports, please post on this topic.
  • For help and troubleshooting, check/post its category.

Hello Team,

I was trying your Universal Remote Script for Ableton Live on Windows and it seems to work very well, great job.

Is it possible to control all Parameters from each Device (using 8 knobs), navigating through different Banks?
If yes, how could I configurate the Script so that I can set buttons to different Banks?

Thank you!
Dfasf

2 Likes

Hello @daniel.fasf, welcome to the forum! and sorry for the late response.

I was trying your Universal Remote Script for Ableton Live on Windows and it seems to work very well, great job.

Cool, thanks!

Is it possible to control all Parameters from each Device (using 8 knobs), navigating through different Banks?
If yes, how could I configurate the Script so that I can set buttons to different Banks?

Nop, sadly it’s not possible on the current version. I’ll add it to the “nice to have” list.

If it is essential for your work I’ll suggest taking a look at Remotify, it’s commercial software so it comes at a cost but it’s possible to archive what you are looking for.

i’m trying to map 12 audio tracks within groups. 3 groups are inside a supergroup.


it seems like if i use the yaeltex universal remote script the volume fader for track 1 is only going to control the “supergroup” called “SAMPLES” and not “1 kicks.”

is this correct?

Yo Skott!

it seems like if i use the yaeltex universal remote script the volume fader for track 1 is only going to control the “supergroup” called “SAMPLES” and not “1 kicks.”

is this correct?

Yes, that is correct.
The script will simply count tracks from left to right, no matter if they are groups or subgroups.

You could:

Hi there
Just set up most of the controller:) works great!

Was wondering if it would be possible to have Device Parameters on the Send (A & B) and Master Tracks.

Also, would be great to one day add some extra scenes in the session box. Maybe using a second midi channel?

Also, how do I set up the LEDs to show which clips are playing. The APC40 MkII for example had it green with oscillating brightness when a clip was playing. The actual colour of the playing clip rather than always green would be even better.

Another ‘nice to have’, would be more control over the LED brightness. Especially if Value to Colour could have a min. value -> low intensity option.

There doesn’t seem to be a functional value to colour feature at all for mute and solo clips. I cannot see which clips are muted or soloed on the controller.

Thanks,
Pascal

Hi @pascal.bauer
Welcome to the forum,

Master track and sends is already supported using the “SELECTED TRACK
DEVICES PARAMETERS” feature. I’ll add the request for specific devices control on sends and master sends to the nice-to-have list.

Can you expand on this? Do you mean more than the current 8?

Noted. We support the option in color-fixed mode, but not on value to color option.

It’s not currently possible, thanks for the suggestion though.

If you want to dive deeper into the coloring of the script, open the Map.py file, located inside the script folder, with a text editor, and search for the line: class YAELTEXColors:
You will find something like this:

class Session:
	StopClipDisabled = MonoColor(0)
	StopClipTriggered = MonoColor(75)
	StopClip = MonoColor(22)
	Scene = MonoColor(118)
	NoScene = MonoColor(0)
	SceneTriggered = MonoColor(57)
	ClipTriggeredPlay = MonoColor(7)
	ClipTriggeredRecord = MonoColor(5)
	RecordButton = MonoColor(121)
	ClipEmpty = MonoColor(0)
	ClipStopped = MonoColor(120)
	ClipStarted = MonoColor(43)
	ClipRecording = MonoColor(109)
	NavigationButtonOn = MonoColor(102)
	NavigationButtonOff = MonoColor(2)
	ZoomOn = MonoColor(36)
	ZoomOff = MonoColor(0)
	SelectedClipLaunch = MonoColor(8)
	SelectedSceneLaunch = MonoColor(88)  

Change the numbers to the color of your liking,
This is the value-to-color table

Be careful not to change the formatting of the text, save the changes, and restart Ableton.

Mm, yes. Mutes and solos are track states, but as you suggested it would be cool to see that reflected on clips, added to the nice-to-have list.

Hey thanks for the quick and detailed response!!

yeah exactly! More than 8. (My controller has 10 haha so not a huge loss, but a bit of a shame)

I will try this! thanks for the suport :slight_smile:

Maybe I’m doing something wrong on my end, but its not lighting up when in Solo or Unmuted state like in the YURS video (nor red when armed). SelectedOn and Off works fine, but Solo, Arm and Mute doesn’t. The commands also work and are reflected in Live.

Check your configuration in Kilowhat; it sounds like some of the buttons are not set to value to color.