Streaming terminology and technical definitions
An external program responsible for encoding and sending audio content to the Mcaster1DNAS server. Source clients capture audio (from files, live input, or automation systems), encode it to the desired format (MP3, AAC, Ogg Vorbis, etc.), and stream it to the server. Examples include Butt, Liquidsoap, SAM Broadcaster, FFmpeg, DarkIce, and IceS.
A resource on the Mcaster1DNAS server representing a single broadcast stream. Mountpoints are named like file paths (e.g., /stream.ogg, /radio.mp3, /live). When listeners connect, they must specify the mountpoint in the URL. Source clients also connect to specific mountpoints. Each mountpoint has its own statistics, settings, and can have different content, bitrates, or formats. Mountpoints are fundamental to how Mcaster1DNAS organizes multiple streams on a single server.
In a relay configuration, the master server is the origin server that has the original stream content. Other servers (slave/relay servers) connect to the master to pull the stream and redistribute it to their own listeners. This allows geographic distribution and load balancing.
In a relay configuration, the slave server (also called relay server) pulls stream data from a master server and redistributes it to its own listeners. The slave acts as a listening client to the master while simultaneously serving as a server to end listeners. This creates a hierarchy that enables scaling to large audiences.
A backup mountpoint configured to automatically receive listeners when a parent mountpoint becomes unavailable. If a source client disconnects or a stream fails, Mcaster1DNAS automatically moves all connected listeners from the failed mountpoint to its configured fallback mountpoint. This ensures continuity of service and prevents dead air.
The amount of audio data sent immediately to a newly connected listener to quickly fill their player's buffer. This reduces startup latency and minimizes buffering interruptions. Burst size can be configured in bytes or seconds and applies to all mountpoints unless overridden per-mount.
The maximum size of the internal buffer for each listener connection. If a listener experiences network congestion and falls behind, Mcaster1DNAS queues data for them up to this limit. If the queue exceeds this size, the listener is disconnected to free resources.
The streaming protocol used by Mcaster1DNAS and Shoutcast servers. ICY is an extension of HTTP with additional headers for stream metadata. Mcaster1DNAS v2.5.1-rc1 supports ICY-META v2.1+ with enhanced metadata capabilities including social media integration and rich content delivery.
Public directory services where streams can be listed for discovery by potential listeners. Mcaster1DNAS can automatically register streams with YP directories when public: true is set. v2.5.1-rc1 includes enhanced YP logging for troubleshooting registration issues.
Security mechanisms to control who can listen to streams. Mcaster1DNAS supports multiple authentication methods including simple passwords, database lookups, and custom URL-based authentication handlers. This allows subscription-based or restricted-access streaming.
A language for transforming XML documents into other formats. Mcaster1DNAS uses XSLT to transform server statistics (XML format) into HTML web pages for the admin interface and public status pages. Custom XSLT files can create personalized interfaces.
Mcaster1DNAS maintains compatibility with the Shoutcast protocol, allowing source clients and listeners designed for Shoutcast to work with Mcaster1DNAS. Special compatibility modes can be enabled in the configuration.
Information about the currently playing content, such as song title, artist, album, and artwork. Mcaster1DNAS v2.5.1-rc1 supports enhanced metadata through ICY-META v2.1+ including social media links, cover art URLs, and custom fields. Metadata is updated in real-time by source clients.
The amount of data transmitted per second in a stream, measured in kilobits per second (kbps). Common bitrates are 128 kbps (standard quality), 192 kbps (high quality), and 320 kbps (maximum quality). Lower bitrates use less bandwidth, allowing more concurrent listeners on the same connection.