Post Reply 
Multiple Instances (Encouraging Feature Development:)
13-11-2015, 18:08 (This post was last modified: 13-11-2015 18:19 by Oliviander.)
Post: #16
RE: Multiple Instances (Encouraging Feature Development:)
(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
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
RE: Multiple Instances (Encouraging Feature Development:) - Oliviander - 13-11-2015 18:08

Forum Jump:


User(s) browsing this thread: 1 Guest(s)