mirror of
https://github.com/lox-audioserver/lox-audioserver.git
synced 2026-04-26 06:45:47 +03:00
[GH-ISSUE #56] Favorites cannot be played directly - Audioserver Serial should be customizable if more than one audio server is required. #16
Labels
No labels
bug
enhancement
pull-request
released
released on @beta
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/lox-audioserver#16
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @bogi9999 on GitHub (Oct 31, 2025).
Original GitHub issue: https://github.com/lox-audioserver/lox-audioserver/issues/56
Hi Rudy, I found your project on LoxForum and did a test installation.
MusicAssistant as a provider with various plugins.
Everything is working great so far, but there are a few minor issues.
First of all, it would be great if you could make the audio server serial editable.
I have more than 10 zones running with Sonos, and one server is no longer enough. With two instances with different IPs, two servers are recognized, but configuring everything to see if it works was too much for me to test.
Because -->
I can't address the individual players via SetFavorite. This means that I have created favorites and address the stations/playlists with their respective IDs (as was also possible with the old MusicServer).
That is, 1 for the first favorite, 2 for the second, and so on.
I have also integrated Soundcloud with Spotify and TuneIn and have to say that MusicFiles can be found there too. Only the playback here is a bit jerky, but it works. Maybe you can find a solution here to fix both problems.
By the Way, if i stay in the Docker System, how much Ram for each container should i adress?
By, Lee
@rudyberends commented on GitHub (Oct 31, 2025):
Yes I will look into this. Already thought about making the server in a way that it can emulate multiple servers in the same instance.
However .... the current server allows for up to 24 zones. If you split al stereo outputs you can get 4 zones from the server and another 20 from the extensions. (2 per extensions with a maximum of 10 extensions). Do you really need that much? 😅
@bogi9999 commented on GitHub (Oct 31, 2025):
But how do you define a Zone? There are Stereo (need both channels of a Extension) and mono.
I have 10 Stereo Zones (10 Extensions) and5 Mono. That exceeds the capability of one Server.
@rudyberends commented on GitHub (Oct 31, 2025):
Just ignore stereo/mono naming in loxone. This is only true for a real Loxone server, not for our emulation
Split everything and you will have 24 zones when you add 10 extensions.
Music Assistant will just send a stereo signal (or whatever your source is) to your zone.
@rudyberends commented on GitHub (Nov 1, 2025):
Your favorites issues should now work in the latest 3.0.0 release. Please start with a fresh config and let me know the results.
@mr-manuel commented on GitHub (Nov 1, 2025):
Should be the same as https://github.com/rudyberends/lox-audioserver/issues/44#issuecomment-3429351537, and that works now.