To stream from Wirecast to BoxCast, choose one of three documented routes: send a direct RTMP feed, send a direct SRT feed, or send Wirecast’s secondary display output to BoxCast hardware such as a BoxCaster. For the direct software routes, schedule the broadcast in BoxCast Dashboard first, then enter the source details in Wirecast and check the incoming signal before the scheduled start.
The right route depends on which sources your BoxCast account exposes, the Wirecast version and computer you have, and whether you already use a BoxCaster. This guide covers the setup and checks for each route; it does not assume the options appear identically in every account or Wirecast release.
Choose the Wirecast-to-BoxCast route
Direct RTMP is a practical starting point when your Dashboard provides an RTMP source and Wirecast can connect to its URL. You copy the server URL and stream key into Wirecast. The main compatibility question is that BoxCast-generated URLs default to RTMPS, while BoxCast’s Wirecast instructions note that standard Wirecast versions may not support RTMPS. Verify your installed version before changing the URL.
Direct SRT is another software route when an SRT source and its configuration details are available in Dashboard. It requires more fields than RTMP—address, port, stream ID and, if encryption is enabled, passphrase—and BoxCast specifies stereo audio at 48 kHz for this Wirecast connection. If you do not want to check those settings, RTMP may be the simpler route when compatible.
A secondary-display feed is for an operator who has BoxCast hardware and a compatible computer display output. Wirecast sends its programme output to a display connected to a BoxCaster, which then handles the hardware encoding. It is not a required extra step for RTMP or SRT, and it is not a reason on its own to buy an HDMI cable or encoder.
| Route | What you need to enter or connect | Worth considering when |
|---|---|---|
| RTMP | BoxCast server URL and stream key | Your account offers an RTMP source and Wirecast can use its connection type |
| SRT | Address, port, stream ID and possibly passphrase; stereo 48 kHz audio | An SRT source is available and you can confirm the audio and connection settings |
| Secondary display to BoxCaster | Wirecast display output, compatible video connection and BoxCaster | You already have the hardware and prefer its encoding and support-data benefits |
BoxCast describes operational benefits for its hardware path, including relieving the computer of video and audio encoding and providing additional broadcast data and logs for support. Its setup material does not establish that one route is best for every production. Consider the load on your computer and the equipment you already own, rather than treating the routes as quality rankings. If the production itself is still a question, our guide to choosing between OBS and FFmpeg for a bhajan channel discusses a different encoder decision; the connection details here are specific to Wirecast and BoxCast.
Schedule in BoxCast Dashboard before connecting
For BoxCast’s documented direct Wirecast RTMP and SRT workflows, a broadcast must be scheduled in Dashboard. Do this before you expect Wirecast to send programme video. The schedule is not merely a label for the encoder destination: BoxCast’s instructions tie the incoming source to a planned broadcast.
Open Dashboard and create the broadcast with the intended start time and other details required by your account. Then go to Sources to create or select the RTMP or SRT source you will use. Keep the broadcast and source details together in your setup notes, but do not put an actual stream key or SRT passphrase in a public document, screenshot or shared chat. Treat credentials as access information.
BoxCast’s Wirecast-specific guide recommends starting Wirecast two to three minutes before the scheduled start so there is time for the feed to arrive. That is a recommendation for this pairing, not a promise that a broadcast will start at an exact second or a universal BoxCast requirement. Its general RTMP guidance gives a different lead-time recommendation, so use the Wirecast-specific advice here and leave enough room to investigate a missing signal.
The broadcast schedule and Wirecast output are separate controls. A scheduled broadcast does not mean Wirecast is already sending, and pressing Stream in Wirecast does not replace creating the scheduled broadcast. For a long-running programme, also plan how someone will notice if the encoder or source stops; the general considerations in remote monitoring for a live playlist stream can help you think through who checks the output and from where.
Configure a direct RTMP source
In BoxCast Dashboard, open Sources and create or select an RTMP source. Copy the displayed Server URL and Stream Key. The source setup and resulting values are described in BoxCast’s RTMP source instructions. Copy the values exactly, and avoid substituting a URL from an unrelated event or source.
In Wirecast, open Output > Output Settings and set Destination to RTMP Server. Enter the server URL in the address or server field and the stream key in the stream field. If your version presents a combined URL field instead, follow that version’s field format rather than adding the key to a separate field without checking. Save the destination if you expect to reuse it, while keeping the key private.
Pay attention to RTMPS compatibility. BoxCast says its generated RTMP URLs use RTMPS by default. Its Wirecast-specific article says standard Wirecast versions do not support RTMPS and advises removing the “s” from the server URL when needed—for example, changing rtmps://rtmp.boxcast.com/live to rtmp://rtmp.boxcast.com/live. Do not make that change automatically: first check whether your installed Wirecast version supports the supplied URL and use BoxCast’s current instructions for your configuration. The change concerns the connection URL, not the stream key.
BoxCast’s general RTMP guidance says third-party RTMP ingestion supports H.264 and does not currently support H.265/HEVC. If Wirecast connects but BoxCast does not receive a usable picture, check the encoder’s video codec rather than repeatedly changing the source credentials. You can review BoxCast’s RTMP encoder guidance for its current requirements. A codec mismatch is different from a connection failure, so note whether the Dashboard shows no incoming feed or an incoming feed with a problem.
Once the output is configured, schedule the BoxCast broadcast and press Stream in Wirecast. BoxCast’s guide says the broadcast can go live at its scheduled time even if the encoder begins sending earlier. Check Dashboard for the incoming source before relying on the scheduled start; an early Wirecast transmission is not a substitute for verifying that the correct source is attached to the correct broadcast.
Configure a direct SRT connection
In Dashboard, open Sources, select the SRT source and open its Wirecast configuration values. You need the provided Address, Port, Passphrase and Stream ID. The passphrase may be blank when encryption is disabled; do not invent one or reuse an RTMP key in its place. If a field is missing, check that you are viewing the SRT source configuration rather than an RTMP source.
In Wirecast, open Output > Output Settings and set the destination to SRT: Secure Reliable Transport. Enter each value in the corresponding field. Recheck the address and port character by character, and preserve the stream ID as provided. If encryption is enabled, enter the Dashboard passphrase accurately. A typo in one of these fields can prevent a connection even when the broadcast itself is correctly scheduled.
Set the encoder audio to stereo, 48 kHz. BoxCast explicitly warns that other values may lead to no audio or audio that sounds incorrect to viewers. This is an operational setting in the Wirecast encoder, not an optional quality preference for this documented SRT workflow. Before the scheduled start, check both that a feed is arriving and that the audio is present and intelligible.
Schedule the broadcast in Dashboard, then start Wirecast in advance so the feed is ready. BoxCast recommends two to three minutes early in its Wirecast-specific instructions. Allow additional time if you are setting up a source for the first time or need to test audio; the recommendation should not be read as a guaranteed start-time window. If the source does not connect, compare all four SRT values with Dashboard before trying a different protocol.
Send Wirecast’s secondary display to BoxCast hardware
The BoxCaster route takes a different path: Wirecast renders its programme output to a secondary display, and that video output is connected to a BoxCast hardware encoder. Use this route only if you have the required encoder and a compatible output on the computer. Confirm the display connector, cable and resolution supported by both devices before the broadcast day. A cable purchase is relevant only to this hardware setup; direct RTMP and SRT do not require an HDMI connection.
BoxCast’s Wirecast setup guide uses Output > Multi-Viewer Output > Configure Displays. Its documented configuration sets the output monitor to 1920x1280, chooses Full Screen, sets labels to Do Not Draw Labels, selects Live, and then selects the appropriate display output. Match these options carefully so the BoxCaster receives the programme rather than a multiviewer view or a screen with labels covering the picture. The menu names and available display choices can vary by setup, so confirm the selected output on the actual connected display.
Then connect that display output to the BoxCaster and confirm that the encoder sees the intended picture and sound. This path can relieve the computer from encoding video and audio, and BoxCast notes that hardware use can provide its support team with additional broadcast data and logs. Those are reasons to consider hardware when it is already part of your operation, not evidence that the output is automatically more reliable in every room or network.
The hardware branch does not replace sensible preparation. Verify the cable connection, display selection and programme feed before the scheduled event. If your immediate goal is a software-only connection, return to RTMP or SRT rather than buying hardware to complete a step those routes do not need.
Check the stream before the scheduled start
Build a short pre-start check into your run sheet. First confirm that the correct broadcast is scheduled in Dashboard and that the source attached to it is the one configured in Wirecast. Then check that Wirecast is outputting to the intended destination and that Dashboard shows an incoming signal. Starting Wirecast early gives time to correct an issue; it does not itself prove that the correct image, sound or event is being sent.
Check the picture and sound as a viewer would encounter them. For RTMP, verify the destination URL and stream key, and ensure the video codec is H.264 rather than H.265/HEVC under BoxCast’s general third-party RTMP guidance. For SRT, verify the address, port, stream ID and any enabled passphrase, then confirm stereo audio at 48 kHz. For the BoxCaster route, inspect the output display and confirm the BoxCaster receives the intended programme frame rather than Wirecast controls or labels.
A written handover is useful if somebody else may need to restart the production. Record the broadcast name and scheduled time, the selected route, where the credentials are stored, and the safe steps for checking the incoming feed. Do not include the actual stream key or passphrase in a run sheet circulated beyond those who need access. If your channel will run for an extended period, planning for a stream that stops when its video ends offers a useful way to think about end conditions and monitoring, although this article’s connection steps remain specific to BoxCast.
If you are testing a recurring show, do not assume a destination saved in Wirecast is the same thing as a broadcast scheduled in Dashboard. Check the event and source pairing each time the schedule or production changes. If a transmission is late, identify whether the failure is in scheduling, the Wirecast output, source details, codec or audio before changing settings at random.
Troubleshoot missing options and connection details
If Dashboard has no RTMP option, BoxCast’s instructions say to add an RTMP source. Go to Sources and create one, then retrieve its server URL and stream key. If you cannot see an SRT source or its configuration, confirm that you are looking at the SRT source entry and that the expected source is available to your account. The exact options may depend on the account; use the Dashboard’s current controls or BoxCast Support Center rather than assuming another account’s screen will match.
If Wirecast cannot connect to an RTMP URL, check the URL type and the capability of your installed Wirecast version. BoxCast’s default generated URL is RTMPS; its Wirecast-specific guide gives the RTMP form without the “s” for cases where Wirecast cannot use RTMPS. Check that the stream key remains in its own field if Wirecast provides separate fields. Never share the key to solicit help; redact it from screenshots and logs.
If SRT connects without sound or with incorrect audio, inspect the Wirecast encoder’s audio configuration and set stereo at 48 kHz as BoxCast specifies. If SRT does not connect at all, verify each supplied parameter—address, port, passphrase where enabled, and stream ID. A blank passphrase is appropriate only where encryption is disabled according to the source configuration.
If RTMP connects but the picture is not accepted, check whether the output uses H.265/HEVC. BoxCast’s general RTMP material identifies H.264 as supported for third-party RTMP ingestion and says H.265/HEVC is not currently supported. If the problem is instead that the broadcast does not appear when expected, revisit the scheduled time and confirm that Wirecast is actually sending to the selected source. For broader questions about live events and channel preparation, our guide to creating a Hindi devotional livestream in YouTube Live Control Room covers a different platform workflow and should not be used as a substitute for BoxCast’s scheduling instructions.
If a display-to-BoxCaster setup is blank, check the chosen output in Wirecast, the computer’s display configuration, the physical connection and the encoder input. Verify that Live is selected and the correct display output is chosen in the Multi-Viewer configuration. Keep the direct software routes in mind as alternatives only if they fit your account and production; do not assume a BoxCaster fault can be fixed by changing RTMP or SRT credentials.
For a recurring broadcast, assign one person to verify the feed before start and another contact who can access Dashboard if the first person is unavailable. Store credentials securely and document how to revoke or replace them if exposed. These steps do not guarantee a successful broadcast, but they make the checks observable and reduce avoidable last-minute confusion.
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
Do I need to schedule a BoxCast broadcast before starting Wirecast?
For the documented direct RTMP and SRT workflows, yes: schedule the broadcast in BoxCast Dashboard first. Wirecast supplies the outgoing feed, while the scheduled broadcast establishes the BoxCast event it is meant to serve.
Should I use RTMP or SRT?
Use the route your account exposes and your Wirecast version can configure correctly. RTMP requires a server URL and stream key, while SRT requires address, port, stream ID and potentially a passphrase, plus stereo audio at 48 kHz for this BoxCast workflow.
Is a BoxCaster required to connect Wirecast to BoxCast?
No. BoxCast documents direct RTMP and SRT software connections as well as the optional secondary-display route to BoxCast hardware. The hardware path is relevant when you have a BoxCaster and compatible display output, not a prerequisite for the direct methods.
How early should Wirecast start?
BoxCast’s Wirecast-specific guide recommends starting two to three minutes before the scheduled start. Treat that as setup guidance, not a start-time guarantee, and leave enough time to confirm picture, sound and the incoming feed.