Alexa Log Console

Sign in with your No Drama Google account to continue.

Drop .LOG files to analyse
Camera log analysis

Alexa Log Console

or drop them anywhere · nothing leaves this browser

Check a camera's own frame accounting in about ten seconds

Drop in the .LOG files from an ALEXA Mini, Mini LF or AMIRA. This page rebuilds every clip the camera recorded and reconciles three numbers that have to agree — then reports what else the logs are complaining about, which drives were involved, and how the camera was running.

The check

Three numbers, per clip

Frames captured against frames committed to the medium; both against the timecode span; and the camera's own booking status. A clip passes only if all three agree. Off-speed clips are reported as not checked rather than quietly passed.

Then

Everything else the log knows

Per-drive media health with write timeouts attributed to the drive that was fitted, a triage of every error and warning, sensor and regulator temperatures, supply voltage, module firmware, and a search across every line.

Getting the files

On the camera

MENU > SYSTEM > INFO > Export Logfiles… writes them to the SD card. Load the whole set rather than one file — the console stitches sessions together across them and spots drives that moved between cameras.

Where the data goes

Nowhere

Parsing runs entirely in this browser. Nothing is uploaded, stored or sent on — so a client's camera logs can go through it without leaving the machine you're sitting at.

Session timeline

One row per power-on. Bars are clips; markers above the track are media write timeouts.

Recording media

Every drive the camera wrote to, with its share of the media write timeouts.

Clip log

Error triage

Grouped by code site. Anything this console has no rule for is marked Unclassified rather than assumed benign.

Environment

Sampled once a minute while powered. Sessions are laid end to end, so gaps between shooting days are closed up.

Supply voltage at the camera

Rig & build

Modules reporting on the internal bus, plus what was recorded and mounted.

How the frame check works

Three independent numbers, per clip

When a clip closes, the camera writes a Recording booked line carrying its own accounting. This console compares three values that should agree, and a clip only passes if all three do:

  • Frames captured vs. frames committed. The two counts in that line. A gap means the sensor delivered frames the medium never took.
  • Timecode span. Start and end timecode converted to frames at the project rate, then compared with the recorded count. This catches a stall that both counters agreed about.
  • Booking status. The camera's own verdict on the clip. Anything other than OK is a flag.

Where the timecode check is skipped: on off-speed clips the sensor rate and project rate differ, so timecode no longer advances one frame per recorded frame. Those clips are counted as not checked rather than quietly passed, and the count is shown in the verdict.

What this cannot tell you. This is the camera's account of its own recording. It is strong evidence about what reached the medium, and it says nothing about what happened afterwards — a card copied badly, a transcode, a playback stutter on set, or a monitoring path fault that looked like dropped frames to whoever reported it. If the camera reads clean but someone saw dropping, the cause is downstream of this log.