Ethernet
And I presume the 4k+…bought it with the black Friday prOmo
…I’m 33min Into movie now connected with external hdd. Further thanI’ve ever gotten so far… No stutter. So it probably is the streaming
Ethernet
And I presume the 4k+…bought it with the black Friday prOmo
…I’m 33min Into movie now connected with external hdd. Further thanI’ve ever gotten so far… No stutter. So it probably is the streaming
Sam, is the default cache setting still 1, 500MB and 5 for read ahead? Just curious if they’ve changed from when Kodi v17 was introduced.
Hi,
Please provide logs, details can found here:
How to submit a useful support request - General - OSMC
Thanks Tom.
How did you mount the SMB share? Via Kodi or directly via the underlying Linux OS? I believe this has performance benefits over letting Kodi do it.
I came from a chromebox with libreelec… So I just copied my sources. Xml file
Ok, the first thing if do is try mounting this directly in Linux rather with Kodi, there is a guide here;
An alternative but equally good way is to use Autofs, have a look at the instructions and see which you prefer.
OkI’ll give that a go. 2 quick questions before I try that… 1. It has to be IP? It can’t be the server name… Since it’s not a fixed ip. And 2…will the library need to Be reloaded? Causeit’s a big one… And not looking forward to resetting the watched status
I think hostname should work instead of ip. As for library, I think it needs reloading but you might be able to trick it providing you mount the new library with the same name as the current library, i’m Not 100% sure on this though.
Edit
This seems to explain a supported way of saving the info when you remove the old source and add the new source
https://kodi.wiki/view/HOW-TO:Backup_the_video_library#Moving_the_library
Path substitution is your friend: https://kodi.wiki/view/Path_substitution
EDIT: I guess path substitution is no longer your friend. Looks like it no longer works in V18 and will not be fixed.
If you bought it on Black Friday 2018, it’ll be a 4K +
OP shouldn’t need to do an fstab mount if he has a 4K + and has Gigabit Ethernet.
Can you go to My OSMC -> Logs and upload a set of all logs and send us the URL so we can check a couple of things?
Cheers
Sam
yes it’s a 4k+ …says so in system.
ok … n00b question … is the logging automatically on ? Meaning I can just do the upload of it ? And it’ll have the info needed (from previous files watched )… or do I first need to turn it on ? And then play a troublesome file until I get the problem … and then upload ?
Nope, we need debug logs. Follow the instructions in the link @Tom_Doyle kindly provided to enable debug mode, play a movie till it stutters, upload the logs and paste the shown url here.
aah yes clear . .sorry … didn’t see his link. Will do that, since logfile I got now is 11Mb
I’ll get back to you
To shrink the size of the logs, just reboot twice.
not sure if I did it right … cause the logfiles were 11Mb again (even after rebooting twice … I can upload it elsewhere if needed). I just used the kodi.log file from the debugging
http://paste.osmc.tv/rivejapidu.vhdl
So I rebooted and played the 4k file which has given me the most trouble so far (MI6).
After about 15 secs, it froze … with message on screen “Source Too Slow For Continuous Playback”.
After a few secs, it continued. The problem then started around the 9min mark. Video would continue to play … audio gets out of sync and then disappears completely. If I pause the movie … wait around 10secs or so and continue … it’s fine again. Depending on the movie … I have to repeat this several times during.
Can it be the HDD on which the files are placed ? I have 1 WD Red in my machine, and 2 WD Blue’s. It just occured to me that all 4k files are on the WD Blue.
EDIT : not the HDD’s … copied the file to the WD Red, same problem
EDIT2 : deleted old dates from the uploadlog … and posted the rest
http://paste.osmc.tv/onikuzazit.md
anyone had time to look at the logs yet ?
Logs created on: 2019-03-22 09:29:33 - (Uptime = 4721098.86)
Uptime is 4.7 million seconds. Hmmm, that’s 54 days.
I’m guessing that permanent logging might be enabled. Does the directory /var/log/journal
exist?
no it does not.
not enough info in the other 2 logs ?
The large log is strange. Please run paste-log /etc/systemd/journald.conf
and tell us the URL.
The Kodi log is showing messages such as:
09:18:28.679 T:3555418880 DEBUG: Readrate 7518000 is too low with 9242245 required
It might be a network problem, but for now I would suggest you increase the readfactor in advancedsettings.xml from (its default of) 5 to 8 and reboot.
ok, i’ll try that & test later on. FYI … I tried with readfactor 6 quickly yesterday morning … but was exactly the same problem. I’ll put it on 8 now. (n00b question … but sudo stopping & starting the mediacenter is enough, right?)