I would also like to see this functionality implemented, as it would be useful if:
1) Bandwidth is inconsistent, but average throughput is sufficient
2) Bandwidth is sufficient most of the time, except for some higher bitrate action sequences
3) Bandwidth is insufficient, but the video can be watched while the file is downloading
I for one like to stream 1080p over the Internet, as I prefer to have my content stored on a personal server in a data centre so that I can access it from multiple locations, and short of having my own strands of fiber pulled to my home, I won't be able to use gigabit. So, 1) and 2) would both apply to my use case. I do appreciate however that it will require somebody to contribute their development time, and I would like to thank in advance whoever takes on this task.
GJones Wrote:Yes, but the majority of discussion has not been about a fluctuating network. Buffers are for fluctuating networks, not slow networks.
Considering the op began the thread with:
galets Wrote:the fundamental problem, which is: network access could be flakey
and that you were the 2nd person to post, it's a bit disingenuous to suggest that the majority of posts are about slow networks, when it's people like you who have operated on false assumptions and subverted the original intent of the op.
GJones Wrote:I won't say smarter or cooler. I will say more experienced with more expertise. I was on a TCP/IP Performance and Design Analysis Team for one of the world's largest IT companies. That does, in fact, make me an expert.
Good for you. What role did you serve on the team? Based on your posts in this thread, it would appear that it was neither requirements gathering nor architecture.
Kevon513 Wrote:And please, try not to forget, No matter how smart and cool you think you are, there is always a room full of people who are smarter and cooler. So play nice
Very wise words. Unfortunately, egos inevitably get in the way and not everyone has the humility to heed them.
atari800 Wrote:Just tossing this in for clarity---
If on wifi, it takes 30 minutes to copy a 20 minute movie - buffering is pointless - too slow (unless you buffer entire movie)
It's still not pointless; you could start watching the movie after waiting only 10 minutes instead of 30 as per 3) above.
Here's an interim workaround for anyone who stands to benefit from increased caching; setup an instance of a proxy cacher like squid, nginx, or varnish, and request the file through it using HTTP. This way, the entire file will get downloaded into a local file cache but you will still be able to stream the file in the interim just using xbmc's buffer.