Recommended Free Tools
Run one Icecast server on your VPS and use Liquidsoap to feed it two independent audio playlists: one to a /hindi mountpoint and one to /punjabi. Listeners choose a stream by opening its URL. This design keeps the channels separately programmed while sharing the same server; continuous operation still depends on your VPS, network, configuration and recovery plan.
How the two-stream setup works
Icecast serves audio streams. It calls each distinct stream path a mountpoint, and one Icecast server can host multiple streams. Liquidsoap supplies the audio: configure a playlist source and Icecast output for each language, using a different mountpoint for each. See the Icecast Basic Setup and Liquidsoap Quickstart.
As an Amazon Associate I earn from qualifying purchases.
- Hindi: a Hindi playlist sent to
/hindi. - Punjabi: a Punjabi playlist sent to
/punjabi.
A listener URL combines your VPS hostname or IP, Icecast port and mountpoint path, for example http://your-server.example:8000/hindi. Substitute your actual hostname and configured port. The second channel uses the same host and port with /punjabi. Icecast also documents .m3u playlist links for compatible players. Choose simple mountpoint names without spaces or unusual characters; the appropriate extension and format conventions depend on the codec and clients you intend to support.
Plan the VPS and stream settings
Estimate bandwidth from listeners, not just channels
Two channels do not mean only two outgoing connections: every listener receives the stream they selected. Estimate outbound data using each stream’s encoded bitrate and its concurrent listener time. To convert bits to bytes, divide by eight; allow additional capacity for protocol overhead. Liquidsoap’s documentation makes the qualitative point that more listeners require more bandwidth, but does not provide a VPS sizing benchmark. Your actual capacity depends on bitrate, audience concurrency and the VPS network limit.
#1 Best Overall
Choose compatible formats and bitrates
Set the encoding in each Liquidsoap Icecast output and check that the resulting format works with your intended listeners and players. A higher bitrate uses more outbound bandwidth per listener; a lower one reduces that demand but may not suit your audio-quality needs. The cited project documentation does not prescribe a universal bitrate or listener count, so test with your selected encoder, format and expected load rather than treating a sample value as a capacity guarantee.
Secure Icecast before exposing it
Replace default source and administrator passwords before making the server reachable from the public internet. Liquidsoap’s Quickstart warns that default credentials can expose source or administrator access. Keep the source credentials used by Liquidsoap separate from public listener URLs, and restrict administrative access according to your hosting and network setup.
Configure and test both channels
The project documentation describes configuration concepts, not a current installation recipe for every VPS distribution. Install Icecast and Liquidsoap using packages and service-management procedures appropriate to your operating system and installed versions. Liquidsoap’s development documentation may not match the syntax in an installed stable release; check the documentation for your version before copying configuration.
- Install the software. Install Icecast and Liquidsoap on the VPS using the operating system’s supported package or installation method. Confirm the versions and configuration-file locations for that system.
- Configure Icecast. Set its listening address and port, then change the default source and administrator passwords. Permit only the necessary network access for listeners and administration.
- Separate the music libraries. Organize the recordings into distinct Hindi and Punjabi playlists or directories. Check that each playlist contains files in formats your Liquidsoap installation can read.
- Create two Liquidsoap sources and outputs. Configure one playlist source and Icecast output for Hindi and another for Punjabi. Give each output the VPS host, Icecast port, source credentials, encoding settings and a unique mountpoint such as
/hindior/punjabi. Liquidsoap documents that one instance can stream multiple audio feeds; maintaining one or multiple Liquidsoap processes is an operational choice, not a requirement to create separate Icecast servers. See Liquidsoap’s Icecast and Shoutcast output documentation. - Plan continuity and restarts. Liquidsoap demonstrates wrapping a playlist source with
mksafeto make a fallible source infallible. Icecast also supports a mount-specific fallback mount, subject to matching streaming format. These mechanisms address source continuity in particular situations; they do not establish VPS, network or end-to-end uptime. Configure service restarts, monitoring and recovery behavior as part of your own deployment plan. See the Icecast configuration reference. - Test from outside the VPS. Start the services, then open both listener URLs from a device or network that is not the VPS. Confirm that each path plays the intended language, metadata is sensible, audio is audible, and a failure or playlist-end condition behaves as you planned.
Keep the channels operationally distinct
Give each stream its own playlist, mountpoint and output configuration so that changing the Hindi schedule does not unintentionally alter Punjabi programming. Check metadata and playlist behavior for each feed, and decide how each should behave if its source fails or its playlist has no playable items. Icecast’s FAQ discusses sources and concurrent distinct mountpoints: Icecast FAQ.
Rank #3
Before launch, confirm you have the rights needed for the recordings, territories and way you operate the service. Requirements can vary with the recording, repertoire, ownership and listener locations. Icecast and Liquidsoap provide streaming software, not music permissions; consult the relevant rights holders or licensing bodies for the territories involved.
Common problems and what to check
- One mountpoint works, the other does not: compare the two Liquidsoap output settings, especially mountpoint spelling, host, port and source credentials. Confirm the second output is configured and the corresponding source is running.
- A listener URL fails: verify the VPS hostname or IP, Icecast port, exact mountpoint path and network access. Test the full listener URL from outside the server. If using a playlist link, make sure the listener’s player accepts the documented
.m3uform. - Audio stops or a mount disappears: inspect the Liquidsoap source and service logs, confirm the playlist still contains readable files, and check the restart and source-fallback behavior you configured. A fallback mount must use a matching streaming format.
- Playback is unreliable as listeners increase: compare actual concurrency and both encoded bitrates with available VPS outbound bandwidth. The documentation does not establish a universal listener limit or instance size.
- Source authentication fails: confirm Icecast and Liquidsoap use the same current source password for the relevant output, and ensure default credentials were replaced.
- Configuration examples do not parse: check your installed Liquidsoap version against the documentation version. In particular, the linked output reference is development documentation, so syntax may differ.
Or let it run in the cloud
For a YouTube channel built around prerecorded Hindi or Punjabi music, StreamNeo is a separate option: upload a recording or build a playlist, add your YouTube stream key, and go live. It loops uploaded videos from the cloud, so nothing has to stay on at home. It streams the upload as made, up to 4K 60fps, at one price per slot; it automatically recovers if YouTube drops the stream. The first day is free with no card. Monthly: $9.99 per month. StreamNeo streams prerecorded video to YouTube only; it is not an Icecast radio setup and does not go live from a camera. See StreamNeo or start the free first day.
Quick Recap
Best Value
- 32GB ( 16GBx2 ) 1866 MHz ECC Reg 240pin Standard Voltage Dual Rank VLP Memory Module.
- Every module is backed by a lifetime limited warranty from the manufacturer. We always have hundreds in stock!
- Free technical support from our experienced technicians.
- Every single module is fully tested by the manufacturer and certified. These parts are not compatible with non-server computers.
- Compatible with most major brand servers. Not sure if your server is compatible? Feel free to contact us. Our experienced technicians can verify if these parts will work for you.
Rank #4
- 128GB ( 16GBx8 ) 1600 MHz ECC Reg 240pin Standard Voltage Dual Rank VLP Memory Module.
- Every module is backed by a lifetime limited warranty from the manufacturer. We always have hundreds in stock!
- Free technical support from our experienced technicians.
- Every single module is fully tested by the manufacturer and certified. These parts are not compatible with non-server computers.
- Compatible with most major brand servers. Not sure if your server is compatible? Feel free to contact us. Our experienced technicians can verify if these parts will work for you.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
