Featured Replies
Recently Browsing 0
- No registered users viewing this page.
By using this site, you agree to our Guidelines. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. - Privacy Policy
I'm a dweeb, so I use the "05-Apr-17" date format. I believe the default is "4/5/2017" -- based upon the options in the Windows 10 "Change data formats" menu.
When you try to use CFSM (specifically when you try to parse songs) while using the former, CFSM will have a tremendously bad time and spit out a ton of "String was not recognized as a valid DateTime" errors while trying to do just about anything. I was having issues while trying to do a full rescan and while trying to repair things -- For the sake of posting the issue, I went ahead and reproduced it. A snippet of the log is included, the CDLC file is an example and it seems like just about anything CFSM tries to work with is affected.
(Also this seems to demonstrate an issue where it's trying to clean the DLC folder once for each core, which ends up taking quite a while on high core-count systems.)
Changing the date format back and then restarting the app works around the issue - the same files all process without any problems. This is occurring on v1.6.0.3, I haven't had a chance to try on the beta build yet. Let me know if there's any more info I can provide.
Edited by nhtk_oriki
added version