Streaming, AutoDJ, and Hosting FAQ

Question 1

Does SPCast support MP3 and AAC+?

Accepted Answer

Yes. SPCast provides native support for the two most widely used audio codecs in web radio broadcasting: MP3 (MPEG-1/2 Audio Layer III) and AAC+ (HE-AAC v1 and v2). You can broadcast your primary master stream at full studio fidelity up to 320 kbps while simultaneously delivering automated transcoders for mobile listeners.
Supported Codecs and Bitrates With SPCast, you can configure multiple parallel output streams across varying quality tiers and bandwidth profiles:
MP3 Primary Stream: 128 kbps, 192 kbps, 256 kbps, or 320 kbps for universal compatibility across all audio players and playback devices. MP3 Transcoders: 96 kbps or 128 kbps for listeners on standard connections or desktop web players seeking bandwidth conservation. AAC+ Transcoders (HE-AAC): 32 kbps, 48 kbps, or 64 kbps for cellular listeners, automotive audio systems, and smart speakers with minimal data consumption. Comparing MP3 and AAC+ Codecs Both codecs utilize distinct compression algorithms suited for specific broadcast scenarios:
MP3 (Universal Device Compatibility) MP3 represents the most established and widely supported audio format on the Internet. Virtually every playback hardware device (from standalone Wi-Fi tuners and AV receivers to contemporary smartphones) plays MP3 streams without third-party codec installations. For balanced stereo imaging and clear highs, a bitrate between 192 and 320 kbps is recommended.
AAC+ / HE-AAC (Maximum Efficiency at Low Bitrates) HE-AAC (High Efficiency Advanced Audio Coding) incorporates advanced tools like Spectral Band Replication (SBR) and Parametric Stereo (PS). Consequently, an AAC+ stream operating at just 48 to 64 kbps achieves acoustic quality comparable to a 128 to 192 kbps MP3 stream. This preserves mobile data quotas for your audience while substantially decreasing server bandwidth consumption.
Real-Time Server-Side Transcoding A major technical advantage of SPCast is its native, resource-efficient transcoding pipeline:
Single Studio Uplink: Your broadcast studio or presenter sends only one high-definition source feed (e.g., MP3 at 320 kbps) to the server. Automated Conversion: The server ingests the master feed and transcodes it in real time into your configured MP3 and AAC+ sub-bitrates. Synchronous Delivery: All listeners receive the identical audio programming simultaneously, regardless of which bitrate option they select in their web player or mobile app. You do not need multiple encoders or extra studio upload bandwidth to supply diverse quality tiers to your listeners.
Understanding Platforms, Codecs, and Protocols Clear distinction between terminology helps ensure proper station configuration:
Audio Codecs (MP3, AAC, OGG): Define how audio signals are compressed and encoded into digital bytes. Streaming Protocols (Icecast 2, SHOUTcast v1/v2, HLS): Govern how audio bytes are transported across the network to listeners. SPCast: The complete management and server platform orchestrating AutoDJ playback, transcoding pipelines, listener metrics, server relays, and APIs. On the protocol layer, SPCast delivers streams over classic HTTP streaming (Icecast, SHOUTcast) as well as modern HLS (HTTP Live Streaming) for frictionless integration with Apple iOS devices, modern web browsers, and Android apps.
Recommended Broadcaster Setup For everyday web radio operations, we suggest the following multi-bitrate configuration:
Channel 1 (Web Player & Desktop): MP3 at 192 kbps (ideal balance between fidelity and bandwidth). Channel 2 (Mobile Apps & On the Go): AAC+ at 48 or 64 kbps (crystal-clear audio with reduced cellular data requirements). Channel 3 (Audiophile / Hi-Fi): MP3 at 320 kbps for discerning listeners on broadband connections. Check technical details at SPCast or contact support for configuration advice.

Question 2

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 robust 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. In SPCast, you can utilize both approaches and combine them seamlessly with automated real-time transcoding pipelines (MP3 and AAC+).
Seamless 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. Seamless 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 3

How much AutoDJ storage is included?

Accepted Answer

The SPCast base package includes 50 GB of high-speed NVMe SSD storage for your web radio instance. This entire quota is fully available for your audio files, prerecorded broadcasts, jingles, airchecks, and system logs.
Storage Allocation and Organization Storage within your instance is completely flexible. You do not need to create rigid partition layouts before uploading files. Instead, you can distribute the capacity according to your station requirements:
AutoDJ Music Library: Audio files in MP3, AAC, M4A, OGG, and FLAC formats for continuous 24/7 playlist rotations. Jingles, Sweepers, and Drops: Short station imaging elements used for hourly station IDs, show transitions, or commercial spots. Show Recordings and Airchecks: Server-side recordings of live moderator shows for subsequent replay or long-term archiving. System Logs and Listener Metrics: Connection logs, listener statistics, and detailed troubleshooting logs. Automated log rotation ensures that historical connection records are compressed or purged after defined intervals. This keeps the vast majority of your storage space available for your music library.
Uploading and Managing Audio Files You have multiple secure methods for uploading and managing your media files:
Integrated Web File Manager: Upload individual tracks or full music packages directly in your web browser using drag-and-drop. ID3 tags such as artist, title, and album are indexed automatically upon completion. FTPS (FTP over TLS): For extensive music collections, connect your preferred FTP client (such as FileZilla or WinSCP) with encrypted transport. This allows parallel high-speed transfers of hundreds of gigabytes. Automated Synchronization: APIs and webhooks allow studio software to synchronize new rotation tracks directly with your remote cloud server. Once uploaded, the media engine indexes new tracks in seconds and assigns them to your configured playlists, rotation rules, or time slots.
Real-World Storage Capacity The actual number of songs you can store within 50 GB depends directly on your chosen audio codec and bitrate:
MP3 at 192 kbps: Approximately 11,500 songs (based on an average track length of 3.5 minutes), providing more than 28 days of uninterrupted music. AAC-LC at 128 kbps: Around 17,500 songs with more than 42 days of continuous rotation at identical or superior acoustic fidelity. MP3 at 320 kbps: Around 7,000 songs for studio-grade archival requirements. For most web radio stations, the 50 GB quota included with the base package is more than sufficient to maintain rich, diverse playlists without frequent repetitions.
Expanding Storage and Quota Upgrades As your radio station library expands, you can increase your storage quota at any time. Upgrades occur on live instances without requiring server restarts or causing interruptions to current broadcasts:
Additional storage capacity in blocks of 50 GB, 100 GB, or larger can be added directly through the customer center. Provisioning of expanded quotas occurs automatically within seconds after ordering. Existing playlists, directory hierarchies, and track scheduling parameters remain completely intact during upgrades. Separation of AutoDJ Storage and Web Hosting SPCast AutoDJ storage is technically and physically separated from web hosting infrastructure. For your station website, CMS software (such as WordPress or WEB-PHP), databases, and email accounts, you can utilize DataDachs web hosting plans.
DataDachs provides dedicated SSD hosting quotas ranging from 5 to 50 GB with isolated resource management via CloudLinux and CageFS. This clean architectural separation ensures that high website visitor spikes never affect your live stream delivery or AutoDJ playback.
View current SPCast packages or discuss your storage needs with support.

Question 4

What SLA availability applies?

Accepted Answer

For standard retail hosting and streaming packages, STREAMPANEL does not offer formal, contractually guaranteed Service Level Agreements (SLAs) with penalty-backed uptime clauses. However, our entire hosting and streaming architecture is engineered for a baseline annual availability target of at least 99.9% and is monitored continuously around the clock.
What 99.9% Uptime Means in Practice A technical availability target of 99.9% across a complete calendar year corresponds to an allowable cumulative outage window (including unforeseen upstream network routing disruptions) of less than 8.76 hours per year:
Monthly Benchmark: A maximum theoretical interruption budget of approximately 43.8 minutes per month. Weekly Benchmark: A maximum theoretical interruption budget of approximately 10.1 minutes per week. Real-World Performance: In most operating periods, our multi-homed datacenter nodes and automated failover pipelines achieve real uptime rates between 99.95% and 100%. Transparency and Public Real-Time Monitoring We prioritize total operational transparency. Through our public status page, you can inspect the operational health and historical uptime of all streaming instances, web hosting nodes, databases, and network backbones in real time:
Minute-by-Minute Heartbeat Checks: Automated external synthetic monitoring of all critical ports (HTTP, HTTPS, Icecast, SHOUTcast, DNS, MySQL, and SMTP/IMAP) from multiple geographic vantage points across Europe. Transparent Incident Logging: When unexpected hardware faults or network disruptions occur, we publish rapid incident notifications and subsequent root-cause summaries. Historical Uptime Metrics: Verifiable uptime statistics covering 30, 90, and 365-day rolling windows across all product lines. Datacenter Facilities and Hardware Redundancy To ensure uncompromising stability for your live broadcast, all STREAMPANEL server infrastructure is deployed within ISO 27001-certified Tier-3+ facilities located across key European Internet hubs (including Frankfurt am Main, Nuremberg, and Falkenstein):
Uninterruptible Power Systems (UPS): Dual independent battery banks coupled with automated diesel generators guarantee uninterrupted electricity during municipal grid failures. Multi-Homed Network Connectivity: Direct peering at major European Internet exchanges (such as DE-CIX and ECIX) supplemented by multiple Tier-1 transit backbones (including Telia/Arelion, Lumen, and Deutsche Telekom). N+1 Climate Control: Redundant precision cooling systems and cold-aisle containment to safeguard hardware components against thermal stress. NVMe Enterprise Storage Arrays: Mirrored SSD arrays with automated failover prevent single-disk failures from impacting broadcast operations. Maintenance Windows and System Updates Routine kernel patches, firmware upgrades, and security updates are necessary to maintain performance and safety. We minimize operational impact through structured policies:
Off-Peak Maintenance: Scheduled infrastructure upgrades are performed during periods of low listener traffic (typically between 02:00 and 06:00 CET). Advance Notification: Planned maintenance events that require brief service restarts are posted well in advance on our status page and communicated by email. Rolling Cluster Upgrades: Where technically feasible, multi-node clusters are updated sequentially to prevent interruptions to live listener streams. Broadcaster Best Practices for Studio Redundancy In addition to server-side high availability, station operators can implement proven measures within their own local studios to protect broadcast continuity:
Configure AutoDJ Emergency Fallback: Maintain an active standby playlist inside your SPCast AutoDJ. If your local studio Internet link drops, the AutoDJ seamlessly engages within seconds, preventing dead air. Dual Studio ISP Connections: Utilize two separate Internet service providers (for example, primary fiber optics with an automated 5G cellular failover). Studio Battery Backup: Power your broadcast workstation, audio processor, and mixer through an uninterruptible power supply (UPS) to absorb transient voltage fluctuations. Custom Enterprise SLAs for Broadcasters For commercial radio networks, media syndicates, and broadcast organizations with strict compliance or contractual obligations, we offer customized Enterprise Service Level Agreements:
Legally binding uptime guarantees of up to 99.95% or 99.99%. Guaranteed emergency response times with 24/7 on-call technical engineers. Multi-region active-passive or active-active stream clustering with automatic DNS failover. Dedicated technical account management for studio engineering workflows. If your broadcasting project requires customized availability terms or dedicated infrastructure redundancy, please contact our support team to discuss tailored enterprise hosting solutions.

Question 5

Which server setups are available?

Accepted Answer

STREAMPANEL delivers specialized infrastructure architectures tailored to the specific needs of contemporary web radio broadcasters and online communities. We deliberately isolate audio streaming, web hosting, team voice communication, and real-time chat onto purpose-built platforms.
Core Infrastructure Platforms Depending on your broadcasting workflow, we provide dedicated platforms engineered to work seamlessly together:
SPCast (Audio Streaming & AutoDJ): Isolated cloud instances for live streaming, HLS delivery, real-time transcoding, listener statistics, and playlist automation. DataDachs (Web Hosting & CMS): Hardened NVMe SSD web hosting with LiteSpeed Enterprise, CloudLinux, CageFS, and cPanel for radio websites, databases, and mail. TeamSpeaks (Voice Servers): Low-latency TeamSpeak 3 voice servers for station management, editorial coordination, and on-air presenter cues. SPChat (Community Web Chat): Modern real-time web chat widget for embedding into station websites and streaming players. SPCast: Isolated Cloud Instances Unlike conventional shared multi-tenant stream servers, every SPCast project operates within its own isolated cloud instance. This design offers crucial operational advantages:
1. Dedicated Compute and I/O Resources Each instance receives dedicated CPU, memory, and fast NVMe SSD storage allocations. High listener traffic or intensive playlist rendering on one station will never affect your own broadcast stream.
2. Elastic Slot Scaling The standard SPCast package begins with 100 listener slots and 50 GB of storage. You can seamlessly scale your capacity to 250, 500, 1,000, or several thousand concurrent listeners as your audience grows.
3. Comprehensive Protocol Support A single instance natively delivers SHOUTcast v1/v2, Icecast 2/KH, and modern HLS streaming from a single central media repository and dashboard.
DataDachs: High-Performance Web Hosting Radio station websites require a fundamentally different server architecture than real-time audio streams. Through DataDachs, we operate an optimized web hosting environment:
LiteSpeed Enterprise Web Server: Delivers dynamic content (such as WordPress or WEB-PHP CMS) up to 10 times faster than standard Apache servers. CloudLinux and CageFS Isolation: Each hosting account is strictly isolated within its own virtualized file system, guaranteeing dedicated CPU, RAM, and disk I/O limits while preventing cross-account security risks. NVMe SSD Storage: Rapid database responses for broadcast schedules, track request forms, staff directories, and listener top charts. Automated Free SSL Certificates: Automatic issuance and continuous renewal of Let&rsquo;s Encrypt SSL certificates for all domains and subdomains. High-Availability and Failover Architectures For commercial radio stations, syndicated broadcast networks, and mission-critical audio feeds, we provide advanced redundancy solutions:
Multi-Datacenter Failover Your broadcast audio stream is mirrored across multiple physically separated tier-3+ datacenter facilities (such as Frankfurt and Nuremberg/Falkenstein). If an upstream transit issue occurs at one location, edge relays and web players switch to the backup facility without audible disruption.
Intelligent Network Routing Anycast and GeoDNS mechanisms automatically direct listeners to the geographically closest and lowest-latency edge nodes.
Multi-Terabit DDoS Protection Every server location is shielded by carrier-grade multi-layer DDoS filtering capable of scrubbing several terabits per second. Layer 3, 4, and 7 attacks are mitigated automatically before reaching your application layer.
Selecting the Right Server Architecture New Radio Station: Start with the SPCast base plan (100 listener slots, 50 GB storage) alongside an entry-level DataDachs web hosting account for your website. Established Broadcaster: Choose an upgraded SPCast tier (500+ slots) with multiple transcoding streams and a high-tier DataDachs hosting plan. Broadcasting Network: We can design custom multi-server clusters with dedicated edge relays and load balancing across Europe. View streaming at SPCast or compare DataDachs web hosting.

Streaming, AutoDJ, and Hosting FAQ

Quick Start and Architecture Overview

General

Technical