Page 1 of 1

Redirecting Subsonic - Why is it better?

PostPosted: Fri Oct 28, 2011 2:39 pm
by bethesdaadk
I'm running Subsonic on a HP Media Smart Server EX470 running WHS v1 upgraded to 2 GB Ram. It's definitely a low powered server. I frequently listen to it from work, but the stream would randomly cut off. I couldn't figure out why. Then one day, I saw the option to redirection to subsonic.org. Well, I'm listening to it now, and not a single song has stopped. I'm happy, but curious. Does this have something to do with the non-static nature of my home ISP (Verizon Fios)? Why is this experience much more solid - redirecting - then just going direct to my server? It seems counter intuitive.

The benefits are: better performance and a much easier URL.

Thanks for your thoughts.

Re: Redirecting Subsonic - Why is it better?

PostPosted: Tue Jan 24, 2012 5:24 pm
by Beowolf
Hello, i have the same box, and have noticed even with my 2mb UL i get choppy aswell, seems i have some slow aches

same box, whs 2011
appache and subsonic

ideas on running smoother?

Re: Redirecting Subsonic - Why is it better?

PostPosted: Mon Jan 30, 2012 8:45 am
by GJ51
I've got an Ex485 - admittedly a bit juiced up - but I've set it up with the SS.org redirect, the servername.homeserver.com:port# method, and I've also connected just entering the external ip:port#.

I have Verizon FIOS

I've never noticed any difference in performance using nay of the connection methods listed above.

Choppiness is usually due to CPU overload or bandwidth issues. You can check task manager on the server when this is happening to see what kind of CPU load is going on. One of the first things I did with th HP homeserver V1 was to ditch Twonky Media, it is a real CPU hog, in fact, that's why I found and switched to Subsonic.

DNS, http redirect, or typing in the ip address and port number essentially due the same thing, they give the two computers involved the correct ip:port# needed to establish the connection.