RadioLogger Setup: Quick Start for Accurate Broadcast Logging
Overview
RadioLogger is a broadcast logging solution that captures airplay data, timestamps tracks and ads, and produces searchable logs for compliance and analysis. This quick-start guide walks you through installation, basic configuration, verification, and common troubleshooting to get accurate, reliable logs fast.
Prerequisites
- A Windows or Linux server (minimum: 4 CPU cores, 8 GB RAM, 100 GB disk).
- Stable network connection with low jitter to audio sources.
- Administrative access to the server and any audio equipment.
- Audio sources available via line input, AES/EBU, or network streams (RTSP/HTTP/UDP).
- License key or trial credentials from RadioLogger.
Installation
- Download installer — Get the appropriate package from RadioLogger’s website (Windows MSI or Linux tar/DEB/RPM).
- Run installer — On Windows, run the MSI as administrator; on Linux, extract the tar and run the provided install script or use the package manager for DEB/RPM files.
- Install dependencies — Allow the installer to add required packages (audio libs, codecs). On Linux, ensure ALSA/PulseAudio or JACK is configured if using local audio inputs.
- Start service — Use Services.msc on Windows or systemctl start radiologger.service on Linux.
Initial Configuration
- Apply license — Open the RadioLogger UI (http://localhost:8080 by default) and enter your license key under Settings → Licensing.
- Time sync — Ensure accurate timestamps by enabling NTP synchronization on the server. Correct time is critical for compliance logs.
- Audio inputs — Add each audio source in Settings → Inputs:
- For line/AES inputs, select the correct soundcard channel.
- For network streams, enter the stream URL and choose the correct protocol.
- Set sample rate and channels to match the source (commonly 48 kHz, stereo).
- Recording paths — Configure storage location with sufficient space and retention policy (daily/weekly). Use separate disks for recordings and system files if possible.
Logging Rules & Metadata
- Matcher library — Import or configure your music/spot database so RadioLogger can identify tracks and ads. Support common metadata formats (ISRC, EAN, title/artist).
- Fingerprinting — If using audio fingerprinting, run an initial import of known tracks to build the reference database.
- Schedules — Define schedule rules for expected programming blocks to aid automated detection and anomaly alerts.
Verification & Testing
- Test stream capture — Play a known track and verify RadioLogger records it end-to-end.
- Check identification — Confirm the system correctly matches track metadata and timestamps.
- Review logs — Generate a sample log report for the test period and verify format and accuracy.
- Simulate outages — Temporarily mute or disconnect a source to confirm the system logs gaps and raises alerts.
Common Troubleshooting
- No audio captured — Verify soundcard selection, driver status, and permissions. On Linux, check ALSA/JACK settings.
- Incorrect timestamps — Ensure NTP is enabled and the timezone is correct.
- Misidentified tracks — Verify fingerprint database completeness and update matcher rules; increase fingerprint sensitivity if needed.
- High CPU/IO — Lower recording quality temporarily, move recordings to faster storage, or scale up server resources.
Maintenance Best Practices
- Monitor disk usage and set alerts for low space.
- Schedule regular database and fingerprint index backups.
- Keep software updated; apply security patches for the OS and RadioLogger.
- Review logs weekly for anomalies and adjust matcher rules as programming changes.
Quick Checklist (first 24 hours)
- Download & install package
- Apply license & enable NTP
- Add audio inputs & set sample rates
- Import matcher/fingerprint library
- Perform capture & identification test
- Configure storage retention & alerts
Follow these steps to deploy RadioLogger quickly and ensure accurate, compliant broadcast logs from day one.
Leave a Reply