Music Assistant
Replies: 3 comments 18 replies
-
|
Just need to understand some more about your setup. Are you running HAOS or docker? |
Beta Was this translation helpful? Give feedback.
-
|
Just looking at your original post again. Your intial description of MA detecting the squeezelite running on the local host is what should happen. You should be able to get that to work. |
Beta Was this translation helpful? Give feedback.
-
|
I yet updated the OP because you brought me to a misconception on my side. Thought that the 'squeezelite-pulseaudio' on the host system would bind the port like a server - which it of course doesn't. So that should actually be no cause of conflict at all. And yes, it works perfectly being found immediately also via discovery by MA. Too pose that question again: If I delete a player - what does actually happen? Is there a config which tells MA not to show it again in the Player View? Does it have an id that is blocked after deletion? I.e. from where is it actually deleted? And why wouldn't it appear again whenever discovery runs? Maybe that can help me to get my player devices back? |
Beta Was this translation helpful? Give feedback.
-
|
No actually it should just be discovered again. If you want to keep it hidden you have to DISABLE it. I'm not sure why it isn't being discovered again. There could be a bug preventing it from being found. I haven't ever deleted an Airplay device that I wanted back... Are there any errors in the logs? |
Beta Was this translation helpful? Give feedback.
-
|
Actually no. Only regarding my local file repo but exactly nothing regarding discovery ... 🤔 That's the only error message. |
Beta Was this translation helpful? Give feedback.
-
|
I now have turned off and on again the discovery service of the SlimProto provider - and see: There's my iMac (as SlimProto device) again. Tried to play - confirmed on my iMac that it may allow it ... No sound. Player stops playing. Doesn't continue before I choose my working onboard sound device. logs: So there's something going on, I guess ... |
Beta Was this translation helpful? Give feedback.
-
|
If you grab the logfile from the MA SETTINGS>>CORE page you will see the start where all the discovery happens. Maybe something useful there? |
Beta Was this translation helpful? Give feedback.
-
Don't think there are any relevant messages in log. |
Beta Was this translation helpful? Give feedback.
-
|
The errors above seem unrelated to your initial issue. I am interested in the stop iteration one. Do you have any albums with more that 100 tracks or folders with more than 100 sub folders? |
Beta Was this translation helpful? Give feedback.
-
|
I was just about to answer "no" but then I remembered that I have actually also audiobooks in my folder and at least one of them has 156 tracks. |
Beta Was this translation helpful? Give feedback.
-
|
Ok audiobooks aren’t supported at the moment so can you move them out and see if that fixes it? If it does we will open an issue. |
Beta Was this translation helpful? Give feedback.
-
|
Unfortunately I can't because it's my read-only repo that I use with funkwhale. And that uses a rather strange directory structure for every track, not for the album as a whole and the folders named not in natural language but - I guess - two-string-parts of hashes. (e.g. /srv/funkwhale/data/media/tracks/00/19/f7/8-some_track.mp3) But when I deactivate that provider and restart the container I get this output That's running only with the local data folder. It stops again BUT: There's not one track in it yet! Maybe that's the reason? No, looks the same :( |
Beta Was this translation helpful? Give feedback.
-
|
Is that one track you put in there properly tagged? |
Beta Was this translation helpful? Give feedback.
-
|
I would assume so ... mp3info shows Title, Artist, Album, Year and Genre . Could german Umlaute be a problem? The title contains ä and ö but mp3info shows both as �. |
Beta Was this translation helpful? Give feedback.
-
|
Can’t say for sure. Please change changing that to a normal a and o just to rule that out. |
Beta Was this translation helpful? Give feedback.
-
As I tried around some time now and don't come to any working idea I hope the swarm can hint me a little 🙂
As I setup MA and my sound surroundings here at home I happened to delete my discovered iMac (AirPlay) as a player.
Later, as I had to run squeezelite on the local host of the MA docker instance to be able to use its soundsystem, it was found as a SlimProto Player. But while I'm asked by my iMac if I want it to have acces and confirmed this there's still no sound to hear there. Also there seems to be flickering on that SlimProto iMac player in the player view. That's why I deactived that player also.
How can I let MA rediscover any player I have deleted (here the Airplay-Player)? Restarting MA/HA doesn't seem to help, a look in the airplay.xml and settings.json didn't either.
Or is it just an interference between the AirPlay provider and the squeezelite on the same host system? Starting squeezelite on it with another port (3484) didn't seem to fix that.Well there was a misconception on my side 🤦 I thoughtsqueezelite-pulseaudiowould bind a port like a server - which it doesn't. So, no, no interference.I'm sure I'm missing something obvious, but I don't see another way to access the soundsystem of the host directly from MA than having squeezelite running on it as there's no e.g. mpd provider, right?
Thank you for any hint that helps me work that out 🙏
Beta Was this translation helpful? Give feedback.
All reactions