+- MinimServer Forum (https://forum.minimserver.com)
+-- Forum: MinimServer (/forumdisplay.php?fid=1)
+--- Forum: Music Tagging (/forumdisplay.php?fid=9)
+--- Thread: Date tag warnings when using full date in JRiver (/showthread.php?tid=935)
Pages: 1 2
RE: Date tag warnings when using full date in JRiver - dan186 - 21-12-2013 23:14
(21-12-2013 19:24)simoncn Wrote:(21-12-2013 16:56)dan186 Wrote: Hello,
I'm still having issues with this problem after upgrading to the new release. Here are the first few messages of the log:
MinimServer 0.8.1 update 12, Copyright © 2012, 2013 Simon Nash. All rights reserved.
Java™ SE Runtime Environment (build 1.6.0_22-b04)
Java HotSpot™ Client VM (build 17.1-b03, mixed mode, sharing)
Platform default charset is UTF-8
starting MinimServer
Warning: truncating incorrect value for DATE tag 2006-22-08 in file DSD/Ann Hampton Callaway/Blues in the Night/09 It's All Right with Me.dsf
Warning: truncating incorrect value for DATE tag 2006-22-08 in file DSD/Ann Hampton Callaway/Blues in the Night/12 The Glory of Love.dsf
Warning: truncating incorrect value for DATE tag 2006-22-08 in file DSD/Ann Hampton Callaway/Blues in the Night/08 Hip to Be Happy.dsf
Thanks.
These dates are not in YYYY-MM-DD format as required by the UPnP AV specification. The only solution is to edit your file tags (in this case, to 2006-08-22).
I believe the TDAT field is in the same format as described in the post above this one (see the Dead Can Dance dsf file). I continue to get the same error with that file and you replied that Minimserver is not handling the TDAT field correctly.
If the TDAT field is 2208, then MinimServer should treat this as 2006-08-22, not 2006-22-08.
Please let me know what software I can use to see the actual TDAT field and edit that field directly or I can FTP this file to you so that you could verify the TDAT field.
Thank you.
RE: Date tag warnings when using full date in JRiver - simoncn - 21-12-2013 23:39
(21-12-2013 23:14)dan186 Wrote: I believe the TDAT field is in the same format as described in the post above this one (see the Dead Can Dance dsf file). I continue to get the same error with that file and you replied that Minimserver is not handling the TDAT field correctly.
If the TDAT field is 2208, then MinimServer should treat this as 2006-08-22, not 2006-22-08.
Please let me know what software I can use to see the actual TDAT field and edit that field directly or I can FTP this file to you so that you could verify the TDAT field.
Thank you.
The problem with TDAT should be fixed in MinimServer 0.8.1. You might need to rebuild the MinimServer cache to get these values recognised correctly. The simplest way to do this is to put any dummy value in the writeAllTags field, then select Rescan from the minim icon. After the cache has been rebuilt, you can remove the dummy value from writeAllTags,
RE: Date tag warnings when using full date in JRiver - dan186 - 22-12-2013 01:28
(21-12-2013 23:39)simoncn Wrote: The problem with TDAT should be fixed in MinimServer 0.8.1. You might need to rebuild the MinimServer cache to get these values recognised correctly. The simplest way to do this is to put any dummy value in the writeAllTags field, then select Rescan from the minim icon. After the cache has been rebuilt, you can remove the dummy value from writeAllTags,
Your fix is good! Rebuilding the cache worked! Thank you very much for your help. Merry Christmas Simon.
RE: Date tag warnings when using full date in JRiver - simoncn - 28-04-2014 17:33
(21-12-2013 23:39)simoncn Wrote: The problem with TDAT should be fixed in MinimServer 0.8.1. You might need to rebuild the MinimServer cache to get these values recognised correctly. The simplest way to do this is to put any dummy value in the writeAllTags field, then select Rescan from the minim icon. After the cache has been rebuilt, you can remove the dummy value from writeAllTags,
In MinimServer update 25, there's a better way to force a full rescan without reading the cache. You can set the startupScan property to 'full' to do this. Remember to reset this property to 'true' or 'false' afterwards so you don't get a full rescan every time.