Fig. 1 — Preferences. Placeholder; replace with assets/img/preferences.png.

How settings are stored and applied

Where the file is

Everything on these pages lives in config.ini in the per-user configuration directory; the dialog prints the path at the bottom left. Nothing is written to the installation folder, so an update or a move keeps the configuration, and two users on one machine keep their own. The file is plain INI text: [Section] headings and Key=Value lines, which is why every table on this page names the key as Section/Key.

When a change takes effect

OK saves every page and then hands the whole configuration to the running application, so most changes are live before the dialog has closed: thresholds, alarm recipients, report schedules, archive limits, the web server. Three groups are the exception:

Change	What happens
Web server / WebSocket port, TLS certificate	The listening socket is rebuilt. Open browser sessions and stream URLs drop and have to be reloaded.
Ribbon or menu bar	Applied at the next start; the toolbars are built once.
Anything that changes the licensed feature set	Read at the next start.

Cancel discards the whole dialog, not only the page in front of you. A password typed into the Web Server Login page is written on OK and never before.

Editing the file by hand

Legitimate for the handful of keys the dialog does not expose (see the last section) and for copying a configuration between machines. Close the application first: it writes the file on OK and on shutdown, and the later write wins. Every value is range-checked when it is read, so a typo produces the default rather than a schedule that fires every second.

Starting with -reset ignores the stored window positions and layouts — the way out of a layout that has moved off-screen. It does not touch the settings on these pages.
A copied configuration carries the web login credential with it. It is bound to the machine only as far as the file is; treat it like a password file.

Application Preferences

Fig. 2 — Preferences, Application Preferences. Placeholder; replace with assets/img/prefs-application-preferences.png.

Directories and file names

Control	Key	Default	Effect
Recording Dir	`General/RecordingDir`	system video folder	Target for recordings and exports. Put it on the fastest disk with room to spare; a TS recording of a full multiplex is roughly 10 GB per hour.
Temporary Dir	`General/TempDir`	application temp	Scratch space for demuxed segments, report attachments and archive playback. Hundreds of files per minute pass through here — a network drive is the wrong choice.
Rec. Scheme	`General/RecordingScheme`	built-in	Template for recorder file names. Understood variables: `%device%`, `%frequency%`, `%channel%`, `%date%`, `%time%`, `%year%`, `%month%`, `%day%`, `%hour%`, `%minute%`, `%second%`, `%computer%`.

A scheme worth copying for unattended use is %computer%_%channel%_%year%%month%%day%_%hour%%minute%: it sorts chronologically in a file listing and still says which box and which channel produced it.

Decoding and power

Control	Key	Default	Effect
Use Hardware Acceleration	`General/UseHWAccel`	on	Lets the player decode on the GPU. Switch it off when the preview tears, shows green blocks or the display driver restarts — a class of fault that comes from the driver, not from the stream. Analysis, loudness and the HEVC Analyzer never use it.
Allow sleep mode	`General/AllowSuspend`	on	Off keeps the machine awake while an input is open. The one setting to change on an unattended monitoring box — a box that sleeps records nothing and answers no scrape.
Region	`General/Satlist`	0	Which channel table the tuner bar offers. Affects the channel names and centre frequencies, not the tuner itself.
Hybrid senders	`General/LoadHybridSenders`	on	Also resolves services whose components arrive from a broadband origin instead of the broadcast. Off keeps the service list to what is really on air, which is sometimes what you want to prove.

Stream workarounds

Three switches for transmissions that do not behave. All of them change what the tool passes on, so they belong in a note next to any measurement made with them.

Control	Key	Default	Effect
Drop broken packets	`General/DropBrokenPackets`	off	A/331 section 3.10.3: discards ALP packets that fail their own check instead of feeding them to the reassembler. Switch on when a faulty transmitter floods the log with reassembly errors and hides everything else. The dropped packets no longer appear as errors — so the fault becomes invisible too.
Always mux to transport stream	`General/AlwaysUseMuxer`	off	Runs the TS muxer even when nothing is reading its output. Only useful when downstream equipment expects a continuous stream regardless of what the UI shows.
Remove filler packets	`General/RemoveFillerPackets`	off	Strips stuffing from the TS output. Saves rate on a link, but the output is then no longer a bit-exact record of the input.

Emergency alerts

Control	Key	Default	Effect
Emergency Alert pop-ups only for current alerts	`General/AutoDisplayMessage`	on	Shows an AEAT alert as a pop-up while it is current, and stays quiet for one that has expired. The EAS widget keeps the full list either way, and the alert is recorded in the history regardless.

Presentation

Fig. 3 — Preferences, Presentation. Placeholder; replace with assets/img/prefs-presentation.png.

Control	Key	Default	Effect
Use Ribbon toolbar	`General/UseRibbonBar`	on	Ribbon or classic menu bar. Both carry the same commands, and the menu bar is the smaller target on a 1280-wide screen. Needs a restart.
Font size slider	`General/Font`	system size	Scales the interface font. The sample text below the slider is rendered at the chosen size, so drag until that line is comfortable at your viewing distance — a wall-mounted box wants two or three steps more than a desk.
Automatic resize of the treeview	`General/AutoResizeColumns`	off	Fits tree columns to their content on every rebuild. Comfortable while browsing one lineup, restless on a stream whose service list keeps changing, because the columns then move under the cursor.
Clear the message window when tuning	`General/ClearTune`	off	Empties the log on every tune or input change. Gives a clean sheet per measurement, and throws away the errors that explain the previous one. Leave it off while chasing an intermittent fault.

Network Settings

Two unrelated things share this page: the multicast input, and the servers this application offers to other machines.

Fig. 4 — Preferences, Network Settings. Placeholder; replace with assets/img/prefs-network-settings.png.

Multicast input

Control	Key	Default	Effect
Address, Port, Protocol	`Network/Address`, `Port`, `Proto`	built-in	The group the network input joins. The fields accept digits and dots only, so a typo cannot become a hostname lookup.
NIC	`Network/NIC`	automatic	Interface to join on. Name it explicitly on a machine with more than one network — automatic follows the default route, which is rarely the measurement network, and the symptom is an input that stays silent while the switch shows traffic.
Network caching	`General/Caching`	2000 ms	Player-side buffer for network input. Higher rides over jitter, lower shortens the delay between air and screen. Analysis is not buffered by this — only the preview.

Web server

Control	Key	Default	Effect
Enable web server	`Network/UseWebServer`	off	Serves the dashboard, the JSON endpoints, the live screenshot, the Prometheus metrics and the tuner control.
Port	`Network/WebserverPort`	8000	Changing it rebuilds the socket and drops open sessions.
Web directory	`Network/WebserverDir`	`public_html` in the resource folder	Where the pages come from. A page dropped in here appears on the index automatically, described by its own `<title>`. The login page is generated inside the application, so a locked server cannot be opened by putting a file here.
WebSocket port	`Network/WebsocketPort`	built-in	Push channel the dashboard uses for live values. Same socket-rebuild behaviour as the web port.

With the login off, all of that is open to anyone who can reach the port — including tune.htm, which changes the receiver state. Either switch on the login on the next page, or keep the port on a network only your own equipment sits on.
The WebSocket has no login of its own. In a build without the authentication hook it is switched off while the login is on, and the message log says so at start.

DASH and HLS output

Control	Key	Default	Effect
DASH server	`Network/UseDashServer`	off	Republishes a received service as DASH, so a browser or an external player can watch what the receiver sees. Segments are passed through, not re-encoded.
DASH memory cache	`Network/DashMemoryCache`	on	Keeps segments in RAM. Off writes them to the temporary directory instead: less memory, more disk traffic.
HLS streaming	`Network/UseHLSStreaming`	off	The same as a transport stream. This is the variant that plays in browsers and in VLC without extra components.

One operator account in front of the whole web server. It is configured here and only here: whoever runs the application owns the machine, so there is no setup flow over HTTP.

Fig. 5 — Preferences, Web Server Login. Placeholder; replace with assets/img/prefs-web-server-login.png.

Account

Control	Key	Default	Effect
Require a login	`WebAuth/Enabled`	off	Puts the gate in front of every page and endpoint. Stays off until a password is stored — switching on a login nobody can pass would lock the operator out of their own dashboard, so the dialog refuses it and says why.
User	`WebAuth/User`	`admin`	Account name, compared case-insensitively. If a login is rejected although the password is right, this is the first field to check — the message log names the configured user.
Password, twice	`WebAuth/Salt`, `Hash`, `Iterations`, `Algo`	—	Written only when both fields match; a mismatch leaves the old password in place and says so. Stored salted, never in clear text, and the fields are emptied after OK.

Sessions

Control	Key	Default	Effect
Session length	`WebAuth/SessionMinutes`	12 h	Idle timeout, refreshed on every authenticated request — an active tab stays signed in, an abandoned one does not. A hard ceiling of 7 days applies on top, which no amount of activity extends.

Sessions live in memory. Restarting the application signs everybody out, which is the honest behaviour for a monitoring box.
Changing the password invalidates it immediately for new logins; sessions already signed in run to their timeout.

TLS

Control	Key	Default	Effect
Use TLS	`WebAuth/UseTLS`	off	Serves HTTPS. Stays off until certificate and key both exist as files, and the dialog says so rather than starting a server that cannot answer.
Certificate, key, host name	`WebAuth/CertFile`, `KeyFile`, `CertHost`	—	PEM files. Create certificate writes a self-signed pair for the host name given, using the OpenSSL binary that ships with the product.

A self-signed certificate encrypts the traffic but produces a browser warning, and that warning trains operators to click through warnings. On a network where it matters, use a certificate from your own authority.

Scripts, players and scrapers

What a browser does with the login form, other clients do with HTTP Basic auth on the same account — curl, VLC and a Prometheus scrape all keep working:

curl -u admin:secret http://box:8000/services.json
curl -u admin:secret http://box:8000/metrics

In prometheus.yml that is a basic_auth block on the job. A request that carries credentials and fails gets a plain 401, never a redirect to the login page — otherwise a wrong password would look to a scraper like a working server serving markup.

Everything is reachable without asking: the gate is off. Either no password is stored, or the switch is off — the System Status widget shows both facts separately, and tvx_web_login_enabled in the metrics is 0.
The password is refused although it is right: set it again on this page. A credential stored by an older build is rejected on purpose, with a line in the message log naming the reason.
The login seems to hang: after five failed attempts from one address the answer is delayed, doubling up to 30 seconds. The counter clears after 15 minutes without an attempt, or on a restart.
The form comes back after a correct password: a browser that rejects the session cookie. Check that the URL host matches what the browser has stored, and that the clock is right.

AC-4 Decoder Controls

How AC-4 is rendered for the player and for the loudness measurement, and whether it is transcoded for output.

Fig. 6 — Preferences, AC-4 Decoder Controls. Placeholder; replace with assets/img/prefs-ac-4-decoder-controls.png.

Rendering

Control	Choices	Effect
Output Channel Configuration	Auto, LoRo, LtRt, Pro Logic II, Headphone, Speaker Virtual, 5.1, 5.1.2	Layout the decoder renders to. Auto follows the presentation. Pick 5.1 or 5.1.2 to hear what a multichannel presentation really carries; the two virtualisers are for judging what a consumer hears on headphones or a soundbar.

Dynamic range control

Control	Choices	Effect
Mode	Default (Home Theatre), Flat Panel, Portable - Headphones, Portable - Speakers, Disabled	Which DRC profile to apply. Disabled reproduces the mix as transmitted; the others are what the matching class of consumer device would do with it.
Output Reference Level	dB	Reference level the DRC works against. Only meaningful while a profile is active.

Dialogue enhancement

Raises dialogue against the bed where the stream carries the metadata for it, with a gain in dB and a Default button back to the neutral value. A rendering aid for listening, not a measurement tool.

What this does to a measurement

Loudness and true peak are measured on the decoded audio. A DRC profile, dialogue enhancement or a downmix therefore change the numbers. For a compliance measurement set the mode to Disabled, dialogue enhancement off, and the channel configuration to what the service actually carries.
The measured value is compared against the metadata the encoder signalled, and the difference is what the loudness deviation rule reports. Rendering settings move the measured half only.

Transcoder (AC-4 to AAC)

Control	Effect
Enable AC-4 to AAC Transcoding	Produces AAC for the TS and HLS output and for equipment that cannot take AC-4. It costs one decoder instance per service, which is a Dolby licence question rather than a CPU one — the System Status widget counts the live instances.
Output Channels	Channel count of the AAC output. Downmixing to stereo here is the usual choice for a monitoring feed.
Bitrate per Channel	Rate of that output, per channel rather than in total, so the value does not have to be recalculated when the channel count changes.

Where the transcoder runs, the loudness measurement gets its PCM for free — the decoder is already paying for itself. That is why a box used for loudness compliance usually has this on.
Multi-service loudness needs the AC-4 Multi feature. Without it, one service is measured at a time; with it, the hidden key Loudness/MaxMonitorDecoders (default 4, clamped to 1…8) caps how many run in parallel.

Video Wall HEVC Decoder

The wall decodes every service at once, so it is deliberately allowed to be sloppy. These controls trade picture quality for the ability to keep up, and none of them affect the Player, the loudness path or the HEVC Analyzer.

Fig. 7 — Preferences, Video Wall HEVC Decoder. Placeholder; replace with assets/img/prefs-video-wall-hevc-decoder.png.

How much is decoded

Control	Key	Default	Range	Effect
Decode rate	`VideoWall/DecodeRate`	100	1…100 %	Share of arriving segments that are decoded at all. Halving it halves the CPU cost and the update rate with it.
I-frames only	`VideoWall/IFrameOnly`	on	—	Key frames only. The cheapest way to keep a large wall moving; motion looks stepped. A service whose segments carry no key frame shows nothing while this is on — which is a stream property worth knowing about.
Worker threads	`VideoWall/WorkerThreads`	1	1…32	Threads per decoder instance. Raise it on a wall with few, large services; leave it at 1 for many small ones, where the parallelism already comes from the number of tiles.

Filters and faulty pictures

Control	Key	Default	Effect
No deblocking	`VideoWall/NoDeblocking`	on	Skips the deblocking filter. Faster, with visible block edges — fine for a presence check, wrong for judging quality.
No SAO	`VideoWall/NoSAO`	on	Skips sample adaptive offset. Same trade.
Show faulty pictures	`VideoWall/ShowFaultyPics`	off	Displays pictures the decoder flagged as damaged instead of dropping them. Switch on when hunting an intermittent transport fault: the corruption pattern says whether packets were lost or a segment arrived truncated.

Timing

Control	Key	Default	Effect
Timeout	`VideoWall/Timeout`	4 s	How long a tile waits for a decodable picture before it goes blank. Too short on a channel with sparse key frames makes healthy services flicker.
Max latency	`VideoWall/MaxLatency`	0 (no limit)	How far behind live a tile may run before frames are skipped to catch up.

Mail Notification

Fig. 8 — Preferences, Mail Notification. Placeholder; replace with assets/img/prefs-mail-notification.png.

When a mail goes out

Control	Key	Default	Effect
Send mail	`Mail/Enabled`	off	Master switch for alarm mail.
From which level	`Mail/SendMail`	errors	Lowest severity that triggers one. Warnings included means a marginal signal will mail regularly — worth it while commissioning, tiring in steady operation.
Delay between mails	`Mail/DelayMin`	10 min	Throttle: at most one alarm mail per interval, so an alarm storm cannot fill a mailbox.
Bundle messages	`Mail/MailBundling`	on	Collects what happened during the throttle window into the next mail instead of dropping it. Leave on, or the throttle silently loses alarms.
Attach report	`Mail/AttachReport`	on	Adds the compliance report, so the mail carries the state and not just the sentence.

The throttle applies to alarm mail only. Scheduled reports and the availability sheet have their own sender: they go out even when this switch is off, and they never consume the alarm throttle. Alarm escalation does respect this switch — but ignores the throttle, because a rung that exists because ten minutes went by must not be dropped by a ten-minute throttle.

Recipient and server

Control	Key	Default	Effect
Receiver, Subject	`Mail/Receiver`, `Subject`	—	Where alarm mail goes and what it is called. Put the box name in the subject when several boxes mail the same address — the body says which channel, the subject line is what shows in a notification.
Use built-in server	`Mail/DefaultSettings`	on	Sends through the vendor SMTP server. Convenient, and it means alarm mail leaves your network to a third party. Off exposes the fields below.
Host, Port, User, Password	`Mail/Host`, `Port`, `Username`, `Password`	—, 465	Your own server. The password is stored encrypted rather than in clear text.
SSL, TLS	`Mail/SSL`, `TLS`	both on	465 with SSL is the usual combination; 587 normally wants TLS without SSL.

NOC Alarm Forwarding

Pushes every alarm off the box, so a monitoring system rather than a person notices first. All three transports can run at once, and each has a Test button that uses the values currently typed into the dialog rather than the ones the application is running with.

Fig. 9 — Preferences, NOC Alarm Forwarding. Placeholder; replace with assets/img/prefs-noc-alarm-forwarding.png.

What is forwarded

Control	Key	Default	Effect
Also forward warnings	`RemoteAlarm/IncludeWarnings`	on	Errors always leave the box; warnings are optional, because on a marginal signal they are frequent enough to be noise in a trap receiver.

Alarms that a maintenance window suppresses, or that an operator has already acknowledged, are not forwarded — they are still written to the log and the history. Suppressing the notification is the point; suppressing the record would be falsifying one.

SNMP trap

Control	Key	Default	Effect
Send traps	`RemoteAlarm/SnmpEnabled`	off	SNMPv1 traps, enterprise-specific.
Trap destination	`RemoteAlarm/SnmpHost`	—	Host name or address of the trap receiver.
Community	`RemoteAlarm/SnmpCommunity`	`public`	As configured on the receiver.
Enterprise OID	`RemoteAlarm/SnmpEnterprise`	placeholder	Replace this before production. The default sits in the private-use arc and collides with everything else that uses it; derive one from your own IANA Private Enterprise Number. The dialog spells this out on the page.

Syslog

Control	Key	Default	Effect
Send syslog	`RemoteAlarm/SyslogEnabled`	off	RFC 3164 over UDP.
Host, Port	`RemoteAlarm/SyslogHost`, `SyslogPort`	—, 514	Collector address.
Facility	`RemoteAlarm/SyslogFacility`	local0	local0…local7 — the range an application is allowed to use.
Tag	`RemoteAlarm/SyslogTag`	`TvXplorer`	Program name in the log line. Put the box name in it when several boxes share a collector.

Severity is mapped from the alarm level, so a collector can filter on it without parsing the text.

Webhook

Control	Key	Default	Effect
POST alarms as JSON	`RemoteAlarm/WebhookEnabled`, `WebhookUrl`	off	One HTTP POST per alarm, body as JSON. The route into a chat system or a ticket queue.

Queue and counters

Sending is asynchronous: an alarm is queued and a worker thread delivers it, because doing network I/O on the receive path would drop packets. Consequences worth knowing:

A dead receiver slows nothing down. When the queue is full, alarms are dropped and counted rather than blocking the measurement.
The page shows what was sent, what failed and what was dropped since start; the same three numbers are in the System Status widget and in the metrics.
A successful UDP test proves the packet left this machine, nothing more. Check the receiver.

Alarm Escalation

The alarm workflow: whether an alarm can be marked as seen at all, and who is told when nobody does. Maintenance windows are not here — an operator adds one minutes before pulling a transmitter, so they live in the Alarms view, next to the alarms they silence.

Fig. 10 — Preferences, Alarm Escalation. Placeholder; replace with assets/img/prefs-alarm-escalation.png.

The workflow switch

Control	Key	Default	Effect
Alarm workflow active	`AlarmWorkflow/Enabled`	on	Allows an acknowledgement or a maintenance window to silence a notification. Off restores the older behaviour: every alarm notifies, nothing can be marked as seen. On a fresh installation the switch changes nothing by itself — with no window configured and nothing acknowledged, every alarm notifies exactly as before.

The ladder

Three rungs, each with the same four questions: after how long, how often, to whom, and by which route. All three ship disabled, so an update sends nothing nobody asked for.

Control	Default	Effect
Rung active	off	Enables this rung.
after (minutes)	5 / 20 / 60	Measured from when the alarm first appeared, not from the previous rung — so a chain reads the way it is spoken out loud: "after five minutes me, after twenty the duty phone". The highest rung that is due is the one delivered, so an hour-old alarm after a restart starts at the top instead of climbing one tick at a time.
repeat every (minutes)	0 / 0 / 30	0 fires the rung once. A value keeps it ringing while the alarm stays unacknowledged.
Mail, to	on / off	Mail for this rung; an empty address uses the alarm address from the Mail page.
NOC transports	off	Also sends the rung through the transports on the NOC page.

Everything is stored per rung as Escalation/Stage0…Stage2.

What stops an escalation

Acknowledging the alarm in the Alarms view. That silences the notification, never the measurement.
The alarm clearing by itself.
A maintenance window covering it.
Escalation is in addition to the notification the alarm already sent, and mail for it respects the Mail page master switch but not its repeat delay.
Timing restarts after an application restart, because the incident does.

Three things that all write to disk: the scheduled compliance report, the long-term recorder behind every trending view, and the caption journal.

Fig. 11 — Preferences, Reports and Trending. Placeholder; replace with assets/img/prefs-reports-and-trending.png.

Schedule

Control	Key	Default	Effect
Automatic reports	`Reports/Enabled`	off	Master switch.
Every N minutes	`Reports/Schedule`, `IntervalMin`	60	Measured from the last run. Switching this on produces one report immediately, so it is visible that it works.
Daily at	`Reports/Hour`, `Minute`	06:00	Before the morning shift looks at it.
Weekly on	`Reports/DayOfWeek`	Monday	Weekday plus the same time of day.
Next report	—	—	Computed from the same stored timestamp the scheduler uses, so the preview cannot disagree with what will happen.

Daily and weekly follow the rule "the moment has passed and we have not run since". A machine started at 09:00 therefore still sends the 06:00 report instead of losing the day — and it does not send it twice.

Archive and delivery

Control	Key	Default	Effect
Folder, Open folder	`Reports/OutputDir`	config dir	Where reports land.
Keep last N	`Reports/KeepFiles`	30	Prunes the oldest compliance reports. 0 keeps everything. Availability sheets are named per month and are not touched by this.
Mail the report, to	`Reports/MailEnabled`, `MailTo`	off	Uses the SMTP settings from the Mail page but not its master switch or its throttle.
Attach application report	`Reports/IncludeAppReport`	off	Adds the full internal state dump as a second attachment — what support asks for.
Generate report now	—	—	Applies the page first and then takes the exact path the schedule takes. A test that avoids the real path is worth little.

Control	Key	Default	Effect
Record trending data	`Trending/Enabled`	on	One sample per interval per service, written to a day file. Everything historical reads from it: the Trend view, the day balance in the compliance report, and the availability report.
Folder	`Trending/Dir`	`trend` beside the config	Changing it closes the current day file, so nothing is appended to the old location.
Keep days	`Trending/KeepDays`	built-in	Retention. A day is a few megabytes per service.

Switch it off and the history stops there. An availability report for a month with the recorder off has nothing to state, and says so rather than reporting 100 %.

Caption journal

Control	Key	Default	Effect
Record caption text	`Captions/Journal`	on	Stores each new cue as broadcast, searchable per day in the Caption Log. On by default because an archive that has to be switched on before the complaint arrives is worthless. It is small: a talking channel produces a few thousand cues a day.
Keyword watch	`Captions/Keywords`	empty	Comma-separated words that raise an alarm when they appear in a caption. Set per site — "tornado, evacuation, boil water". One alarm per word per service until a different word hits.

The journal keeps running even with threshold monitoring switched off: an archive with holes is not an archive.

Availability Report

The monthly SLA sheet — availability in percent, outage minutes, number of outages, the longest one and MTTR per service, as HTML plus the same figures as CSV. This is the page an operator hands to their own customer.

Fig. 12 — Preferences, Availability Report. Placeholder; replace with assets/img/prefs-availability-report.png.

Schedule

Control	Key	Default	Effect
Produce a monthly report	`Reports/SlaEnabled`	off	Master switch.
on day of month	`Reports/SlaDayOfMonth`	1	Capped at 28 on purpose: a report scheduled for the 30th would never fire in February, and a monthly sheet that silently skips a month is worse than one that arrives two days early.
at	`Reports/SlaHour`, `SlaMinute`	07:00	Time of day.
Next report	—	—	Names the moment and the month it will cover, so there is no doubt which period is meant.

A scheduled run always covers the month that just ended; the month in progress is never reported on, because a sheet saying "so far this month" gets read as a full month. Same restart rule as the daily report: a machine that was off on the 1st sends it when it comes back. For any other period use Availability report… in the menu, which asks for yyyy-mm.

Delivery

Control	Key	Default	Effect
Mail the report, to	`Reports/SlaMailEnabled`, `SlaMailTo`	off	HTML and CSV as attachments, so the recipient can paste the figures into their own reporting.
Generate last month now	—	—	Same path as the schedule, and it deliberately does not move the schedule's own timestamp — a manual sheet for an old month must not mark this month as done.

The file is named after the month it reports on (availability-2026-08.html), not after the day it was written, so a re-run overwrites rather than duplicates.

How the numbers are made

Five buckets, and the difference between them is what makes the sheet honest:

Bucket	Counts as
On air	Available.
Disturbed — black, frozen, a dead channel, encrypted	Available, and reported separately. It was on air; hiding it gets found out, calling it an outage sells you short.
Unavailable — no data, no lock, no service	The outage the percentage is against.
Not monitored — recorder off, day file missing, service absent	Neither. Always printed: a percentage that treats "we were not looking" as "it was fine" is the one number a customer must never be handed.
Planned — inside a maintenance window	Removed from the calculation entirely.

Only windows that apply to every alarm category count as planned air time. A window that silences audio alarms during a repair says nothing about whether the channel was on air, and using it to erase downtime would be exactly the kind of quiet correction that makes an availability figure worthless.
MTTR is outage time divided by the number of outages. An outage spanning midnight is counted once per day, because a day is the unit the measurements are stored in — the sheet says so too.
The figures come from the recorded trending data, so trending must have been on for the month in question.

A/V Archive

The proof-of-airing ring buffer: received segments are kept on disk exactly as they arrived, so a complaint can be answered with the picture and sound that were really transmitted. Nothing is re-encoded, which is what makes it evidence rather than a rendering.

Fig. 13 — Preferences, A/V Archive. Placeholder; replace with assets/img/prefs-a-v-archive.png.

What is recorded

Control	Key	Default	Effect
Folder	`Archive/Dir`	beside the config	Put this on its own disk. It is the one feature that will fill whatever it is given.
Services	`Archive/Services`	empty = all	Restricts recording to named services. The cheapest way to make the budget last.
Start recording when the application starts	`Archive/AutoStart`	off	Deliberately off. Applied once at start, so opening this dialog never starts or stops a recording behind your back.

How much is kept

Control	Key	Default	Effect
Continuous	`Archive/Mode`	continuous	Keeps everything until a budget below is reached, then drops the oldest.
Triggered by alarms only	same key	—	Keeps only the window around an incident. Turns days of disk into weeks of evidence, and misses anything no rule fired on.
Pre-roll, post-roll (s)	`Archive/PreRollSec`, `PostRollSec`	—	How much before and after a trigger is protected. Pre-roll is why the buffer runs even in triggered mode.
Keep incident for (min)	`Archive/TriggerKeepMinutes`	—	How long a protected window survives the retention budget — long enough that somebody gets to look at it.
Disk budget (GB), Keep at most (hours)	`Archive/MaxGB`, `KeepHours`	—	Whichever limit is reached first prunes the oldest material.

The Archive widget plays the buffer back on a time axis and exports a clip as MP4. Marked incidents are protected from the budget, so "the pictures around 03:47" survive even when everything else has rolled off.

Speech Detection

A voice activity detector on the decoded audio. Its purpose is not to display speech but to gate the caption rules: "no caption text for three minutes" is a fault only if somebody was talking. Without the gate, every music bed and every silent slate looks like a caption failure.

Fig. 14 — Preferences, Speech Detection. Placeholder; replace with assets/img/prefs-speech-detection.png.

Switching it on

Control	Key	Default	Effect
Enable	`VAD/Enabled`	off	Needs the model file below; without it the detector stays off and says so.
Model path	`VAD/ModelPath`	empty	The Silero ONNX model file that ships with the product.
Gate CAPTION BLANK	`VAD/GateCaptionBlank`	on	Reports blank captions only while there is speech. This is the reason the detector exists.
Threads	`VAD/Threads`	1	Inference threads. One is enough for a handful of services.

Sensitivity

Control	Key	Effect
Threshold	`VAD/Threshold`	How confident the model has to be. Raise it on a channel that reports speech during music, lower it on one with quiet dialogue.
Window (ms)	`VAD/WindowMs`	Length of the window the ratio below is measured over.
Minimum speech (ms)	`VAD/MinSpeechMs`	Shortest run that counts as speech at all — filters out single words in an effect.
Hangover (ms)	`VAD/HangoverMs`	How long speech is still assumed after the last detection, so a pause between sentences does not close the gate.
Minimum speech ratio	`VAD/MinSpeechRatio`	How much of the window must be speech before the gate opens.
Use centre channel	`VAD/UseCenterChannel`	On a 5.1 presentation dialogue lives in the centre, and using it alone is both cheaper and more accurate. Off mixes all channels — the setting for a stereo service.

The speech ratio is recorded in the trending data as its own lane, so the gate's decisions can be checked against a day afterwards instead of being taken on trust.

Logo Detection

Checks whether the station logo is in the picture — the cheap continuity check for "are we still watching the right channel", and the signal a break detector uses, since most logos disappear during advertising.

Fig. 15 — Preferences, Logo Detection. Placeholder; replace with assets/img/prefs-logo-detection.png.

Presence detector

Control	Key	Default	Effect
Enable	`LogoDetect/Enabled`	off	Master switch for the whole page.
Presence detector	`LogoDetect/DogEnabled`	on	Model-free: looks for a stable high-contrast area in the corner region. Cheap, robust, and it cannot say which logo it found.
Score, edge threshold	`LogoDetect/DogScore`, `EdgeThreshold`	tuned	How much structure has to be there. Raise them on a channel with a busy corner.

Model detector

Control	Key	Effect
Model, labels	`LogoDetect/ModelPath`, `LabelsPath`	Optional ONNX detector that can name what it found. Without it, only presence is known.
Score, IoU, max detections	`LogoDetect/Score`, `IoU`, `MaxDetections`	Confidence threshold, overlap suppression and the cap per frame.
Mean values, BGR order	`LogoDetect/MeanB/G/R`, `BGR`	Input normalisation. These have to match how the model was trained, or it detects nothing at all.

Hold times

Control	Key	Effect
Found hold, lost hold (ms)	`LogoDetect/FoundHoldMs`, `LostHoldMs`	How long a state has to persist before it counts. Without them a single dark frame would report the logo as gone, and a break would be reported as programme again after one frame.

Certificate Settings

How the LLS signature chain is checked — the part of the analysis that says whether the signalling really came from the station that claims it.

Fig. 16 — Preferences, Certificate Settings. Placeholder; replace with assets/img/prefs-certificate-settings.png.

Control	Key	Default	Effect
Root PEM file	`Certificates/PEMFile`	bundled	The trust anchors. Additional authorities belong in the `roots` directory next to it rather than pasted into this file, so an update does not overwrite them.
OCSP URL	`Certificates/OCSPUrl`	bundled	Responder asked whether a signing certificate is still valid. Reachability matters: with no route to it, the answer is "unknown", not "invalid".
Warn N days before expiry	`Certificates/Threshold`	30	When a certificate approaching its end raises a warning. 30 days is enough notice for a station to renew.

A chain that cannot be verified is reported as such, and the LLS widget shows where the chain broke — a missing intermediate looks different from an expired leaf.

Auto Start, Websocket, Debug Logging

Fig. 17 — Preferences, Auto Start, Websocket, Debug Logging. Placeholder; replace with assets/img/prefs-auto-start-websocket-debug-logging.png.

Auto Start

One switch per widget (AutoStart/<FormName>), so a box comes up showing what this installation is for. On an unattended box switch on exactly what the operator needs to see and nothing more: every open widget costs decoding, drawing or both, and the Video Wall costs the most.

Websocket Settings

Which measurements are pushed to the dashboard over the WebSocket. + and - add and remove values, Default restores the shipped selection, Reset All clears the list. Fewer values mean less traffic on a slow link; the dashboard simply shows nothing for a value it is not sent.

Debug Logging

Control	Key	Default	Effect
Logging Level	`Hardware/LogLevel`	3	Verbosity of the receive and hardware layer, 0…7. Raise it only while chasing a fault: at the top level the log fills faster than it can be read, and the lines that matter scroll away.

This is the driver and receive path only. What appears in the message log from the analysis — alarms, signalling findings, licence messages — is not affected by it.

License Manager and DRM

The License Manager page lists every installed key — the primary licence plus up to five add-on slots — with the features it grants and its expiry date, and is where keys are added and removed. The licensing chapter covers keys, activation and the periodic online check in full; only what belongs to this dialog is repeated here.

Fig. 18 — Preferences, License Manager and DRM. Placeholder; replace with assets/img/prefs-license-manager-and-drm.png.

A feature shown greyed out is one this build knows but your keys do not grant.
Removing the primary key keeps the add-ons in their slots; removing an add-on takes only its feature away.
Changes to the feature set reach the running application at the next start.
An expiring key warns 31, 14 and 7 days ahead and then daily. An expired add-on does not stop the application — its feature goes away and a message says which one.
The DRM / YubiKey page exists only in builds compiled with DRM. It selects the YubiKey slot (DRM/YubiKeySlot, default 9a) the CDM uses. Without the DRM feature in the licence the page stays hidden.

Keys the dialog never writes

A few values exist only in config.ini, on purpose: they are for a support case or a test, and a normal installation does not have them at all. Add them by hand under the section shown, with the application closed.

Key	Meaning
`General/OnlineCheckMinutes`	Shortens the licence online check for testing. It can only make the interval shorter than the product rule of 14 days; 0, garbage or anything longer falls back to the full interval. A shortened interval is written to the message log once per run, so it cannot travel unnoticed.
`General/KillCheckMinutes`	How often the published package list is fetched, so a build that was withdrawn stops itself instead of running until somebody restarts it. Default 6 hours, again only shortenable.
`Loudness/MaxMonitorDecoders`	How many AC-4 decoders may measure loudness in parallel. Default 4, clamped to 1…8, and only effective with the AC-4 Multi feature — no setting hands out seats the licence does not cover.
`WebAuth/Iterations`	Work factor of the stored web credential, written when a password is set. Lowering it makes the login cheaper and guessing cheaper with it.
`General/LastPos`, `General/LastDevice`	Housekeeping: timestamp of the last successful licence check, and the input that was open last. Not meant to be edited; deleting them costs nothing.

Everything else in the file is owned by this dialog. Hand-editing such a value is safe but pointless — the next OK writes it again.
Values are range-checked on load, so a typo produces the default rather than a schedule that fires every second or a threshold that never fires.

See also