Streaming, AutoDJ, and Hosting FAQ

Question 1

How does stream relay work?

Accepted Answer

A stream relay (also known as a slave or edge server) receives an existing audio broadcast from an upstream master server or external audio source and redistributes that stream to a large listener audience. With SPCast, you can easily configure stream relays to conserve uplink bandwidth, scale reach, and build reliable failover setups.
How Stream Relays Operate The fundamental purpose of a stream relay is decoupling broadcast encoders from end-user listener distribution:
Master Source Feed: Your studio encoder or an external broadcast provider (such as laut.fm, a local Icecast server, or a syndicated network feed) transmits a single audio stream. Relay Pull Connection: The SPCast instance connects to the configured source URL and continuously ingests the audio bitstream. Local Audience Distribution: Listeners connect directly to your SPCast relay server. The upstream master server experiences the resource load of only a single listener connection. Common Use Cases for Stream Relays Broadcasters deploy relay architectures in several everyday production scenarios:
1. Studio Bandwidth Offloading Home studios and small broadcast booths often have limited residential upload speeds and cannot serve hundreds of simultaneous listeners directly. The studio encoder sends a single stream to an internal master, while high-capacity SPCast relay servers in datacenter clusters distribute the stream to thousands of listeners.
2. External Platform Ingestion If you broadcast on existing platforms (like laut.fm) but wish to provide custom HLS streams, branded HTML5 web players, and dedicated listener statistics on your own station website, you can ingest that external feed into SPCast as a relay source.
3. Geographic Edge Clustering For global audiences, relay nodes can be positioned across different regions (such as Europe and North America). Listeners automatically connect to their regional relay, reducing latency and avoiding network buffer underruns.
Comparing Pull Relays and Push Relays Depending on your network topology, two fundamental relay methodologies exist:
Pull Relay (Standard in SPCast): The relay node actively reaches out to the master server URL to request and pull the audio stream. This requires no administrative access to the source server configuration. Push Relay: The source encoder or master server pushes live audio packets directly toward configured relay endpoints. Check the available outputs in product management for the intended relay. The format guide explains changes to transcoding and relays since version .096.
Direct Integration with AutoDJ SPCast gives you full control over server behavior when the upstream relay feed disconnects:
Automatic Fallback to AutoDJ: If the live relay source drops (for instance, due to a local studio Internet outage), the integrated AutoDJ immediately initiates playback from your pre-loaded backup playlists. Your audience experiences no silence or abrupt stream disconnections. Automatic Live Restoration: Once the upstream master source comes back online, the server smoothly transitions back to the live relay signal. Live Metadata Passthrough: Track titles, artist names, and ID3 metadata provided by the master source are passed through to all connected listeners in real time. Configuring a Relay in the Web Dashboard Setting up an audio relay in SPCast requires only a few configuration steps:
Navigate to the server settings in your SPCast dashboard. Select the operating mode: Relay or Master with AutoDJ Fallback. Enter the full URL of the source instance (e.g., http://master.example.com:8000/live). Provide optional authentication credentials if the source stream is password-protected. Set the reconnect interval (e.g., 5 seconds) to ensure prompt reconnection after temporary network dropouts. Save changes. The server will immediately establish the pull connection to the remote stream. View SPCast or ask support about relay configuration.

Question 2

How much AutoDJ storage is included?

Accepted Answer

The base plan includes 50 GB of AutoDJ storage. AutoDJ accepts MP3 files only. This also applies to recorded shows and jingles played through AutoDJ.
Prepare files and check storage Keep your original audio on your own storage device. Convert other formats to MP3 before uploading; changing the filename extension does not convert audio. Check levels, the start and end of each file and track information on a small sample before uploading your full library.
Storage use depends on bitrate and duration. Check the sizes of your prepared MP3 collection and the storage usage shown in AutoDJ. Delete files only after keeping a local backup and updating any playlists that use them.
Add storage The base plan includes 100 concurrent listeners, 50 GB of AutoDJ storage, broadcaster accounts and streaming at up to 320 kbit/s. AutoDJ accepts MP3 only.
Service Monthly price SPCast base plan 30 €* Each additional concurrent listener 0.18 €* Each additional GB of AutoDJ storage 0.11 €* Optional web hosting from 5 €* A listener slot is one simultaneous stream connection. Choose capacity for your busiest listening periods, not the total number of listeners over a month.
Review the requested upgrade and total price in the customer portal. Extra storage does not automatically increase concurrent listener capacity.
Separate AutoDJ from live broadcasting Live support for formats such as AAC, M4A, OGG and FLAC does not mean AutoDJ can accept these files. The format guide explains encoder output and playback. The AutoDJ guide covers playlists, scheduling and taking over live.

Question 3

What SLA availability applies?

Accepted Answer

Binding availability commitments depend on the documents for your particular plan and any individually agreed terms. A technical description or status display does not establish a universal service level agreement.
Clarify requirements before ordering Describe which broadcasting periods are critical to your station. Discuss restoration times, maintenance windows, support scope and any compensation terms through contact before ordering. Obtain confirmation of commitments for your particular offer.
Status and your own checks The status monitor shows published operational information. During an incident, also check your audio source, encoder and public listening URL. Distinguish a failure of your own internet connection from a hosting service incident.
Prepare station operations Keep local copies of audio files and encoder settings. Test the return to AutoDJ after disconnecting a live source. The setup tutorial explains these checks. Report errors with the time, time zone and observed behaviour without sharing passwords publicly.

Question 4

Which audio formats does SPCast support?

Accepted Answer

AutoDJ accepts MP3 only. Live broadcasting supports MP3 as well as AAC, M4A, OGG and FLAC. This does not mean every encoder or browser supports every format.
Files, encoders and playback MP3, AAC and FLAC identify audio formats or codecs. M4A and OGG identify containers; the codec inside must also be supported. Your encoder determines the signal it sends to SPCast. The player and listening device determine which output can be played.
For an initial connection test, use an MP3 encoder with the settings shown in product management. Test any additional formats separately afterwards. The BUTT tutorial explains this starting point.
Transcoding and software versions The SPCast changelog documents that version .096 changed the 192, 128 and 96 kbit/s outputs to Fraunhofer FDK AAC (HE-AAC v2). Since that change, /stream256 and /stream320 relay the main programme rather than acting as separate Liquidsoap transcoders.
A path name alone therefore does not establish codec or bitrate. Check your installed version and the outputs available in product management. Raising an output bitrate cannot restore detail lost in a source file.
Listen before publishing Test the public stream on the devices your audience will use. Check audio, track information and transitions between AutoDJ and live shows. The player guide covers integration and playback checks. AutoDJ files remain subject to the MP3 storage requirements.

Question 5

Which server setups are available?

Accepted Answer

Your audio stream and website use different services. SPCast manages radio streaming. Web hosting serves your website. You can therefore keep an existing website hosting agreement alongside SPCast.
Select services for your station SPCast: Radio stream management, AutoDJ for MP3 files and broadcaster accounts for live encoders. DataDachs: Hosting for a website and its applications. TeamSpeaks: Voice communication for your team. SPChat: Community chat. Plan stream capacity The base plan includes 100 concurrent listeners and 50 GB of AutoDJ storage. AutoDJ accepts MP3 only. The hosting overview lists monthly costs and upgrades.
Plan slots around simultaneous stream connections. Check available capacities and locations when ordering. A separate management environment does not establish exclusive physical hardware or unlimited capacity.
Discuss specific requirements Describe expected peaks, storage requirements and existing encoders or players. Requirements for redundancy, multiple locations or particular resources must be clarified for the specific offer. Use contact and read the availability and SLA guidance.
The SPCast setup tutorial covers the first test. DataDachs describes website hosting plans.

Streaming, AutoDJ, and Hosting FAQ

Quick Start and Architecture Overview

General

Technical