Illustrative worked examples showing how Multilarm is configured for each use case. Each post walks through a representative scenario, the actual configuration, and the specific features doing the heavy lifting — example setups rather than records of specific customers, with real, working config you can adapt.
The full Adhan, in your own Qari’s voice, out of the mosque’s real speakers, automatically five times a day — offline, multi-zone, with quiet-hours caps and a phone remote. Why a software player beats a phone app, a smart-speaker skill or a sealed Azan clock.
Timed announcements, bells, multi-zone paging and a browser remote from one $35 board — no PBX, no DIY Python glue, no cloud dependency you can’t switch off. The scheduling software that finishes the build the forum threads start.
A single-board computer, a pair of speakers, and an XML file. How a small mosque can replace a failing commercial Adhan clock — with time-of-year-aware scheduling, short-notice skips, and a phone-friendly remote.
Existing PA speakers still work, but the bell controller has died. With MirrorDevices, a laptop, and the Web Remote, office staff can run period bells, lunch chimes and live announcements from a browser tab.
A small manufacturing plant uses scheduled folders for shift changes, the Voice Broadcast card for impromptu supervisor messages, and multi-device mirroring so every workshop zone hears the same audio at the same moment.
Scheduled programmes, live voice inserts, TTS station IDs and an internet radio feed — all driven by one XML config and a browser. Cloud Relay keeps the presenter in control even when the studio isn’t on the same network.
A boutique yoga and HIIT studio can run its entire class day from one box — two studios as independent Multilarm instances pinned to separate USB outputs, VolumeProfileRules caps for the quiet hours, and a Web Remote tablet in place of the handheld PA mic.
A regional museum drives four galleries, a rotating temporary exhibition and a cafe from one mini-PC. AlarmIndexData cycles walk through language folders in rotation; TTS covers closing announcements; AlternateConfig date rules swap the whole schedule on exhibition day.
A small receiving house runs each zone as its own Multilarm instance; TTS-spoken pre-show calls fire from absolute times in DateAndTimeData, and a per-curtain config variant swaps in via AlternateConfig. A dedicated Alerts instance with MirrorDevices fans the evacuation tone across every zone in one tap.
Six zones, six independent soundtracks, per-zone fallback radio for when a folder empties, per-zone volume caps for the noise ordinance, and a Cloud Relay dashboard the duty manager runs from their phone.
Every example above runs the same binary. The scenario changes, the Multilarm.xml changes, the hardware changes — but the engine is identical: timers fire against a schedule, the /api/* endpoints expose control, and MirrorDevices (setting #25) broadcasts one stream to many outputs. That’s it. No plugin framework, no subscription, no cloud dependency you can’t turn off.
If you’re running Multilarm in a scenario we haven’t written up yet, we’d genuinely like to hear about it — the site comments section is the fastest way to reach us.