Ableton Forum

Keep us posted.

Hey all. Does this still work as expected? I’m on the latest version and when I try to select two tracks I don’t get any visual representation, nor do I get the tracks being grouped. Only the track where I entered the grouping menu gets put in the group.


Same for me... I can't group tracks ...

Please make sure to report to Support, thx.

Mmmhh, interesting one, I didn't notice (or maybe forgot?) about that change.
I'll ask around.
Isn't there any Theme that suits your needs?

I don’t want to sound rude or like I’m lacking empathy, but a DAW is just a very specific type of files manager. It’s as dumb as any Finder/Explorer… If the user isn’t aware of how it’s working, the computer won’t do the work for you.
I’m not saying the technology is too dumb, I even have the ...

Here's the link to Support.

Nice one Rivanni.

Nope.

silicon1138 wrote: ↑

Tue Jun 03, 2025 12:07 pm

Is the main data wheel meant to feel as rigid as the 8 encoders?

No, it is looser. But it shouldn't feel loose to a point where you're wondering if something's wrong.

FYI, that's documented here.

Thanks!

dontfret wrote: ↑

Wed May 28, 2025 3:56 pm

I have verified that this behavior does consistently occur when moving clips in Note that are shared from Move in the cloud.

Hmm, interesting. Sounds like a bug then.
Did you already report to Support?

I'm colorblind so I can't judge from your picture.
But, the currently selected/playing clips use a different color VS the track's color. Are you sure that's not what you're seeing here?

ianstudio wrote: ↑

Tue May 27, 2025 12:16 pm

so would 'guess' it is related to certain plugins.

Mainly to the number of plugins afaik. I think the upcoming L12.2 might offer some improvements in this area, but my memory might be wrong. Worth checking the beta release notes.

There is a "Fixed an issue with inconsistent fades when Arrangement loop would coincide with a playing Session clip loop" listed in the beta 12.2b14 Release Notes, seems it could be this issue

I have tested in Live 12.2b18 and it does not fix the issue. That note did look promising though ...