"Save Live Set as" deletes all Browser Tags. Does this make sense to you?

[Stefan Jantschek]

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.

[[jur]]

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...

Since your "variation" is a new .als it makes sense that you need to tag it: it didn't exist before.
But maybe you're talking about the "parent .als" losing its tag?

[Stefan Jantschek]

"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"?

There might be changes that might affect certain tags.
But just delete all of them?
I know it´s controversial, that´s why I am asking for opinions.

*S.

[[jur]]

Ok you're working on a variation within the same project, but still, you're creating a new .als.
You could make a feature request for something like: if an .als is tagged, then automatically tag every new .als within the same Project.

[Stefan Jantschek]

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 "EQ".

But I certainly understand that L12 Browser Tags can´t work that way.
It seems not to be a Metatag-System.
The tag-data is not saved within the file, isn´t it?

*S.

[[jur]]

Tags are saved in their « own » files.

[Angstrom]

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 make an alteration and then save it as a variation I'm always a bit cheesed off that I must re-enter all the tags. I should only be flagging the differences, the things I changed. It's quite common to load a sound, tweak it a little, then save a version. Perhaps a save modal for "keep tags" is required here (similar to the "move samples" dialog when saving a sample based instrument)

[Stefan Jantschek]

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 make an alteration and then save it as a variation I'm always a bit cheesed off that I must re-enter all the tags. I should only be flagging the differences, the things I changed. It's quite common to load a sound, tweak it a little, then save a version. Perhaps a save modal for "keep tags" is required here (similar to the "move samples" dialog when saving a sample based instrument)

Well explained.

Exactly the way I see it, too.

Thanks!

[Angstrom]

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

[jonljacobi]

Tags should be persistent.

[Stefan Jantschek]

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
here at HQ Berlin.

[Street Spirit]

Yeah that's just hilarious

[Stefan Jantschek]

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.