Skip to main content

Fine-Tuning and Troubleshooting

Here you can explore solutions to some common issues users face.

Error 500 When Cutting from FR Recorder​

If you're encountering a 500 Internal Server Error when attempting to cut from the FR Recorder, it's likely due to old or invalid recordings in its database. You can resolve this issue by deleting outdated sessions from FR Recorder. But first, let's confirm if this is the cause.

Troubleshooting Steps​

Follow these steps to diagnose the issue:
1️⃣ Check Network Access:

  • Try connecting to the shared folder on the FR Recorder machine.
  • Use File Explorer or Total Commander with the following credentials:
    • Username: fr
    • Password: fr
  • If you can access the shared folder, proceed to the next step.

2️⃣ Test API Connectivity:

  • Open your browser and visit: 
    http://<FR Hostname>:9696/api/ping
    Replace <FR Hostname> with the actual name of the computer running FR Recorder.
  • If the ping is successful, try fetching the recordings by visiting: 
    http://<FR Hostname>:9696/api/recordings
  • If you encounter an error here, it's highly likely that invalid recordings are causing the problem.

Solution: Deleting Old Sessions​

To fix this, follow these steps inside FR Recorder:
1️⃣ Open FR Recorder and click Switch Session.
2️⃣ Delete old sessions, starting from the oldest and moving to the newer ones.
3️⃣ After each deletion, try fetching the recordings again (as previously described).
4️⃣ Once the API call succeeds, the connection between FR Recorder and CutterV2 should work smoothly.

My Computer is Slow, and CutterV2 Runs Slowly​

CutterV2 supports up to 4 simultaneous threads for faster processing, with 3 threads set by default. If your computer is lower-spec, you can improve performance by adjusting the number of cutting processors.
To modify this setting, update the Number of Cutting Processors field in the Settings tab. Valid values range from 1 to 4.

Disabling FFmpeg for Cutting Clips from Offline Recordings​

CutterV2 uses FFmpeg to speed up the process of cutting clips from offline (non-live) recordings.
If you prefer not to use FFmpeg, you can disable this feature by unchecking the Use FFmpeg for non-live recordings option in the Settings tab. Note: Acceptable values for this setting range from 1 to 4.

CPU Usage Throttling​

CutterV2 uses CPU throttling by default, which helps prevent excessive CPU load during clip processing. Before starting each task, CutterV2 checks the total CPU usage; if it exceeds a defined threshold, processors will wait briefly before starting to reduce the strain on your system.

The default CPU usage threshold is set to 65%. You can customize this value in the Settings tab by modifying the CPU Usage Throttling Threshold field, with acceptable values ranging from 50% to 80%.
If you prefer not to use CPU throttling, you can disable it by unchecking the Use CPU Usage Throttling option in the Settings tab.