More > JRiver Media Center 30 for Windows

Finding DLNA renderer in "Playing Now"

<< < (3/4) > >>

PhDSM:
I did some tests with the different startup options:

If I use auto startup of MC+MS : (which is my normal settings)
  both MS & MC start normaly but no DLNA devices are shown
      after  5mn :   nothing
      after refresh dynamic entries : nothing
      after restarting MC only  : nothing
      again 5mn and refresh : nothing
      if I close MS and restart both  : all DLNA devices are found after 5s.  it works fine

If I use auto startup of MS :
  both MS  start normaly and no DLNA devices are shown
      after  5mn :   nothing
      after refresh dynamic entries in MS : nothing
      when  I start MC  : nothing
      again 5mn and refresh : nothing
      if I close MS and restart only MS all DLNA devices are found after 5s.
      then MC  works fine

If I do not use auto startup  :
  After system is completely started +1-2  minutes I start MS : all DLNA devices are found after 5s.
      then MC  works fine

If I use auto startup of MC :
   MC start normaly and all DLNA devices are shown after 8s
 
It seems the problems occurs only if MS is in auto-startup mode in such case It never finds DLNA devices until  the process is restarted.

I have a question on the exact role of Media Server vs MC when using network acces, in which case we need it ?
I have DLNA renderer devices, I use Gizmo and Web access, also remote from another instance of MC on another PC, also access files directly from my TV.
During these tests,  I noticed that all these remote access seems working without MS running
What is the role of MS ? I think I misunderstood it

JimH:
https://wiki.jriver.com/index.php/Media_Server

PhDSM:
Still confused between Media Server and Media Center.  Reading documentation seems that media server is running in order access media from the network or other devices, so that why I put both MS and MC as startup.

Based on my recent experience with the previous testing, now I run only MC (not MS) and all my remote access (From TV, other Computer, Gizmo or Web) are still working without needing Media Server.

So why we need MS  if all remote access works with MC ?

markf2748:
Here's my outsider's take:

If JRiver Media Center 30 Service (MS) starts up "independently" of the Media Center 30 Process (MC, the usual GUI), it seems that proper communication between the MS servers and MC is not guaranteed until MC is restarted, as you have reported.

If MC starts up first, it will subsequently start up MS (if set to do so).  Apparently in this case MC properly displays the responses to the MS UDP M-SEARCH blasts (device discovery).  That is why I set them both to start up with Windows in the MC settings, but set MS startup type to "Manual" in Windows Services. I think these settings effectively insure that MC starts up first, followed by it opening MS.  In this case the whole shebang works even without logging into your desktop.

MS must be running on the server computer for other networked devices (player phone apps, MC clients) to remotely access the MC libraries on the server computer using DLNA.  If you do not explicitly start up MS, then it can be started by MC on the server computer.  To confirm, have a look at Windows Services on the server PC - I'll bet a $ that you find MS running in the background, in addition to the usual MC process.

A pure MC client has no need for local MS.  You will not find MS running as a Service on the client computer and the client's Media Network display does not show any servers.  At least that is how it appears based on what is exposed to this Windows user.

3/30/2023 Corrections & clarifications.

JimH:
Media Server _is_ Media Center, but just uses less memory and has no user interface.  If it's running, the Media Center interface will open faster.

PhDSM,
I think your problem is your complex network configuration.  Why are you using switches?

Navigation

[0] Message Index

[#] Next page

[*] Previous page