Settings reference
Last updated: 26 October 2026
Every setting the Video Ingester has, what it does, and why it exists.
Most settings live in the Settings dialog, opened with the SETTINGS button in
the top-right corner of the main window. A few advanced settings exist only in the
settings.json file and are listed at the end of this page.
Changes take effect only when you click Save settings. Clicking Cancel, or closing the dialog with the ✕, discards everything you changed.
Appearance
Language
The language of the user interface. English and French are available.
Changing the language requires a restart. After saving, the Ingester offers to restart itself for you; if you decline, the new language appears the next time you start the program.
Dark mode
Switches the whole application between a dark and a light colour scheme. Unlike the language, this applies immediately — no restart needed.
Dark mode is the default for a fresh installation. It exists because Ingester PCs often sit in darkened control rooms next to a video wall, where a bright white window is uncomfortable and distracting.
API Configuration
These three settings tell the Ingester which platform to upload to and how to authenticate. Nothing works until all three are filled in — the Ingester refuses to save the settings and refuses to create jobs without them.
Backend System
Which platform this Ingester serves:
| Choice | Used for | Stored in settings.json as |
|---|---|---|
| JudoManager | National federation and club events managed in JudoManager. | JM |
| Judobase | IJF events published on Judobase. | JB |
Choosing a backend system automatically fills in the matching API url below. If the API url field already contains a different address, you are asked whether to replace it.
This dropdown exists because picking the wrong endpoint used to be the single most common configuration mistake: an operator would upload to Judobase with a JudoManager address, and every contest code would come back "not recognised".
API url
The address of the backend the Ingester talks to.
| Backend System | API url |
|---|---|
| JudoManager | https://datav2.judomanager.com |
| Judobase | https://datav2.ijf.org |
The field is read-only and is filled in for you when you choose a Backend System.
Older versions of this documentation called this field JMSharp API url. It is the same setting; the label was shortened.
API key
The secret key that authorises this Ingester against the backend. It is issued to you — contact the Control Room team if you do not have one.
If the key is missing or wrong, uploads fail with Access Denied. See Troubleshooting.
File Settings
Watch folders
The folders the Ingester monitors for new video files, separated by semicolons — for example:
D:\Cutter\Mat1; D:\Cutter\Mat2
Sub-folders are included automatically, so pointing at a parent folder is enough.
Folders that do not exist are silently dropped when you save. If you save and a folder disappears from the list, the path was mistyped or the drive was not connected.
If no watch folders are configured at all, the Ingester tells you so and offers to open the Settings dialog.
Video file extensions
The file types the Ingester treats as video, separated by semicolons — by default
.mxf; .mp4. Anything else appearing in a watch folder is ignored.
This list exists so that the working files a cutter leaves behind — project files, thumbnails, temporary files — never become upload jobs.
Extensions are compared case-insensitively and are stored in lower case.
File chunk size (in MB)
How large each piece of a multi-part upload is. Available values: Auto, 5, 10, 25, 50, 100, 150 MB. The default is Auto.
- Auto (recommended). The Ingester works out the chunk size for each file from its size and the number of parallel connections, between 10 and 50 MB. Once an upload has used Auto, the entry shows the size it chose last, for example Auto (last 25 MB).
- A fixed size is used for every file. Choose one only when support asks you to, or
when a Network Report suggests one:
- Slow or unreliable connection → smaller chunks. If a chunk fails, only that chunk has to be re-sent.
- Fast, stable connection → larger chunks. Fewer round trips means less overhead.
A 100 MB file uploaded with a 10 MB chunk size is sent as 10 chunks.
An Ingester upgraded from an older version that was set to the old default, 10 MB, switches to Auto. A different size you had chosen yourself is kept.
Parallel connections
How many chunks of a file are uploaded at the same time. Available values: Auto, 4, 8, 10, 16, 20, 32. The default is Auto.
- Auto (recommended). The Ingester learns the best number for the venue network from how fast its uploads go. It starts at 10, tries more connections while that makes uploads meaningfully faster, and steps back when the network starts dropping or refusing chunks. Every 20 uploads or so it tries one step up again, in case the network has improved. When the PC is moved to another venue network, it starts learning again. The entry shows the number in use right now, for example Auto (now 16).
- A fixed number is used for every upload and switches the learning off. Choose one only when support asks you to, or when a Network Report suggests one.
More connections make a fast link faster, but on a weak or congested link they only cause more failed chunks.
Upload rate limit (Mbps)
A ceiling on how fast the Ingester may upload, in megabits per second. 0 means
unlimited, which is the default. Any value you enter below 5 is raised to 5.
Use this when the venue's internet connection is shared with something that must not be starved — a live stream, scoring system or commentary feed. Without a limit the Ingester will happily consume the entire uplink.
The limit applies to the whole program, not per job, so it holds no matter how many uploads are running.
Setting a limit also sets the number of parallel connections, whatever Parallel connections says: one connection per 10 Mbps of the limit, at least 1 and at most 4 — for example 2 connections for a 20 Mbps limit. Opening many connections you cannot feed only adds overhead. While a limit is set, Auto (now …) shows this number, and Auto does not learn from the uploads.
Processing Settings
Deinterlace
Older broadcast cameras record interlaced video, where each frame is made of two half-images captured a fraction of a second apart. Played back on a computer screen this produces visible comb-like artefacts on movement. Deinterlacing removes them during encoding.
Two independent rules decide whether a file is deinterlaced:
| Control | Effect |
|---|---|
| Default | When ticked, every video is deinterlaced. |
| With Name + text box | When ticked, a video is deinterlaced if its file name contains the text in the box. The default text is .mxf, which effectively means "deinterlace everything recorded as MXF". |
Either rule is enough to trigger deinterlacing.
There is also a third, automatic path: if neither rule matched and the Video CutterV2's
companion .json file explicitly marks the recording as not progressive, the
Ingester turns deinterlacing on by itself. The camera knows better than a file-name
rule, so its own flag wins when it is available.
Deinterlacing can also be toggled per job in the Contest Data form.
Raise priority when filename contains
If a file name contains this text, the resulting job is created with a higher priority — priority 4 (High 2) instead of the default 5 (Medium 1) — and is processed before the others. Upper and lower case are ignored when matching.
The typical use: two cameras record every fight, front and rear, but the front angle
is the one people want to watch first. Entering front here means front-angle files
jump the queue while rear-angle files follow behind.
Leave it empty to disable the boost. See Job priority for the full picture.
Ignore Canceled
Controls what happens to files you have cancelled when the watch folders are scanned again.
| State | Behaviour |
|---|---|
| Ticked (default) | A cancelled file is remembered and is not picked up again. |
| Unticked | A cancelled file is treated as new and a fresh job is created for it. |
Leave it ticked in normal operation — otherwise a file you deliberately cancelled comes straight back on the next scan. Untick it temporarily when you cancelled a batch of files by mistake and want them all re-queued.
Overlay
Overlay image URL
A web address pointing at an image — typically a sponsor or broadcaster logo — that is burned into the encoded video by the platform's encoder.
Rules:
- It must be a full
http://orhttps://address. Local file paths such asD:\logos\sponsor.pngare rejected, because the encoder runs in the cloud and cannot reach your disk. - Leave it empty for no overlay.
- The Open URL button opens the address in your browser so you can confirm the image is reachable and is the right one.
The URL is stored with each job as it is created. Changing it affects new jobs only — jobs already in the queue keep the overlay they were created with.
If the address is invalid, the Ingester writes OVERLAY IMAGE WILL NOT BE ADDED TO THE
ENCODER DATA! to the log and continues without an overlay rather than failing the job.
Support
Network Report
The Network Report button measures the venue's internet connection to the upload storage, which takes about 6 minutes, and saves the result as a file to send to support and to the venue's internet provider. When it finishes, a summary shows the most important numbers — including a suggested File chunk size and Parallel connections — and Windows Explorer opens with the saved file selected.
While the report runs, uploads that have not started yet wait until it ends; an upload already running carries on.
The report only measures: it never changes any setting. See Network Report for what it measures and how to read it.
Settings on the main window
Two settings are not in the Settings dialog because you change them while working:
WATCHER / WORKER
The two toggle buttons at the top of the main window switch the Watcher and Worker roles on and off. They take effect immediately and are saved automatically.
Switching Worker off is the normal way to pause uploading — for instance to free the connection during a live stream — without losing the queue. Jobs keep accumulating and are uploaded when you switch it back on. While worker is off and jobs are waiting, the WORKER button blinks as a reminder.
Advanced settings (settings.json only)
The settings below have no field in the Settings dialog. Edit
C:\FairReplay\Ingester\settings.json with the Ingester closed, then start it
again — the Ingester rewrites the whole file whenever it saves (after Save settings,
after toggling WATCHER or WORKER, and when you fold a group or resize a column), so edits
made while it is running are lost.
| Setting | Default | What it does |
|---|---|---|
MaxEncodeThreads | 4 | How many encoding workers run in parallel. Clamped to 1–5. |
DefaultPriority | 5 | The priority given to a new job when no priority boost applies. See Job priority. |
EncoderQueueId | not set | Routes encode requests to a specific encoder queue on the platform. |
ApiRequestTimeoutSeconds | 120 | How many seconds the Ingester waits for the platform to answer one request — for upload links, finalising an upload or an encode request — before treating it as failed. Uploading the chunks themselves is not affected. |
The file also keeps what you set elsewhere in the program. Change these in the program, not in the file:
| Setting | Default | What it holds |
|---|---|---|
ChunkSize | "Auto" | File chunk size: "Auto" or a number of MB. |
MaxDegreeOfParallelism | "Auto" | Parallel connections: "Auto" or a number. |
UploadLimitMbps | 0 | Upload rate limit in Mbps; 0 is unlimited. |
IsWatcher, IsWorker | false | The saved state of the WATCHER and WORKER buttons. |
UiLanguage, UseDarkTheme | English, true | The saved state of the Appearance settings. |
JobGridFolded | not set (Done and Cancelled folded) | Which groups of the job grid you left folded. |
JobGridColumnWidths | not set | The widths you gave the job grid's columns. |
Version | — | Which one-time upgrades of the file the Ingester has already made. Never edit it. |
A few further entries exist in settings.json that are not listed here. They are
development and testing switches rather than operator settings, and changing them can
alter what is published to the platform. If you find one you do not recognise, leave it
alone and ask the Control Room.