Model and documentation reference
Exact model: Magewell Ultra Encode AIO. The references are the preserved 130-page English manual with ©2026 notice and official model documentation. Record installed firmware separately rather than deriving it from the PDF filename. Ultra Stream, Ultra Encode II or Director functions are not transferred here.
Magewell · Ultra Encode AIO · exact-model product
Event application
If production provides a finished program, identify that handoff format and audio before adding another mix. If AIO will combine HDMI and SDI, the manufacturer describes a single combined output using picture-in-picture or side-by-side, not two independent productions. Agree on program preparation, destination administration and external-reception monitoring owners.
Trace program input to the intended result
| Stage | Model reference | Event information |
|---|---|---|
| Source / Mixer | HDMI, SDI or composite selection | Actual delivered signal and audio |
| Main / Sub | Distinct encoding profiles | Intended resolution, rate, codec and bitrate |
| Delivery session | Main or sub profile assigned per session | Destination, protocol, profile and owner |
| Recording | Separate task and storage medium | Profile, file, location and recipient |
Magewell · Ultra Encode AIO · exact-model product · Ultra Encode AIO · English manual · 130PDFpages · ©2026 · selectedsections
Profile assignment is not destination verification
Draw program → selected source → profile → session → receiver. Each destination row identifies protocol, format, audio and observed state without keys in the worksheet. The manual allows main or sub per session; do not assume two destinations use the same profile. Separate recording from delivery and define the required file. Neither encoder preview nor a server connection establishes correct audience picture and speech.
Ultra Encode AIO · English manual · 130PDFpages · ©2026 · selectedsections
When only one platform fails
Preserve source and configuration while comparing the affected destination with the others. API documentation distinguishes DNS resolution, authorization and server connection; these are stream states, not HTTP codes or measured results here. For an authentication rejection, review event and permissions with the account administrator; higher bitrate does not fix that rejection. If connected playback breaks up, record intended formats, bitrates and delivery workload against the actual network path rather than promising capacity from one speed test.
Magewell · Ultra Encode AIO · exact-model product · Ultra Encode AIO · English manual · 130PDFpages · ©2026 · selectedsections
Prepare and test each destination
- Record AIO label, observed hardware/firmware, source and owner. Preserve operating settings before proposing changes.
- Prepare destination and file rows: profile, format, audio, protocol or medium, owner and expected result. Keep credentials outside the worksheet.
- Check source and composition. The manual warns that Mixer format reference must match the present input; do not automatically attribute a blank picture to the network.
- Agree on an off-program test using speech, text and motion. Review local sample, external reception and recorded file separately under the actual intended simultaneous tasks.
- Retain time, state and problem logs with the agreed alternative and return plan. Do not start with log deletion, reboot or firmware changes. No stream or recording starts here.
Ultra Encode AIO · English manual · 130PDFpages · ©2026 · selectedsections
Frequently asked questions
Are main and sub two independent cameras?
They are encoding profiles of the selected program; document the source or composition and each session assignment. Two profiles do not establish two independent productions.
Does a connected session prove conference playback?
Documented code 22 means server connected, not audience playback. Acceptance and receiver picture/listening need separate checks.
How do DNS and authentication differ?
The API reference distinguishes 28 as DNS resolution and 30 as authentication error. Record the actual state without treating it as a diagnosis of the entire network; review the relevant segment with its owner.
Does a correct local file validate delivery?
It establishes no destination access, authorization or playback. Preserve both samples and the profile used by each task to locate where results differ.
Can any simultaneous combination be promised?
Conditions depend on protocol, profile and version. Define actual tasks and check documentation and an agreed test rather than adding maxima from different pages as if cumulative.
Follow video and audio paths
Official edition-specific documentation
Ultra Encode AIO manual: source p. 30, main p. 41, sessions p. 45, recording p. 78, information/reports p. 121 and logs p. 122. API-state documentation is distinct from querying an actual device. No stream, recording, account access or device API call was performed.
