Unable to access playlists in new version of MusicBee on Airsonic server
Closed this issue · 13 comments
After a recent upgrade to the newest version of MusicBee 3.4.7764, and most recent release of the plugin, I get the error Unable to access playlist X error. Folders will load and play correctly. I'm connecting to Airsonic 10.6.2.
This is the error on the Airsonic when MusicBee tries to load the playist:
2021-04-08 04:55:17.407 INFO --- o.a.p.s.LoggingExceptionResolver : 10.0.0.71: Client unexpectedly closed connection while loading http://clotho.local:5050/userChart.view?type=download (java.io.IOException: Broken pipe)
2021-04-08 04:55:17.411 INFO --- o.a.p.s.LoggingExceptionResolver : 10.0.0.71: Client unexpectedly closed connection while loading http://clotho.local:5050/userChart.view?type=total (java.io.IOException: Broken pipe)
2021-04-08 04:55:17.411 INFO --- o.a.p.s.LoggingExceptionResolver : 10.0.0.71: Client unexpectedly closed connection while loading http://clotho.local:5050/userChart.view?type=stream (java.io.IOException: Broken pipe)
If I create a new playlist on the server and try to access it via MusicBee I get this error:
MusicBee v3.4.7764.37422D (Win10.0), 8 Apr 2021 5:02:
System.NullReferenceException: Object reference not set to an instance of an object.
at #=z1v6HwQ___W9fot3mUPBSD6cwyKsC.#=z66JHsCuXzfaD.#=zdj43$88kkcDD()
at #=z1v6HwQ___W9fot3mUPBSD6cwyKsC.#=z66JHsCuXzfaD.#=zd0RxR5X4Cyz2wZLmkQ==(Boolean #=zYIQauaGIisW6)
at #=z1v6HwQ___W9fot3mUPBSD6cwyKsC.#=zEMn8uwSoyRcD.#=zeRbH5biG0OQm()
at #=z1v6HwQ___W9fot3mUPBSD6cwyKsC.#=zEMn8uwSoyRcD.#=zym5ceek=()
at #=z1v6HwQ___W9fot3mUPBSD6cwyKsC.#=zDdO58tFqV5RS(Boolean #=zMRpceRiM6Rc3GtLGpg==, Boolean #=zsBzR_cV8nwer)
at #=z1v6HwQ___W9fot3mUPBSD6cwyKsC.#=zEIINnCgSyAA7(#=zVT6OcTl8G4_i9xkvMBK84pA= #=zkIQ3TMX9ASsH, Boolean #=zmq9aU94VmRN0, #=z5nmymsU= #=zCqFWx9U=, #=zlxXdb0SA1Oy1Z$5SqhLSf2A= #=zcLhNzN$sAeuy, Boolean #=zVh7LQS99IZ29, #=z8BuTedZa$xuoc3ENpZBZWOE= #=zf3u3FXxO$JCD, #=zdRuRBjJKzFl3CpL3$zAlhBc=[] #=zJcS3rKvvqIvv, Boolean #=zIgWudnqnKuuf)
I have the same thing happening I believe. I can't access any playlists. It says Unable to access: Subsonic:\playlist-id. I can ping the server fine.
2021-07-30 20:42:10 stdout [33mWARN[0m[91015] HTTP: GET http://domain:5001/app/rest/ping.view?u=user&p=[REDACTED]&v=1.12.0&c=MusicBee [33melapsedTime[0m="35.807µs" [33mhttpStatus[0m=404[33mremoteAddr[0m=m.y.i.p [33mrequestId[0m=navidrome-copy/frLu9zZpvK-003182 [33mresponseSize[0m=19
2021-07-30 20:42:07 stdout [33mWARN[0m[91011] HTTP: GET http://domain:5001/app/rest/ping.view?u=user&p=[REDACTED]&v=1.12.0&c=MusicBee [33melapsedTime[0m="36.843µs" [33mhttpStatus[0m=404 [33mremoteAddr[0m=m.y.i.p [33mrequestId[0m=navidrome-copy/frLu9zZpvK-003181 [33mresponseSize[0m=19
2021-07-30 20:38:29 stdout [33mWARN[0m[90794] HTTP: GET http://domain:5001/app/:5001/rest/ping.view?u=user&p=[REDACTED]&v=1.12.0&c=MusicBee [33melapsedTime[0m="70.95µs" [33mhttpStatus[0m=404 [33mremoteAddr[0m=m.y.i.p [33mrequestId[0m=navidrome-copy/frLu9zZpvK-003170 [33mresponseSize[0m=19
Please test with the latest versions of MB and the plugin?
I just did a quick test with MB 3.4.7805 P and MB_Subsonic v2.32 (updated today), and I can create a playlist and access it normally, through MB.
Update works for me mostly. Except playlists on the Airsonic server says unable to access. All of the folders, etc. work fine just the playlists say unable to access.
Some digging into the ErrorLog.dat for MB. If I click on a playlist this is the error I get:
8/10/2021 3:13:01 AM - 10.0.19043.0 - 3.4.7805.33439D - System.NullReferenceException: Object reference not set to an instance of an object. at #=zziapYCHkKIL0B5EplaYmmhGl87_u.#=qWidhpxXMOE3dJ_36Zc3QXt7PRLJtfIS5lwQPQ7q5Tgw=._Lambda$__0()
Using the latest for both MB and this repo, I still can't access playlists. I can ping server and see the lists of playlists, but I'm unable to access the songs.
Error log when I click a playlist:
8/13/2021 15:39:10 - 10.0.19042.0 - 3.4.7805.33439P - System.NullReferenceException: Object reference not set to an instance of an object. at #=zziapYCHkKIL0B5EplaYmmhGl87_u.#=zmqrj1uLUGPmd.#=zxqbUD1U=(#=zfgePm4rHnB8nCHoceaeMlnQ= #=zP4uVpOM=, #=zDS75MM6CY57FAu1dYwKk3w0=[] #=z2b$peok=) at #=zziapYCHkKIL0B5EplaYmmhGl87_u.#=qWidhpxXMOE3dJ_36Zc3QXt7PRLJtfIS5lwQPQ7q5Tgw=._Lambda$__0()
Can you create new playlists, and play those back?
It may be that old/existing ones don't work, but new ones do... I tested creating a new one, and it worked for me - but I didn't have an older one to check.
I had the same thought about creating a new playlist but received the same issue as above.
I tried installing all of the 3.4 branches that were available with no luck. Rolling back to 3.3.7491, everything works.
Strange that I can't recreate it so far, using the latest version. I'll have to try again and see if I can cause this, to figure out what changed and why it's failing for you guys...
I tried it again today, using the following steps:
- Created a new playlist in Airsonic this time
- Fired up MusicBee 3.4.7805 P using the latest version of the plugin
- I could see the Playlist in the root directory of my Subsonic tree
- However, clicking on the Playlist showed no contents (even though it contained 2 songs)
Checking on the back-end, it seems that MusicBee calls "GetPlaylists" first (correctly, to get the list of playlists on the server), but when you click on one of those playlists, instead of calling "GetPlaylistFiles()" it calls "GetPlaylists" again.
This seems like a MusicBee bug from what I can see.
I've opened up a forum thread regarding this as well, here: https://getmusicbee.com/forum/index.php?topic=35468.0
Hopefully we can find a solution.
While testing with older versions of the plugin, I found that v2.28 seems to work as expected with the Playlists, in both 3.3 and 3.4 versions of MB. I'll have to see what changes came since then, to figure out what might have triggered this behavior.
In the meantime, can anyone else please confirm if that's the case?
Fixed in a new release: https://github.com/midwan/MB_SubSonic/releases/tag/v2.33
Please note, there is also a bug in MusicBee 3.4 itself, which needs to be fixed. I tested it with a patched version (3.4.7913 P) which seemed to work.