- Author royshilkrot
- Creation date
-
- Tags
- ocr scoreboard
A phone as the camera, a smoother preview, and clock fixes from the
Discussions: soccer clocks past 59 minutes, and clocks whose colon isn't
read while they're stopped.
Added
- Phone camera. A new source: an iPhone or Android phone sends its camera to ScoreSight over Wi-Fi, from its browser, with no app to install. Choose Phone camera in the Source list and scan the QR code the picture shows. ScoreSight serves the phone's page over HTTPS (phone browsers open the camera only on a secure page) on the port after the HTTP server's, with a certificate of its own, so the phone warns once that the connection isn't private. The phone sends a picture per detection; while none comes, the boxes aren't read (Video Sources: Phone camera).
- Smooth preview. View > Smooth preview refreshes the picture in the viewer up to 20 times a second (15 for a 30 fps source) instead of about once, so a running clock moves like video. It uses more CPU; the readings and the outputs don't change. Off by default (#165).
Fixed
- A clock read without its colon. Some boards light a third dot in the clock's colon while the clock is stopped, and the OCR then read 2:36 as 236, which the Time format rejected, so the outputs kept the last value until the clock ran again. When a reading is only digits and fails the box's Format, ScoreSight now puts back the separator of the box's last good reading at the same place (2:38, then 236 is 2:36; 23.6, then 225 is 22.5), if the Format then takes it (#167, Box Settings: Format).
- Soccer clocks past 59 minutes. The Time formats with minutes (Time mm:ss.d, the Time field's default, Time mm:ss or ss:d and Time mm:ss) took minutes 0–59, so a clock that counts up was rejected from 60:00 on and the outputs stayed at 59:59. They now take up to three digits of minutes (90:00, 120:00). Boxes that use those formats are updated once when you open this version; a custom format is kept (#163, Box Settings: Format).
- The UNO page no longer says that overlays take the match time as mm:ss: the Soccer Scorebug's SetMatchTime takes seconds. The page says what ScoreSight sends and what to do when a command takes something else (#162, Overlays.uno).