alexlyee
commented
1 year ago actually, it turned out it was doing some kind of massive loading process (probably my many playlists) at boot which was eating all of the app's bandwidth. Once it finished loading (6-7 minutes) it connects fine. I've ran into a second problem where it can't play audio as the mopidy user. I'm running pipewire and trying to connect them via. pipewire-pulse right now, but pipewire-pulse isn't starting, and I think it might be related to wireplumber not starting w/out dbus configurations.
I'll mark it as completed because I think my problem isn't as I originally described, though I haven't actually heard spotify playing music yet.
hey, I've been trying to get spotify working w/ mopidy on arch for quite some time now. I went from blindly using the mopidy-spotify aur package, to compiling the dependencies as written in the readme and installing via. elevated pip, to now using the mopidy-spotify-git package --..which seems to be doing the compiling for us?
Anyways, the first one didn't work obviously, but at least I could connect to my mpd w/ it still, the second way was very unhappy to even start and would dump it's memory immediately upon mopidy starting, and this third way appears to be connected and downloading things from spotify in the debug log (!!!) but for some reason I cannot reach the mpd server using ncmpcpp at all only when the plugin is enabled. I've tried countless other things too, including disabling the caching and running mopidy under my user.
Does anyone have any idea what's happening?
thank you