A time-of-day playlist schedule in Cesbo Astra Streaming could not be verified in the official documentation reviewed for this article. Before you configure anything, confirm which Astra product and version you use, then ask its documentation or support team whether that edition supports scheduled playlist switching.
A channel’s position in a playlist and its on-demand activation are not the same as choosing different playlists at set times. Do not rely on channel numbering, an assumed schedule screen, or a procedure for a different product named Astra as evidence that daypart switching is available.
Identify the exact Astra product and version
Start with the product name as it appears in your own account, interface, package, or installation records. “Astra” is used by more than one product. The Cesbo Astra streaming software is relevant to channels and streams; an unrelated Astra observatory-automation system also has scheduling documentation. Similar names do not make their settings interchangeable.
Record the edition or product variant, version, and where it is hosted or installed. If you do not know the version, look in the product’s own About, status, or account area, or ask the administrator who installed it. Avoid posting a stream key, login credential, or unredacted configuration file when asking for help. A screenshot of the product heading and version, with private details hidden, is usually a more useful starting point.
Then phrase the question precisely: “Does this Astra edition and version support switching between specified playlists according to time of day or day of week? If so, where is the documented procedure?” This separates a verifiable feature request from the broad question of whether Astra can play a channel or playlist at all.
The official Cesbo Astra Advanced Settings page documents particular stream settings. It describes a channel number used to order channels in a playlist, along with on-demand activation controls. The page reviewed does not describe time windows, days of the week, recurring schedules, time-zone behaviour, or a hand-off between playlists. That is a limit of the evidence reviewed, not proof that no version or separate tool could ever offer such a feature.
Separate channel order from timed switching
A playlist can be ordered without being scheduled. Cesbo’s documentation describes Channel Number as a way to order channels in the playlist. A numbered channel list tells you about relative position; by itself, it does not establish that one set of content replaces another at a particular hour.
This distinction matters if you are planning a devotional channel that should play morning bhajans and evening aarti, a local news loop that changes at a bulletin time, or a study stream that shifts from quiet music to a lecture. Those are scheduling requirements: you need a documented way to select content by time, define when the selection applies, and determine what happens at the boundary. An ordered channel list does not answer those questions.
The same caution applies to Start stream on demand and Keep Active. The Advanced Settings page describes starting a stream in response to an incoming request and keeping a channel active for a period after the last client disconnects. It also says on-demand start is turned off for channels with UDP or HLS outputs. These settings concern activation and activity after clients disconnect; they do not document a daily playlist timetable.
If you are trying to plan an actual rotation rather than evaluate an Astra feature, a separate workflow may be relevant. For example, a Python-script approach to rotating playlists on a YouTube 24/7 stream discusses a different way to build rotation. It should not be treated as an Astra procedure, and a script introduces its own requirements for testing, process monitoring, and recovery.
Verify that your edition documents a schedule
Before following instructions from a forum post or video, look for documentation tied to the exact product and version you recorded. A reliable procedure should identify where the schedule is created, how you choose the playlist or content source, how the time range and recurrence are set, and what clock or time zone the schedule uses.
It should also explain what happens when schedule entries overlap, when no playlist is eligible, or when the stream is not running at a hand-off time. If a page only explains how to order channels or start them on demand, it has not answered those scheduling questions. Do not fill gaps by guessing that a cron expression, a JSON schedule, or another product’s “schedule” screen will work in Cesbo Astra.
The observatory product’s Astra scheduling syntax documentation belongs to a separate astronomy-automation application. It is useful here only to distinguish products with the same name, not as a media workflow or source of syntax for Cesbo Astra.
If you contact the vendor, include the intended use in a short, concrete example: “Playlist A should play during the morning, and Playlist B should play in the evening, every day in India Standard Time.” Ask whether your edition supports that behaviour natively, whether the time zone is configurable, and whether the stream must remain active across the change. Ask for a version-specific documentation link before making the setup depend on it.
Until you have that confirmation, describe the feature as unverified for your edition. That is more useful than spending a night testing an invented setting and discovering that the control was for a different product, or for channel activation rather than content selection.
Compare the scheduling choices before committing
There are two separate decisions: whether your current Astra product has a documented daypart feature, and what to use if it does not. Do not choose a workaround until you know which part of the job it must perform. “Play the same loop continuously” is a different requirement from “switch sources at a local time and recover cleanly if a hand-off fails.”
| Approach | What to verify | Main trade-off |
|---|---|---|
| A documented Astra schedule | The exact edition and version, schedule controls, time zone, recurrence, overlap rules, and behaviour at a hand-off | It may fit your existing workflow, but do not assume the feature exists until its own documentation confirms it. |
| A separate playlist or scripting workflow | How it selects content, what machine or process must stay available, and how it handles a missed change | It can provide more control, but you take responsibility for testing and recovery. |
| A fixed, continuously repeated programme | Whether one prepared file or playlist is enough for the whole day | It is simpler to operate, but does not provide daypart changes. |
For a script-based route, the article on using a playlist file with FFmpeg to schedule videos is a relevant starting point, not a guarantee that it implements time-of-day switching as you need it. Read it against your actual requirement: whether different lists must play at different hours, whether a hand-off can interrupt playback, and who will notice and fix a process that stops. A one-file playlist and a time-aware controller solve different problems.
Your operating conditions matter as much as the feature. If a small shop is streaming from a home or shop PC, a workflow that depends on that machine staying on and connected may be less suitable than one that does not. If you run an internet-radio-style stream and already manage a separate always-on system, a script may be reasonable, provided you can monitor it. For bandwidth and connection planning, the guide to bitrate, latency, and stream stability can help you assess the network side; it does not confirm Astra scheduling support.
Make a decision only after writing down the wanted timetable and fallback. For instance, specify which programme should play outside the listed dayparts, what should happen if a change is missed, and whether a brief interruption is acceptable. These are practical acceptance criteria you can test before depending on a workflow overnight.
Test with a small, observable schedule
If the exact product documentation confirms a scheduling feature, test it with material that is safe to play and easy to recognise. Use short, distinct sample clips or otherwise obvious content in each intended slot. This lets you see whether the correct source starts at the expected boundary without relying on an audience member to report that the wrong programme remained on air.
Use the time zone stated by the product or account, not an assumption based on the location of your viewers. If your audience is in India but the software is hosted or administered elsewhere, check which clock controls the schedule. Confirm whether a time entry means the start of a slot, the end of one, or both. Where the documentation leaves these points unanswered, ask support rather than infer them from the appearance of a time picker.
Test more than the happy path. Check the transition between slots, the result when the stream is stopped at the scheduled change, and what happens when a programme is not available. If two entries can overlap, establish which one takes precedence. If there is a fallback playlist, confirm when it is used. Keep notes of the version, settings and observed result so that another person can repeat the test.
Do not test a new schedule for the first time during an important broadcast. A live devotional service, scheduled local bulletin, or school session has a real audience and a real start time. First establish whether the feature is supported, then validate it in a controlled period, and only then decide whether it is dependable enough for the channel’s operating routine.
If Astra documentation confirms only ordering or on-demand activation, you have not failed to find a hidden schedule by not clicking around further. You have learned that those particular controls do not establish the daypart feature you need. Return to the product documentation or vendor support with the exact requirement, or assess a separate workflow with its own test and recovery plan.
Build a fallback for the hours you cannot watch
A schedule is not only a list of intended changes; it is also a plan for what happens when one does not occur. Before relying on any confirmed feature or external workflow, choose a fallback programme and decide how you will detect a failed hand-off. A static image or a single safe loop may be preferable to an empty output if the planned playlist is unavailable, but only if that matches your channel and the platform’s requirements.
For a YouTube broadcast, distinguish the scheduling of content inside your playback system from the live event and stream configuration on YouTube. YouTube’s live streaming help explains the platform’s live-streaming setup. Check the current official instructions for your account and event rather than assuming a playlist schedule creates or configures a YouTube event automatically.
Keep a simple record of what you expected to happen and what you observed: the local time, selected content, whether the stream remained active, and any message shown by the product. This is especially useful when the channel is managed by more than one person. It turns a vague report such as “the evening show did not work” into a question about a specific transition, event, or source.
Avoid promising viewers a precise change until the feature has passed a test under the same conditions you will use in production. If you are using an external script or playback arrangement, identify who will check it and how they can restore the default programme. A fallback is operational work, not a claim that any system cannot fail.
Ask for evidence, then choose the workflow
A useful support reply should match your product identity and answer the scheduling questions directly. Save the reply or documentation reference with the setup notes. If the answer applies only to a later version, a particular output type, or a separately licensed component, record that condition before planning around it. A feature name without version and scope is not enough to establish that your installation can use it.
If no time-of-day playlist procedure is documented for your edition, choose among a simpler fixed programme, a separately maintained scheduling workflow, or another product whose official documentation explicitly covers the required behaviour. Compare the work involved in keeping it running, not just whether it can make the desired change once. A solution that switches programmes but needs an unattended computer and manual repair may be the wrong fit for a channel that has no night operator.
For creators whose main problem is keeping a prepared video broadcasting without leaving their own computer running, StreamNeo removes that particular burden: you upload the file once and the 24/7 YouTube broadcast continues with your computer switched off. It is YouTube-only and is not an Astra daypart scheduler, so it does not establish that separate playlists can be selected by time of day.
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
Does Cesbo Astra support different playlists by time of day?
The official Cesbo Advanced Settings page reviewed here does not document time-of-day playlist switching. It describes channel ordering and on-demand activation settings instead. Check documentation for your exact edition and version, or ask Cesbo support for a procedure that explicitly covers scheduled playlist changes.
Does Channel Number schedule a playlist?
No. The documented purpose of Channel Number is to order channels in a playlist. An order does not define times, recurrence, time zone, or a hand-off between different playlists.
Can I use the other Astra product’s scheduling syntax?
No. The scheduling page at docs.withastra.io is for an observatory-automation application, not Cesbo Astra media streaming. Confirm the product identity before using any instructions or syntax.
What should I do if my version has no documented schedule?
Do not infer a schedule from on-demand controls or copy a procedure from a different Astra product. Ask the vendor whether your exact version supports the requirement, or assess a separate workflow and test its timing, fallback, and recovery before depending on it.