Multiple Instances (Encouraging Feature Development:)

[Oliviander]

(09-11-2015 22:21)simoncn Wrote:  This is an interesting and creative approach for how to select the combination of genre and composer/artist in a single operation.

I have considered your request very carefully, trying to think of a more "normal" situation where the proposed new feature would be useful. I haven't been able to come with one, so I won't be adding this feature at the present time.

Fortunately, there is a way for you to do what you want without the new feature. You can change your tag update file to the following:

@ALBUM_CATEGORY=Klassik
+KLASSIK=1
+JAZZINTERPRET=0
+POPINTERPRET=0

@ALBUM_CATEGORY=Jazz
+JAZZ=1
+KLASSIKKOMPONIST=0
+KLASSIKINTERPRET=0
+POPINTERPRET=0

@ALBUM_CATEGORY=Pop
+POP=1
+KLASSIKKOMPONIST=0
+KLASSIKINTERPRET=0
+JAZZINTERPRET=0

Your tagValue settings should be as foolows:

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

The only problem with this is that the menu for Jazzinterpret (etc.) will start with a 0 entry because 0 is sorted before alphabetic characters in the MinimServer collation order. To move this entry to the end of the list, you can change the 0 to any Unicode character that sorts after alphabetic characters. The Unicode character U+02CD (low macron) should be suitable.

Hi Simon
THX very much for this clue

[Oliviander]

Hi Simon,
your clue [THX again] is working but with a limitation
as I told you my exanple was a simplification
therefore I have some more ALBUM_Categories
and some Albums have two exisiting entries.
In such a case they would get a zero as a TagValue
for any searchpath and would therefore would be hidden.
im any path.

I am aware that I can circumvent this by reversing the
the process:
Setting the TagValue to zero for all Tags and all Tracks used this way.
Then deleting the Tag for all matches of the Tracks.

But to do that I have to set the TagValue of the used Tags
to zero for all tracks in the beginning.

I haven't tried it but I if I am understanding your manual right.
you can't just add a tag for all tracks in the tagUpdatefile
without using a match condition.

Therefore I should have at least one Tag in my collection,
that has the same value for all tracks.

In the Moment I haven't any but before adding one to all my tracks
maybe you have an idea how I can trick MinimS to do it
without that need for such a nonsense tagvalue in my collection.

--> This would not be needed if there was a modified replace
TagValue function as suggested.

Thinking about that I have another questionable idea:
Minimserver could add an internal tag to the tracks
it's value simply displaying the source (the contentDir) value
(either in cleartext or simply an increasing number for the lines)
when reading the files. By using this value as a condition
I could even better bend the limits.

[simoncn]

(12-11-2015 08:31)Oliviander Wrote:  Hi Simon,
your clue [THX again] is working but with a limitation
as I told you my exanple was a simplification
therefore I have some more ALBUM_Categories
and some Albums have two exisiting entries.
In such a case they would get a zero as a TagValue
for any searchpath and would therefore would be hidden.
im any path.

I'm sorry but I don't understand this. Please can you post a specific example of this case.

[Oliviander]

(12-11-2015 13:21)simoncn Wrote:  Please can you post a specific example of this case.

I wanted to point out the following problem:

Assume You have a Tag Album-Category, which can have only
the following TagValues:

Jazz or Pop or Both of them

As you pointed out you would have the TagUpdate file

@ALBUM_CATEGORY=Jazz
+JAZZ=1
+POPINTERPRET=0

@ALBUM_CATEGORY=Pop
+POP=1
+JAZZINTERPRET=0

TagValue Settings:

Jazzinterpret.default={ARTIST_SORT},
Popinterpret.default={ARTIST_SORT}

It works for all tracks that have either Pop or Jazz
as the ALBUM_CATEGORY Tag.

But a track that has both entries
would neither show up under Jazzinterpret nor under Popinterpret.

If it would be possible to set the TagUpdate file to

+POPINTERPRET=0
+JAZZINTERPRET=0

@ALBUM_CATEGORY=Jazz
+JAZZ=1

@ALBUM_CATEGORY=Jazz
&JAZZINTERPRET=0
-JAZZINTERPRET=0

@ALBUM_CATEGORY=Pop
+POP=1

@ALBUM_CATEGORY=Pop
&POPINTERPRET=0
-POPINTERPRET=0

with the same TagValue settings you would get the
correct output for the Tracks that have both
ALBUM_CATEGORY Tagvalues: Jazz and POP

As I understand a condition for
the first to lines is mandatory so I would need a DummyTag
that has the same value for all tracks to make it:

@DUMMY=1
+POPINTERPRET=0
+JAZZINTERPRET=0

@ALBUM_CATEGORY=Jazz
+JAZZ=1

@ALBUM_CATEGORY=Jazz
&JAZZINTERPRET=0
-JAZZINTERPRET=0

@ALBUM_CATEGORY=Pop
+POP=1

@ALBUM_CATEGORY=Pop
&POPINTERPRET=0
-POPINTERPRET=0

Or is it possible
to use

@DUMMY=
+POPINTERPRET=0
+JAZZINTERPRET=0

and just add the non existent DUMMY tag to the
itemTags section
or is there another solution ?

[simoncn]

(13-11-2015 08:09)Oliviander Wrote:  or is there another solution ?

Thanks for explaining this.

I could add support for an "and not" (^) match condition in the tagUpdate file. You would use this as follows:

@ALBUM_CATEGORY=Jazz
&ALBUM_CATEGORY=Pop
+JAZZ=1
+POP=1

@ALBUM_CATEGORY=Jazz
^ALBUM_CATEGORY=Pop
+JAZZ=1
+POPINTERPRET=0

@ALBUM_CATEGORY=Pop
^ALBUM_CATEGORY=Jazz
+POP=1
+JAZZINTERPRET=0

Would this enable you to do everything you want?

[Oliviander]

(13-11-2015 13:57)simoncn Wrote:  

(13-11-2015 08:09)Oliviander Wrote:  or is there another solution ?

Thanks for explaining this.

I could add support for an "and not" (^) match condition in the tagUpdate file. You would use this as follows:

@ALBUM_CATEGORY=Jazz
&ALBUM_CATEGORY=Pop
+JAZZ=1
+POP=1

@ALBUM_CATEGORY=Jazz
^ALBUM_CATEGORY=Pop
+JAZZ=1
+POPINTERPRET=0

@ALBUM_CATEGORY=Pop
^ALBUM_CATEGORY=Jazz
+POP=1
+JAZZINTERPRET=0

Would this enable you to do everything you want?

Hi Simon,
thx for your suggestion.
that might work, but in my case it would end in a very confusing
TagUpdate file :
In reality I have 8 ALBUM_Category possibilities and I can think of cases
with 4 Entries in one track.
So you would have to make Entries for way too many condition combinations.

I would prefer if it were possible to
begin an update group without a condition

Maybe you could define
a single @ without a condition as always true

So I could make my Tagupdate file like

@
+POPINTERPRET=0
+JAZZINTERPRET=0

@ALBUM_CATEGORY=Jazz
+JAZZ=1

@ALBUM_CATEGORY=Jazz
&JAZZINTERPRET=0
-JAZZINTERPRET=0

@ALBUM_CATEGORY=Pop
+POP=1

@ALBUM_CATEGORY=Pop
&POPINTERPRET=0
-POPINTERPRET=0

This would even be a good addition to your suggestion and expand the "and not "
to a simple "not":

@
^ALBUM_CATGEGORY=Klassik

[simoncn]

My apologies for the delay in responding.

The tagUpdate facility isn't designed to make the tag changes that you want to make. Tag updating has always been activated by an exact match for a specific tag name and value and I don't think it woiuld be a good idea to change this by adding a new operation to match all items.

The tagValue options are already complex and there is a difficult balance in deciding whether adding a new capability in this area justifies the extra complexity. The use case that you have described is very unusual and is effectively a means of "bending the rules" as you have said in an earlier post. As such, I am not convinced that this use case justifies adding a new tagValue option that would only be used for rule-bending purposes.

I have tried hard to think of some other way to do what you want using existing MinimServer capabilities but I haven't been able to come up with anything suitable. Taking a step back to the problem you are trying to solve, you want to use MinimServer to create some additional tags (e.g., JazzInterpret) that aren't in your library. The usual way to add extra tags to the library is to use a tagging program to do this. Some tagging programs such as Mp3tag can perform bulk scripting actions using regular expressions and it is likely that this approach would provide sufficient flexibility to add the tags that you want.

[Oliviander]

(21-11-2015 17:16)simoncn Wrote:  My apologies for the delay in responding.

The tagUpdate facility isn't designed to make the tag changes that you want to make. Tag updating has always been activated by an exact match for a specific tag name and value and I don't think it woiuld be a good idea to change this by adding a new operation to match all items.

The tagValue options are already complex and there is a difficult balance in deciding whether adding a new capability in this area justifies the extra complexity. The use case that you have described is very unusual and is effectively a means of "bending the rules" as you have said in an earlier post. As such, I am not convinced that this use case justifies adding a new tagValue option that would only be used for rule-bending purposes.

I have tried hard to think of some other way to do what you want using existing MinimServer capabilities but I haven't been able to come up with anything suitable. Taking a step back to the problem you are trying to solve, you want to use MinimServer to create some additional tags (e.g., JazzInterpret) that aren't in your library. The usual way to add extra tags to the library is to use a tagging program to do this. Some tagging programs such as Mp3tag can perform bulk scripting actions using regular expressions and it is likely that this approach would provide sufficient flexibility to add the tags that you want.

THX for your detailed opinion - I will use minimS anyway