View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0008184 | MMW v4 | Properties/Auto-Tools | public | 2011-07-24 12:17 | 2011-08-10 16:59 |
Reporter | Assigned To | ||||
Priority | urgent | Severity | minor | Reproducibility | always |
Status | closed | Resolution | fixed | ||
OS | Windows x64 | OS Version | 7 | ||
Product Version | 4.0 | ||||
Target Version | 4.0 | Fixed in Version | 4.0 | ||
Summary | 0008184: Auto Organize Drops Leading Zero (regression) | ||||
Description | As reported here, when auto organizing it drops the leading zero of the season and episode field for tv files:http://www.mediamonkey.com/forum/viewtopic.php?f=6&t=59526 | ||||
Steps To Reproduce | Add a zero in the season and/or episode field run the autoorganize and you will notice the leading zero is not a part of the mask | ||||
Tags | No tags attached. | ||||
Fixed in build | 1415 | ||||
|
<Season#:2> and <Episode#:2> need to be used to get leading zero. |
|
Resolving pending user clarification. |
|
Actually, I can confirm this issue. It previously worked as expected in build 1408, and I believe it's a regression introduced by another fix in 1409 (http://www.ventismedia.com/mantis/view.php?id=6680#c26870 being the fix in question). When using the "<Track#>" mask, if you have "05" in the field then it will retain the leading zero and output the field "as-is." That's how it works in 3.2 as well. However, when using "<Season#>" with "05" in the field, it's only outputting "5", which is incorrect based on how "<Track#>" functions. I believe you may be misinterpreting the reported problem as the user having "5" in the field, and expecting "<Season#>" to output "05" in which case you would be correct in that "<Season#:2>" will _add_ the leading zero. Though, "<Season#>" should not be _removing_ an already present leading zero. The previously reported problem that was fixed was that "<Season#>" was _forcing_ a leading zero, apparently incorrectly outputing "5" as "05" (functioning as if it were "<Season#:2>" which indeed would be incorrect) however in fixing it, it now drops the leading zero from the field if it's already present which is incorrect. Mind you, I've used "<Season#>" in my testing, but "<Episode#>" is likely suffering similarly seeing as it too was reported by the user. |
|
Fixed in build 1415. |
|
Verified in 1415 |