Welcome to BroadcastLabs
Community radio is built from thousands of small decisions. Someone prepares the programme. Someone checks whether the supplied audio arrived. A presenter adjusts the running order when an interview goes long. A volunteer notices that the music library contains several versions of the same track. Another person needs to find what went to air at a particular time. None of those jobs is glamorous on its own, but together they determine whether a station sounds confident, remains dependable, and gives its community a service it can trust.
BroadcastLabs exists to make those jobs easier. It is an independent Australian software initiative created and managed by David Gilbert, a software developer, technology specialist, community-radio broadcaster, and President of 92.3 FM 2YYY Radio in Young, New South Wales. The applications are informed by direct experience of the studio, the office, the equipment rack, the volunteer handover, and the responsibility of keeping a local station on air.
Software shaped around recognisable station work
Large broadcast systems often try to solve every problem in one environment. That approach can suit organisations with dedicated engineering teams, formal training programmes, and substantial budgets. Smaller stations live with a different reality. Computers may have been acquired at different times. Volunteers may use the studio once a week. Procedures must remain understandable after a committee change. A useful tool needs to solve its task clearly without demanding that the station reorganise everything around it.
That is why each BroadcastLabs application has a focused purpose. BroadcastMate supports playout, live assist, scheduling, carts, and unattended operation. BroadcastLogger keeps a searchable audio record. BroadcastSync retrieves supplied programmes and other remote content into known local folders. BroadcastTrimmer analyses and standardises leading and trailing silence. BroadcastDeDuper helps a station find, compare, quarantine, and recover duplicate music. BroadcastVerifyAI screens supported music locally for indicators associated with AI generation.
A station can use one application or several. There is no requirement to adopt them as a suite, and the BroadcastLabs website itself is not a downloadable product. It is the place where visitors can understand the applications, obtain current releases, read documentation, participate in community discussions, and request direct support.
Free to use, with a clear distinction
BroadcastLabs applications are provided free of charge because cost should not prevent a community station from solving a practical operational problem. Free distribution gives a station room to evaluate an application away from air, train the people who will use it, and adopt it only when the workflow makes sense. It also helps regional and volunteer-run broadcasters direct limited funds towards content, transmission, facilities, and the people they serve.
Free does not mean open source. The applications are independently developed products, and their source code is not published as an open-source project. That distinction matters because stations should know exactly what they are adopting. Product pages and supplied licence information explain the intended use, while release records identify the current version and platform.
Local control and honest product information
Broadcast environments deserve conservative technology choices. An application should not quietly make an operational dependency out of a cloud service, an account, or an API when the job can be completed locally. BroadcastDeDuper performs its comparison work on the station computer. BroadcastVerifyAI uses a bundled local detector and does not upload audio for analysis. BroadcastSync is deliberately one-way and download-only. Across the portfolio, the emphasis is on visible actions, reviewable results, recoverable changes, and clear limits.
Honest documentation is part of the product. A guide should say what an application does today, explain how to prepare for a change, and identify where human judgement remains essential. BroadcastVerifyAI, for example, provides probabilistic screening evidence rather than proof of origin or authorship. BroadcastDeDuper offers quarantine and undo because a likely duplicate still deserves review by ear. BroadcastTrimmer supports dry-run analysis because processing a library should begin with measurement, not an irreversible batch operation.
A community around useful answers
The site brings several kinds of help together. Documentation is the quickest place to learn setup and everyday operation. Public forums allow broadcasters to search previous answers, compare station workflows, and share a resolution that may help someone else. Private support tickets are available when a question includes logs, account details, system information, or anything that should not be posted publicly. Contact forms provide a straightforward way to reach David without displaying an email address throughout the website.
The aim is not to manufacture engagement. It is to create a useful body of practical knowledge around broadcast work. A focused question with the product version, operating system, expected outcome, and steps already tried is valuable. So is a short follow-up explaining what solved the problem. Community radio becomes more resilient when stations can learn from one another without each repeating the same investigation alone.
Where to begin
Start with the job that is causing friction today. Read the relevant product page, then follow its documentation and safeguards. Check the current release record before downloading. Test the application on a non-air computer with representative files and settings. Keep the previous installer, configuration backup, and rollback path until the new workflow has been proven under the conditions in which it will actually operate.
BroadcastLabs will continue to grow as new broadcast problems justify focused solutions. The number of applications is not the mission. Better local radio is the mission: more time for programmes and people, fewer preventable operational failures, and practical technology that respects the realities of the stations using it.
Photo by Mustafa Sheikhmouss on Unsplash.