Greg Hazel
-
Posts
725 -
Joined
-
Last visited
Content Type
Profiles
Forums
Gallery
Downloads
Events
Blogs
Store
Everything posted by Greg Hazel
-
Ah, I see.
-
Sorry, why would a limit of 1300kB/s do anything if the available bandwidth is only 450-550kB/s, max of 900kB/s?
-
Ok. Could you test again with rate limits, and see how low you have to limit it to get smooth video playback simultaneously?
-
The test was with no limit? You previously said: Which made me think you were setting a limit of 1300 kB/s.
-
No, number of packets. This is referred to (in TCP as well) as the "congestion window".
-
uTP measures the difference in latency between the smallest latency it has seen to a peer and the current latency. It transfers more or less data to make that difference match a target (100ms).
-
It uses ping times, and those are connected to the data rate. If it does not seem to be using your entire connection, please run the logging build and post the logs here.
-
Depends. uTP adjusts to network congestion, so if the congestion is not stable than the uTP transfer rate will be constantly adjusting to match.
-
This is actually not due to uTP. This is due to net.calc_overhead being on. uTorrent now actually reports the packet overhead due to ACKs and such. So, you would see this same behaviour if you enabled net.calc_overhead on 1.8.1 with TCP only.
-
They were switched in the statistics window, sorry. 5 == TCP, 10 == uTP
-
Can you test this again, with no upload or download rate limits? (both set to "Unlimited") I know it seems backward, but it might work, and demonstrate that we can improve something.
-
Even if you limit uTP down to 5kB/s? It seems unlikely that would have any effect on streaming at all. Let me know where the real threshold seems to be. Also, please run the logging build (13911) and send me the log files.
-
What's the use of custom encryption? Current encryption has not been broken.
-
You're running 13911... go use 13910 instead.
-
It does work, promise. Make sure you enable bep22 in the client. Options > Preferences > Advanced > isp.bep22
-
You could set up a DNS response and enable BEP 22 http://bittorrent.org/beps/bep_0022.html That should have the same effect, with no custom programs.
-
Please install Debugging Tools for Windows: http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx Then run uTorrent again. When it crashes, post the .dmp file on http://mediafire.com
-
What kind of plugins?
-
13911 is just 13910 with logging...
-
The UDP tracker spec is insufficient in many ways. The original author is aware, and there is discussion of the new spec here http://forum.bittorrent.org/viewtopic.php?id=18&p=1 When it comes out, uTorrent will look at supporting it.
-
Oh... k , though it looks like the selection is gone in the cat list.... Probably moved to a separator, which is not drawn.
-
The IPv4 address in the &ipv6 parameter
-
Going to have to wait for Richard to get back from vacation to fix that. It's not clearing anything, it's that inserting or removing a label causes the selection in the category list to stay where it was, even though it's selecting a new category.
-
New build: http://forum.utorrent.com/viewtopic.php?pid=377049#p377049
-
Same here. Now my stats are all screwed up' date=' I hope that is not permanent?[/quote'] Fixed, thanks! Sadly, it was permanent.