The media devices i am using (wdtv live) will see the server after a reboot of both server and media device. But this problem, is really annoying for media devices that as relying on browsing the network for media files. If i were just using windows clients this would not be a problem for me, mapped drives and so on still works. I then tried \\ip.adress and this would still work. I have experienced that even this did not work.
When this happens i can most of the time still manually type \\servername and be able to browse the shares. It usually still see the the server as a media service, but not the shares. But after a while if you restart client it will no longer find the server i network browsing. And as long as the client is online it will "remember" the server in this view. I'm only trying to reporting that isn't working with this two particular DLNA servers and I ask you help to debug myself or maybe ask you to reproduce and fix the issue (I'm not the only one who reported the issue, you know).I am having the same problem as described here.Īfter a reboot of both server and client, the server will usually show up in network. I don't have dubts that it will work with Windows Media Player and I'm not complaining that the DLNA support in DeoVR isn't working with every DLNA server out there. I don't want to switch to another DLNA server such as Windows media server because I already have Serviio running on my network for years.
We just have to understand what DeoVR doesn't like listing the files in the DLNA folders when accessing these DLNA servers. But I really want to make DeoVR working too. I'm able to play contents served by Serviio with every other DLNA client, including other VR players on the Quest. I had only the opportunity to test Serviio DLNA server and I unfortunately can't see any file inside the DLNA folders. Seems that DeoVR lacks of compatibility with the Serviio and SimpleDLNA DLNA servers (but is perfectly working with other DLNA servers).
0 kommentar(er)
