top of page

Download Score Reader for vMix

Stop updating score manually. Automate your scoreboard directly from a camera feed. No manual input. No delays.

v0.6.9

Score Reader download page, free trial available
Month

1 Month

14.99 EUR

Year

1 Year

149.99 EUR

LifeTime

Lifetime (limited)

360 EUR

Real-time score, timer and data detection

Instant download access

Direct integration with vMix & OBS

logo_edited.jpg

Automated Time and Period formatting

Up to 50ms detection frequency

Live Scoreboard OCR Software

Blue Digital Icon

How to Use?

Quick Tutorial about the basic functions and how to use.

Video Guides

See How to "ScoreRead"

How to connect ScoreReader to OBS Studio?

How to select corners?

Frequently Asked Questions

Smart Setup Starts With Clear Answers

  • Yes.

    ScoreReader can be used to send live score to OBS Studio using OBS-compatible output workflows, including WebSocket Server based connection.

  • Yes.

    ScoreReader supports vMix through vMix API / title integration. Detected scoreboard values can be used in vMix titles, overlays, and custom graphics.

  • You need a:

    • Windows 10/11 64-bit PC

    • a video source showing the scoreboard

    The video source can be a camera, capture device, NDI source, RTSP/HTTP stream, or video file for testing.

  • No.

    ScoreReader does not replace official timing systems, score controllers, or official game data systems. ScoreReader reads the visible scoreboard from video and turns that information into live data for broadcast graphics.

  • Yes.

    MCTV ScoreReader requires an internet connection for license activation and periodic license validation.

    After activation, ScoreReader is intended for live production use, but license checks may still be required from time to time. Internet or local network access may also be needed depending on your workflow, especially when using NDI, OBS WebSocket, vMix API, HTTP, WebSocket, or other network-based outputs.

    For production reliability, we recommend preparing and validating your license before the event starts.

  • Accuracy depends on the video feed and setup.

    Best results come from clear scoreboard digits, stable camera positioning, consistent lighting, reduced glare, and correctly configured recognition zones.

  • No.

    One MCTV ScoreReader license can only be active on one Windows PC at a time.

    You may use the same license on different computers, but not simultaneously. To move the license, remove or deactivate it from the currently active PC, then activate the same license key on another Windows device.

    If you need to run ScoreReader on multiple computers at the same time, separate licenses are required.

  • Yes.

    You can move your license to another Windows PC by removing it from the currently active device and activating the same license key on the new computer.

    This is useful if you change production laptops, replace a PC, or need to use ScoreReader on a different machine for another event.

    Only one active use per license is allowed at a time.

  • Yes.

    ScoreReader is built for multi-sport workflows. You can create custom fields and recognition areas depending on the scoreboard layout and the data you want to send to your graphics.

  • ScoreReader supports:

    • vMix

    • OBS Studio

    • HTTP/Web APIs

    • WebSocket workflows

    • CSV

    • XML outputs

  • MCTV ScoreReader includes an auto digit selection tool, but this feature is currently in beta.

    Because scoreboards, camera angles, lighting, colors, digit styles, and venue environments can vary a lot, automatic digit detection may not always find the correct areas reliably.

    For best results, we currently recommend adding digit regions manually one by one. Manual digit setup takes a little more time at the beginning, but it is much more reliable for real production workflows.

  • Yes.

    ScoreReader can also be used with symbol-based recognition for simple binary states, such as on/off indicators.

    This can be useful for scoreboard elements that are not normal digits but still show important game information, for example:

    • Team fouls indicators

    • Timeout indicators

    • Possession indicators

    • Bonus lights

    • Period indicators

    • Other visible scoreboard symbols or lights

    Instead of reading a number, ScoreReader can detect whether a configured symbol or area is active or inactive and output that as a usable value (1;0) for your graphics workflow.

  • Yes.

    ScoreReader supports project save and restore, so venue setups can be reused when the scoreboard layout and camera position remain the same.

  • Yes.

    ScoreReader is built around custom fields and recognition zones.

    You can create fields for the scoreboard values you want to use in your graphics, such as scores, clocks, shot clocks, periods, fouls, timeouts, or other visible scoreboard elements.

    This makes ScoreReader flexible for different sports, scoreboard designs, and production workflows.

  • Yes.

    ScoreReader is actively being improved. We continue to work on recognition accuracy, stability, setup tools, output workflows, and usability. User feedback helps us improve the software for real production conditions.

  • For best results, the scoreboard preview should look clean and simple.

    The digits should be white, and the background should be black. Try to remove anything that is not part of the actual scoreboard digits.

  • First, check the scoreboard preview.

    If the digits are not clearly visible, use the image adjustment sliders to improve the image. The goal is to make the digits white and the background black.

    Also check that the camera is focused, stable, and pointed clearly at the scoreboard.

  • If parts of the digits are missing, adjust the image settings until the numbers look more complete.

    The digits should be easy to read by eye in the preview. If you cannot clearly understand the number yourself, ScoreReader may also struggle to read it reliably.

  • If the digits look too thick, blurry, or connected to other scoreboard elements, use the image adjustment sliders to separate them better.

    Each digit should be clearly visible on its own, without merging into nearby numbers, lines, or lights.

  • Yes.

    Good image adjustment is one of the easiest ways to improve ScoreReader accuracy.

    Even if the scoreboard looks fine in the normal camera view, the recognition preview should be cleaned up so the software sees only the digits it needs to read.

  • If the scoreboard image is flickering or pulsing, the issue is usually caused by the camera settings not matching the scoreboard refresh rate.

    In many cases, the camera shutter speed is too fast compared to the scoreboard display refresh rate. Try adjusting the camera shutter speed first. Slower shutter values often help reduce or remove flickering from LED scoreboards.

    You can also adjust the camera iris/exposure settings to get a cleaner and more stable image.

bottom of page