INTERACT FORUM

Please login or register.

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

Author Topic: DLNA Renderer Problems  (Read 3180 times)

markf2748

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 692
Re: DLNA Renderer Problems [Solved]
« Reply #50 on: November 17, 2021, 10:44:11 am »

Sorry for the huge pictures. How do I stop it from being so big? :)
Scale down the picture size in a photo editor app on your PC or phone before posting.
You can edit the old posts, delete and replace pictures with smaller ones.
Logged

zender

  • Junior Woodchuck
  • **
  • Posts: 56
Re: DLNA Renderer Problems
« Reply #51 on: November 17, 2021, 11:38:57 am »

I still don’t see anything useful in the log other than that failed play command.

If you want to keep pursuing this, I need a wireshark trace.
Install wireshark for your PC.
Set a capture filter to only show packets from your rendering device
ip host 1.2.3.4
Change 1.2.3.4 to your renderer IP address.
Start the capture just before you push a track to the renderer and stop it right after the failure.
Save the capture pcap file and email it to
bob (at) jriver (dot) com
Thanks.
capture was sent
Logged

zender

  • Junior Woodchuck
  • **
  • Posts: 56
Re: DLNA Renderer Problems
« Reply #52 on: November 17, 2021, 11:53:03 am »

Scale down the picture size in a photo editor app on your PC or phone before posting.
You can edit the old posts, delete and replace pictures with smaller ones.
Thanks!
Logged

markf2748

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 692
Re: DLNA Renderer Problems
« Reply #53 on: November 17, 2021, 12:46:11 pm »

Reviewing the pictures again, it does appear that you selected the Buchardt DLNA renderer (as you stated) rather than the Buchardt Chromecast renderer.  While they both appear on the phone, apparently only the active renderer is in the MC server Playing now zones, as Bob described above (since you have not deployed BubbleUPnPServer on PC). 

You may find that Chromecast is limited to 16/24 bits, up to 96 KHz, no gapless if it is constrained by the original Chromecast Audio specs.  Within these limitations, I have confirmed the BubbleUPnPServer over MC is bit perfect playing to original CA dongle.
Logged

zender

  • Junior Woodchuck
  • **
  • Posts: 56
Re: DLNA Renderer Problems
« Reply #54 on: November 17, 2021, 02:32:24 pm »

Ok, we found a solution to the problem!
Turning off the DLNAExtra flag did the trick and now I have a clear path to the stereo hub and everything is working fine.
Logged

zender

  • Junior Woodchuck
  • **
  • Posts: 56
Re: DLNA Renderer Problems
« Reply #55 on: November 17, 2021, 02:36:32 pm »

Reviewing the pictures again, it does appear that you selected the Buchardt DLNA renderer (as you stated) rather than the Buchardt Chromecast renderer.  While they both appear on the phone, apparently only the active renderer is in the MC server Playing now zones, as Bob described above (since you have not deployed BubbleUPnPServer on PC). 

You may find that Chromecast is limited to 16/24 bits, up to 96 KHz, no gapless if it is constrained by the original Chromecast Audio specs.  Within these limitations, I have confirmed the BubbleUPnPServer over MC is bit perfect playing to original CA dongle.
I didn't know of the option to deploy BubbleUPnPServer on PC. What will it give me? a bypass to the MC and going straight to my HDD fils?
Logged

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 71462
  • Where did I put my teeth?
Re: DLNA Renderer Problems
« Reply #56 on: November 17, 2021, 03:38:39 pm »

I didn't know of the option to deploy BubbleUPnPServer on PC. What will it give me? a bypass to the MC and going straight to my HDD fils?
Please start a thread on the Third Party board here.

Closing this now.
Logged
Pages: 1 [2]   Go Up