Skip to main content

Glossary

Last updated: 10 August 2026

Terms used throughout the Video Ingester and its documentation.

Backend system​

The platform the Ingester uploads to. Either JudoManager (stored as JM) or Judobase (stored as JB). Chosen in Settings → API Configuration; it decides which API url is used and whether a partner is required.

Chunk​

One piece of a file during a multi-part upload. Files are split into chunks so that a failure only costs one chunk rather than the whole transfer. The size is chosen from a short list — 5, 10, 25, 50, 100 or 150 MB — and defaults to 10 MB.

Companion file​

A small file written next to a video file by the Video CutterV2: <video>.json, carrying the contest metadata. See how files are found.

Contest code​

The identifier that ties a video to one specific fight in JudoManager or Judobase. Without a valid contest code the platform cannot attach the video to anything, and the upload fails. Supplied automatically by the Video CutterV2, or typed into the Contest Data form.

Deinterlacing​

Removing the comb-like artefacts produced when interlaced video — each frame made of two half-images captured moments apart — is shown on a progressive display. Applied during encoding. See the deinterlace settings.

Encoding​

Converting the uploaded video into the format the platform streams. Performed in the cloud; the Ingester only requests it.

FairReplay Cloud​

The website where licences and machine activations are managed: https://backend.fairreplay.com.

Job​

One video file making its way through the system, together with all the metadata the encoder will need. Jobs are stored in the local queue and move through a series of statuses.

Job queue​

The local SQLite database FileWatcherIngester.db in the installation folder, holding every job. Published to workers over a local web API on port 18472.

Machine key​

A fingerprint derived from the PC's hardware, used to tie a licence to one machine. See Registration.

Manual mode​

Uploading a file the Video CutterV2 did not prepare, where you enter the contest data yourself. Contrast with automatic mode.

Overlay​

A logo image burned into the encoded video — typically a sponsor or broadcaster mark. Configured as a URL in Settings → Overlay.

Partner​

The federation or organisation that owns an event in JudoManager, for example Judo zveza Slovenije or European Judo Union. A contest code is only unique within one partner's events, which is why the partner is mandatory for JudoManager jobs. The list comes from IngestPartners.json. Judobase does not use partners.

Payload​

The JSON block stored with each job: file path, contest code, camera name, deinterlace flag, overlay URL and so on. Viewable with Show payload on the job's right-click menu.

Playable​

The record on the FairReplay platform representing the finished, streamable video. Its identifier appears in the Playable column of the job grid once it exists.

Priority​

A number from 1 (most urgent) to 10 (least urgent) deciding which job uploads next. See Job priority.

Progressive​

Video where each frame is captured as a whole image, as opposed to interlaced. Progressive video does not need deinterlacing. The Video CutterV2 reports this in the companion .json file.

Video CutterV2​

The companion program that slices continuous mat recordings into one file per contest and writes them, with their companion .json files, into the Ingester's watch folders.

Watch folder​

A folder the Ingester monitors for new video files, including its sub-folders. Configured in Settings → File Settings.

Watcher​

The role that finds new files and creates jobs. See the two roles.

Worker​

The role that takes jobs from the queue, uploads the files and requests encoding. See the two roles.