SAM Broadcaster Pro combines a music library, dual decks, playlist logic, voice input, audio processing, statistics and stream encoders in one Windows application. It can run a live assisted show or provide continuous automation, but its flexibility requires careful setup. This guide connects SAM Broadcaster to an RCAST SHOUTcast or Icecast service and develops a dependable operating workflow around the connection.
Plan SAM Broadcaster's role
Decide whether SAM will run unattended automation, assist a live presenter, or encode the output of an external mixer. For internal operation, SAM plays and mixes library items through its audio pipeline. For an external studio, a physical console may create the final programme, which must enter SAM through a line input or sound card source.
Avoid building both workflows at once. Start with one clearly documented programme source and one primary stream. Add secondary encoders and advanced scheduling only after the main service has passed a continuous test.
Install and protect the database
Use a current supported SAM Broadcaster release obtained from the official publisher. During installation, follow the supported database option for that release and record where the database and configuration are stored. The database holds library references, categories, history and scheduling information, so it is part of the station, not disposable cache.
Create a backup before upgrades or large library imports. Confirm that another authorised operator knows how to restore it. A backup of media without the SAM database may lose rotations and history, while a database backup without the audio files leaves broken references.
Prepare RCAST connection details
Open the RCAST service page and collect server type, source hostname, source port, source password and any username, mount point or SHOUTcast stream ID. Keep the public player URL separate from the encoder destination.
| Item | Icecast | SHOUTcast |
|---|---|---|
| Server type | Icecast 2 | SHOUTcast v1 or v2 as supplied |
| Host and port | Source endpoint | Source endpoint |
| User | Often source or a DJ user | Use the supplied authentication mode |
| Mount | Path beginning with slash | Not an Icecast mount |
| Stream ID | Not used | Used for SHOUTcast v2 when supplied |
Add the encoder window
Use the SAM desktop layout menu to display the Encoders window if it is not already visible. Add a new encoder and select the plugin or format supported by the installed edition. The exact labels can vary between SAM releases, but the profile must define both audio encoding and server connection.
- Add an encoder and choose MP3 or AAC according to the station plan.
- Set bitrate, sample rate and channel mode.
- Select SHOUTcast or Icecast as the server family.
- Enter the source hostname and port.
- Enter the source password and any required username.
- For Icecast, enter the mount point with its leading slash.
- For SHOUTcast v2, complete the stream ID or authentication fields supplied by RCAST.
- Enter public station information and save the encoder.
Start the encoder manually for the first test and watch its status. A profile that repeatedly reconnects is not ready for automatic startup.
Select format and bitrate
MP3 at 128 kbps stereo remains a practical baseline for a general music service. AAC can deliver good quality at lower rates but must be tested across the station's players and directories. Speech services may use mono and a lower bitrate effectively. Do not exceed the bitrate allowance of the RCAST plan.
Match sample rate through the pipeline where practical. A library and audio device based around 44.1 kHz does not become better merely because the encoder is set to 48 kHz. Each additional encoder uses processor time and upload bandwidth, so commission them individually.
Configure the audio pipeline
SAM's audio pipeline combines decks, sound effects, voice input and processing before the encoder. Confirm that Deck A and Deck B reach the output at consistent levels. Test the Voice FX path separately and use headphones to prevent loudspeaker feedback.
If an external mixer supplies the programme, select its interface input deliberately and prevent SAM's internal decks from being mixed a second time. A line output belongs in a line input, not a sensitive microphone input. Make a local recording from the selected input to prove the route before testing the server.
Set levels before processing
Correct library tracks with unusually low or clipped source audio rather than asking the final processor to solve everything. Set microphone preamp gain for the loudest realistic presenter voice and preserve headroom. Watch the pipeline meter during transitions when two decks and voice may overlap.
Use AGC, compression, equalisation and limiting conservatively. Heavy processing can raise noise, exaggerate breaths and create listening fatigue. Compare changes at matched loudness and listen to the encoded return because lossy encoding can make aggressive high frequencies more obvious.
Import and organise the library
Back up before a large import. Use consistent artist, title, album and genre tags. Remove filename extensions and promotional text from fields that may reach listeners. Organise categories by programming role, such as Power, Core, Recurrent, Specialty and Imaging, rather than by arbitrary storage folders.
Verify that file paths remain stable. Music stored on a removable drive or network share can disappear after a restart or login failure. Use a monitored storage location and keep enough free space for database work, recordings and logs.
Create rotations without obvious repetition
Use playlist rotation logic to alternate categories and apply artist separation. Small categories need longer separation or more content; otherwise the same titles return predictably. Keep jingles and station IDs in dedicated categories with rules suited to short imaging, not music.
Review history reports by listening hour, not only by reading the rule configuration. A rotation can satisfy technical separation while still sounding repetitive because similar tempos, eras or voices cluster together.
Use PAL scripts carefully
SAM's PAL scripting can automate complex actions, but a script can also stop programming, enqueue duplicate content or create repeated network requests. Add one function at a time, document its owner and keep a tested copy of the previous version. Never paste an unreviewed script from a forum into a production station.
Set reasonable loops, timeouts and error handling. Test scripts on a non-production instance or during a controlled maintenance window. The station should have a fallback that does not depend on the same script.
Configure metadata and station information
SAM can send current artist and title to the streaming server. Public metadata depends on clean library tags and correct encoder settings. Create intentional titles for shows, news, live talk and syndicated programmes. Do not expose internal comments, file paths or traffic references.
Check the result in the public player. During crossfades, decide which deck should control the title. Allow for normal cache delay before assuming an update has failed.
Test the complete service
- Start with one encoder and a short controlled playlist.
- Confirm the encoder remains connected without retries.
- Listen on a phone using mobile data.
- Test deck transitions, Voice FX and an imaging item.
- Verify stereo channels, loudness and metadata.
- Leave automation running through several category changes.
- Stop the encoder intentionally and verify RCAST fallback behaviour.
- Reconnect and confirm normal service returns.
Troubleshoot connection problems
Authentication failed
Retype the source password and verify server type, user, mount or stream ID. Check that SAM has not retained an old password in a duplicate encoder profile.
Connection timeout or refusal
Confirm the source hostname and port. Test wired Ethernet, firewall rules and another network. A public listening URL can work while the source port remains incorrectly configured.
Source already connected
Another encoder, AutoDJ mode or presenter may own the source. Coordinate the handover and use the supported takeover method rather than repeatedly forcing a connection.
Troubleshoot audio problems
Connected but silent
Inspect pipeline and encoder meters. Confirm the decks feed the selected output and that an external input is not muted. Record locally from the same pipeline to separate audio routing from server delivery.
Voice is missing
Check Voice FX input selection, push to talk or microphone state, and whether the hardware mixer routes the microphone into the returned programme signal.
Audio stutters
Review processor load, database activity, audio buffer, storage health and upload stability. Large imports or reports should not run during critical live periods.
Metadata is frozen
Compare the current library item with the encoder metadata settings and server status. Confirm the playing file has valid tags and no script continually overwrites the title.
Build backup and recovery
Back up the SAM database, media library, PAL scripts, sound effects, configuration and encoder details. Store source credentials securely rather than in an unprotected procedure. Keep at least one backup separate from the automation computer.
Test recovery on another suitable system. Confirm that file paths, database connectivity, audio device names and encoder profiles can be restored. Document the minimum procedure for getting a basic playlist and stream back online before rebuilding optional features.
Run SAM continuously
Use a dedicated Windows account and wired network. Disable sleep while preserving planned restarts and updates. Schedule database maintenance, backups and library scans away from important programmes. Monitor free disk space and archive recordings before the drive fills.
After Windows, driver or SAM updates, verify audio devices and run an external listening test. Default inputs can change even when the application opens normally.
Frequently asked questions
Can SAM Broadcaster send multiple streams?
Yes, supported configurations can use several encoders. Each consumes processor and upload capacity. Add and test one at a time.
Can SAM replace RCAST AutoDJ?
SAM can provide station automation from its own computer. RCAST AutoDJ remains useful as server side continuity when the studio source is unavailable. Design which system has priority.
Should the database and music be on one computer?
They can be, but storage must be reliable and backed up. Network storage introduces another dependency that must be monitored and tested after restart.
Why is there delay between SAM and listeners?
Audio buffering, encoding, server delivery and player buffering add latency. Some delay is normal for internet radio.
SAM Broadcaster becomes dependable when its database, library, audio pipeline, encoder and fallback are treated as one operational system. Begin with a simple working stream, test the public return, document the configuration and protect the data required to rebuild it.