View Single Post
Old 24th September 2017, 23:38   #5
Major Dude
dopelabs's Avatar
Join Date: Oct 2006
Location: Silicon Valley
Posts: 531
Send a message via AIM to dopelabs
the most common cause for the problems you are experiencing are some type of network latency/packet loss between you and the DNAS. network conditions can change at any time for any number of reasons...

a switch or a router somewhere is failing or in a bad state
any of the links along the path become saturated
some idiot with a backhoe digs through a trunk of fiber and the new route you have to take isnt as good
bad weather causing utility lines to sway and eventually over time things can jiggle loose
maybe your windows is compromised as they tend to do by some malware or legit app thats decided to use upstream network resources...

you can try changing the wifi password or disabling wifi all together and testing again. this way you can be sure there arent any other devices on the network that could be hogging the bandwidth. something as simple as having an iphone that has icloud enabled and taking a picture can cause the stream to buffer as the photos are pushed to icloud servers as you take them since it will use all available bandwidth to upload.

i have never recommended using wifi for broadcasting. from what i have experienced in the ~2 decades ive been doing this stuff, ive only seen wifi work, and be stable without any interruptions or buffers a handful of times.. thus ive always made it a mandatory requirement that my djs use a hardline. much less hassle.

one of the best tools you can use to see what network path your taking to get from your home to the DNAS is called MTR. there are versions for every OS available. *osx and *nix will be available via command line. windows has a gui version you can use..i think its called winmtr... this tool combines ping and traceroute and will show you the ping times and any loss of every hop between you and the the DNAS. you can easily spot any hops that are causing problems if they have high loss, latency, or high deviation/jitter. if you notice any problems you can report them to your ISP. if they do their job correctly and can also reproduce the results, they should open a trouble ticket for their network engineers or escalate the issue to their upstream provider(s)

you can also try taking your laptop to another location (preferably a different ISP) and try testing a broadcast from there. or try going through a proxy or vpn so that the path is different.

and even though technology advances every day, many of the methods remain the same... turn it off and on again. try power cycling all network equipment that you have access to between you and the DNAS. make sure you fully disconnect the power source until any and all status LED's go dark for a few seconds. then power everything back on sequentially starting at the outer most device and working your way back to your local machine.

also, be patient. sometimes if there are network problems, it may take some time for them to coordinate hardware replacements or repairs or for them to track down any configuration errors, etc.. most times things will work themselves out if its issue is causing major problems. many ISP's will not work in a proactive manor, and basically rely on their customer base to start reporting problems before they will even notice or investigate.

lastly this could also be a simple case of oversubscription or server problems on the DNAS end. many providers will oversubscribe so they can rake in more $$$. unfortunately its the customer that sees the negative impact when inevitably one or more of their clients gets popular, everyone else suffers.
dopelabs is offline   Reply With Quote