To stream a Centova Cast radio station to YouTube Live, start the station, connect a compatible live-source application with the station’s Centova connection details, then send that application’s output to YouTube using the stream URL and key. Centova Cast does not send the stream to YouTube by itself: the live-source application is the link between the station audio and YouTube.
The exact connection fields depend on your station host and server setup. Find them in Centova Cast under Quick Links → Live Source Connections, and confirm application compatibility with your hosting provider before configuring the encoder. Test the complete path before scheduling a broadcast.
How Centova Cast, an encoder, and YouTube fit together
Think of this as two connections rather than one. First, a live-source application connects to your Centova Cast station and receives or supplies station audio according to the host’s configuration. Then that application sends an encoded live stream to YouTube. Centova’s manual describes starting the server and connecting a live source; YouTube’s encoder workflow describes the separate connection from an encoder to YouTube.
The application must be compatible with the protocol and connection details provided for your station. Do not assume that a particular encoder supports every Centova host’s source configuration, or that a programme intended for video production can automatically take the station audio as an input. Ask your provider which live-source applications are suitable for your account, and check how the application routes that audio into its YouTube output.
AutoDJ and a live source are different ways of getting audio to the station. If your hosting account includes AutoDJ, it can play uploaded media when the server is running. AutoDJ is not included with every account, and a running server without AutoDJ still needs a live source to supply audio. Starting the Centova server alone does not create a YouTube broadcast.
For a station that already has a playlist, the key practical question is whether AutoDJ is playing and whether the live-source setup can use it as intended. For a presenter sending a live programme, the application’s audio input and the station’s source connection matter. This distinction also helps you choose a workflow: a station relay is not the same as building a visual scene or mixing a microphone and other inputs. If you need a broader overview of the YouTube side, see this beginner’s guide to going live on YouTube.
Start the Centova Cast server
Sign in to Centova Cast and use Start under Server. Wait for the control panel to show that the server is running before trying to connect a source. If it will not start, resolve that issue with the hosting provider first; encoder settings for YouTube cannot fix a station server that is stopped.
Next, establish which audio source your account is using. If AutoDJ is available and configured, check that it is playing the intended media. If you are using a live source, make sure the application you plan to use is ready to connect with the station’s source details. A green or running server status is not proof that audio is reaching either the encoder or YouTube, so listen to the station output or use the monitoring information available in your panel.
Centova documents a special consideration for SHOUTcast v1 when AutoDJ is active: stop AutoDJ before starting a live broadcast. Its instructions say this is not necessary for SHOUTcast v2 or IceCast. Because a host can configure a station in different ways, confirm the server type shown for your station rather than applying the SHOUTcast v1 procedure to every account.
Starting and checking the station first separates Centova problems from YouTube problems. If the station audio is absent, troubleshoot the source at Centova before adding YouTube to the chain. Once you can confirm the station’s audio is available, proceed to the live-source connection details.
Find the station’s live-source connection details
In Centova Cast, open Quick Links and find Live Source Connections. Copy the connection values shown there into the compatible live-source application. Use the values for your own station, not a generic example from a forum or another account. Centova’s live broadcast instructions explain where to find these settings; your provider is the right source for confirming which applications and source protocols its particular setup accepts.
The details may include a host, port, source password and other connection fields. Treat the source password as a credential. It is distinct from the Centova administrator login and should not be pasted into a public stream description or shared with viewers. Keep a private note of which password belongs in the live-source application and which belongs in the YouTube encoder; they serve different connections.
Do not substitute localhost or 127.0.0.1 for the station’s actual address. Those names refer to the computer running the application, not necessarily the Centova server. Likewise, a port from an unrelated station is not a safe assumption. If Quick Links is unclear or the application rejects the supplied host and port, ask the provider to confirm the values and whether the relevant port is reachable from the computer or service running the application.
Connect a compatible live-source application
In the application, create or select a source connection for the Centova station and enter the host, port, password and any other fields supplied by Quick Links. Select the source type or protocol only as instructed by the host. Centova’s documentation does not establish one universal application that works with every provider configuration, so compatibility should be verified rather than inferred from an application’s name or general streaming features.
You also need to know how the chosen application makes the station audio available to its YouTube output. Some workflows receive a station feed; others route audio through an input or a local audio path. The relevant requirement is that the signal being sent to YouTube is the intended station programme, not silence, monitoring audio or a microphone that was selected by default. Make a short test and listen to the YouTube preview before relying on a scheduled broadcast.
If the source connection fails, check the basics in a deliberate order. Confirm the host and port against Quick Links, use the source password rather than the administrator password, and verify that the address is the server’s actual address rather than a loopback address. Check whether AutoDJ or another source is already occupying a SHOUTcast connection, and ask the provider whether firewall access to the stream port is permitted.
Centova’s troubleshooting guidance notes that for SHOUTcast v1 the source port is the stream port plus one; its example pairs 8000 with 8001. Treat that as a server-type-specific detail, not a universal adjustment to make on every Centova station. Do not change a port unless the station’s displayed details or provider confirms it. For more on planning a long-running broadcast rather than just making the initial connection, see this guide to a dependable 24/7 stream schedule.
Enter YouTube’s stream URL and key
In YouTube Studio, choose Create → Go Live and use the Stream tab, or schedule a broadcast under Manage. Live Control Room provides the stream URL and stream key for the broadcast. In the live-source application, enter the URL in its server or destination field and the key in its key or stream-name field. The field labels differ between applications, so follow the selected encoder’s own instructions as well as YouTube’s guide to creating a live stream with an encoder.
The YouTube key is a credential that authorises the encoder to send to the associated stream. Keep it private, do not include it in the public description, and avoid sending screenshots that expose it. If you believe it has been shared, replace or reset it through YouTube Studio before the next broadcast, then update the encoder with the new key. Do not confuse it with the Centova source password: one is used for the station connection and the other for YouTube ingest.
Before starting the encoder, confirm that you have selected the intended YouTube stream and destination. A saved key can sometimes remain in an encoder after a previous test, so check the visible title or scheduled event in Live Control Room. If you are preparing a recurring radio station, keep a private checklist of which stream entry and key are current, without putting either credential in a shared document or public-facing schedule.
Prefer RTMPS when the encoder supports it
YouTube supports RTMPS, an encrypted connection for sending an encoder stream. If the application supports RTMPS, copy the RTMPS URL shown in Live Control Room and use that rather than changing an RTMP address by guesswork. YouTube explains the option in its RTMPS help page; Google’s RTMPS ingestion guide specifies the rtmps protocol and port 443, and notes the hostname requirement for TLS SNI authentication.
Support must exist in the encoder and be correctly configured. If an application only accepts RTMP, use the supported URL and check the current YouTube settings rather than forcing an unsupported scheme or port into a field. If RTMPS reports a certificate or timeout error, verify that the URL uses rtmps, that the application supports it, and that the port is 443. Where the encoder exposes hostname or TLS options, do not replace the URL hostname with an IP address: correct hostname handling is relevant to SNI.
RTMPS protects the connection in transit; it does not establish that your audio is correct, that the network can sustain the chosen quality, or that the broadcast will remain uninterrupted. It is a sensible preference when supported, not a substitute for testing the route and monitoring the stream.
Set quality for the connection you have
Choose video and audio settings that the encoder, network and YouTube ingest can sustain. A radio station may use a static image or simple visual, but even that is a video stream to YouTube. Follow YouTube’s current encoder settings and bitrate guidance for the intended resolution, frame rate and codec rather than copying a number from an unrelated setup.
YouTube’s guidance includes H.264, H.265 (HEVC) and AV1 video, AAC or MP3 audio, constant bitrate (CBR), and a recommended two-second keyframe interval with a four-second maximum. Its bitrate table gives different targets according to codec and video mode; for example, for 1080p at 30 frames per second it lists 14 Mbps for H.264 and 10 Mbps for AV1 or H.265. These are YouTube’s published encoder targets, not evidence that your internet connection or encoder can maintain them. A simple visual does not remove the need to choose a mode the rest of the path can handle.
Test upload capacity from the location where the encoder runs. YouTube recommends a speed test to test your upload bitrate. Allow for ordinary variation in a home or business connection, and choose a less demanding setting if the test or preview shows instability. Avoid selecting a resolution or bitrate just because it is the highest available: the practical objective is a stable, correctly received programme with intelligible audio.
When comparing applications, look at the station host’s specific protocol compatibility, RTMPS support, audio input and routing, monitoring and restart behaviour, operating-system support, and cost. There is no need to buy a hardware encoder just to relay an existing station feed if a compatible software workflow meets the requirement. Conversely, a dedicated device or a locally operated encoder may suit you better if you need local inputs or hands-on control. For a setup that relies on a personal computer remaining on, account for the power and operating demands; this VPS guide for a 24/7 bhajan stream discusses a different operating approach and its trade-offs.
Preview, test, and check stream health
Start the live-source application and confirm that it connects to Centova. Then start or send the YouTube output and wait for the incoming stream to appear in Live Control Room. For a scheduled stream, the preview is a checkpoint: inspect it and click Go live when ready. Starting the encoder and seeing a preview does not necessarily mean the scheduled event has been published to viewers.
Use the preview to check the complete chain. Listen for the correct station audio, adequate level, and any silence, clipping or unexpected input. Confirm that the visual is present and that playback looks representative of the planned broadcast. YouTube recommends testing before going live, including audio and representative movement in video. This is particularly useful for a radio station with a static image: check that the image and sound are both reaching the intended event, rather than assuming the live-source connection also proves YouTube ingest is healthy.
Watch the stream-health information in Live Control Room after going live and respond to warnings rather than leaving the stream unattended. For a channel run overnight, make a practical monitoring plan: know who checks the event, how they will notice a drop, and what steps they can take to reconnect the source or encoder. A guide to monitoring a YouTube radio livestream when nobody is watching can help you think through that operational gap. Neither a successful test nor a monitoring routine guarantees uninterrupted broadcasting.
When finishing, stop the encoder and, for a scheduled event, use End Stream in Live Control Room as appropriate. YouTube states that streams under 12 hours are automatically archived. Check the resulting archive in Studio after the event, especially if you need to confirm that it is available or use it as a record. For a broadcast expected to run longer, do not assume the archive will behave the same way; consult YouTube’s current live-stream guidance.
If you need a workflow that avoids keeping your own computer on solely to relay a prepared video file, StreamNeo can remove that particular computer-running burden by turning an uploaded video into a YouTube live stream. It is YouTube-only and addresses a different workflow from connecting a live Centova radio source, so it is not a replacement for the Centova-to-encoder steps above.
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
How do I stream my Centova Cast radio station to YouTube Live?
Start the Centova server, get the live-source values from Quick Links → Live Source Connections, and connect an application confirmed compatible with your station. Enter YouTube’s stream URL and key in that application, then test the preview and monitor stream health. The Centova source connection and YouTube ingest are separate parts of the setup.
Can I broadcast my internet radio station on YouTube without AutoDJ?
Yes, but the running station server needs a live source to provide audio if AutoDJ is not available or not being used. AutoDJ is an account-dependent feature, not something to assume is included. Ask your host which compatible live-source application and connection details apply to your station.
Where do I put the YouTube stream key in my encoder?
In the encoder’s YouTube destination settings, enter the key in the field labelled stream key, key, or stream name, and enter the URL in the server or destination field. Labels vary by application, so use its documentation alongside YouTube’s Live Control Room instructions. Treat the key as a credential and keep it out of public descriptions and shared screenshots.
Does RTMPS guarantee that my stream will stay live?
No. RTMPS encrypts the connection to YouTube when the encoder supports it and the URL and TLS settings are correct, but it does not guarantee stable audio, network capacity or uninterrupted broadcasting. Test the stream, choose quality for the connection available, and monitor Live Control Room for health warnings.