2015-06-02, 17:13
I'm trying to understand how the settings explained here are intended to work: http://kodi.wiki/view/HOW-TO:Modify_the_video_cache
I set this up in advancedsettings.xml (correctly placed and confirmed by logs):
First of all, the playback info (O) report something around 218MB of cache being filled. Shouldn't it be higher? I have 16GB of RAM on the machine where I'm testing this, it shouldn't be a problem.
Second, on local files, the file starts pretty instantly (understandably), with the cache pretty much already filled to 218MB. The same file, played through a virtual drive (I'm using NetDrive2, accessing Google Drive) fills abou the same amount of cache but it waits a lot before starting, stating that it's "buffering". Now if I revert to standard cache settings, eliminating the entries in advancedsettings.xml, this doesn't happen.
The same holds true when seeking. I sometimes see the cache filling up to 60MB or so before playback resuming. And it doesn't make any sense.
It's as if, according to some of the above settings, there's a certain minimum amount of buffer that Kodi "thinks" it's needed before starting playback.
The real problem is that this happens, with the above settings, even when accessing "local" SMB resources, and that's more problematic for me than the gDrive stuff (which is more or less archival material).
Is this something already known? Expected behaviour?
PS
I see this happen, more or less with no differences, with both 14.2 and 15 nightlies.
PPS
To have cache working (assuming I'll manage to have it work correctly) with SMB shares, do I need buffermode 0 or buffermode 1?
I set this up in advancedsettings.xml (correctly placed and confirmed by logs):
Code:
<network>
<buffermode>1</buffermode>
<cachemembuffersize>457286400</cachemembuffersize>
<readbufferfactor>20</readbufferfactor>
</network>
First of all, the playback info (O) report something around 218MB of cache being filled. Shouldn't it be higher? I have 16GB of RAM on the machine where I'm testing this, it shouldn't be a problem.
Second, on local files, the file starts pretty instantly (understandably), with the cache pretty much already filled to 218MB. The same file, played through a virtual drive (I'm using NetDrive2, accessing Google Drive) fills abou the same amount of cache but it waits a lot before starting, stating that it's "buffering". Now if I revert to standard cache settings, eliminating the entries in advancedsettings.xml, this doesn't happen.
The same holds true when seeking. I sometimes see the cache filling up to 60MB or so before playback resuming. And it doesn't make any sense.
It's as if, according to some of the above settings, there's a certain minimum amount of buffer that Kodi "thinks" it's needed before starting playback.
The real problem is that this happens, with the above settings, even when accessing "local" SMB resources, and that's more problematic for me than the gDrive stuff (which is more or less archival material).
Is this something already known? Expected behaviour?
PS
I see this happen, more or less with no differences, with both 14.2 and 15 nightlies.
PPS
To have cache working (assuming I'll manage to have it work correctly) with SMB shares, do I need buffermode 0 or buffermode 1?