What this guide helps you do
Build reliable AutoDJ rotation by separating media organisation, playlist purpose, scheduling and fallback behaviour. A good AutoDJ library is structured around programming intent. Uploading thousands of files and checking every playlist option at once produces unpredictable output. Start with a small known library, build a general rotation, then layer scheduled shows, jingles and specialist rotations one at a time. This guide is written for production-minded administrators and site owners: make a backup before material changes, keep credentials private, and prefer the controls supplied by your own hosting provider when its environment differs from a generic example.
Before you begin
Record the domain, server or station you are changing and the current working state. If the task touches DNS, SSH, firewall rules, databases, stream credentials or application configuration, make sure you have a recovery path first. Screens and menu names can vary between cPanel, AzuraCast, VDO Panel and Linux releases, so follow the purpose of each step rather than forcing an old screenshot onto a newer version.
Step 1: Upload media with consistent tags. Correct artist and title metadata before relying on public Now Playing displays, because the automation can only publish what the media library knows.
Upload media with consistent tags. Correct artist and title metadata before relying on public Now Playing displays, because the automation can only publish what the media library knows.
Step 2: Create a general rotation playlist that can fill ordinary time. Keep specialist content in separate playlists so you can understand which rule selected a track.
Create a general rotation playlist that can fill ordinary time. Keep specialist content in separate playlists so you can understand which rule selected a track.
Step 3: Use scheduled playlists for programmes that truly need a window. Confirm station timezone and avoid overlapping schedules until the basic schedule is proven.
Use scheduled playlists for programmes that truly need a window. Confirm station timezone and avoid overlapping schedules until the basic schedule is proven.
Step 4: Use jingles or station IDs with an appropriate interval or weight instead of putting them into every music folder. Listen to a real hour of output to judge repetition.
Use jingles or station IDs with an appropriate interval or weight instead of putting them into every music folder. Listen to a real hour of output to judge repetition.
Step 5: Define fallback behaviour deliberately. If live presenters disconnect, know whether AutoDJ resumes automatically and how long any handoff takes. Test this before a live show.
Define fallback behaviour deliberately. If live presenters disconnect, know whether AutoDJ resumes automatically and how long any handoff takes. Test this before a live show.
Verification checklist
Listen for at least one full scheduling cycle and verify track metadata, playlist transitions, jingle frequency, timezone behaviour and live-to-AutoDJ fallback. Review logs when output differs from the schedule instead of repeatedly restarting services. Always test from the user side as well as the administrator side. A control panel saying “active” is useful evidence, but it is not the same as an external browser, player or SSH client proving that the full path works.
Troubleshooting method
When the result is not what you expected, avoid changing several unrelated settings at once. Identify the last known-good point, collect the exact error message and determine which layer is failing: DNS, network, authentication, service process, application configuration, web/stream delivery or browser/player. Check timestamps and logs around the failure. If you need to escalate to hosting support, include the affected hostname or station, the time of the test, what you expected, what happened instead and the checks you already completed. Do not include passwords, API keys or private stream keys in a public ticket or screenshot.
Keep the system maintainable
Document the final configuration after it works. Note the important URLs, service names, backup locations, renewal/expiry dependencies and any change that would surprise another administrator. Revisit the setup after major platform upgrades because defaults, supported runtimes and interface labels evolve. A reliable environment is not one that was configured once; it is one whose current state is understood, monitored and recoverable.
Where to go next
Use the related guides below to expand the setup rather than solving the same problem from scratch. If the platform has outgrown shared hosting or you need managed implementation, the service recommendation at the bottom of this guide links to the most relevant hosting, streaming, development or optimisation option on this site.
Interface labels and supported versions can change. Use the controls and documentation supplied with your current hosting environment, and keep a backup or recovery path before material changes.