NV Play Cricket v9.2.1 Update - Release Notes (22 April 2025)

General Scoring

  • Added the new 'Newbery' cricket ball to Web Admin, Desktop Client, and Match Reporting for matches where the 'Newbery' ball is used (#16449)
  • The Edit Match Result/Points dialog has been updated to include a free text field for entering the reason for a points deduction. This reason will be displayed as a footer on the Match Centre points tables, allowing viewers to understand why a team received a points deduction (#10693)

 

Stats Wizards

  • Enhanced the ball-by-ball CSV exports by including additional data for Penalty Runs, Pitchside Analytics Fielding Coordinates, Player IDs for Batter, Bowler, and Non-Striker, Competition Name, and Boundary Sizes to support more comprehensive analysis (#16144 and #16441)
    • NB: If any users are currently mapping directly to column numbers, please be aware that future releases may cause integrations to break due to these changes. For greater resilience to modifications, we strongly recommend mapping to column headers instead
    • Please also note that Competition Name and Boundary Sizes are limited to the Live ball-by-ball, Match Stats Wizard, and Full Multi-Match Stats Wizard exports only
  • Improved performance for large date ranges in the Multi-Match Stats Wizard (#15904)
  • Updated the CSV export functionality to ensure the Team Profile name is included when a team is configured with a secondary Team Profile for specific match types (#16062)

 

Collaborative Scoring

  • Added support to ensure Decision Review System (DRS) data is synchronized with the server when either the Live Scorer or Video Analyst codes it, even if the other does not. This means the Video Analyst is no longer required to code the DRS data (#13757)
  • Fixed issue where a Video Analyst’s Ball Clip Offset was incorrectly resetting to 0 after a Force Full Upload from the Live Scorer occurred (#15977)

 

Video Capture

  • The Video Configuration menu has been updated to allow users to enable Auto Capture alongside Auto Score, enabling users with the Video Analyst role to create ball clips on a secondary machine automatically (#16235).
    • This feature is not recommended in environments with networking issues
    • For more details, please refer to our Knowledge Base article at: 

https://support.nvplay.com/hc/en-gb/articles/42353237578777-Auto-Score-from-Live-Scorer-Feature

  • Fixed issue where the Video Player would not frame forward at the very beginning of ball clips (#12414)

 

Live Streaming

  • Improved the logic of score overlays to prevent a new over starting with the previous over’s bowler and bowling figures being displayed (#14658)
  • Fixed issue where an erroneous 0 could sometimes be displayed on the score overlay at the start of a new over, before the first ball is bowled/scored (#15737)
  • Fixed issue where the previous batter could be displayed in the score overlay after selecting Unknown and then the actual new batter (#15792)
  • Resolved issue where Auto Capture Video would fail in multi-camera setups if this was enabled after the live stream had already been started (#15493)

 

Vision AI

  • General improvements to the accuracy of Vision AI Ball Arrival height detections
  • Update to the latest Vision AI models for improved accuracy and consistency
  • Implemented general improvements to the Vision AI mechanics, enhancing ball tracking and detections for full tosses and swinging deliveries in certain scenarios (#16429)
  • Added new functionality to Vision AI to automatically add the ‘Appeal’ coding event for greater automation and reduced manual tasks (#8683)
  • Improved live Vision AI processing logic to better handle dirty cameras interfering with ball detections (#15283)
  • Fixed issue where sometimes connected writers or readers would not receive live updates without a restart (#15909)

 

Pitchside Analytics

  • The latest upgrade to Pitchside Analytics 2.1.0 ensures full compatibility with the newest versions of iOS and Android, resulting in the discontinuation of support for Android 11 devices (#14817)
Was this article helpful?
0 out of 0 found this helpful