If you are choosing between BoxCaster, Teradek VidiU and Digicast DMB-8800A, start with the platform your channel already uses and the way you produce its video. The only direct comparison located is a BoxCast-authored test from 2018; it is useful historical evidence, not a current or independent ranking of these devices.
The original BoxCaster requires a BoxCast streaming subscription to activate and works exclusively with that platform. VidiU and DMB-8800A have documented third-party RTMP setup routes, but you should verify the specific hardware revision and the destination platform’s current ingest requirements before relying on either.
Quick comparison and the historical-test caveat
These devices are not interchangeable boxes whose test scores settle the choice. Their fit depends on where your stream is going, which inputs your camera or switcher provides, and whether you need a general RTMP workflow or an encoder tied to BoxCast. If your aim is a YouTube channel, check that the hardware and its setup route can send to your current YouTube ingest configuration; documentation showing a route into BoxCast is not proof of compatibility with every destination.
| Device | Workflow and platform | Evidence available | Main decision point |
|---|---|---|---|
| Original BoxCaster | BoxCast platform only; subscription required for activation | BoxCast’s historical side-by-side test and its product/support material | Do BoxCast’s workflow and format handling suit your production? |
| Teradek VidiU | Hardware encoder; the reviewed test used an RTMP/TCP route into BoxCast | BoxCast’s 2018 test and a current BoxCast support collection listing a VidiU setup article | Does your specific VidiU revision still meet your destination’s requirements? |
| Digicast DMB-8800A Premium / ChurchStreamer | Hardware encoder with a documented ChurchStreamer-to-BoxCast RTMP route | BoxCast’s 2018 test and setup guidance | Can you confirm model revision, saved configuration and ingest settings? |
The table describes what the cited material establishes, not a guarantee of present-day stock, firmware or manufacturer support. The reviewed material does not settle those questions for every legacy revision. Before buying used equipment, ask for its exact model and revision, test it with your own source and destination, and confirm what support is available.
BoxCast’s 2018 comparison favored BoxCaster in the conditions it tested. BoxCast itself said the objective scores were relative to that experiment and should not be compared with results from other comparisons. Keep that qualification beside every mention of its results: the figures do not establish how a device performs with your camera, network, firmware or platform today.
What BoxCast’s 2018 test measured
BoxCast described splitting a 720p HDMI source, the Creative Commons video “Big Buck Bunny”, among the three encoders. It streamed each feed to BoxCast, downloaded the resulting recordings and compared a section lasting 2:29 with the source. The source was 24 frames per second and was converted to 30 frames per second for the comparison. BoxCast said alignment between the source and recordings was difficult, and that the frame counts compared varied by less than 0.3%.
Settings were not identical. BoxCast set the VidiU and DMB-8800A Premium to 720p, high profile and 3,300 kbps. It limited the BoxCaster to 3.0 Mbps, describing that as the closest manual setting; the same article said BoxCaster could encode up to 4.8 Mbps. This mismatch matters because the results reflect a particular configuration, not a controlled comparison in which every variable was made identical.
The reported objective video metrics placed BoxCaster ahead of the other two in this experiment. BoxCast listed average PSNR values of 25.085 for BoxCaster, 18.613 for VidiU and 14.853 for DMB-8800A. Its SSIM all, dB figures were 9.423, 6.217 and 5.302 respectively; its VMAF figures were 30.306, 10.092 and 25.388 respectively for BoxCaster, VidiU and DMB-8800A. These are numbers reported by a vendor in its own test, not independent ratings or a general measure of image quality across programmes.
A source with motion, fine text or darker scenes may expose differences in ways that one short sample does not. So may a different input format, encoder revision or bitrate. If image quality is central to your decision, try the actual content you intend to broadcast and inspect a recording at the destination. Do not read a 2018 score as a prediction that BoxCaster will produce the best-looking YouTube broadcast in your installation.
The network observations need the same care. BoxCast shared a network connection from a MacBook Pro and used Apple’s Network Link Conditioner to simulate conditions. In its packet-loss scenario, with a 3.5 Mbps uplink, BoxCast reported VidiU disconnected at 9% packet loss, DMB-8800A at 5% with about four seconds of discontinuity, and BoxCaster at 10% with reduced encoded bitrate and no noticed artifacts, lost data or discontinuity. These are observations from that setup and path, not a field guarantee.
In a reduced-uplink test, BoxCast reported about four seconds of discontinuity for DMB-8800A and roughly four seconds of visual artifacting without audio discontinuity for BoxCaster. The distinction between these observations and a dependable overnight result is important: a simulated test cannot represent every home broadband connection, router, ISP route or ingest service. If drops are your concern, understand what should happen when ingest drops and test recovery behaviour on the exact setup you plan to keep on air.
BoxCaster’s platform dependency and formats
The original BoxCaster is not a standalone, open-platform RTMP encoder. BoxCast’s product sheet says it works exclusively with the BoxCast platform and requires a BoxCast streaming subscription for activation. That dependency is a practical part of the purchase decision, not a minor setup detail: if you want to point the hardware at YouTube or another platform directly, do not assume the original BoxCaster offers that route.
For an organisation already producing broadcasts through BoxCast, this may be a sensible fit. A church or community group that uses the platform’s scheduling and distribution workflow may value an encoder made for that system more than direct control over destination settings. But if your plan is a YouTube-only 24/7 channel, ask whether BoxCast is the workflow you actually want before you weigh an encoding result from the old comparison.
Input compatibility deserves a separate check. BoxCast describes HDMI and composite video inputs, H.264 high-profile level 4.2 encoding, and embedded or RCA stereo audio on the original BoxCaster. Its support page lists supported HDMI formats through specified 1080p rates and analog NTSC/PAL over composite. The exact input standard matters: a camera, switcher and encoder need to agree on resolution and frame rate, rather than merely having matching connectors.
BoxCast says 1080p30 inputs output natively at 1080; other 1080 sources generally output at 720 unless a qualifying 1080i60 signal is manually set to 1080. Check the precise source format and the current support documentation before assuming your stream will retain 1080 output. BoxCast also warns that changing video standards during a broadcast, such as changing resolution or switching from HDMI to RCA, can cause video failure. A stable programme should be configured before going live, rather than relying on mid-stream format changes.
The support page’s practical lesson is to test the complete chain: camera or playback device, cable, encoder, destination and recording. If you are using a video loop rather than a live camera, stability also depends on the playback system and the way it recovers from a freeze. Our guide to stopping a looping waterfall video from freezing on YouTube Live covers that separate failure mode; an encoder choice alone will not fix a frozen source.
VidiU and third-party RTMP routes
Teradek VidiU is relevant if you already own a unit or need hardware that can be configured for a third-party destination. BoxCast’s test treated it as a hardware encoder and used an RTMP/TCP path into BoxCast. Its article described the tested unit as using strict constant bitrate behaviour and reported an interruption at 9% simulated packet loss. Those statements belong to the unit and software used in 2018; they should not be generalised to every VidiU revision or present firmware.
BoxCast’s support collection lists a VidiU setup article, which establishes that a setup route has been documented for BoxCast. It does not establish current support for every revision, nor does it mean the same menu steps or ingest options apply to YouTube. Confirm which VidiU model you have, what firmware it runs and whether the required output protocol and settings remain available. A seller saying “VidiU” without the exact version leaves an important question open.
The DMB-8800A Premium was previously offered by ChurchStreaming.tv as ChurchStreamer, according to BoxCast’s support guidance. That material documents a ChurchStreamer-to-BoxCast RTMP setup path. It says the device ships with a static address by default and provides example output settings: 1080p at 4,800 kbps, 720p at 2,800 kbps, or lower resolutions at 1,000 kbps, with frame-rate settings keyed to source standards. These are BoxCast’s documented directions, not a claim that every unit is still sold or supported, or that those settings suit every destination.
The DMB-8800A instructions also warn that power cycling can erase its configuration. That is a material operational risk for an always-on channel: if a restart resets settings, you may need to restore them before the broadcast resumes. Before installing one out of reach, test a controlled power cycle and confirm the unit returns to the intended configuration. Keep a written record of the working values and the exact revision.
Neither of these third-party routes should be confused with automatic compatibility. RTMP is a way to send a stream, but a destination can still impose its own supported resolutions, frame rates, bitrate limits, stream key handling and account settings. YouTube’s live encoder settings are the place to check the current destination requirements. If a YouTube stream goes offline, encoder capability is only one part of the fault; network conditions, ingest configuration and restart behaviour also matter. See our practical guide to fixing a YouTube live stream that goes offline by itself before treating a hardware swap as the answer.
Choose for the workflow you already have
Start with the source and destination, then compare the encoder. A local news loop may come from a switcher with HDMI output and require a direct YouTube ingest route. A devotional channel might play a prepared programme continuously from a computer, or route a camera and mixer through hardware. A small business may value a simple, repeatable operator hand-off more than control over encoding parameters. The same unit can be suitable in one of those arrangements and awkward in another.
If your organisation already uses BoxCast for its broadcasts, the BoxCaster’s platform tie may simplify a workflow that is already built around that platform. Its historical test result can be one input to a decision, provided you keep the age and ownership of the test in view and verify the input formats. If you need a YouTube-directed RTMP path without BoxCast activation, the original BoxCaster is a poor match on the documented facts, regardless of how it scored in its vendor’s experiment.
If you have a VidiU or DMB-8800A in storage, first identify the exact unit and test it before buying another device. Confirm that it boots, accepts your source format, keeps settings after a power interruption and can connect to your intended destination. Since the available documentation does not establish current retail availability, firmware status, warranties or support for every revision, a used-device purchase should include a return arrangement or a practical test where possible.
Compare a hardware encoder with a software or cloud workflow only after clarifying what you are trying to avoid. Hardware can suit a camera-based production with a stable signal path and an operator who can check the device. Software can be easier to change when the source or graphics change, though it may place more load on the computer and require careful restart planning. For a video that is already prepared and must repeat without leaving a computer on, a cloud workflow may address the overnight machine and recovery problem directly; StreamNeo is designed for that specific uploaded-video-to-YouTube use case, rather than camera input or ing.
This distinction matters for a 24/7 channel. A hardware encoder does not by itself make a programme loop, prevent a source computer from sleeping, resolve music rights, or guarantee that an ingest remains connected. Your operating plan should say who notices a failure, how the source resumes, and how you check that the public stream is actually playing. A Gurbani stream software guide can help frame those workflow questions when your channel is built around devotional programming rather than a live camera feed.
What to verify before choosing
First, write down the actual signal path: source device, video and audio outputs, encoder input, network connection and destination. Match the source’s resolution and frame rate to the encoder’s supported formats and the destination’s current ingest options. A connector that fits does not prove the format is supported. For BoxCaster, pay particular attention to the specific 1080 input behaviour and avoid changing standards during a broadcast.
Second, settle the platform question before comparing image scores. For BoxCaster, confirm that BoxCast’s subscription and platform workflow are acceptable and that activation can be completed for the unit you are considering. For VidiU or DMB-8800A, confirm that the exact revision can still be configured for the destination you intend to use. Ask the vendor or seller for written confirmation where the published support material is unclear; do not infer current support from a historical test or an old setup article.
Third, exercise the failure cases while you can observe them. Test a brief network interruption, a source restart and a controlled encoder power cycle. Watch whether the encoder reconnects, whether the destination resumes, whether the device retains its settings and whether someone must intervene. The 2018 simulated packet-loss observations are not substitutes for a test on your broadband connection and actual ingest path. If you are choosing a wider operating approach, our explanation of running a prerecorded YouTube livestream on AWS sets out a different kind of workflow to evaluate, not a claim that it replaces these encoders in every situation.
Finally, compare total ownership effort rather than treating the device price as the whole cost. Include any required platform subscription, cables or conversion equipment, the person who can configure it, the ability to replace or repair it, and the time needed to restore a failed stream. No current prices or availability for these legacy models are established by the reviewed sources, so request current terms directly and date your notes. For YouTube-specific setup and account requirements, consult YouTube’s live streaming help as well as the encoder documentation.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Did BoxCaster really perform better than VidiU and DMB-8800A?
In BoxCast’s 2018 test, its reported PSNR, SSIM and VMAF results ranked BoxCaster ahead of the other two devices. BoxCast authored the test, settings were not identical, and the company cautioned that the scores were relative to that experiment. Treat the result as historical evidence, not an independent or current ranking.
Can the original BoxCaster send directly to YouTube?
The reviewed BoxCast product material says the original BoxCaster works exclusively with BoxCast and requires a BoxCast streaming subscription to activate. Do not treat it as a general-purpose RTMP encoder. Check current BoxCast documentation if your intended workflow involves a different platform.
Are VidiU and DMB-8800A guaranteed to work with YouTube?
No. BoxCast documents third-party RTMP routes into BoxCast, but that does not establish compatibility with every YouTube setup, firmware revision or unit. Identify the exact model, check YouTube’s current ingest requirements and test the full source-to-destination path before relying on it.
Which encoder is best for a 24/7 YouTube channel?
There is no universal answer from the evidence available here. Choose according to source format, destination compatibility, platform dependency and your ability to recover the system after a failure. For a prepared video rather than camera input, compare the hardware route with workflows that can run without keeping your own computer on.