Skip to main content

Glossary

Last updated: 26 October 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.

Backoff​

The short wait before the Ingester tries a failed encode request again by itself — about 1 minute after the first failure and 5 minutes after the second. Jobs serving one are counted in the Queued header. See When an encode request fails.

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 set to Auto by default, which works it out for each file, or to a fixed 5, 10, 25, 50, 100 or 150 MB. See File chunk size.

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.

Encoding stalled​

Uploaded jobs waiting while no encode request has succeeded for 10 minutes. Shown as a red ENCODING STALLED banner across the main window. See Troubleshooting.

FairReplay Cloud​

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

Group​

One of the five headings the job grid lists jobs under, by what you need to do about them: Needs attention, Working now, Queued, Done and Cancelled. See The job groups.

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.

Needs attention​

The group of jobs only you can move on: pending jobs waiting for contest data, uploads that ended in error, and jobs whose encode request failed. Its header — and its count in the Today strip — turns red while it holds a job. The Next action column says what each job needs.

Network Report​

A measurement of the venue's internet connection to the upload storage, started from SETTINGS → Support. It takes about 6 minutes and saves a file to send to support and the venue's internet provider. It only measures; it changes no settings. See Network Report.

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, European Judo Union or JM IJF. 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.

Queued​

The group of jobs that will still run without you: new jobs waiting to upload and uploaded jobs Waiting for encode, in the order they will be picked up.

Retry encode​

Asking the platform again to encode a failed job's file, without uploading it again. The job gets a fresh set of three attempts. Lighter than a Re-run, which uploads the file again from the start. See Retrying the encode request.

Upload Hold​

The pause on starting new uploads while a Network Report runs. Uploads already running carry on, and encode requests go on as usual. The Queued header says how many jobs are waiting for it.

Upload Tuning​

The Ingester choosing each upload's settings by itself while File chunk size or Parallel connections is set to Auto: the number of parallel connections, learned from how fast earlier uploads went on this network, and the chunk size, worked out from the file's size. See the settings reference.

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.

Waiting for encode​

The status of a job whose file is uploaded and that waits for its encode request to be sent — including while it waits out a Backoff. The log files call this status uploaded.

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.

Working now​

The group of jobs the Ingester is moving right now: the one uploading and those whose encode request is being sent.

Worker​

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