mpw222
2009-02-08, 19:04
Once in a while I get pauses in high bitrate (Blu-Ray remuxes, 40mbps or so) due to a delayed response from my file server. While I'd like to figure out what's causing this, I thought that xbmc should be able to handle this on the player side as well by caching more than the current 2MB default or 16MB max for network files.
My idea is that you could set up 2 caching values, one would be the minimum to start playback. After playback started, xbmc could continue to read ahead in the file until it hit a much larger cache value. With 2GB of memory costing next to nothing these days, being able to use up to 256MB or 512MB of it to ensure smooth playback in the event of network congestion or load on whatever is serving files doesn't seem crazy. It might make sense to make this value adaptive - cache the next 30 seconds of data based on the current bitrate.
I imagine the 16MB limit now has something to do with the limited amount of memory on an xbox, so this feature would only be for the Linux/Mac/Win versions.
My idea is that you could set up 2 caching values, one would be the minimum to start playback. After playback started, xbmc could continue to read ahead in the file until it hit a much larger cache value. With 2GB of memory costing next to nothing these days, being able to use up to 256MB or 512MB of it to ensure smooth playback in the event of network congestion or load on whatever is serving files doesn't seem crazy. It might make sense to make this value adaptive - cache the next 30 seconds of data based on the current bitrate.
I imagine the 16MB limit now has something to do with the limited amount of memory on an xbox, so this feature would only be for the Linux/Mac/Win versions.