BATS - ClipInfos đź“‹

Also available in:

Deutsch

All the details of a clip – including the projects it is used in

“Which projects am I actually using this clip in – and in which sequences?” ClipInfos answers that question with a right-click: BAT Server assembles an overview page that your default browser opens. It shows all the details EDIUS has recorded for the selected clip – and, most importantly, the list of all projects that use the clip (including bins and timeline sequences, resolution, frame rate, colour space and audio channels). If the media carries GPS metadata (e.g. phone footage), the page also shows a map of the recording location.

Adding the menu entry

“Clip Informations” is not a built-in entry – it is added through the “Add function...” assistant (right-click a clip in the BIN → Add function...). BAT Server walks you through a couple of short questions and creates the .bat0 template that makes up the new context-menu entry:

  1. Pick the extension: The BAT Server tab opens the list of bundled extensions (with a tag filter). Choose ClipInfos - with GPS map support.
  2. Question 1 – placement: “Please select where you want to add the menu and confirm” – the new entry appears in the BIN or the timeline context menu (or in both, by simply running the assistant twice).
  3. Question 2 – name: “Please add the name of the BAT file:” – the default is Clip Informations...; invalid file-name characters (< > : " / \ | ? *) are rejected on the spot.
  4. Finish: Use [Preview '.bat0' file] to inspect the generated template, then [Add menu entry] to write the .bat0. If a file with the same name already exists, an overwrite checkbox confirms the replacement. The new context-menu entry is available immediately.

How to use it

  1. Select a clip: right-click a clip (in the BIN or on the timeline) → Clip Informations...
  2. Your default browser opens the overview page. The top section lists Used in Project – every EDIUS project containing the clip: the project file path (one click opens the folder in Explorer), plus resolution | frame rate | colour space | audio channels, created/modified dates, and Found in Bin / Found in TL-Sequence with the affected names.
  3. Below that: Asset Details – all properties EDIUS/Chorus Hub has recorded for the clip (created, modified, file path – also clickable, opening the folder) – and JSON raw [click to see] for the unfiltered raw data.
  4. GPS map: if the media contains GPS coordinates (e.g. smartphone video), an OpenStreetMap map of the recording location appears next to / below the list. Media without GPS metadata simply omits the map area.

Good to know

  • EDIUS must be running: the page is assembled live from EDIUS’s Chorus Hub index (local interface, port 1225). Clips the running EDIUS instance does not (anymore) know – e.g. because the project was closed – are not listed; you get an error message instead of details.
  • Read-only snapshot: the overview is a purely read access – nothing in your files, bins or projects is changed.
  • Stays local: everything runs over localhost; no data leaves the machine.
  • Clickable paths: both the project files and the clip’s source path open the matching folder in Windows Explorer with one click – handy for quickly locating the original media of a project.

Managing the preset

Unlike e.g. “Instant Video Share”, “Clip Informations” is a user preset, not a system preset: the generated .bat0 file (in the BIN: C:\ProgramData\EdiusPowerTools\BAT-server\bat_files\BIN\, with the timeline choice under …\bat_files\timeline\) can be freely edited or deleted – which removes the context-menu entry again.

For advanced users: as with all BATS presets, the .bat0 is a template that BAT Server fills with the clip’s specifics on every run (here: {bat_url} and the EDIUS {asset_id} of the selected clip). The entire ClipInfos template is a single work step: curl.exe --url {{bat_url}}/getAsset?asset_id={{asset_id}} – i.e. BAT Server requests the overview page and the browser opens it. The directives source_dont_check=1 (no file presence required) and ediusrender_prohibit=1 (no EDIUS render slot occupied) control the behaviour around that call.