If by Astra you mean Cesbo Astra, its settings govern the channels and outputs configured in Astra; they are not automatically the encoder profile YouTube receives. For a conventional H.264 news feed, use YouTube’s published recommendations as a starting point to test: RTMPS, CBR, a two-second keyframe interval, and 1080p at 30 fps with 14 Mbps video.
That is not a verified one-click Astra preset, nor a guarantee of uninterrupted streaming. Your exact setup may use Astra as a source receiver or relay and a separate encoder to send the feed to YouTube, so first identify each part of the chain and test it on the actual connection you plan to use.
Confirm which Astra you are configuring
This guide assumes Cesbo Astra, the broadcast stream software documented at astra.cesbo.com. “Astra” alone does not identify a product version or tell us what job it performs in your setup. It might receive a source, process or relay a channel, or sit upstream of a separate encoder. Establish that role before changing settings.
Astra describes a stream as a media flow that receives content from sources, processes it, and delivers it to clients. A configured Astra channel can have its own source and output behaviour. The feed YouTube ingests, by contrast, is governed by the encoder or relay that connects to YouTube. Sometimes a component may perform more than one role, but do not assume that the presence of an Astra output means its controls map directly to a YouTube encoder profile.
Write down the path from the news source to the YouTube broadcast. For example: a live news source enters Astra, Astra provides a feed to a separate encoder, and that encoder sends an RTMPS feed to YouTube. Your arrangement may differ; verify it against the actual software and connections rather than copying this example as a prescribed design. Note where audio is mixed, where resolution and frame rate are set, and which component holds the YouTube stream key.
This distinction also helps when something goes wrong overnight. If Astra reports a source problem, that is different from YouTube reporting that it is not receiving enough video. A YouTube stream-health message cannot by itself prove that Astra’s input, channel or configured output is healthy, and an Astra monitoring status does not establish that YouTube is accepting a healthy ingest.
Separate Astra channel controls from YouTube encoder settings
Cesbo documents global general settings that serve as defaults for streams unless an individual stream overrides them. These include “Start stream on demand”, “HTTP Keep Active”, “Backup Start Delay” and “Backup Return Delay”. They affect Astra channel behaviour; they are not controls for YouTube video bitrate, codec or keyframe frequency. Astra’s documentation also says that saving general settings restarts Astra, so account for that effect rather than casually changing global defaults during an active broadcast.
The documented default for HTTP Keep Active is zero, which means a channel turns off immediately when its last client closes the session. That behaviour may matter if the channel is meant to remain available continuously, but its significance depends on how your source and output clients use Astra. Check the actual stream configuration and client workflow before changing it. Do not assume that changing a keep-active option forces a YouTube broadcast to stay live: the YouTube ingest connection still depends on the component sending it.
Astra’s advanced stream settings include monitoring, on-demand start and Keep Active. Cesbo explains that with on-demand mode enabled, Astra waits for an incoming request before starting a stream. It also notes that on-demand start is turned off for channels with UDP or HLS outputs. That is a useful reminder to check the output type and specific channel rather than assume the same option applies to every stream.
For an always-on news channel, decide what should happen when a viewer or downstream encoder disconnects. Is the Astra source expected to run continuously, or should it start only when requested? Is there a backup source, and do its start and return delays suit the actual feed? Check Astra monitoring for the channel that matters. These are operational decisions within Astra, separate from setting the encoder’s YouTube output.
The official Astra pages do not establish a universal direct YouTube RTMPS route or a field-by-field YouTube profile for Astra. If you have a separate encoder or relay, configure the YouTube-facing settings there. If your version appears to offer a direct route, verify the feature and its documented controls for that exact version before applying any values below.
Start with RTMPS and H.264
YouTube recommends RTMPS for secure delivery and lists H.264, H.265/HEVC and AV1 as video codec options. For a conventional news setup, H.264 is a practical baseline to test because YouTube publishes resolution- and frame-rate-specific H.264 bitrate recommendations. Treat those values as YouTube platform guidance, not as measurements of your equipment or a promise that your internet connection can sustain them. Check the current YouTube live encoder settings before publishing or reconfiguring a production channel; platform guidance can change.
Choose the protocol and codec in the component that actually sends the feed to YouTube. If Astra is only supplying an upstream channel to an encoder, setting an Astra output format alone does not set the YouTube ingest codec. Likewise, setting H.264 in the encoder does not confirm that the source arriving from Astra is stable or that its audio and video stay in sync.
The recommended baseline in this guide is RTMPS, H.264, constant bitrate (CBR), a two-second keyframe interval, and 1080p at 30 fps with 14 Mbps video. It is a starting configuration to test, not a guaranteed best setting or a verified Astra preset. YouTube’s guidance permits up to 60 fps and recommends a two-second keyframe frequency, not exceeding four seconds. For audio, YouTube lists AAC or MP3; for stereo it lists 44.1 kHz and 128 Kbps. Use the format your encoder supports and check that the output audio is intelligible and in sync with the news footage.
For standard dynamic range (SDR), YouTube lists Rec. 709 and 8-bit depth. Keep colour handling consistent across the source, any processing stage and the encoder when those controls are available. A mismatch can make the picture look different from the source even when the stream is being ingested. Do not change colour parameters blindly in Astra if it is not the stage encoding the YouTube feed.
Choose resolution, frame rate and bitrate together
Select the picture size and frame rate before choosing a bitrate. YouTube’s published H.264 recommendations differ by output mode; taking a bitrate intended for one mode and pairing it with another can produce a poor fit. For a mostly static studio shot, 1080p30 may be a reasonable test. For rapidly moving footage, a higher frame rate may help motion look smoother, but YouTube’s recommended bitrate rises with the mode. A lower-resolution setting may be more practical if the connection cannot reliably carry the higher-rate profile.
| YouTube H.264 output | Recommended video bitrate |
|---|---|
| 720p at 30 fps | 8 Mbps |
| 720p at 60 fps | 8 Mbps |
| 1080p at 30 fps | 14 Mbps |
| 1080p at 60 fps | 17 Mbps |
| 1440p at 30 fps | 15 Mbps |
| 1440p at 60 fps | 24 Mbps |
| 2160p at 30 fps | 30 Mbps |
| 2160p at 60 fps | 35 Mbps |
These are YouTube’s recommended H.264 video rates, not promised results or universal connection thresholds. The lower-resolution option of 720p30 at 8 Mbps can be a sensible test when 1080p30 at 14 Mbps is not sustainable. That is a trade-off: less picture detail for a lower target video rate. Do not treat a higher resolution as automatically better for a news audience if it makes delivery less stable on the actual link.
There is no separate India-specific YouTube bitrate in the cited guidance. Your location matters because the upload path must carry the chosen bitrate continuously, but an ISP name or city does not tell you that it will. Measure the actual production connection, test at the time and place you intend to operate, and leave practical headroom rather than designing around a speed-test peak. If the line is shared with office traffic, account for that traffic as well.
Also consider what the video contains. A fixed presenter shot with graphics behaves differently from a fast-moving field report, scrolling tickers or frequent cuts. Test representative footage, graphics and audio together; a short static test card will not reveal how your actual programme behaves. For another example of matching a YouTube profile to a connection, see the OBS settings for a 24/7 stream on BSNL. It is a different encoder and connection scenario, so use it for comparison rather than copying values into Astra.
Check keyframe interval and CBR
YouTube recommends CBR bitrate encoding and a two-second keyframe frequency, and says not to exceed four seconds. If the encoder exposes the keyframe setting in frames rather than seconds, the required frame count depends on the output frame rate. Confirm what the control means in your encoder and use its documentation; avoid copying a frame count without checking whether the output is 30 or 60 fps.
CBR aims to keep the video bitrate at a consistent target instead of allowing it to vary widely with picture complexity. It does not mean that every frame consumes precisely the same amount of data, or that the network path is guaranteed to deliver every packet. A news feed with changing scenes still needs a target that the connection and encoder can sustain. A target set too high for the link can result in ingest problems; one set lower than appropriate may reduce picture detail.
When comparing primary and backup ingest feeds, keep their relevant configurations aligned. YouTube’s Live Streaming API health documentation identifies differences in frame rates, keyframe frequencies, codecs and bitrates as configuration issues. If your workflow uses backup ingest, verify that the backup has the same intended output mode and does not silently send a different codec or rate.
For a deeper look at the bitrate trade-off, the 4K 60 fps continuous-stream guide discusses a much heavier output mode. A local news channel should not adopt its resolution just because it is available. Choose the mode that fits your footage, audience and tested connection.
Test stream health before continuous operation
YouTube’s advice is direct: “Make sure to test before you start your live stream.” Run a private or otherwise suitable test using the exact encoder, output settings, news source and production internet connection you intend to use. Let representative content run long enough to expose recurring source interruptions, audio drift, changing network conditions or a failure that appears only after a restart. A brief successful connection proves only that it connected at that moment.
Watch YouTube’s stream health while the test is running and inspect the actual picture and sound from the viewer side. The Live Streaming API represents stream status with states including ready, active, inactive, created and error. Its health documentation describes warnings such as low video bitrate and video ingestion starvation, where YouTube is not receiving enough video for smooth streaming. Consult the YouTube Live Streaming API health documentation when interpreting API health details, and use the Live Control Room’s current guidance for the broadcast you are testing.
If a warning appears, work through the chain in order. Confirm that the source is present in Astra, that the configured channel and output are behaving as intended, and that the encoder is actually producing the selected codec, resolution, frame rate and bitrate. Then check the connection and YouTube ingest health. Lowering resolution or bitrate may be worth testing if the link cannot sustain the chosen profile, but change one factor at a time so you can tell what improved the result.
Astra monitoring and its backup-source delays are separate checks. Confirm that monitoring is enabled where you need it, and that a backup source actually starts and returns as expected in your configuration. Do not infer a successful Astra failover from YouTube’s health panel alone. For a headless setup in a specific Indian city, the Linux VPS streaming guide for Mumbai offers a separate operating context; its hosting assumptions do not establish that your own connection or Astra channel is healthy.
Finally, treat the YouTube stream key as a credential. YouTube explains that the key tells an encoder where to send the feed and allows YouTube to accept it. Do not publish it in screenshots or share it casually. If it is compromised, reset it in Live Control Room and update the encoder that uses it; remember to verify any backup encoder that also needs the key. A key change does not repair a source or bitrate problem, so test the broadcast again after updating it.
Decide what to keep running, and what to monitor
A 24/7 channel is an operating workflow rather than just an encoder preset. Record which component owns each task: receiving the news source, maintaining an Astra channel, encoding the feed, sending it to YouTube, and monitoring the broadcast. A short handover note with the selected output mode and the location of each relevant control is more useful at night than a list of unexplained values.
Decide what an alert should prompt someone to check. If YouTube reports low bitrate or starvation, inspect the encoder output and delivery path. If Astra monitoring reports a channel issue, inspect its configured source and output. If the viewer hears audio but sees a frozen picture, review both the source and the encoded feed rather than assuming the platform’s status settles the diagnosis. The point is to distinguish symptoms and locate the right stage, not to promise that monitoring prevents every interruption.
For a single uploaded programme rather than a changing news feed, the operating problem is different. StreamNeo removes the need to leave your own computer running for that file-based workflow: you upload a video, provide the YouTube stream key, and the broadcast is operated remotely, with monitoring and automatic restarts if it drops. It is YouTube-only and does not replace a live Astra source chain for incoming news. Consider it only if the channel’s content and workflow fit that distinction.
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
What are the best Astra settings for a 24/7 YouTube live channel?
There is no verified universal Astra-to-YouTube preset in the documented material. First identify what Astra does in your chain, then configure the encoder that sends the feed to YouTube. Test a YouTube-guided baseline such as RTMPS, H.264, CBR, a two-second keyframe interval and 1080p30 at 14 Mbps, adjusting to the results on your actual connection.
What bitrate should I use for 1080p YouTube live in India?
YouTube recommends 14 Mbps for H.264 1080p30 and 17 Mbps for H.264 1080p60. Its published settings do not specify a separate India rate, so test whether the particular upload connection can sustain the mode you choose; consider 720p30 at the recommended 8 Mbps if a lower-rate starting point is needed.
How do I keep an Astra stream running continuously?
Check the actual channel’s source, output, monitoring and on-demand or Keep Active behaviour in Astra, including any backup-source delays. Those controls govern Astra’s channel operation, not whether a separate encoder continues delivering to YouTube. Test both sides of the chain and monitor YouTube stream health during operation.
Does Astra send RTMPS to YouTube directly?
The cited Astra documentation does not establish a universal direct YouTube RTMPS route or a standard field-by-field YouTube profile. Your setup may use a separate encoder or relay. Confirm the version and actual path before applying encoder guidance to any Astra control.