TITAN TWO

Titan Two and computer vision

Troubleshooting an intermittent Titan Two CV preview

A Titan Two CV workspace can work initially and fail later when a video source changes, a device reconnects, or processing stalls. A useful diagnosis identifies the first stage where a good input becomes a bad one.

Check whether frames arrive before processing

Open the Computer Vision panel in Gtuner IV and select the source that shows the fault. Leave the GCV script stopped for the first pass. Use a visible repeating change, such as a menu highlight moving once a second, so a frozen frame is easy to distinguish from a still scene. Note whether the preview goes black, stays on one old frame, or continues to show movement while a script output stops updating.

Record the event immediately before the fault. Examples include resizing a window, reconnecting a capture device, and switching the console’s video mode. If the device has its own preview application, try the same event there as a separate pass. Close it before reopening Gtuner IV if the source allows only one active application.

Gtuner IV Computer Vision pane with a video-source selector and a racing-game preview
The source selector sits above the live preview. This view isolates the Computer Vision pane from a published Gtuner IV 1.7 Beta screenshot. Scachi on the Gtuner IV issue tracker

Reproduce a dropout with one deliberate change

Run a 30-second baseline with the source and resolution fixed. For a window source, repeat for another 30 seconds and resize the window once at the halfway point. For a device source, leave the window alone and repeat the video-mode transition that normally causes the fault. Record the time of the change, whether the picture froze, and whether it resumed by itself.

In an illustrative fault log, the preview shows movement from 0 to 14 seconds, freezes when a window is resized at 15 seconds, and resumes when the source is reselected at 23 seconds. The failure happened without a script running, so the source or preview deserves the next test. A preview that keeps moving while only a read-only script output stops calls for a different check.

Separate a script error from a capture error

With a stable preview, check the first relevant error from the read-only script and inspect its expected image size, color format, and crop. If you can test its processing separately, use a short saved clip with the same dimensions and orientation. The OpenCV video guide explains file and device inputs for that separate comparison.

Change one variable per retest and note the Gtuner IV version, selected source, and whether any other application was using it. Save an example of the visible preview and the first error together. That is more useful in a support request than reporting a black screen without identifying which stage stopped.

Sources

publishes these guides independently. ConsoleTuner makes the Titan Two device and Gtuner IV.