INTERACT FORUM
Mac => JRiver Media Center 32 for Mac => Topic started by: kschiefer on March 30, 2024, 03:46:29 pm
-
Hello,
for the past couple of months I've been experiencing a strange issue with the way times are displayed in MC 31 and 32. I'm located in Germany, but I have set the language in MC to English, and while the date in e.g. the Last Played fields is formatted as DD/MM/YYYY, the time is formatted in the American 12 hour format instead of the European 24 hour format. In System Prefences, the format is set to 24 hours, but MC doesn't appear to adhere to that.
-
MC uses the system settings for date/time display.
Running Windows 10 here, I used, in Windows, "Settings > Time & Language > Region > Change data formats" to switch between 24 and 12 hour time display. The change is reflected inside MC, immediately.
Double check your Windows 'Short Time' and 'Long Time' settings to ensure they're both set to 24 hours.
-
Hi Marco,
Mac user here, so the Windows time and date settings don't apply, but, as I said already, in the Mac System Preferences the slider for "24-hour time" is activated. It's just that MC doesn't seem to acknowledge that.
-
Mac, doh! I usually pay close attention to critical info such as that, apologies for the wasted time. I know nothing of the world of Macs. Someone who does will chime in soon though...
-
Bob would probably know the answer to that. If MC doesn't use the system settings for time/date display on Mac chances are it doesn't work in Linux either.
-
Maybe a regression, v27 already had this issue:
https://yabb.jriver.com/interact/index.php/topic,129261.msg900984.html#msg900984
-
Unlike on Windows it looks like MC on the Mac does not use/recognise the OS 24 Hour setting for Time
-
Maybe a regression, v27 already had this issue:
https://yabb.jriver.com/interact/index.php/topic,129261.msg900984.html#msg900984
Yeah, I had the same issue back then already, but it was fixed after a while. It only reverted back to the current behavior a couple of months ago.
-
When the next build comes out, give that a try. I think it should be fixed (at least from my testing).
All 3 platforms have very different code BTW.
-
I'm happy to report that the current build (32.0.38) has fixed it for me. :)