Checking everything works

The quickest end-to-end check, in order:

• Detection — walk in front of the camera and watch the motion meter. It should rise past the orange line and read TRIGGERED, then fall back within a second or two of you stopping.
• Region — draw a shape around one part of the scene. Movement inside it should register; movement outside it should leave the meter flat. This is the check most worth doing, because a region that doesn't line up with what you drew is invisible until something goes unrecorded.
• Recording — press Start Monitoring, trigger it once, and open the folder. The clip should start before the movement, thanks to the pre-roll buffer, and contain audio in step with the picture.
• Sound — if you use it, speak at a normal volume and check the sound meter crosses its line. A mouse click should not.
• Overnight — the only test that really matters. Leave it monitoring against the real scene and count what it caught and what it invented in the morning.

The Diagnostics readout in the toolbar reports frame rate, dropped frames, CPU and memory for your machine specifically. Dropped frames climbing steadily is the signal that it's genuinely behind rather than merely busy.

The readout is live only — nothing is written to disk. Copy, at the right-hand end of it, puts the current figures plus the machine and its settings on the clipboard, which is the quickest way to get them off a Mac you aren't sitting at.

For a continuous record, Settings › Advanced can write a diagnostic log of frame timing, detector output and a performance sample every ten seconds. It's written to OdinCam's own Logs folder and named after the Mac that wrote it, so logs copied off two Macs never overwrite each other. The same panel has a button to reveal it in the Finder. Useful if something behaves oddly and you want the numbers rather than an impression — particularly for something intermittent, where a live readout tells you nothing after the fact.