Time Field rejects values from 60:00 minutes onwards

[miranbehluli]

Hi Roy!

As you can see in this recording, as soon as the timer hits 60:00 and onwards, it rejects the value.

Recording.2026-10-28.181545.mp4

Any ideas?

[royshil]

Hi Miran, thanks for the clear recording!

The cause is the Time field's Format. The Time mm:ss preset is ^[0-5]?\d:[0-5]\d$, which only allows minutes 0–59 because it was written for countdown clocks (basketball, hockey). From 60:00 on, the reading no longer matches the format, so ScoreSight rejects it, and the outputs keep the last good value (59:59).

Workaround for now: select the Time field, choose Custom in Format and enter:

^\d{1,3}:[0-5]\d$

That accepts 0:00 to 999:59, so the second half and extra time pass. It still needs the colon and seconds 00–59, so misreads are still filtered out. The Soccer game tracking already handles clocks past 60 minutes, so you don't need to change anything else.

The preset should work for soccer out of the box. I'll widen it in an upcoming version, and existing setups will be updated automatically.

[miranbehluli]

Thanks for the clarification, Roy.

I tried using the Custom Format and it works.

As for choosing "Soccer" as the Sport, and using mm:ss format, it doesn't work. Am I missing something?

Using the custom format is a bit of a workaround and I'm planning a Tutorial video about the whole setup for ScoreSight + overlays.uno and this adds another layer of complexity to the whole thing.
I will think about it some more.

Thanks.
Miran

[royshil]

Glad the Custom format works!

You're not missing anything. My earlier sentence was misleading: choosing Soccer as the Sport doesn't change the Time field's Format. The Format is checked first, on every reading. With Time mm:ss it rejects 62:43 before the Soccer tracking ever sees the value (that's the ⚠ next to '62:43' in your screenshot). I only meant that the Soccer tracking itself has no 59-minute limit.

I agree that the Custom format is one step too many for a tutorial. I'll fix the presets themselves: Time mm:ss (and Time MM:ss and ss.m, the default for the Time field) will accept minutes past 59, so soccer clocks work without a Custom format. Setups that use those presets today will be updated automatically. Since the overlays.uno tutorial is on hold anyway (#162), it can show the default Time field once that version is out.

[miranbehluli]

I see. Will keep an eye out on the new update, so I can try to see if it works again with a regular mm:ss format.

Thank you!

[royshil]

This is out in ScoreSight 0.4.3. The Time formats with minutes (Time mm:ss.d, the Time field's default, Time mm:ss or ss:d and Time mm:ss) now accept minutes past 59 (62:43, 90:00, 120:00), so a soccer clock works without a Custom format.

Boxes that use those formats are updated once when you open 0.4.3. Your Custom format is kept, so to go back to a regular preset, pick Format > Time mm:ss (or the default) on the Time box. On Windows, an installed ScoreSight offers Update now at startup.

[miranbehluli]

Thank you for the update!
I will test it soon and let you know in case I find any issues.