Detecting Cuts
First time analysis
To analyse the clip do one of the following:
- Click the "Analyse" button in the lower left corner
- Press "Enter"
The analysis can be constrained to a specific region
If the clip has burn-ins that change for each shot, it may be smart to analyse the burn-in instead of the entire clip for more accurate results
If you only want to analyse a specific region of the clip, you can do so by holding Ctrl (Cmd on mac) and dragging a rectangle across the region you wish to analyse.
See the purple outline in the above image.
Right click to delete the drawn region.
There are currently two options to analyse the clip:
-
Content
The content-aware scene detector detects jump cuts in the input video. This is typically what people think of as "cuts" between scenes in a movie - given two adjacent frames, do they belong to the same scene? The content-aware scene detector finds areas where the difference between two subsequent frames exceeds a given threshold value that is set. The threshold can be adjusted interactively once the detection is complete (see Sike Graph)
-
Adaptive
The adaptive content detector compares the difference in content between adjacent frames similar to detect-content but instead using a rolling average of adjacent frame changes. This helps mitigate false detections where there is fast camera motion.
Re-use previous analysis
If the clip was previously analysed, the results are automatically saved in a CSV file and CutDetector will offer to just read those values:
The per-clip csv files are saved in different locations depending on the operating system:
- Windows: %APPDATA%\CutDetector\OHUfx (Roaming profile)
- macOS: ~/Library/Application Support/CutDetector/OHUfx
- Linux: ~/.local/share/CutDetector/OHUfx
The location of those csv files should not matter to the user during the regular workflow.
Saving the project will include the csv data as well, so the .cdui project file is fully portable.