Hi all,
I'm getting an error a lot on my XBOX One S saying "source too slow for continious playback". The files are on my nas and are regular HD, all cables are Gigabit. the Problem doesnt happen on other devices. Anybody have any idea what this may be? I'm getting the feeling my Xbox isnt getting proper Gigabit Speeds.
It would sound that way. What protocol are you using the share the files from the NAS? SMB, NFS, FTP, something else?
A logging enabled
debug log (wiki) uploaded to our paste site and the URL shared here may help. See the wiki link for details, but simplest route is the log uploader addon.
(2019-08-09, 12:39)DarrenHill Wrote: [ -> ]It would sound that way. What protocol are you using the share the files from the NAS? SMB, NFS, FTP, something else?
A logging enabled debug log (wiki) uploaded to our paste site and the URL shared here may help. See the wiki link for details, but simplest route is the log uploader addon.
I'm using the Emby addon but I think thats using NFS. I also tried playing a file outside of emby using nfs and the same problem occured. I'm at work at the moment, I'll create a log when I get home. Is there a specific protocol I should be using. I also tried playing a 4k file once and got the same error so I tried it in VLC and got a similar error. For normal HD the error only happens sometimes and goes away shortly after and resumes Play.
thanks!
NFS is usually preferrable, although SMB is common as well.
If it's happening across apps it's most likely something in your network or device set-up, as you already mentioned.
Looks to me like either a server issue or an Emby one:
Code:
2019-08-09 16:48:54.352 T:6760 NOTICE: Emby.emby.core.http -> ERROR:: HTTPConnectionPool(host='192.168.178.53', port=8096): Max retries exceeded with url: /emby/system/info/public (Caused by ConnectTimeoutError(<requests.packages.urllib3.connection.HTTPConnection object at 0x000001B059DB7B70>, 'Connection to 192.168.178.53 timed out. (connect timeout=8)'))
2019-08-09 16:48:54.353 T:6760 NOTICE: Emby.emby.core.connection_manager -> ERROR::
2019-08-09 16:48:54.354 T:6760 NOTICE: Emby.emby.core.connection_manager -> ERROR:: test failed for connection mode 2 with server Server2019
2019-08-09 16:48:54.354 T:6760 NOTICE: Emby.emby.core.connection_manager -> testing connection mode 0 with server Server2019
2019-08-09 16:48:54.355 T:6760 NOTICE: Emby.emby.core.connection_manager -> tryConnect url: http://{emby-server}/emby/system/info/public
Code:
2019-08-09 16:49:21.125 T:1420 ERROR: Playlist Player: skipping unplayable item: 0, path [http://127.0.0.1:57578/emby/kodi/movies/24170/file.strm?KodiId=73&Name=Bumblebee+%282018%29+Remux-2160p+Proper.mkv&Id=24170]
2019-08-09 16:49:22.060 T:5628 NOTICE: EMBY.hooks.webservice -> --<[ queue play ]
2019-08-09 16:49:41.349 T:1420 ERROR: CCurlFile::Stat - Failed: Timeout was reached(28) for http://188.96.217.232:8096/emby/Videos/24170/stream?static=true&MediaSourceId=a6453131254e1523aa5ea1db834fc855&api_key=a63d5319356f4987a4f3f9e6295ac348
2019-08-09 16:49:41.398 T:1420 NOTICE: VideoPlayer::OpenFile: http://188.96.217.232:8096/emby/Videos/24170/stream?static=true&MediaSourceId=a6453131254e1523aa5ea1db834fc855&api_key=a63d5319356f4987a4f3f9e6295ac348
As Emby isn't technically part of Kodi you're probably best to raise it with them. It sounds like the set-up isn't right, and as it's not our code you're better talking to them about it.
https://emby.media/support.html
(2019-08-09, 17:16)DarrenHill Wrote: [ -> ]Looks to me like either a server issue or an Emby one:
Code:
2019-08-09 16:48:54.352 T:6760 NOTICE: Emby.emby.core.http -> ERROR:: HTTPConnectionPool(host='192.168.178.53', port=8096): Max retries exceeded with url: /emby/system/info/public (Caused by ConnectTimeoutError(<requests.packages.urllib3.connection.HTTPConnection object at 0x000001B059DB7B70>, 'Connection to 192.168.178.53 timed out. (connect timeout=8)'))
2019-08-09 16:48:54.353 T:6760 NOTICE: Emby.emby.core.connection_manager -> ERROR::
2019-08-09 16:48:54.354 T:6760 NOTICE: Emby.emby.core.connection_manager -> ERROR:: test failed for connection mode 2 with server Server2019
2019-08-09 16:48:54.354 T:6760 NOTICE: Emby.emby.core.connection_manager -> testing connection mode 0 with server Server2019
2019-08-09 16:48:54.355 T:6760 NOTICE: Emby.emby.core.connection_manager -> tryConnect url: http://{emby-server}/emby/system/info/public
Code:
2019-08-09 16:49:21.125 T:1420 ERROR: Playlist Player: skipping unplayable item: 0, path [http://127.0.0.1:57578/emby/kodi/movies/24170/file.strm?KodiId=73&Name=Bumblebee+%282018%29+Remux-2160p+Proper.mkv&Id=24170]
2019-08-09 16:49:22.060 T:5628 NOTICE: EMBY.hooks.webservice -> --<[ queue play ]
2019-08-09 16:49:41.349 T:1420 ERROR: CCurlFile::Stat - Failed: Timeout was reached(28) for http://188.96.217.232:8096/emby/Videos/24170/stream?static=true&MediaSourceId=a6453131254e1523aa5ea1db834fc855&api_key=a63d5319356f4987a4f3f9e6295ac348
2019-08-09 16:49:41.398 T:1420 NOTICE: VideoPlayer::OpenFile: http://188.96.217.232:8096/emby/Videos/24170/stream?static=true&MediaSourceId=a6453131254e1523aa5ea1db834fc855&api_key=a63d5319356f4987a4f3f9e6295ac348
As Emby isn't technically part of Kodi you're probably best to raise it with them. It sounds like the set-up isn't right, and as it's not our code you're better talking to them about it.
https://emby.media/support.html
Thanks Darren. I deleted the cache and tried a 4k movie again and this time it works when using a direct path but not with emby. It indeed looks like an emby problem, thanks again for the help.