Streams¶

The Streams screen is the node’s central workplace: a single list of the configured streams with their state, active input, bitrate, “Uptime” and the “CC” continuity error counter. The active input is marked by a number and a transport badge — #2 and, say, udp; the number is the input’s place in the redundancy list, the same one the input carries in the expanded row, in the stream editor and in the text of an alert (Source redundancy). Every row expands on a click and shows the stream’s inputs and outputs with their state, redundancy priority, notes and active alerts; an individual input or output can be paused and resumed from here, and the “Show in library” button next to the address opens the list of the other points of the domain on that address (Library — this feed). The reason an input or output failed is shown differently in the expanded row: while the point is failing right now — as a red line; when it is stopped — dimmed and with an age, “Last failure 3h 04m ago: …”; and a paused point has no line at all, which comes back only when it resumes. An input that has started working keeps no reason — the node erases it together with the time, and the line disappears. A dimmed line does not mean a fault: it is history, and on a healthy stream with redundancy it is normal under a stopped backup input. The age is the difference between the browser’s clock and the timestamp the node put there, so a clock discrepancy on either side shifts it. The notion of a stream and the delivery model are described in Transmission model: Stream, Sender, Receiver, Peer; SPTS processing — in SPTS streams, the MPTS multiplex — in MPTS streams.

The list is grouped by type: single streams (SPTS) form a common list, below it are the “MPTS streams” and “Adaptive streams” (ABR bundles) groups. The navigation and control facilities are placed above the list:

Search and filters: The “Find stream…” field searches by stream number, name, note and input/output address and highlights the matching row without shortening the list; under each result it is stated which field matched, and next to the name stands the number — #85 for a stream and ABR #3 for an adaptive set, because the two are numbered independently of each other. Searching by text starts at three characters, by number at the first one; while fewer than three characters have been typed only the number is searched, which is what the hint “Enter at least 3 characters or a stream ID” says. The number is matched from the start: 150 will find stream 1500 and will not find 4150, and the form #150 is equivalent to 150. First comes the exactly typed number, then the matches by text and only then the numbers for which what was typed is merely a beginning. The “Tags” filter limits the list by stream labels, the “SPTS / MPTS / Adaptive” switch shows or hides the type groups, and the “All / Active” segment hides paused streams. Arriving at the screen by a link that names a particular stream — from the node overview, from a graph, from the library, from the transcoders screen or from an adjacent node — resets all three filters at once, expands the row of that stream and scrolls the list to it: otherwise a filter left over from an earlier task could hide it. The browser going back to such an address, or opening it from a bookmark, counts the same way — except for the jump from the transcoders: that one expands the row and immediately removes itself from the address, so it does not end up in a bookmark, and going back with the browser leads to the transcoders screen instead. Switching the segment to “All” is visible on the screen, and the former value is easy to bring back — but it has to be brought back by hand: the segment is remembered by the browser, and after the jump it will stay at “All” the next time the screen is opened as well. Opening from the list itself leaves the filters alone: the row that was clicked is in plain sight anyway.
Actions on the selected stream: The header contains the actions applied to the expanded (selected) stream or ABR bundle: “Stream statistics” (Stream statistics), “Open in pipeline” (Pipeline), “Configure stream” (Configure stream) and “Delete stream”. The “+ New stream” button opens the creation window. The administrator can drag rows to change their order — among single streams and within the “MPTS streams” group, each inside its own bounds; ABR bundles are not reordered. Filters are no obstacle to reordering: the move is counted over the whole list, so streams hidden by a filter keep their relative positions. The same move is done with the Alt+↑ and Alt+↓ shortcuts (Keyboard operation); on a phone the order is only displayed.
Selecting several rows: In a window at least 1080 points wide, several rows are selected with the mouse: Ctrl``+click (on macOS ``Cmd``+click) adds a row to the selection or removes it from it, and ``Shift``+click takes the whole span. An expanded row counts as the current one and takes part in the gesture: after a click on one row and a ``Ctrl``+click on another, both are selected. An ordinary click while something is selected only clears the selection and does not expand the row; ``Esc does the same. The selection is homogeneous — either single streams, or MPTS streams, or ABR sets: an attempt to mix them is answered with “One selection holds one kind: streams, MPTS or ABR sets”, and in a narrow window the gesture is refused with the explanation “Group selection needs a wider window”. While rows are selected, the actions on a single stream are unavailable — they are marked “Acts on one row — click the row without Ctrl” — and dragging rows is suspended; what stays available is the “Open in pipeline” button, which opens the group view (Pipeline). Above the list a bar appears with a counter of what is selected, the number of rows hidden by the filter, a hint about the gestures and a “Clear selection” button. A row hidden by the filter does not lose its selection; a row that has disappeared from the node drops out of the selection, and the bar reports how many rows dropped out. More than twelve rows can be selected, but the group view will show the first twelve — the bar warns about this in advance.
State and alerts: A color state indicator, the stream attribute badges (CBR/VBR, scrambling, DRM protection, operation on the backup input, audio-only or video-only, codecs, TRACE) and the mark of active alerts. Alerts are bound to the stream and to its inputs and outputs (Alerts (alerter)); the TR 101 290 report and the deep analysis section are opened directly from the row.

The individual windows of the screen are described below.

New stream¶

The stream creation window. The type is selected with a switch: a single program (SPTS), a multiplex (MPTS) or an adaptive bundle (Adaptive); for SPTS the “Content type” is specified additionally. After an SPTS or MPTS stream is created, the editor opens immediately (Configure stream). No separate editor is opened for an adaptive bundle — the members and their bitrates are set directly in this window, because the bundle is built from already configured OTT streams. The differences between SPTS and MPTS are described in SPTS streams and MPTS streams, adaptive bundles — in Adaptive bundles.

Configure stream¶

The main stream editor. The settings are grouped into tabs; for MPTS streams the “OTT” tab is not shown.

Stream

Identification (name, display name, for SPTS — the stream type, note) and stream behavior: timeout, check interval, re-check of the main input, mosaic generation (Mosaic), EIT extraction into the EPG database (EPG Database) and the scrambling attribute for SPTS. For SPTS, EIT generation from the selected EPG source and its channel is configured here as well (EIT generator).

Inputs

The list of the stream sources with their priority and reservation (Source redundancy and distribution). The rows are numbered in order — #1 is the main one, the rest are backups in the same order. The administrator can edit the order — here or in the expanded row of the stream list: a row is moved by its handle, and from the keyboard by putting the focus on that handle and pressing Alt+↑ or Alt+↓. A hint above the list says the same; it appears when there is more than one input and editing is available. An added input always goes last, that is, a new source never takes the place of the main one. Adding and editing an input open the input and output editor (Input and output editor); an individual input can be paused. The muxer input is offered only in an empty list: in an MPTS stream it is added first, and while it is there the “Add input” button is disabled with the note “The muxer input must be the only input of the stream.” — a multiplexer has no input reservation. An MPTS stream that receives a ready multiplex over the network does not have this restriction: its inputs are ordinary and are reserved.

Outputs

Delivery of the stream over the transmission protocols (Peer protocols for reliable transmission) and the standard transports (Other inputs and outputs). Every output is added and edited through the same editor. A stream can have only one ps1 output — when the next one is being added, this type is no longer in the list; the other types are repeatable.

MPEG-TS

The bitrate mode of the output transport stream (Bitrate control) and — for SPTS — the “Network ID”, fixing of the PAT/PMT interval, filtering of the service tables (CAT/ECM/EMM, EIT, NIT, SDT, subtitles, TDT, teletext; MPEG-TS filtering), rewriting of the SDT and of the program number (Stream modification), as well as automatic PID arrangement for the program and the base PID of its window (Automatic PID arrangement).

Saving any setting on this tab other than “Bitrate mode”, “Padding bitrate” and “Network ID” closes and reopens the stream’s inputs and, on a stream with OTT delivery, also rebuilds the OTT pipeline — the viewers reconnect; a note on the tab itself warns about this.

OTT

OTT delivery of the stream, laid out by delivery plan: the stream name in the URL — shared by the progressive delivery and by HLS/DASH alike; the HLS service (Delivery modes), its tracing and the extraction of teletext subtitles into WebVTT; chunks and low latency (Segmenter); DVR recording to the selected storage (OTT and DVR); the HTTP service with its own tracing; and DRM content protection — HLS AES-128 or CENC (Content protection (DRM)). Subtitles and DVR are configured only in the OTT modes of the HLS service. For SPTS only.

Analysis

Quality control of the transport stream: verbose tracing, deep analysis of the elementary streams, the TR 101 290 monitor, analysis of PCR/PTS discontinuities and of the T-STD video buffer, synchronization drift compensation (Analyzer).

Alerts

The general switch of the stream alerts and the delay before raising alerts on the errors of its inputs and outputs (Alerts (alerter)); the thresholds are set at the node level (Alerter).

Saving changes that affect a recorded DVR archive is additionally protected by a confirmation (Confirm DVR changes).

If the stream is deleted from the node while its editor is open, the message “This stream no longer exists on the node.” appears at the top of the panel and saving becomes unavailable — the same reason is stated next to the button. The fields remain editable, but there is nowhere to write them: the object is no longer on the node. The message clears by itself if a stream with the same identifier is created again; the same line appears above the processing diagram (Pipeline) if the stream is deleted while the diagram is open. The node has reported this since 2.0.2.302 — before, all the lists of such a stream simply emptied, which looked like a stream with no inputs and outputs configured.

The individual windows of the editor are described below.

Input and output editor¶

The window for adding and editing a stream input or output. The transport type is selected at creation and cannot be changed afterwards (to change the transport, the input or output is re-created). The captions of the transport’s own fields the interface does not translate: these are technical designations, and in any language they are printed in English. The fields of every transport — with their values, ranges and the differences between input and output — are listed in Input and output fields by transport. The parameters are distributed over tabs:

Properties

The address, port, binding to a network interface and the connection parameters of the selected transport. Peer protocols and standard transports are described in Planning and data transmission protocols; encryption — in Stream encryption. For PS1 and SRT inputs, automatic sign-in by Meshwork peer authorization is available, with the option to switch to a manual login and password. The address can be pasted from the clipboard (“Paste URL”) or a source can be selected from the domain catalog (“Select from library…”, Library sources). For a transcoder input, the decoder and the encoding parameters, including the frame resize mode, are set here as well (Transcoders).

MPEG-TS PID

Selection and remapping of PIDs on an input or an output: PID accept (white-list), PID reject (black-list), remapping of PIDs and of the audio-track language. While automatic PID arrangement (Automatic PID arrangement) is enabled for the stream, the PID remapping group is hidden on the inputs and has no effect; the accept and reject lists keep working as before. On the muxer output PID remapping is retained — it belongs to the multiplexer (PID mapping) — but the source PIDs in its pairs become the PIDs assigned by the automatic arrangement.

Beside every number it is shown what kind of PID it is: on an SPTS — the kind and the codec (Video · H.264), on a multiplex — the program the PID belongs to as well, before that (01 ПЕРВЫЙ КАНАЛ · Teletext). An MPTS input has no decoded program of its own — the services live one level below, one per multiplex program, and all of them appear in the label. The add row carries a “Select PID…” list with the PIDs the source actually carries; it fills the number into the field, while manual entry remains — the transport may carry a PID about which nothing has been decoded. If nothing is known about the source — neither fresh data nor saved — there is no list and only the number field is left; data from elsewhere is not substituted, and a stopped input does not take the program composition from a working neighbour of the same stream: their source may be a different one, with a different PID plan. In PID remapping the list serves the “From PID” side — the PID on the right is assigned, not looked up; in language remapping it shows audio PIDs only. On a stopped input the blacklist runs without labels and without a selection list: a stopped input remembers the program composition as it was after its own filter, and the role left in that snapshot for a rejected PID is a trace, not a fact.

BISS

BISS descrambling keys for a scrambled source — a single key for SPTS or one key per program (PNR) for MPTS (BISS descrambling).

CI/CAM

Handing the input over to a separate CI module for descrambling (CI/CAM on a stream input).

CI/CAM on a stream input¶

The “CI/CAM” tab of the input editor gives the whole transport of the input to a separate CI module: the node pumps the stream into the module and takes it back already unlocked. The list of programs on the tab states not what goes into the module but what the module has been told to unlock — the input goes into the module in its entirety. That is exactly what the hint below the form says.

A separate module is not the same as a module welded into the tuner: the welded one is configured on the DVB adapter itself, by the adapter’s own program (Descrambling), and is not offered on this tab at all. How to tell them apart in the hardware inventory is stated in Hardware.

The tab exists on an input only, and only on a node of build 2.0.2.361 or newer; on an older node it is not there — not dimmed, but absent altogether, without explanation. Among the transports it is not given to transcoder and test-stream, which no transport reaches from outside, nor to RTMP and RTSP, which do not carry MPEG-TS; the rest have it. The form on the tab depends not on the transport but on the type of stream the input belongs to: an SPTS stream gets a single “CI slot” field, an MPTS stream a stack of cards, each with a “Program (PNR)” and “CI slot” pair. An SPTS stream has no program controls at all — that key does not exist for it. In practice DVB and muxer inputs occur only on a multiplex, while HLS, the demultiplexer, RTSP and RTMP occur only on an SPTS stream, so the form with the programs is reached on MPTS alone.

Cards are added with the “Add program” button below the list and removed with the “Delete program” cross in the corner of the card; neither asks for confirmation. An empty list reads “No program has been handed over to the CI module.”.

CI slot. The list holds “Off” and every separate module the node has reported; each is labelled with the slot identifier, the module name and, if the slot is already taken, a note on who holds it. A taken slot is not removed from the list: two inputs may take one module in turn, and the note here is a warning, not a prohibition. The holder is the node’s own service prefix, of the form [stream][input#1.udp][cam0]; it is printed as it comes, is not translated and is not the name of a stream. If the node reports nothing about CI hardware, the list degenerates into an ordinary text field, so that an identifier set elsewhere stays available for editing.

CI clock (Mbit/s). A single numeric parameter, presented as an “Automatic” checkbox and a field next to it. The checkbox is ticked by default; while it is ticked, the field is locked and shows “Measured from the input”. The automatics measure the bitrate of the input and drive the module about a third above it, watching the input as it goes — a source whose bitrate has sagged needs no new value. The clock sets the pace in both directions: far above the input the module returns mostly stuffing and packets are lost, far below it the pipe seizes up.

Some checks lock the save button, others only warn:

Condition	What it does	Message
The slot identifier is longer than 16 characters	locks	“The CI slot identifier must be at most 16 characters.”
More than four different slots are named (repeats of one do not count)	locks	“At most 4 different CI slots. Repeating one slot for several programs is allowed.”
There is more than one slot and the lists differ in length	locks	“If there is more than one slot, state a slot for every program: the lists are matched by position.” — with a “Fix the pairing” button next to it
The clock is not an integer from 0 to 200	locks	“The node accepts an integer from 0 to 200. A refusal is not rolled back: everything the node read before this field will stay applied.”
The clock is outside 20…120 Mbit/s	warns	the value is applied as given
The program number is outside 0…65535	nothing	only a red outline

The last row is the only place on the tab where an invalid value reaches the node: there is no message, saving is not locked, and the node will refuse the request. What that threatens is stated in How errors arrive: a refusal is not rolled back, and the fields read before the program number will stay applied. On seeing a save refused, the form is reopened to see what is in it now.

The “Fix the pairing” button is the tab’s only action besides adding and deleting cards. It stretches both lists to the length of the longer one: the program numbers are padded with zeros, the slots with a repeat of the last one named. A zero here is not a mistake but a deliberate gap: it arms nothing and holds a position in the pair. A repeated slot does not create an extra stage. The button throws away nothing that has been typed and asks about nothing.

One slot serving several programs is a legitimate and ordinary arrangement; the limit of four applies to different slots only. That is exactly what everything configured before 2.0.2.361 looks like.

If saving is locked because of the CI/CAM tab while the operator is looking at another tab, the line “First fix what is on the CI/CAM tab.” appears above the form. Locking the save here is preferable to sending it on spec precisely because a rejected write is not rolled back: a pairing that fails the end-to-end check would reach the settings file in full, and at the next start-up the loader would switch CI off on this input.

The work of the module is visible in the stream statistics (Stream statistics), and the state of the slots and their release on the “Hardware” screen (Hardware).

Library sources¶

Selection of an input from the common resource catalog of the Meshwork domain: a list of the streams of the same transport already delivered on the nodes of the domain, from which a source can be connected without entering the address manually. The list is filtered by source node and by text and is split into pages; sources of the same domain in peer protocols are marked with the “peer” attribute (Shared resource catalog). Not to be confused with the Library — this feed window: here the catalogue is used to pick a source, there to see who else works with an address that has already been set.

Library — this feed¶

The “Library — this stream” window: the source and the consumers of one address. — The “Library — this stream” window: for the input of a stream it shows the source (`output`) and two other consumers (`input`) of the same address.¶

The window answers the question “who else works with this address”. It is opened by the “Show in library” button next to the address of an input or an output: in the expanded row of the stream list, in the input and output lists of the stream editor, on the input and output cards of the pipeline (Pipeline) and in the statistics window — at the active input and in the “Outputs” section. The subtitle of the window is the address of the endpoint it was called from.

The button exists only for the transports that enter the shared domain catalogue: UDP, RTP, Pro-MPEG, RIST, PS1 and SRT (Shared resource catalog). A transcoder, muxer, demuxer, file or test generator input has no entries in the catalogue, and therefore no button either — this is not a sign of a fault.

The window lists the other endpoints of the domain that work with the same address. The own inputs and outputs of this stream do not enter the list, including its backup inputs: the operator sees them anyway. Another stream of the same node listening on the same address, however, is an ordinary neighbour and is shown on a par with the rest.

The “Direction” column shows the role of the endpoint: output — it delivers this stream (the source), input — it receives it (a consumer); the sources are listed first. The other columns are the same as in the shared catalogue: “Proto”, “Node”, “Stream” and “Destination” (the address and the port). After the address the “verified” mark is shown: this pair was confirmed by the node through the domain authorization rather than inferred from matching addresses — when working through NAT the addresses of the two sides do not match anyway. No more than one row per listening socket receives the mark: the node names a single representative among the confirmed sessions, and it changes as clients connect and disconnect. The absence of the mark therefore does not mean that the link is not real.

A click on a row opens the admin UI of its node at the statistics of its stream. A row of the own node opens in place, a row of a neighbour according to the “Open nodes in” setting of the top bar (Common bar); Ctrl or ⌘ forces a new tab. The row of a node that is unavailable or unknown to the network has no action and carries the “Node unavailable” tooltip.

A match is computed by protocol and by the full address — the group and the port — and for UDP, RTP, Pro-MPEG and RIST by the VLAN and the SSM source as well. An endpoint on the same group but in a different VLAN or with a different SSM source will therefore not enter the list, and neither will an endpoint of another transport at the same address. For PS1 and SRT no address match is required at all: the calling side names its partner by host name, and that name is matched against the membership of the domain — which is why the address of a row found this way may look entirely different. The confirmed pair is found the same way, by the node and stream names given by the listening side.

The two messages about the absence of neighbours mean different things:

Message	What it means
“There are no other registered endpoints at this address.”	The endpoint is announced in the catalogue and has no neighbours.
“This endpoint is not announced in the library (only running network inputs and outputs are announced).”	There is no entry for the endpoint itself in the catalogue: the stream is not running, the input or output is paused, has only just been started or has been excluded from publication by the Peer private field (Shared resource catalog). In this case the neighbours are not absent — they are unknown.

The same catalogue in its entirety is shown by the Library screen.

Programs¶

The multiplex (MPTS) program editor, opened from the muxer input configuration window: the program composition of the output stream, the program order in the PSI and PID assignment. A program is added from among the configured SPTS streams or removed; the order is changed by dragging, and on a narrow screen by the Alt+↑ and Alt+↓ shortcuts (Keyboard operation); an individual program can be paused. When automatic PID assignment is disabled, the PMT PID and the elementary stream PIDs are edited for each program; when the composition of a member program could not be read, the PID editor shows the request error rather than “No media info — the source is not being decoded.” — a silent source and a failed request call for different things. Multiplex assembly is described in Multiplexer, the allocation of programs and PIDs — in Program parameters and PID mapping, transit and analysis of MPTS streams — in MPTS streams.

Confirm DVR changes¶

A warning shown before saving stream changes that affect an already recorded DVR archive: disabling the recording, switching to another storage, reducing the retention period or the protected minimum, as well as changing the DRM key of a stream with recording (the previously recorded encrypted segments then become inaccessible). The window lists exactly what will be affected and requires confirmation; safe changes (the first attachment of a storage, an increase of the retention period) are saved without a prompt. Recording and archive retention are described in OTT and DVR and DVR: the stream archive.

Stream statistics¶

Detailed stream statistics in a separate window, updated in real time. Opened by a link from another screen, the window also shows this stream in the list behind it (Streams); a link that opens not the statistics but the stream editor behaves the same way. The sections are:

State summary

The current state and message of the stream, the attribute badges, the active input and the number of outputs, the bitrate mode, the picture format and codecs, the OTT delivery links and a live frame snapshot (Mosaic). Here as well are the TR 101 290 verdict icon that opens the full report and the “Show in library” button at the active input (Library — this feed).

If the active input of the stream is a transcoder input, its value becomes a link: the jump opens the “Transcoders” screen (Transcoders) with the row of the instance that feeds this input expanded; the active-instance filter is cleared in the process, so a stopped instance is visible too — and it is precisely that one people usually follow such a link for. A “Decoder source” badge appears beside it with the name of the stream that instance decodes; it opens the stream list with the row of that stream expanded (Streams). If the node does not report the name of the source, the badge carries its number, and if there is no source at all, there is no badge. Both links are available in any role: they only show, changing nothing.

Multiplex / KPI

For SPTS — the key counters (input bitrate, CC errors over the window and in total, scrambled packets); for MPTS — the multiplex table with the aggregate rates and the state of the programs (Per-program analysis).

For a program unlocked by a CI module, a “CI” row with the slot number and the module’s verdict appears in the expanded detail (CI/CAM on a stream input). It is a row of the detail, not a column of the table: the columns are as before. On a live multiplex such a row is usually carried by one program in ten, and the column would stand empty for all the rest.

Charts

Time series: bitrate, continuity and scrambling, PCR jitter, packet loss. The window is picked with the “15m”, “1h”, “6h” and “24h” presets; the arrow buttons ‹ and › (the “Earlier window” and “Later window” tooltips) page it backwards and forwards, the “Live” badge marks a window that abuts the current moment, and its bounds are captioned above the charts. The sampling step is set by the preset, but the node does not give out data finer than its own step: on a node with a coarse step the shortest window, “15m”, is built from fewer points and comes out coarser. The other presets are not affected.

MPEG-TS check

An express check of the structure (TS, PAT, PMT, PCR, audio/video and their ES), the overall TR 101 290 verdict and the program signaling attributes (Validity check).

Input diagnostics

Expandable blocks: “Media information”, “Input connection”, BISS decryption, EIT generation, “Analyzer” (PCR and synchronization metrics, and below them the PID table of the active input with the “PID”, “Type”, “Bitrate” and “Packets/s” columns), stuffing and “Deep analysis” — the GOP structure, the T-STD buffer, the video codec passport, PTS/DTS discontinuities, SCTE-35 (Continuous measurements, In-depth analyses). The composition of the section depends on the input: on UDP, RTP and Pro-MPEG inputs the “Input connection” block gains the “Socket buffer (granted)” line — the useful volume of the receive buffer that the socket actually got (Recommendations for network tuning for multicast); a muxer input has no section at all — it has no socket, and the programmes are shown by the multiplex table; on network reception of a ready MPTS only “Input connection” with the indicators of its own transport remains, while “Media information”, “Analyzer” and “Deep analysis” are hidden — such an input has no per-programme measurements. BISS decryption is shown for SPTS only: for MPTS the BISS counters are kept per programme (BISS descrambling). The EIT generation and stuffing blocks appear by themselves when the stream generates EIT or adds NULL packets.

CI/CAM

The work of the CI modules to which the inputs of this stream have been given (CI/CAM on a stream input). The section is collapsed by default, its header carries the total number of stages, and it appears only when at least one input of the stream names a CI slot.

The section shows all inputs of the stream, not just the active one. A backup input may well be holding the slot — it is for such a case that the release of a slot on the “Hardware” screen exists (Hardware). The blocks of an inactive input are labelled “On input” with the type and the number of that input.

Each stage of the cascade gets its own block; when an input has more than one module, the blocks are headed “Stage 1”, “Stage 2” and so on. The look of a block depends on whether the slot has been taken. A taken one has “State”, “Module”, “Clock” (the one in effect now; while the node does not report it, “automatic” is written), “Delay”, on pass-through “Passes unchanged”, then the counters, “Verdict” and “Error” with “Module message”. An untaken one — the measurement is still running or the slot could not be taken — has only “State” and the line “The slot has not been taken yet, so there are no counters.”: the node gives out almost nothing for such a slot, and a wall of zeros would be misleading. A zero that is printed all the same therefore means “the slot is taken, but nothing has happened”.

The counters are split into two groups on purpose, because resetting the cumulative statistics clears only the first: “Delay line” (inserted, unlocked, lost, duplicates, mismatches, timeouts, not accepted) is reset, while “Pipe” (given out, returned, group errors, stale, stuffing, write congestion, read timeout, resets) is not; its counters start over when the slot is taken anew.

They are worth reading with two reservations. The verdict unknown (like reserved) is not a failure: many modules do not answer such a query at all while carrying on unlocking perfectly well — the judgement is made from the growth of the counter of unlocked packets. And growing losses and group errors usually mean too high a CI clock; a lost packet goes on exactly as it arrived, that is, scrambled.

The values that come from the node are printed as they are and are not translated: the slot identifier of the form 0:1, the state (empty, module-present, initializing, ready, error, unavailable, measuring), the name of the module’s application, the verdict, the error text and the module message.

Outputs

Telemetry of every output that is not paused: state, destination, bitrate, counters of the traffic sent and the indicators specific to the transport (PRO-MPEG FEC, PS1, RIST, SRT, RTMP); paused outputs do not appear in this list. Outputs in the transports of the domain’s shared catalog have a “Show in library” button (Library — this feed). The reason an output failed is shown here the same way as in the expanded row of the list: as a red line while the output is failing right now, and dimmed, “Last failure N ago: …”, when it is stopped. Without an age, simply “Last failure: …”, the line is shown on nodes of earlier builds — those that do not report the time of the error.

OTT / DVR

The delivery URL templates, the metrics of the chunk ring and of the DVR archive, the charts of archive coverage and of subtitle replicas (OTT and DVR, Archive playback (VOD)).

Profiler and Stream log

The load of the processing threads (share of a core) and the structured log of the stream events.

The TR 101 290 report also opens as a separate window; the analyzer as a whole is described in Analyzer, the TR 101 290 monitor — in TR 101 290 monitor. The administrator can reset the cumulative statistics and erase the DVR archive.

Adaptive bundle¶

The adaptive bundle (ABR) configuration window: the bundle name and the name in the URL, the composition of the member streams and their bitrates (“0” — auto). Only SPTS streams with OTT delivery enabled can be members; they are added and removed directly in the window, and the bitrate is set for every variant. The bundle is published as a single master playlist by which the client selects the quality. Adaptive delivery is described in Adaptive bundles, DVR recording for OTT — in OTT and DVR.