INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: 1 [2]   Go Down

Author Topic: DLNA problem  (Read 22393 times)

bob

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 13943
Re: DLNA problem
« Reply #50 on: July 29, 2013, 03:24:37 pm »

You shouldn't get a BYE message except for when MC is exiting or you are going into options (exiting options resets the servers).

If you wanted to send a wireshark tracing of the interaction that'd be great. If it comes and goes without any other action going on in the network then it should be pretty easy to get a clean, small trace.

http://wiki.jriver.com/index.php/Sharing_Plug-in_Debugging_Hints
Logged

chf

  • Recent member
  • *
  • Posts: 12
Re: DLNA problem
« Reply #51 on: July 31, 2013, 01:28:13 am »

Thanks Bob.

I just ran a wireshark trace, sent you a PM...

Cheers,

Charles
Logged

chf

  • Recent member
  • *
  • Posts: 12
Re: DLNA problem
« Reply #52 on: August 01, 2013, 12:56:59 am »

I performed another test, which may be helpful in finding the root-cause...
I played audio to the Samsung Dock using different DLNA controller and sources:

- using the PlayTo function of Windows Media Player on same PC as JRiver MC is on: OK
- using BubbleUPNP on my Android phone as controller, with JRiver MC as DLNA server: OK
- using SendTo in JRiver MC directly to the Samsung Dock: NOK

So it seems that the JRiver MC controller is the key factor in this.

/Charles
Logged
Pages: 1 [2]   Go Up