by Mizery_Made » Fri Oct 30, 2009 11:32 pm
It's one of "those days," so forgive me if I come across a little slow. However, what I gather is anytime you have something other than a number in the Track # field, in build 1282, those files always show as unsynchronized. If that is what you're implying, then I don't think the issue is that broad because I just ran this node and came up empty. I have a few cases of "##.#" and one case of "##+##" and neither of these displayed in the node.
I just edited a file to contain "16/19" and re-ran the node.
This file comes up, so it looks as those it's specific to "#/#" and not any/all alphanumeric combinations. There's already reported issues regarding the behavior of MM when it comes to these values, so it might be related to them. (only one I can remember off the top of my head is:
5878: MM hides the /n part (disc qty) of WM/PartOfSet and ID3 TPOS (discnumber))
It's one of "those days," so forgive me if I come across a little slow. However, what I gather is anytime you have something other than a number in the Track # field, in build 1282, those files always show as unsynchronized. If that is what you're implying, then I don't think the issue is that broad because I just ran this node and came up empty. I have a few cases of "##.#" and one case of "##+##" and neither of these displayed in the node.
I just edited a file to contain "16/19" and re-ran the node. [i]This[/i] file comes up, so it looks as those it's specific to "#/#" and not any/all alphanumeric combinations. There's already reported issues regarding the behavior of MM when it comes to these values, so it might be related to them. (only one I can remember off the top of my head is: [url=http://www.ventismedia.com/mantis/view.php?id=5878]5878: MM hides the /n part (disc qty) of WM/PartOfSet and ID3 TPOS (discnumber)[/url])