I don’t search the solution, i try to found a testcase definition, what can I do to create usefulls testcase and logfiles.
Before the october update i’ve issues when i try to play for/back a file (recorded from french TNT), sometime Kodi freeze I need to restart the Mediacenter from SSH.
Now (sometime) when i try to for/back this files the image freeze, but not Kodi. I can stop and restart with the remote .
Other things, I’ve two VERO 4 box, one with HDMI CEC remote, one with the OSMC remote. For the moment i’ve the issues only with the CEC remote.
(and I remember) that before the october update i (think ???) that it’s works better with the Kodi Android apps as with the CEC Remote
Now when i try to play the same file (NAS synology nfs ) with the two box, it isn’t the same.
Vero4(10) CEC remote Box have sometime (but not allways) buffer issues, file (image) is freeze when i start CEC remote forward, play is freeze, but Kodi works. I can get out the file and restart play with the menu.
-Vero4 (11) with OSMC remote and the same file works for the moment fine.
I’ve see in the log
osmc CRenderManager::WaitForBuffer - timeout waiting for buffer
Before uploading any logs, you should ensure that Debugging is enabled in Kodi. This can be done by going to Settings -> System -> Logging -> and selecting Enable Debugging. You should then perform a reboot of your device and perform only the minimum actions required to replicate this issue so that it is easy to identify the cause of the problem.
If you are using the default OSMC skin, then My OSMC will be accessible via your Home screen. If you are using Confluence then it will be available via the Settings sub-menu. For other skins, My OSMC can be found via the Programs section. …
After opening My OSMC, navigate to Logs.
I use NFS /Kodi with Synology NAS and two Vero4Box.
I (remember ??) that in the Kodi 17.5 Github some works do to play for/back.
And it’s works better then before October Update.
New are some Buffers issues and I’m not sure that my cache setitings are the best.
I push readfactor to 6 , it’s better,but maybe it’s can be more…
Before i play with memory and after reading the kodi wiki, i prefere to ask, if somebody has some ideas.
It is “imaginable” that play for/back with the same file (on the same NAS) can be different
on the same Vero4 box with CEC remote or Kodi apps.
on another Vero4 Box with OSMC remote.
Yes I’ve, but I think it isn’t the problem. The network works allways, but sometime when i try to play forward or backward I’ve issues.
Before the oct update Kodi freeze (ssh restart mediacenter) now (only) sometime the image freeze, but i can go back to the menu and restart the movie.
Here I think it’s a buffer issues (and when I remember right I 've copy my cache settings from one of your threads)
With Kodi 17.5 and the new ffmpeg perhaps better cache settings are possible ??
And the second point I’ve not this issue (with the same movie) everytime, and I use different remote on my two box.
But there is the jungle.
Perhaps found in first time the best cache settings.
I thought it was at least worth mentioning the possibility of broadcast storms.
I doubt if increasing the readfactor higher than 6 will help - but it won’t do any harm, though it will probably cause Kodi to use all the network bandwidth in short bursts.
The memorysize is a little more difficult to recommend. The Kodi wiki continues to suggest that it will use RAM that is 3 times the number you specify. However, people have examined the actual code and this no longer seems to be correct. So you’ll need to experiment - but at least the Vero4K has more RAM than a Raspberry Pi, so you have more scope for experimentation.