# Lyrion Music Server for Squeezebox and Compatible Players > Lyrion Music Server is a Perl-based audio streaming server for Logitech Squeezebox hardware and compatible software players. It suits users who want local music, plugins, internet radio, and music-service content delivered to LMS-compatible players. **LMS-Community/slimserver** — Server for Squeezebox and compatible players. This server is also called Lyrion Music Server. - Repository: https://github.com/LMS-Community/slimserver - Website: https://lyrion.org - Stars: 1,815 · Forks: 388 - Language: Perl - License: NOASSERTION - Published: 2026-10-16 · Updated: 2026-10-16 · Language: en - Canonical page: https://hysenlabs.com/projects/lms-community-slimserver ## Why Lyrion Music Server Exists for Squeezebox Fleets Lyrion Music Server addresses the gap between a stored music library and the audio players that need to consume it. Its documented audience includes owners of Logitech Squeezebox devices such as the Squeezebox 3rd Generation, Squeezebox Boom, Squeezebox Receiver, Transporter, Squeezebox2, Squeezebox, and SLIMP3. The server also supports software players including Squeezelite and SqueezePlay. That distinction matters because LMS is not presented as a general-purpose audio player or as a standalone streaming service. It is the server layer that sits between music sources and LMS-compatible endpoints. The library itself can include local music, while plugins add access to music services and internet radio stations. This gives an existing Squeezebox installation a path to online content without replacing the server with an unrelated playback stack. It is most relevant to a household, office, or other environment where one server needs to serve compatible players. The README does not document capacity limits, concurrent-user targets, transcoding behavior, or quality settings, so those adoption questions cannot be answered from the project description. The server's platform reach is broad in principle. The README says it runs on "pretty much any platform that Perl runs on" and names Linux, Mac OSX, Solaris, and Windows. It also identifies a Raspberry Pi, desktop, laptop, and NAS as possible host categories. That is a compatibility statement rather than a promise that every host has identical installation packages or support. ## LMS Server, Perl, and the Player Endpoint Boundary The implementation is written in Perl, and the repository layout reflects several distinct server responsibilities. `slimserver.pl` is the visible entry point at the top level. `Slim/` and `lib/` hold the main server and library structure, while `SQL/` is the repository's database-related area. Separate top-level scripts include `scanner.pl` and `gdresized.pl`, indicating that music-library processing and image resizing are handled as identifiable components rather than being hidden behind a single undocumented command. Player support is implemented across files such as `IR/`, which is consistent with the project's support for infrared-controlled hardware, and player-facing resources are separated from the server code. Configuration files also occupy the top level. `modules.conf` and `types.conf` indicate that module and content-type configuration are part of the project structure, although the README does not explain their syntax. `convert.conf` suggests a separate conversion configuration surface, but the repository summary does not document which conversions LMS applies or which formats are supported. Based on that layout, a useful adoption model is library and plugin sources on one side, the LMS server and its configuration in the middle, and Squeezebox or compatible software players at the edge. The exact network protocol, database schema, plugin API, and scanner data flow are not described in the README, so they should not be treated as documented interfaces for custom development. ## Plugins Extend the LMS Content Boundary Plugins are the main documented extension point beyond local music. The README states that they allow LMS to stream content from "many music services and internet radio stations." This makes plugin availability part of the server's practical value, particularly for users who want a mixed library of local files and online sources while keeping Squeezebox-compatible playback. However, the README does not name those services, describe plugin installation, list supported plugin repositories, or state whether a particular service works with LMS 9.2. It also does not explain whether every service uses the same account or subscription model. A user should therefore treat plugin and service support as separate compatibility checks. Installing the server itself does not establish that a desired music service or radio-directory plugin is available. The top-level `modules.conf` provides a concrete configuration file to inspect during installation. The README does not show its contents, so it would be inaccurate to invent a module declaration or plugin-management command. Likewise, the README links to the project documentation rather than presenting an inline setup recipe. For a deployment decision, the practical question is not merely whether LMS supports plugins in principle, but whether the plugins needed by the intended library are documented for the selected release and host installation. ## Getting Started Documentation, Not a Repository Install Recipe The repository directs users to the Getting started documentation for installation. It identifies Windows, macOS, and Linux hosts, as well as Raspberry Pi, desktop, laptop, and NAS systems, but it does not provide operating-system-specific commands, package names, ports, environment variables, or configuration snippets. The first supported setup action is therefore to consult the linked documentation for the intended platform. For the first real use, start with a host supported by that documentation, install Lyrion Music Server, make the local music collection available to LMS, and connect a documented Squeezebox model or a compatible software player such as Squeezelite or SqueezePlay. After the server recognizes the endpoint, point the player at the library and select local audio as the initial source. Add plugins only after the local-library path works, because the README does not document the interaction between plugin configuration, service credentials, and ordinary library playback. No commands are shown here because the repository README contains none to copy exactly. The contribution commands in the README are for repository development, not server installation or configuration. They should not be mistaken for an LMS deployment procedure. ## Squeezelite Is an Alternative Client, Not an LMS Replacement Squeezelite is the clearest documented comparison point, but the difference is architectural rather than a contest between two server implementations. LMS is the server for Squeezebox hardware and compatible players. Squeezelite is listed as a software emulator or client that can play from an LMS installation. It can replace physical Squeezebox equipment as an endpoint, while LMS remains responsible for the server side of that relationship. SqueezePlay appears in the same client category. Users choosing between a hardware Squeezebox and SqueezePlay are choosing an output endpoint, not automatically changing the server that organizes local and plugin-provided content. This can be attractive when an existing LMS library should remain central but particular hardware is unavailable or unwanted. Neither client reference in the README provides setup instructions, supported operating systems, audio backends, or codec behavior. They also do not establish that Squeezelite or SqueezePlay can replace LMS when the requirement is specifically to manage content for legacy Squeezebox hardware. The practical alternative is consequently endpoint substitution, not a general-purpose replacement server. ## Licensing, Upgrades, and Maintenance Boundaries The repository is not archived, and its last push was on 2026-10-12. That status supports treating the source tree as receiving recent repository changes, but it does not by itself define a release cadence. GitHub reports no releases, and the README does not provide a release tag, package version policy, upgrade procedure, migration guide, or rollback instructions. There is therefore no documented release artifact here against which an upgrade procedure can be written. The repository classification identifies the licence as custom rather than as one of GitHub's standard open source classifications. The actual terms are in `License.txt`. Anyone evaluating redistribution, modification, packaging, or commercial deployment must read that file directly. This review does not offer legal advice or infer permissions that the text does not state. The mismatch between the project's open source language and GitHub's custom classification is a reason to inspect the file before adoption, not evidence of a particular restriction. Development history is visible through `Changelog.html` and the numbered `Changelog1.html` through `Changelog9.html` files. Their presence suggests a substantial change record, but their contents were not included in the repository description, so individual compatibility changes cannot be summarized. The first verification should be the licence text, followed by the platform-specific getting-started instructions and the upgrade notes available with the intended installation. ## Conclusion Lyrion Music Server is appropriate for users who own Squeezebox hardware or run Squeezelite or SqueezePlay and want plugins that can extend a local or streaming audio library. It is not a suitable choice for someone seeking a documented turnkey installation, a permissively classified open source licence, or release-tagged upgrades. Before adoption, inspect License.txt, confirm that the getting-started documentation supports the intended operating system, and verify that the required player or controller is compatible with LMS. ## FAQ ### What devices can Lyrion Music Server stream to? The README lists several Logitech Squeezebox models, including Squeezebox 3rd Generation, Squeezebox Boom, Squeezebox Receiver, Transporter, Squeezebox2, Squeezebox, and SLIMP3. It also names Squeezelite and SqueezePlay as compatible software emulators. ### Can Lyrion Music Server stream internet radio and music services? The README says that plugins can stream content from many music services and internet radio stations. It does not name the services or document plugin installation, so support for a particular service needs separate verification. ### How do I install Lyrion Music Server? The README directs users to the Getting started documentation at lyrion.org and identifies Windows, macOS, Linux, Raspberry Pi, desktop, laptop, and NAS hosts. It does not include installation commands in the repository README. ## Sources - [Issues](https://github.com/LMS-Community/slimserver/issues) - [LMS-Community/slimserver on GitHub](https://github.com/LMS-Community/slimserver) - [Project website](https://lyrion.org) - [README](https://github.com/LMS-Community/slimserver/blob/public/9.2/README.md) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/lms-community-slimserver