Activate/Deactivate tracks

Feature Requests
1

Thank you Leo, This new version is amazing!!! Is it possible to create a “activate/Deactivate” track command.

This woulld allow very large projects with multiple songs. If possible we could create a command to activate songs in the song list and all other tracks would remain inactive, or create a midi command before and after each song to activate/deactivate.

I have seen some conversation on this through max for live but i haven’t tried it but if possible throguh ableset, this would be amazing and really help again with larger project files

2

Hey Nick,

Thanks again for the great feedback — really glad you’re enjoying the new version :raising_hands:

Regarding your idea of an “activate / deactivate track” command:

AbleSet itself doesn’t natively enable/disable Live tracks (since that’s outside of its direct control scope at the moment), but you can absolutely achieve this by controlling Live via AbletonOSC and triggering those OSC messages from AbleSet.

AbletonOSC exposes full track control, including:

/live/track/set/mute <track_index> <0|1>
/live/track/set/arm  <track_index> <0|1>
/live/track/set/solo <track_index> <0|1>

You can read more about this here.

So your architecture would look like this:

  1. AbleSet (Canvas button, MIDI mapping → Custom OSC, or +OSC track clip)
  2. AbleSet sends OSC to AbletonOSC (port 11000)
  3. AbletonOSC sets mute/arm/solo state per track index

For example, from a +OSC track in AbleSet you could send:

127.0.0.1:11000/live/track/set/mute 5 1;
127.0.0.1:11000/live/track/set/mute 6 1;
127.0.0.1:11000/live/track/set/mute 7 1;

And then another clip at the next song to unmute the relevant tracks.

Let me know if this approach would work for your use case!

3

Thank you,

I tried this and seem to have the general set up working however I cannot find any script that will activate or deactivate a clip, only to mute/unmute or arm tracks.

I am hoping to deactivate tracks to safe my disk space to allow for more songs in the file.

I have had overload issues live and the only way I have found to avoid this is by deactivating the tracks, however this is cumbersome and also defeats the purpose of having a large data base at my disposal.

Please advise

Thank you

4

Hey Nick,

Just to make sure I understand correctly:

When you say “deactivate tracks”, are you referring to deactivating individual devices / plugins inside the track, freezing tracks, or something else entirely?

Live doesn’t actually have a true “deactivate track” function — only mute/arm at track level. The only thing that really reduces CPU load is disabling devices.

If you could clarify exactly what you’re manually doing right now to avoid overload, we can look into the cleanest way to automate it.

I’m looking forward to your reply!

5

Yes, So I am running tracks in arrangement view and running a fairly large project of about 80+ songs. I am having Disk overload issues and i have found that if I deactivate the individual tracks (Maybe proper to say clips?) and only have limited tracks/clips activated then this solves the issue. So 3 options I see available are

  1. Only have clips/tracks activated for the songs i plan to do in the set - however a mid set last add on would be cumbersome requiring me to highlight appropriate tracks and activate them
  2. Structure my system around a multiproj set up - I tried this and it was a bit slow and not the best workflow for us
  3. Figure out how to automate activating and deactivating tracks. This would allow essentially an unlimited amount of songs in a single file.

Hope this explanation helps explain the situation and what i am hoping to solve

6

Hey @Psnick,

Thanks for the detailed explanation.

It would be great to understand a bit more about how the session is configured. A few things that could be helpful to check:

• Are all your audio files rendered with the same sample rate and bit depth?
• Are the clips warped or playing unwarped?
• Are any of them loaded into RAM?
• Is the session extremely zoomed out in Arrangement View while playing? In very large sessions this can sometimes impact performance because Live has to render a lot of UI elements.
• Are the backing tracks coming from the same disk as the Live project?
• Are you using CPU hungry VSTs that maybe don’t need to be running for every song?

If you’d like, you could also send a log package so we can take a closer look at how the project is set up. That often makes it much easier to spot potential bottlenecks.

You can create a log package by opening AbleSet’s status window, clicking the settings icon on the top right, and then selecting “Create Log Package” .
Please make sure to include your project files as well (just the.als files, no audio needed)
To send the files, you can upload them to AbleSet’s support inbox.

Happy to dig into this with you and see what might be causing the dropouts.

I’m looking forward to your reply!