Is flow control enabled at the host level? I would think it could cause issues there as well.
Several others including myself have reported this problem but it hasn't gotten fixed. I stopped getting responses in the below thread while trying to help troubleshoot it for them. There is definitely something in the Windows version of this software causing the issue. I'm currently running a separate old Ubuntu box just for Channels because of this issue.
If you right click on the system tray it should show a flow control fix option. It might already be disabled- if it's not the dvr web UI would show a warning about it.
It might be worth enabling flow control to see if that fixes this issue. If it's really only happening on 100mbps connections that's helpful information we didn't have before.
I do not have an option to disable or enable flow control. The option does not seem to exist in my VM. And yes, I have now tested on 3 different ATV 4th gens, it is only happening on 100 mbps connections.
Correct, this is all that it shows
There is some weird interaction happening with the dvr software and the windows networking stack, but we haven't been able to figure out what exactly yet.
If you'd like to try the latest dvr pre-release you can hold the shift key and click Check for Updates. There are changes in there that might help.
Okay let me try that, I'll let you know if it fixes it. Gotta wait till the house goes to sleep so I don't disrupt any recordings
You can shift click and it will wait to update until everything is idle.
Ah gotcha, will do
Just tested, it feels maybe ever so slightly faster, but could just be a placebo effect. It is generally fast after the first skip, but anything after that or skimming through the recording takes a bit for it to load.
Not sure if you've tried this, but you could disable Windows network autotune.
Go to an admin command prompt and type:
netsh int tcp set global autotuninglevel=disabled
You'll probably need to reboot the computer.
If you find it doesn't help, you should probably re-enable autotune. To re-enable Windows network autotune use:
netsh int tcp set global autotuninglevel=normal
I've not used this for Channels as I use it on a Macbook Pro. But I have had to disable Windows network autotune for other server based apps where it was affecting the throughput.
That actually fixed it! We should mark this as the solution for anyone else having this problem or put it on the FAQ
Wow, thanks for that @AndreVaux
Looks like there are several other options for the autotuning option, so it might be worth trying some of the others to see if they also fix the problem.
autotuninglevel - One of the following values: disabled: Fix the receive window at its default value. highlyrestricted: Allow the receive window to grow beyond its default value, but do so very conservatively. restricted: Allow the receive window to grow beyond its default value, but limit such growth in some scenarios. normal: Allow the receive window to grow to accommodate almost all scenarios. experimental: Allow the receive window to grow to accommodate extreme scenarios.
Reading more about autotuning, it doesn't seem like its a good idea to turn it off. It will negatively affect other internet based downloads. However, if it really does make a difference that gives me an idea of something I can change in the app that might fix the problem.
@Marino13 @Bob_Prendergast @nonebeter99 Can you try disabling autotuning to see if it fixes the problem for you as well? Let me know, and if it does I will send out a beta build with some changes and you can try that with autotuning set back to normal.
Well, I wasn’t complaining because my ATV4k was fast, but my ATV had a 3-sec skip that I wasn’t complaining about (cause I was still saving 27secs), but this made it fly like the 4K was.
Thanks @AndreVaux for pointing this out!
I've put out a new beta build (available via getchannels.com/beta) which should fix the seeking problem even with autotuning enabled. Let me know how it works.
No worries. In the real world I've not seen any negative effects of disabling autotune. If the pc is solely for Channels use its probably fine to leave disabled. But if there's a new build that takes the autotune settings into account that's good
I have to say this is a great product - we'll done to the developers
My seek with the new beta was the as it being enabled. Re-disabled and it works again.
Okay thanks for testing. Perhaps the issue is that autotuning doesn't understand the other side is only running at 100mbps and is trying to tune it more than possible.
In any case I'm glad we finally found a solution to this long standing issue!