mirror of
https://github.com/lox-audioserver/lox-audioserver.git
synced 2026-04-25 22:35:53 +03:00
[GH-ISSUE #88] Music Assistant 2.7.x support #37
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#37
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 @mr-manuel on GitHub (Nov 21, 2025).
Original GitHub issue: https://github.com/lox-audioserver/lox-audioserver/issues/88
Is it possible to already have a branch that supports Music Assistant 2.7.x even if it's still in beta? Version 2.6.x has a memory leak and does not run anymore longer than a few hours without crashing. I have assigned it 32 GB of RAM with 7 players...
See this links. I added them as code to not create a link in these issues.
@rudyberends commented on GitHub (Nov 22, 2025):
There are dedicated mappers in the code for 2.7 already, but you have to do it manually. You can just rename them and you will have support for 2.7.
mappers are in "src/model/adapters/musicAssistant/state"
@mr-manuel commented on GitHub (Nov 23, 2025):
Somehow Lox-Audioserver does not start at all, if I have Music Assistant 2.7.x running (with and without renaming the files before building). When I turn back to 2.6.x then Lox-Audioserver starts instantly.
In the Lox-Audioserver logs there is nothing special:
@mr-manuel commented on GitHub (Nov 23, 2025):
Probably it would be nice, that Lox-Audioserver fetches the Music Assistant version and then loads the correct modules?
@rudyberends commented on GitHub (Dec 29, 2025):
4.x release will support 2.7