Severe BUG in - aliasTags -

[Oliviander]

Hi Simon,
i just discovered a malfunction of the aliasTags property
and it took me quite some time to pin it down

I just tried a very easy aliasing:

aliasTags = WORK:Album

I think you can see what I wanted to do

but when I viewed the resulting Albums list
some Albums were either only renamed or
splitted in several albums and renamed just as antcipated.

But some were not, they retained their original album Tag
and therefore were of course never splitted.

It took me some time to find out in which cases it works
and in which cases it doesn't work:

It depends on the order the tags appear in the file header.
In all cases where the WORK tag appeared before the original album Tag
the aliasing worked perfectly.

But it didn't in those cases where the album tag appeared before
the work tag.

I can only assume that the tag is already read from the file
when the aliasing should take place and then it stops the aliasing
from working correctly.

[simoncn]

(17-04-2013 20:56)Oliviander Wrote:  I can only assume that the tag is already read from the file
when the aliasing should take place and then it stops the aliasing
from working correctly.

Edit: My original response was incorrect. I think there may be a bug here. I'll post another update soon.

[simoncn]

(17-04-2013 21:09)simoncn Wrote:  

(17-04-2013 20:56)Oliviander Wrote:  I can only assume that the tag is already read from the file
when the aliasing should take place and then it stops the aliasing
from working correctly.

Edit: My original response was incorrect. I think there may be a bug here. I'll post another update soon.

Have you checked the log for warning messages? Are there any messages that say:

Warning: conflicting ALBUM tag value xxxxx ignored for file yyyyy

[Oliviander]

(17-04-2013 21:23)simoncn Wrote:  Have you checked the log for warning messages? Are there any messages that say:

Warning: conflicting ALBUM tag value xxxxx ignored for file yyyyy

Hah! I didn't think of that, because with a few testfiles
MinS it starts up pretty fast.

Yes you are right, there is exactly one conflict warning for each file.

The second value is always ignored either the album or the work
tag depending on the order

I just could solve the problem with an additional album:nil entry:

Now my entry says

aliasTags = WORK:Album, Album:nil

and no more error in log and everything is responding correctly