[Solved] Can't get 10.20.0 working.

[JDN165]

(as requested moved from the Announcements section)

For some reason I can't get 10.20.0 working.

Version 10.19.0 runs without problem (serving audio FLAC files on my pc, mediaplayer Sangean WFT-3, client: BubbleUPnP).

When I upgrade 10.19.0 to 10.20.0 (no clean install), I notice that the field "Default renderer when automatic detection fails" on the General Settings tab is changed to "Unknown renderer" for some reason (and I can't select another one from the pulldown menu, this is the only entry, see attachment).
Then, if I try to connect to UMS with BubbleUPnP, there's an error message:

Browse error
Reason: Current state of service prevents invoking that action. Error reading response failure message. Can't transform message payload: org.xmlpull.v1.XmlPullParserException:
Unexpected token (position: TEXT Failure: 500 Int...@1:35 in java.io.InputStreamReader@6cdbf39).

The Sangean WFT-3 also couldn't connect anymore to UMS (which always worked with 10.19.0). The UMS server is visible, but selecting it result in an error.

Next thing I did was completely remove UMS, I also deleted the folders <program files>\Universal Media Server and <programdata>\UMS. Then I did a clean install of 10.20.0, but same problem: again the "Unknown renderer" in the pulldown menu (which is the sole entry), the same error message in BubbleUPnP above and the Sangean can still not connect.

I eventually reinstalled 10.19.0 (without uninstalling 10.20.0, so overwriting the 10.20.0 installation) and everything worked fine again. Renderers can be selected again, and BubbleUPnP (and the direct connection with my Sangean) can connect to UMS.

I created Trace Logs, both for version 10.20.0 and (after overwriting the 10.20.0 installation with 10.19.0) also for version 10.19.0. So, the 10.20.0 log represents the situation when UMS failed and when the 10.19.0 log was created everything worked fine again.

Any idea what's wrong here?

[mik_s]

I did see this error that appears to stop UMS from initializing properly.

Code: Select all

DEBUG 2022-04-30 08:28:07.495 [main] net.pms.PMS 
java.lang.NullPointerException: null
	at net.pms.dlna.RootFolder.addVirtualMyMusicFolder(RootFolder.java:100)
	at net.pms.dlna.RootFolder.<init>(RootFolder.java:87)
	at net.pms.configuration.RendererConfiguration.getRootFolder(RendererConfiguration.java:497)
	at net.pms.PMS.getRootFolder(PMS.java:171)
	at net.pms.PMS.init(PMS.java:724)
	at net.pms.PMS.createInstance(PMS.java:928)
	at net.pms.PMS.main(PMS.java:1094)
ERROR 2022-04-30 08:28:07.495 [main] net.pms.PMS A serious error occurred during Universal Media Server initialization: null

It might be a bug that the devs will have to look at, possibly to do with your virtual folders.
You could try removing your VirtualFoldersGBS.conf and see if that makes a difference.


I think the reason why the default renderer list is empty is because of these settings and is ignoring them

Code: Select all

selected_renderers =Sangean
renderer_default =Sangean WFT-3
renderer_force_default =true

It is best to leave these as default and let UMS decide which .conf to use for each device, especially if more than 1 device connects to UMS.


Also the cache is disabled.

Code: Select all

use_cache =false

It is used for various things not just for speeding up listing of your files.
It could also be a reason why it is failing, but is probably a bug too if it is. Try enabling it and see if that helps.

[JDN165]

Thanks for your reply.

I limited the renderers on purpose to only the Sangean, because that's the only one I am using for my audio (and I don't use UMS for video). Earlier the renderers weren't limited, but this sometimes resulted in unwanted behavior. Perhaps nowadays it's no longer a problem, but since I only use the Sangean, I forced it to be the only renderer (and the default).

Same applies for the cache. Enabling the cache resulted in strange behavior several times, so I disabled it (I think this was a suggestion I found on this forum).

I will try to reinstall 10.20.0 again without using the virtual folder file, but this will be tomorrow before I find the time for this. To be continued...

[SubJunk]

The fix for this will be in 10.21.1 and v11.0.0-a2, thanks for reporting it!

[JDN165]

Thanks, will wait for the update!

[DJWolverine]

I have the same problem..10.19 and all before worked fine ..but 10.20 and the beta 11 both give me
no connection on my WDLIVE....It shows the like top end folder but although they're all still listed in the
Shared Content list, none of them shows up on my TV Screen ...so back to 10.19 I have gone...for now

[SubJunk]

The fix is being released today, thanks for reporting

[DJWolverine]

happy to find that new updated version works perfectly...THANKS!!!