1256 /n of discnumber fails to show [#5878]

[chrisjj]

EDIT: was "V3.0.2.1131 SEVERE BUG Loss of second # of WMA PartOfSet", but loss from tag has been fixed, leaving only loss (hiding) from display.

Add/rescanning loses the slash and second number of the WMA PartOfSet tag(displayed as Disc #) from the display and editing ANY tag erases the slash and second number from the tag stored in the file.

E.g.

1 set a track's Disc # to 1/2
2 delete track from Library
3 Add/Rescan
4 See tracklist shows 1 !

This is a severe bug! It will hinder up my testing of MM3 so I hope it can be fixed soon!

[jiri]

Well, it's a little more complicated. The value you enter (i.e. '1/2') is stored in WM/PartOfSet field in WMA tag. It specifies that it can store both Disc# and Total Disc# fields separated by slash. I.e. when MM scans such a file, it shows you only '1' as Disc# and '2' isn't shown.

We have to find a way how to best handle this issue. It seems that the only really solution it to include Tottal Track# and Total Disc# fields in MM interface. I'm not personally a big fan of this approach, but it would probably prevent any further problems.

Jiri

[chrisjj]

> I.e. when MM scans such a file, it shows you only '1' as Disc# and
> '2' isn't shown. We have to find a way how to best handle this issue.

A far higher priority issue than what MM displays is that MM erases the data from the file, even when the tag being edited is a different one entirely. This needs fixing urgently, regardless of any fix to the display.

[jiri]

You are right, this will be fixed in the next release, Total Disc and Track # will be properly preserved in WMA tags.

Jiri

[chrisjj]

About the Total Disc #, that's great news - thanks.

> Total... Track # will be properly preserved in WMA tags.

I suggest this needs careful thought, since unlike PartOfSet for total disc #, the field used for track #(http://msdn2.microsoft.com/en-us/librar ... S.85).aspx) does not support total track # . I.e. n/m in TrackNumber is non-compliant, and IIUC it is not MM policy to write non-compliant tags.

[jiri]

Right, the specification doesn't explicitely describe this, but I'm sure that many people have tags in this format and thus I think it makes sense to preserve the value there.

In any case, some future update of MM should include more powerful tools for clean up of tags and then it should be easier to e.g. remove all such values, etc.

Jiri

[chrisjj]

EDIT: (loss is...)

Confirmed fixed in 3.0.2.1134. Thanks!

[chrisjj]

> It seems that the only really solution it to include
> [...] Total Disc# fields in MM interface.

Is this planned?

[jiri]

Yes, probably in MM 3.1, but it isn't definite yet.

Jiri

[chrisjj]

Excellent - thanks!

[chrisjj]

> Yes, probably in MM 3.1, but it isn't definite yet.

I find no fix made 3.1. I hope it is still planned

EDIT: And needing to make an addition to this Mantis entry but finding none exists, I have created one: http://www.ventismedia.com/mantis/view.php?id=5878

[MMuser2011]

Is this bug still open?

I see another problem:
If you edit a track with the visible disc # 2 to the value 2/2, it will be stored to id3tag DISCNUMBER as 2/2/2.

The problem:
In the Edit Window (SHIFT-ENTER on a track) you can't be sure, if the Disc# field visible as 2 is already populated with 2/2. As soon as you edit the visible value 2 to 2/2 it will be added to the final 2/2/2.

[Lowlander]

Is this bug still open?

Yes, it is set as assigned, not closed.