Help center
Video

XML inspector

Fix an XML file's codes and times, then save the result or use it straight in an import.

View as Markdown
On this page

The Inspector is the third tab of the XML preview drawer, next to Summary and Source. Open it from the XML library or from an import to retime a clip, rename a code, or line up a file tagged against a different cut of the video.

The table

Every timed instance in the file — clips and events together — lists in time order, with its Code, Start and End editable right there. Events are points in time, so their End column shows a dash.

Against a video, two lines can cut across the table: one at 0:00, "what is above does not make it," and one at the video's end, "what is below does not make it." Rows on the wrong side get a red tint. Nothing is deleted while you look — those rows are only left out when you save, and the count shows in the footer, and in the import's own success message too.

Editing a cell

Click a code or a time, type the new value, and press Enter to commit it. Esc puts it back. A cell you opened and left untouched — a click in, a click out, nothing typed — isn't recorded as an edit.

Selecting rows

Tick a row's checkbox to select it; shift-click another row to select the whole range between them. With rows selected:

  • A ladder of quick nudges shifts the selection by a fixed amount, either direction.
  • Move to a time shifts the whole selection by whatever delta puts its earliest row there — spacing between rows doesn't change.
  • Rename relabels every selected row at once.
  • Delete removes them.

Categories

Switch to Categories to see one row per code, with its count and total time. Click a category's code to rename it, same as a table cell — rename it onto a code that already exists and the two merge, which the inspector confirms first. A small trash icon deletes the category and every instance under it.

Aligning on the detected start

Align all… shifts every instance by the same amount, keyed on the match's detected start: a period-start marker in the file — something like "Start Period" or "Comienzo primer tiempo" — or, failing that, an "offsets" row in the first two minutes. With neither, the earliest instance is used. Type where that start should land and confirm with Align.

Converting 25 to 30 fps

Some tablet tagging tools write their times at 25 frames per second even when the video runs at 30, so every clip lands a little later the further the match goes. When a file carries those tools' match start and end markers, Convert 25 → 30 fps appears above the table: it moves every time at once, and undoes like any other edit. Without the markers it is not offered — a duration alone cannot tell you a file's frame rate is wrong.

Which files open

Besides XML — in UTF-8 or UTF-16, with or without a byte-order mark — the library, imports and the Inspector open .nacmac, .nac_to_import, .SCTimeline, .lgm and .csv. Each is converted to XML as it opens, with its codes, times and, where the file has them, colours and descriptors; from there it is inspected, saved and imported like any other.

A .csv of tagged clips — the export other analysis tools share, or one you build in a spreadsheet — is read by its header row, in any column order: a code or category, a start, and an end or a duration are what it needs; notes and descriptors are optional, and every other named column becomes a descriptor group. Times can be seconds or hh:mm:ss, with a dot or a comma for decimals, and the columns can be separated by commas, semicolons or tabs. A row whose times don't read is skipped.

An Opta F24 event feed opens the same way, as a plain .xml. Every on-ball event becomes a clip a few seconds either side of the moment (longer for shots and goals), labelled with period, team, player shirt, outcome and pass, shot or card type, with its pitch point. Opta draws each team attacking right; cliply keeps one pitch, drawn from your team's attack, so the rival's points are turned around to match — your shot near the right goal and theirs near the left one. When the feed opens, cliply asks Which team is yours?, already pointing at the side whose name matches one of your teams; it remembers the answer for that match in this browser, so opening the same feed again doesn't ask. Closing without answering keeps the home team's attack. Times run from the first-half kick-off with the break left in, and each kick-off comes in as a Start Period code, so one shift lines up a recording that runs straight through; a second half cut separately is aligned from its own Start Period 2. A feed carries ~1,500 events — drop the codes you don't want (Pass, Ball Touch) in the Inspector before importing.

Any other events XML with times in it — a provider's export, a spreadsheet saved as XML — opens a Map this XML step instead of failing. Pick which element is one event, which field is the start (and the end or a duration, if there is one), which is the code, and which fields become labels. Seconds, milliseconds, frames, clock times like 1:02:03 and dates all read; dates count from the earliest one, and a start with no end becomes a clip a few seconds either side. The preview updates as you choose, and the mapping is remembered on this browser for the next file laid out the same way.

Undo and discard

Undo steps back one edit at a time. Discard drops every edit from this session and puts the file back as loaded — it asks you to confirm first, since there's no way back once you do.

Edits change the file, not the clips

Nothing here reaches your project until you save. Editing a file never touches clips already imported from it — to carry a fix into your library, re-import the corrected file, or edit before you import.

Saving, or using it in an import

ActionWhat it does
Save as copyAdds the edited file to the XML library under a new name, alongside the original
Replace originalOverwrites the original in the XML library — the tagging tool's version can't be recovered after
Use in the importHands the edited file straight to the import you opened it from, no separate save

From an import, the entry point is Review and edit rather than a plain preview, and an Undo edits action drops the changes without reopening the inspector.

What's untouched, and what's refused

Everything the inspector doesn't act on — labels, colors, ids, any other markup your tagging tool wrote — comes through byte-for-byte. Some tools also export a leading index instance ("Orden") listing label positions rather than a match moment; the inspector never shows it as a row, so it's kept exactly as it was.

Two things are refused rather than applied silently: an instance whose end lands at or before its start, since a file can't hold that and saving stays blocked until it's fixed; and a file whose layout the inspector can't line up safely, which it leaves untouched rather than risk an edit landing on the wrong instance.

Exporting a video as XML or CSV

The XML import / export hub (Option + X) also exports a video's clips: as an XML for another tagging tool, or as a CSV for a spreadsheet. Both carry the same clips, filtered the same way, and each row holds the clip's code, times, name, reactions, variants, players, zone and point, status and the staff's notes; notes guests left through a share link stay out.

Support

Rather talk to a person?

If the guide isn't enough, message us on WhatsApp or by email. Someone on the team answers, no bots.