Time Sync

[ainaars]

Can't figure out what's wrong with rds clock after move to winter time.
Here in Latvia winter time is from last sunday of october (this year - 25.10.2026 at 03:00) but some other applications (for example samsung MagicInfo TV management) thinks that winter time will be from last saturday of october (this year - 31.10.2026 a 03:00). So, there is no one universal standart...
Looks like Magic RDS 4 thinks wrong (for my region), because every time I correct clock it jumps back one hour ahead (usually within a hour).
Does MagicRDS4 only looks on PC system clock or it calculate its own time based on somewhere defined [wrong] dst schedule?

Server clock is correct. Time zone correct (utc +02:00 Riga).
In MagicRDS >
Extensions > General > Clock Sync. = Enabled.
Extensions > CT Encoder = Off. (if ON - then immediately time is incorrect +1h)
Device setup > Date and Time > Local time offset = Auto.
Device setup > Date and Time > Show PC Time = in long term doesn't change anything.

I can manually set correct time, click [Test] [Apply] [Read] - it is correct. but not for very long time.

What is wrong and ho to correct RDS clock?

[Jan]

What Magic RDS version do you currently use?

[ainaars]

Version 4.3.2
Help > Check for Updates > ... Up to date.
RDS encoder P164

[Jan]

Thanks for the report. Yes, I’ve found a bug in this Magic RDS version that causes this behavior.

For measuring time intervals, we switched from real-time to a system (monotonic) timer for certain functions to avoid issues with leap seconds or transitions between daylight saving time and standard time. Unfortunately, the time-keeping mechanism for RDS encoders is now also tied to this monotonic timer, which is why it completely ignores the transition.

You can resolve this by simply restarting the application. We will fix this later today, so everything should go smoothly when the next transition occurs in the spring