If by Astra you mean Cesbo Astra, the available documentation reviewed here does not verify a workflow for scheduling uploaded prerecorded videos. Before building a timetable, confirm the product and version, then distinguish a playlist of channels from timed playout of video files.
That distinction matters: Cesbo Astra’s documented stream configuration centres on media flows with inputs and outputs, while its HTTP Play playlist provides access to enabled channels. Neither establishes that you can upload several videos, assign times, and have Astra play them in sequence. If you meant a different product called Astra, check its name and documentation before following Cesbo-specific references.
First identify which Astra you mean
“Astra” is not enough information to identify a streaming product. This guide uses Cesbo Astra, documented at Cesbo’s Astra site, as its reference. The title alone does not establish that this is the product or version you have installed.
Write down the vendor, release number, and what you want to schedule. For example: “Cesbo Astra version X, playing a sequence of MP4 files at set times” is more useful than “Astra video schedule”. Also note whether you run Astra yourself on a Linux server or access a hosted service. Those details affect which documentation applies.
The word “schedule” can mean several things. You may want a channel guide listing services, a playlist that lets viewers choose channels, a continuous loop of a file, or timed playout in which different prerecorded programmes start at particular times. A feature that meets one of those needs does not necessarily meet the others.
If you are building a YouTube channel rather than a broadcast system, keep the destination in view too. A workflow that exposes channels to compatible players is not automatically a way to send a scheduled programme to YouTube Live. For a broader view of source and destination choices, how to create a looping YouTube Live stream with a YouTube playlist covers a different YouTube-oriented approach; it should not be read as Cesbo Astra instructions.
What Cesbo Astra documents
Cesbo describes a stream as an individual channel or media flow that receives content from sources, processes it, and delivers it to clients. Its stream configuration documentation describes source and output configuration. Listed source types include network feeds such as HLS, HTTP MPEG-TS, UDP/RTP, SRT and RTSP, as well as broadcast reception options.
This model is useful when you need to receive and distribute a feed. It does not by itself tell you whether Astra can manage a calendar of uploaded files. Receiving a feed and scheduling a library of prerecorded programmes are separate jobs: one starts with a source that supplies content; the other needs a way to select files, place them in a sequence or timetable, manage transitions, and send the resulting output somewhere.
Cesbo’s HTTP Play material documents how enabled channels can be exposed over HLS or HTTP MPEG-TS. Its playlist documentation describes M3U8 or XSPF playlists as ways to organise access to channels. That is useful for clients choosing a channel, but it is not evidence of a timed video-file schedule.
The reviewed documentation also discusses HLS segmentation. Segmentation divides a continuous stream into pieces suitable for HLS delivery; it does not create a programme timetable. The HLS segmenter guide notes that transcoding and caching require additional software. Treat this as a delivery detail, not as confirmation of file scheduling.
The practical conclusion is deliberately narrow. The documentation cited here explains stream inputs, channel delivery, playlists, and HLS-related handling. It does not show a current workflow for uploading multiple prerecorded videos and assigning each a date or start time. Absence from these reviewed pages is not proof that no version or add-on can do it; it is a reason to request version-specific evidence rather than inventing menu steps.
A channel playlist is not a playout schedule
A channel playlist is usually an index for clients. It can tell a compatible player which channels are available or where to find them. A playout schedule is a control plan for what goes out, in what order, and when. The similar word “playlist” can hide that difference.
| Question | Channel playlist | Timed playout schedule |
|---|---|---|
| What is listed? | Channels or stream addresses | Video items and, often, live sources or breaks |
| Who uses it? | A player or viewer selecting a channel | The playout system deciding what to transmit |
| Does it establish a start time for each video? | No, not by itself | It should, if timed scheduling is the feature you need |
| Does it prove that files can be uploaded? | No | The documentation should state supported files and limits |
An M3U8 or XSPF file can be called a playlist without representing a daily programme plan. Check what its entries point to. If they refer to channel streams, that is channel discovery or access. It does not mean the server will switch between a folder of uploaded programmes at specified times.
This distinction helps avoid a common detour: preparing a channel list and expecting it to behave like a TV playout calendar. If your aim is a devotional channel that repeats a set of bhajans, or a study stream that changes lectures at morning and evening times, you need documentation that explicitly covers file-based sequence or timed playout. A YouTube channel playlist is another concept again; the guide to keeping a church sermon stream from repeating the same video discusses repetition as a viewer-facing programming problem, not as evidence of an Astra feature.
Ask the vendor to show what the playlist contains and who acts on it. If it is a list for player applications, it is not a schedule. If it is a timetable consumed by a playout engine, the documentation should explain how items are assigned to times and what happens when a file ends early, runs long, or is missing.
Check whether your setup supports file playback
A limited historical reference deserves careful handling. The official documentation for Astra 4.4.182 includes an MPEG-TS file input using a file://path address and a loop option. This is a legacy-version detail, not confirmation for current releases. It also describes looping a file, not scheduling several videos at different times.
If you find this reference while searching, do not assume it applies to your installation. Check the exact release you run and ask whether the relevant input is supported in that version and configuration. The Astra 4.4.182 documentation is the primary reference for that older release, but it cannot establish current behaviour.
The format matters too. The legacy note is specifically about MPEG-TS; it does not establish that Astra accepts MP4, MOV, or other files as inputs. Nor does a supported input format necessarily include file validation, transitions, a schedule editor, recovery from a missing file, or an output suitable for your destination. Each is a separate capability to verify.
Before testing, make a small inventory: release number; file container and codec; whether the file is local or reachable by a path; output protocol; destination; and whether you need a loop, a sequence, or date-and-time starts. If you are converting source material for YouTube, how to convert ProRes files to smaller H.264 videos can help with a separate media-preparation question. It does not imply those resulting files can be scheduled in Cesbo Astra.
For a real test, use a non-critical channel and a short sample, after confirming the procedure for your release. Observe whether it starts, repeats, and remains available to the intended client. Do not infer that a successful single-file loop proves multi-file scheduling. If the stream is meant to run overnight, test the exact sequence and output path you plan to use before relying on it.
What to verify before building a schedule
Ask for documentation or a demonstration that answers the specific questions below. A “yes, it plays files” answer is not enough if you need a daily timetable. Keep the answers in writing and match them to your installed release rather than a general product page.
- Scheduling model: Can items run sequentially, at specified times, or both? Can the schedule repeat by day, and can you set a date range?
- Media support: Which containers and codecs are accepted? Are files uploaded into the product, referenced by a path, or supplied as a live source? Are there size or duration restrictions?
- Timing behaviour: Must items meet end-to-start exactly? Can you add a planned break? What happens if an item is shorter or longer than its slot?
- Recovery: What happens if a file is absent, unreadable, or the process restarts? Does output resume at the same point, restart the item, or wait for operator action?
- Output and destination: Which protocols and destinations are supported? If you need YouTube Live, is that destination explicitly documented for this workflow?
- Monitoring and control: Can you see which item is on air, revise a future slot, and tell whether output has stopped?
These questions are not a substitute for official instructions. They are a way to spot where the documentation is incomplete before you make a channel depend on a feature. If the intended setup is a continuous YouTube stream, also test the full path from playback to YouTube and monitor the result. Advice on recovering a 24/7 Hindi music stream after an internet outage covers an outage scenario, but does not establish a Cesbo scheduling workflow.
Plan for the unglamorous cases. A file may fail to decode, a schedule may have a gap, or an operator may need to replace tomorrow’s programme. Write down who checks the output and what they do if it is not playing. For a small channel, a short run-through that includes a restart and a file change can reveal more than a long feature list.
Alternatives to investigate without assuming compatibility
If timed prerecorded playout is essential, investigate tools whose own documentation explicitly describes that function. Treat each as a separate product with its own supported formats, outputs, limits, and operating model. A documented workflow in another service is evidence for that service only; it does not add a feature to Cesbo Astra.
For example, Castr’s TV Playout guide describes a Castr workflow for creating a playout, adding content to a timetable, choosing a schedule or loop, and setting a date and destination. Its article also describes gaps and a Break element. These are Castr instructions, not Astra steps. The article is dated July 13, 2026; check Castr’s current documentation for plan limits and workflow changes before choosing it.
Castr also documents a separate pre-recorded-stream feature in its guide to streaming prerecorded videos. That article describes selecting saved recordings, ordering a playlist, and choosing loop or date-and-time scheduling. It says that the feature supports MP4 and that file count and size limits depend on subscription. These details describe Castr’s feature, not Cesbo Astra; recheck current limits on the vendor’s documentation before planning around them.
Compare alternatives against the job you actually have. A fixed all-day loop, a daily timed schedule, and a programme that mixes live sources with recorded items have different requirements. You might also need to publish to a destination other than YouTube, maintain an EPG, or insert intentional breaks. A feature matrix is more useful than a generic claim that a product “supports playlists”.
| What to compare | Why it matters |
|---|---|
| Sequence, loop, and date/time controls | Determines whether the schedule matches a repeating channel or a clock-based programme |
| File formats and upload limits | Determines whether your library is usable without a conversion step |
| Live sources, recorded items, and breaks | Shows whether a mixed programme is possible |
| Output destinations and EPG support | Confirms how viewers or platforms receive the channel |
| Version and plan restrictions | Prevents a test on one edition from being mistaken for a feature in another |
If you already operate Cesbo Astra for receiving or distributing channels, it may still suit that part of the system. The question is whether a separately documented playout function can provide the missing schedule and hand off the result to your existing setup. Ask both vendors about the exact input and output path, and do not assume that products interoperate just because each handles streaming.
For a creator whose need is simply to keep a YouTube broadcast running from a prepared video without leaving a personal computer on, StreamNeo removes that specific always-on computer burden by running an uploaded video as a YouTube live stream. It does not provide Cesbo Astra scheduling, and it is YouTube-only, so it is not a substitute if you need an Astra channel, an EPG, or multiple broadcast destinations.
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
Can Cesbo Astra schedule uploaded prerecorded videos?
The Cesbo documentation reviewed for this guide does not verify a workflow for scheduling uploaded videos by time. Confirm your Astra version and ask for documentation covering timed playout specifically; do not treat a channel playlist or a file loop as proof of that feature.
Is an Astra M3U8 playlist a video schedule?
Not on the evidence in the documented HTTP Play workflow. The playlist organises access to enabled channels; a timed programme schedule needs instructions for choosing video files and assigning them to times.
Does the old Astra file input mean I can schedule MP4 files?
No. The Astra 4.4.182 reference describes MPEG-TS file input and looping, and it does not establish current support or a timed multi-file schedule. Check the documentation for your exact version and format.
Can I follow Castr instructions to set up Astra?
No. Castr and Cesbo Astra are separate products, and Castr’s documented playout steps apply to Castr. You can evaluate Castr as an alternative if its documented formats, destination, and current limits fit your requirements.