More > JRiver Media Center 27 for Windows

Best DLNA setup

<< < (3/4) > >>

JimH:
For port forwarding use your manufacturer 's site and Google.
Firewall the same.

Windows Defender thread on the forum.

musicmahn:
Well to be clear I don't think it's totally a matter of knowing how to get into the settings but rather an understanding of what's being asked:
"Ports 52100 to 52200 should be open.  So should 1900 (for SSDP)"

I don't know whether that is incoming/outgoing UCP or TCP and what IP these should be pointing to.
What I've done (I think) is simply open up every possibility of the above as possible.

markf2748:

--- Quote from: musicmahn on July 11, 2021, 08:37:06 am ---Everything just seems to good with what you mention above.  I can see the renderer in BubbleUPnP -  JRiver sees it.  JRiver can still play to it - just very very poorly to the point of being unusable.  Moving BubbleUPnP to the PC yielded the same results.

...would prefer an optical output going into my receiver.

--- End quote ---

Which Chromecast are you using?  How long and what type is the output cable?  Sharp bends?

FYI:
The output port of the original Google Chromecast Audio dongle doubles as both an optical and coaxial SPDF output.  When the dongle receives a signal, the optical output is a bright uniform red diverging beam, easily seen as a red spot shining on a piece of paper within a half inch of the port.  The output of a fiber optic cable connected to the port should be a similarly bright uniform circular spot.  The appearance of the spot should not change when the fiber optic cable is jiggled around.  In the past, I had a very cheap poor quality, defective optical fiber connected to the port.  The fiber's output spot was distorted, dim, barely visible, sensitive to fiber motion, resulting in very poor audio performance (pauses, clicks, static etc.), which worsened with higher bandwidth signals.  Replacing with a better fiber optic cable (but not audiophile crazy) fixed the problem for me.

musicmahn:
It's not the chromecast as I can get it to play from Plex very reliably.  Lately I just try JRiver for a minute for the hell of it, google some more, cry and then play my music with Plex  :P

BubbleUPnP shows me the renderer all the time.  The renderer shows up in JRiver about 20 seconds after startup.  I play something and hear the "ding" that occurs when the chromecast is called.  5 seconds of silence and then it stops. 

I had plenty of this back in the day until I tweaked my ports etc.  What's extra weird about this bout is that music often will play, about a minute or so after it "doesn't".  Also new is watching the playing now list disappear before my eyes.  Things are setup, it's playing a track maybe even two and I watch all of the tracks before and after just disappear - leaving only the currently playing track.

I don't even push it this far any more though.  As soon as it "times out" for that 5 seconds I just give up because I know it's still messed up.

markf2748:

--- Quote from: musicmahn on July 11, 2021, 08:37:06 am ---I'm surely not the best with port forwarding stuff though it's never seemed to hold me back in the past.  Can this be spelled out in a detailed manner? 

--- End quote ---

FWIW, I never fooled around with port forwarding.  I just install the apps (MC27, MC28, BubbleUPnP) and allow them to open whatever ports they require by default (local home LAN using McAfee Total Defender).  Using "netstat -aon" in an elevated command window I can see all the LISTENING ports on the server, but I never had a need to decipher them.

In MC28, if I disconnect power to the Chromecast while playing, MC raises error messages about the lack of DLNA control, but does not delete the playlist in front of me.  Maybe it's worth a fresh install with a free trial of MC28 before giving up.

I will admit that occasionally, when connecting with JRemote2, it jumps back to start of track in the first few seconds and then restarts the first track, or sometimes jumps to the 2nd track.  Some kind of initial connection problem, but after that, playback is normal.  Can also happen when launching from a PC client to a Chromecast renderer.  I don't recall seeing this when launching to Chromecast from the server directly.

Navigation

[0] Message Index

[#] Next page

[*] Previous page