Ableton Forum

If it behaves like this without Playback being active, it is the expected behavior.

Really?
You expect that your complex arrangement changes from i.e. 130 to 89.50 bpm just because you
stopped playback before clicking on Capture Midi?
I do not expect that, honestly.
And to find back my original ...

Manual:
"If playback is not running and there are no existing clips in the set , Capture MIDI analyzes the average tempo of the captured MIDI and adjusts Live's tempo once the Capture MIDI button is pressed."

That does not work well.

The tempo of my whole set does randomly change after clicking ...

My Assumtion / My Vision:

Multi-Touch-Touchscreen-Contoller.

Features:

High sensitive Multi-Touch-Screen for MPE preformance
Size approx. 38 cm x 16cm to display at least a two octave full size Keyboard or 16 (!) Mixer Channels
Slim is sexy
No mechanical parts
Touchscreen-Controller-GUI ...

Angstrom wrote: ↑

Wed May 01, 2024 7:44 pm

Have you created a Centercode suggestion for this?
I had a quick look and didn't spot it.

Btw, I am not shure if Centercode suggestion is the right space
to discuss it, imo that case affects all L12 users now.

I will consider posting this suggestion here on the
Feature Wishlist board...

*S.

Have you created a Centercode suggestion for this?
I had a quick look and didn't spot it.


@Angstrom,
No, not yet.
I would respectfully let you take the lead.
Your description is more to the point than mine.
And, in general, you are my first vote for the Ableton Live Senior Browser Consultant ...

I feel that tags should persist on all derivatives unless expressly cleared or changed.

I also save my songs within a project as mysong-001.als, mysong-002.als, etc. whenever I make a substantial change to the song.

So tags should persist there.

When I load a rack , instrument or effect to ...

yes, there is a reasonable request for tagging folders.
That would do it in that certain case, imo.

My approach is more, lets say, "Permanent Tags".

I mean, an EQ, once tagged as, will always remain EQ, no matter how many different
presets I save.
Now I have to tag every saved EQ-Preset again as ...

"New" is exactly the controversial question I want to talk about.

When I load a project at a certain point of progression, do some minor tweaks
and save that project (or a copy) with a continuous version-Nr. (Tagfever V1.1.als, Tagfever V1.2.als)
could each version really be considered as "New ...

Hi there,

L12 tagging feature is fantastic imo.
It´s mainly one thing that confuses me.

If I save a variation of my set with a different name in the same project folder,
I have to re-tag that set again and again...

What do you think about it, does it make sense?

Love to hear your thougts...

*S.

Wow, finaly someone is talking about it.
Thanks!
It is bugging me for ages, mainly in Session View/Dark Themes there´s
no difference visible between disabled, deleted or empty slots.

Do we have to go the long way >Suggestion>Vote>Wait>Hope
or are there any workarounds known, theme settings etc.?
:D

I want a way of setting up a layout, saving that layout to my library and then enabling that layout with a hotkey. Each layout helps me with a different stage of my workflow...


This is something quite a lot of users would like to have.
The topic is discussed e.g. here:
https://forum.ableton.com ...

The new Tag Browser System works much better for Collections.
The previous "Collections" can be used as "Favorites" now.
And therefore, the amount of "Favorite Groups" is enough, imo.
My personal difference is:

Collections should grow over time,
Favorites should change over time.
:D

*S:

Followed Jur´s suggestion, I forwarded the topic to Centercode Forum.

I would love to get your thoughts on the topic there.

*S.

Well, I suspect by the time I get access to centercode that L12 will be released. I'm also doubtful that it will accomplish anything though. I'm not sure what leverage the accessibility expert on staff has, so I doubt random forum users can accomplish much here.

Come on Dude,
"They" ripped the ...

Definitely bring this discussion to Centercode please! Some L12 changes in this area are terrible mistakes imo, it’s a very serious topic and it needs more voices, especially since those changes are motivated by improving accessibility.

Okay, thanks Jur, I see.

"terrible mistakes" is an ...