Troubleshooting

Troubleshooting

Live Diagnostics & Monitoring

The Debug tab is a tool for monitoring the raw data flow arriving from the JudoNet.
  1. Enable / deep packets: Checking Enable displays Scoring Breakdown and Contest Metadata. Checking deep packets displays Raw JSON Data.


  1. Scoring Breakdown: Actively tracks the current tatami score for White (W) and Blue (B), including IPPON, Waza, Yuko, Penalty, HansokuMake, TimerOsae, and the GoldenScore boolean state.
  2. Contest Metadata: Tracks the DisplayMode (e.g., 6 means active contest), whiteid, blueid, timerms, names, club, team, winner, the active referee (Reef), team Result, TotalDuration, timerflag, and the showSB/reef/intro/win boolean state.
  3. Raw JSON Data: Displays the comprehensive data packet containing the MachineId, IDEvent, weightcategory, round description, and detailed athlete demographic data (names, IDs, and club affiliations).

Rendering Confirmation (CasparCG Server Console)

Look at the separate CasparCG Server console window (the black command prompt). Look for the continuous presence of the log entry Sent message to 127.0.0.1: CG OK. This confirms that the CasparCG rendering engine is actively communicating and successfully executing rendering instructions.

Troubleshooting and data.ini Configuration

The data.ini file (located in your SW folder) is a configuration file for CGplay. If necessary, you can manually adjust the values with a text editor (e.g., Notepad). Below is a list of parameters, troubleshooting scenarios, and manual fixes. Make your changes, save the file, and restart CGplay to apply them. Note: Changes in the data.ini file apply to all CGplay instances running on the same computer.


Directory

  1. wattermarkpath=c:\CG\media\ 
    1. Troubleshooting: Missing images.
    2. Manual Fix: Ensure wattermarkpath matches the media-path setting in your casparcg.config file and that media files are in folder c:\CG\media\.
  2. flagspath=file:///c:/CG/img/
    1. Troubleshooting: Missing country flags, team logos, or other images.
    2. Manual Fix: First, right-click the ONLINE status indicator and select Refresh Flags or Refresh Club Images. If that fails, manually verify that flagspath is set to file:///c:/CG/img/. Ensure the required images are in their respective subfolders (e.g., imgflags, imgclubs). Flags must be named using IOC country codes (e.g., FRA.png). Additionally, ensure wattermarkpath matches the media-path setting in your casparcg.config file and that media files are in folder c:\CG\media\.

CasparCG Server Communication

  1. serverhost=localhost; serverport=5250 
    1. Troubleshooting: CGplay will not connect to the CasparCG rendering engine. 
    2. Manual Fix: Ensure serverhost is set to localhost if both programs run on the same computer. Verify that serverport matches the <controllers><tcp><port> setting inside your casparcg.config file (5250 is the standard AMCP communication port). 
  2. CGplusminus=-5 
    1. Troubleshooting: Mats are outputting to the wrong channels or completely failing to render on a secondary PC. 
    2. Manual Fix: Adjust this channel offset value using the formula: [Mat Number] + [CGplusminus Value] = [CasparCG Output Channel]. If Computer 2 handles Mats 6 through 10, and you want Mat 6 to output to Channel 1, set CGplusminus=-5 (because 6 - 5 = 1).

Graphics

  1. tempversion=jm 
    1. Do not change, unless support explicitly instructs otherwise.
  2. introofftime=5; winontime=4 
    1. Troubleshooting: The intro graphic stays on screen too long, or the winner graphic disappears too quickly.
    2. Manual Fix: Adjust introofftime to set how many seconds after the match starts the intro automatically transitions to the main scoreboard. Adjust winontime to set how many seconds the Winner graphic remains visible before clearing. 
  3. SBleftdispl=0 
    1. Troubleshooting: The Main Scoreboard is covering sponsor or competition logos on the right side of the screen.
    2. Manual Fix: Increase this value to manually shift the entire scoreboard graphic to the left, creating empty space on the right side of your stream.
  4. doctorTXT=FIGHT PAUSED - DOCTOR ON TATAMI 
    1. Troubleshooting: The lower-third template displays an incorrect message when the doctor is called.
    2. Manual Fix: Rewrite this text string to customize the message displayed during a medical intervention.
  5. wattermark1=...; edDoctorimg=doctorcall.png; edDoctorimg1=doctor.png 
    1. Troubleshooting: A specific mat is showing the wrong watermark or doctor image.
    2. Manual Fix: Update the filename associated with the specific mat number (e.g., change wattermark3 or edDoctorimg3 to fix an issue specifically occurring on Mat 3).
  6. language=en
    1. Troubleshooting: The graphics are displaying in the wrong language.
    2. Manual Fix: Change this value to your desired language code (e.g., En for English, Fr for French).  
  7. competition=National Championship for Juniors 
    1. Troubleshooting: The wrong tournament title is displayed on the graphics. 
    2. Manual Fix: Manually type the exact name and year of the current tournament into this string. 

Network & Data Connection

  1. boundudpport=5000  
    1. Troubleshooting: CGplay receives no live contest data from the scoreboard. 
    2. Manual Fix: Ensure boundudpport matches the Graphics Broadcast Port configured in the active JudoNet software.
  2. boundudpIP=
    1. Troubleshooting: CGplay receives no live contest data from the scoreboard.
    2. Manual Fix: Type the IP address of the desired receiving network card into this field to force CGplay to use that specific connection. If you leave this field blank, the software will automatically listen for incoming UDP packets across all available network interfaces.
  3. senderIP=172.20.1.10 
    1. Troubleshooting: CGplay receives no live contest data from the scoreboard.
    2. Manual Fix: Ensure this matches the specific network IP address of the active JudoNet sender PC. If you leave this field blank, CGplay will accept data packets from any sender on the network. 
  4. currentsrvIP=172.20.1.2  
    1. Troubleshooting: Missing competition data and images.
    2. Manual Fix: Verify and update this IP address to match the JudoManager server providing the competition data.

[Appstate]

This section saves the radio button and dropdown selections from your CGplay Settings tab so they persist upon restarting the application (e.g., cpat={Club#}{Category} saves your Custom pattern). Alter these via the controller interface, not the text file.

Common Problems & Solutions

Symptom

Diagnostic Step & Resolution

No contest data received (UDP is disabled)

1. In JudoNet, verify the correct UDP Send Interface is selected and "Broadcast UDP to Graphics" is checked.

2. Verify that JudoNet is actively receiving information from the scoreboards.

3. Ping CG ↔ JudoNet to verify cabling/IP.

4. Check the Windows Firewall on the Graphics PC to ensure it allows inbound UDP.

Referee name is missing from the graphic

Ensure referee has been assigned to the specific tatami in the main JudoManager system.

Sponsor logos (watermarks) have a solid background instead of being transparent

The CasparCG rendering engine requires image files to have an embedded Alpha Channel for transparency. Ensure your sponsor graphics (defined in data.ini as wattermark1, etc.) are saved strictly as 32-bit .PNG files, not .JPG.

Wrong contest showing on a mat

Coordinate with the Competition Manager to confirm the scoreboard connection and check the JM Server contest order on their end.

Lines or halos rendering around graphics

Press Windows + R and run sysdm.cpl. Under the Advanced tab, click Settings inside the Performance section. In the Visual Effects tab list, uncheck "Smooth edges of screen fonts" (ClearType). Click Apply and OK to save the fix.


No NDI output visible on Video mixer PC

If your live graphics are missing from the Video mixer PC, first ensure that the CasparCG program is running only once on your Graphics PC. Next, open the NDI Studio Monitor application on the Video mixer PC to verify that the video feed is successfully traveling across the local network. Finally, check your video mixing software (e.g., vMix or OBS) to ensure its NDI input settings are properly configured to capture that specific feed.