Multiple Instances (Encouraging Feature Development:)

[Oliviander]

(05-11-2015 17:01)simoncn Wrote:  

(02-11-2015 23:43)simoncn Wrote:  I am open to providing a shortcut capability that would enable a tag choice to be autoselected based on matching a user-specified value such as "true" or "1". My intuition is that this shouldn't be too difficult to implement but I won't know until I start work on it.

This feature is available now in update 70.

Hi Simon,
I love this feature. Thank you very much.


That you neither plan to support predefined searchin paths
nor multiple instances is a pity IMO, but it is your choice and I respect that.
[Either of them would help to accelerate and tighten the selection prozess]


But maybe you could implement the following little feature.
With this I could at least come to a point where I
(and especially my wife) would be comfortable with.
Today I experimented to simulate a simple quickselect feature with existing MinimS mechanics - and I came close but one option didn't work
as I expected :

The TagValue option Replace doesn't only replace a TagValue
with a new one but also creates one if the Tag was not existing before.

If you could add a TagValue method that works exactly like replace but only kicks in if there is at least one existing value for the selected Tag
I would be where I want to be.

So what did I try (the following is a simplified example):

In my files I have a Tag named ALBUM_CATEGORY which only can have
Specific values: Klassik - Jazz - Pop

I created a TagUpdate file:

@ALBUM_CATEGORY=Klassik
+KLASSIK=1
+KLASSIKKOMPONIST=1
+KLASSIKINTERPRET=1

@ALBUM_CATEGORY=Jazz
+JAZZ=1
+JAZZINTERPRET=1

@ALBUM_CATEGORY=Pop
+POP=1
+POPINTERPRET=1

Then I tried to replace the some of these tags with actual values

Klassikkomponist.replace={COMPOSER_SORT},
Klassikinterpret.replace={ARTIST_SORT},
Jazzinterpret.replace={ARTIST_SORT},
Popinterpret.replace={ARTIST_SORT},


indexTags are (thx to your new feature):

Klassik=1, KlassikKomponist, KlassikInterpret, Jazz=1, JazzInterpret, Pop=1, PopInterpret, .....


As you can see This would have worked perfectly if the
TagValue replace option would not create tags where none existed before
and would only replace the existing "1" entries.

I assume it shouldn't be very difficult to add another method to the
TagValue section that behaves like suggested.
This would make me very happy



(and maybe the possiblity to suppress the [unknown] entry for
some selections. Maybe an entry in the indexTags like

Klassikinterpret<>[unknown]

That would be obviously nice for these
selections but, I admit, one can still live without it)


What do you think of this idea ?

THX for the greatest Musikserver there is