Jump to content

DLNA server not detected by Bigscreen on Oculus Quest 3


Recommended Posts

Posted

Hello,

I have an Emby server ver. 4.8.10.0 running in a podman container with DLNA server activated (DLNA plugin ver. 1.4.5).

In the local LAN, I can play videos via DLNA server on an android smartphone with vlc, while the server is not detected by bigscreen app in oculus quest 3.

What I noticed is that vlc on the smartphone takes circa 2 minutes to detect the DLNA server, while bigscreen on quest 3 after a few seconds stops the search with the message that no DLNA server is available.

Reading the emby forums, I had the idea to increase the frequency of "blast alive messages", but I cannot find where to tweak this setting.

I activated the debug logging in DLNA plugin and in Emby server, but nothing is logged regarding DLNA when trying to connect via bigscreen.

I restarted Emby a few times but nothing changed.

Any ideas on how to solve the issue?

Thanks a lot in advance

Maurizio

 

Posted

Hi, that's strange because there were numerous BigScreen Dlna fixes that were made about a year ago:

The server beta channel does have some general dlna fixes so you could also try that if you are feeling adventurous.

Posted

Hi Luke,

thanks for your reply.

Actually I read the thread "DLNA in Bigscreen on Oculus" and I found that people not detecting the DLNA server solved the problem setting a lower "Blast Alive Message" (see attached message).

The problem is that I don't find this setting. I don't know if this is no more present in the current plugin version; eventually, could you please tell me how to adjust it?

Thanks again

Maurizio

 

Screenshot from 2024-11-28 18-35-04.png

  • 2 weeks later...
Posted

Hi @bludus, with bigscreen open, if you restart emby server, does that get it to show up?

  • 3 months later...
JackBowman
Posted

I know this is an old thread, but I am dealing with this issue as well. Emby DLNA will show up sporadically. Is there a setting for this "Blast Alive Message Interval"?

JackBowman
Posted (edited)

I rebooted my mesh routers and the Server. Things appear to be working fine now.

Edited by JackBowman
  • Thanks 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...