Jump to content

Playback fails frequently with Emby for Kodi

chjohans

By chjohans
in Kodi

 Share

Recommended Posts

Luke Emby Team

Luke   37050

Posted
Posted

He brings up a good point though, whether or not it's related to subtitles or resuming, can you try to find common factors? How is it playing through the server?

Link to comment
Share on other sites
TeamB

TeamB   2352

Posted
Posted

From you first post log

    Line 1166: 2019-10-03 21:41:22.950 T:9112   ERROR: Playlist Player: skipping unplayable item: 0, path [http://127.0.0.1:57578/emby/kodi/tvshows/153643/4736927/file.strm?KodiId=10745&Name=5x12+-+Ner+Tamid.mkv&Id=4736927]
    Line 2760: 2019-10-03 23:22:25.821 T:9112   ERROR: Playlist Player: skipping unplayable item: 0, path [http://127.0.0.1:57578/emby/kodi/tvshows/153643/4736927/file.strm?KodiId=10745&Name=5x12+-+Ner+Tamid.mkv&Id=4736927]
    Line 5229: 2019-10-04 13:03:14.961 T:9112   ERROR: Playlist Player: skipping unplayable item: 0, path [http://127.0.0.1:57578/emby/kodi/tvshows/153643/4789582/file.strm?KodiId=10746&Name=5x13+-+Leave+What+You+Don%27t.mkv&Id=4789582]
    Line 7416: 2019-10-04 17:11:28.351 T:9112   ERROR: Playlist Player: skipping unplayable item: 0, path [http://127.0.0.1:57578/emby/kodi/tvshows/153643/4789582/file.strm?KodiId=10746&Name=5x13+-+Leave+What+You+Don%27t.mkv&Id=4789582]
    Line 7622: 2019-10-04 17:12:21.150 T:9112   ERROR: Playlist Player: skipping unplayable item: 0, path [http://127.0.0.1:57578/emby/kodi/tvshows/153643/4789582/file.strm?KodiId=10746&Name=5x13+-+Leave+What+You+Don%27t.mkv&Id=4789582]
    Line 7801: 2019-10-04 17:13:12.327 T:9112   ERROR: Playlist Player: skipping unplayable item: 0, path [http://127.0.0.1:57578/emby/kodi/tvshows/153643/4789582/file.strm?KodiId=10746&Name=5x13+-+Leave+What+You+Don%27t.mkv&Id=4789582]
    Line 7922: 2019-10-04 17:13:40.290 T:9112   ERROR: Playlist Player: skipping unplayable item: 0, path [http://127.0.0.1:57578/emby/kodi/tvshows/153643/4789582/file.strm?KodiId=10746&Name=5x13+-+Leave+What+You+Don%27t.mkv&Id=4789582]
    Line 8484: 2019-10-04 17:18:27.479 T:9112   ERROR: Playlist Player: skipping unplayable item: 0, path [http://127.0.0.1:57578/emby/kodi/tvshows/153643/5089876/file.strm?KodiId=10747&Name=5x14+-+Today+and+Tomorrow.mkv&Id=5089876]
    Line 11018: 2019-10-04 22:10:46.851 T:9112   ERROR: Playlist Player: skipping unplayable item: 0, path [http://127.0.0.1:57578/emby/kodi/tvshows/153643/5089877/file.strm?KodiId=10748&Name=5x15+-+Channel+5.mkv&Id=5089877]
    Line 11170: 2019-10-04 22:12:40.116 T:9112   ERROR: Playlist Player: skipping unplayable item: 0, path [http://127.0.0.1:57578/emby/kodi/tvshows/153643/5089877/file.strm?KodiId=10748&Name=5x15+-+Channel+5.mkv&Id=5089877]
    Line 11399: 2019-10-04 22:13:22.718 T:9112   ERROR: Playlist Player: skipping unplayable item: 0, path [http://127.0.0.1:57578/emby/kodi/tvshows/153643/5089877/file.strm?KodiId=10748&Name=5x15+-+Channel+5.mkv&Id=5089877]
    Line 11502: 2019-10-04 22:13:45.650 T:4968   ERROR: CCurlFile::Open failed with code 0 for http://127.0.0.1:57578/emby/kodi/tvshows/153643/5089877/file.strm?KodiId=10748&Name=5x15+-+Channel+5.mkv&Id=5089877:
    Line 11503: 2019-10-04 22:13:45.652 T:4968   ERROR: XFILE::CFileCache::Open - failed to open source <http://127.0.0.1:57578/emby/kodi/tvshows/153643/5089877/file.strm?KodiId=10748&Name=5x15+-+Channel+5.mkv&Id=5089877>
    Line 11523: 2019-10-04 22:13:54.740 T:4968   ERROR: CCurlFile::Open failed with code 0 for http://127.0.0.1:57578/emby/kodi/tvshows/153643/5089877/file.strm?KodiId=10748&Name=5x15+-+Channel+5.mkv&Id=5089877:
    Line 11524: 2019-10-04 22:13:55.176 T:4968   ERROR: XFILE::CHTTPDirectory::GetDirectory - Unable to get http directory (http://127.0.0.1:57578/emby/kodi/tvshows/153643/5089877/file.strm?KodiId=10748&Name=5x15+-+Channel+5.mkv&Id=5089877)
    Line 11525: 2019-10-04 22:13:56.664 T:4968   ERROR: XFILE::CDirectory::GetDirectory - Error getting http://127.0.0.1:57578/emby/kodi/tvshows/153643/5089877/file.strm?KodiId=10748&Name=5x15+-+Channel+5.mkv&Id=5089877
    Line 11602: 2019-10-04 22:14:50.363 T:9112   ERROR: Playlist Player: skipping unplayable item: 0, path [http://127.0.0.1:57578/emby/kodi/tvshows/153643/5089877/file.strm?KodiId=10748&Name=5x15+-+Channel+5.mkv&Id=5089877]

Most of these actually worked, ignore the skipping unplayable item as that is not a fail from what I can see

    Line 11502: 2019-10-04 22:13:45.650 T:4968   ERROR: CCurlFile::Open failed with code 0 for http://127.0.0.1:57578/emby/kodi/tvshows/153643/5089877/file.strm?KodiId=10748&Name=5x15+-+Channel+5.mkv&Id=5089877:
    Line 11523: 2019-10-04 22:13:54.740 T:4968   ERROR: CCurlFile::Open failed with code 0 for http://127.0.0.1:57578/emby/kodi/tvshows/153643/5089877/file.strm?KodiId=10748&Name=5x15+-+Channel+5.mkv&Id=5089877:

These are the actual fails I think.

 

Can you confirm you had a bunch (11 or so) work and then two fails in the first post log?

Link to comment
Share on other sites
chjohans

chjohans   32

Posted
  • Author
Posted

He brings up a good point though, whether or not it's related to subtitles or resuming, can you try to find common factors? How is it playing through the server?

Yes it's indeed a good point, I've had problems with playback of titles with subtitles in the past, especially with the iOS client. But I've done some pretty extensive testing of this issue the past few months and I've found no pattern, playback will fail about 75% of the attempts, and if the video file has subtitles or not made no difference to that. But very often, playback will actually start at the same moment I get the error message in Kodi, problem is when I close that error message box playback stops again.

 

Playback of the same video files on any other Emby client (iOS, Roku, Chrome, Emby Theatre) works just fine with no issues whatsoever.

 

I have 6 Kodi installation with this issue, 3 using one Emby server and 3 using another, pretty much identical setup. A common factor would be that all the Kodi clients was upgraded from Kodi 17 to Kodi 18. So I tried a clean install of Kodi 18 on a Windows test client, but it had the exact same playback issue. 4 of the clients are Windows based, 2 are RPI's running the latest OSMC, that makes no difference they all have the same playback error.

 

So it's not like I posted here "crying for help" without doing some pretty extensive testing first but right now I'm pretty much stuck.

 

So to not annoy my extended family too much (who are using these boxes) I uninstalled Emby for Kodi from most of the clients and they are playing directly from my NAS boxes the "old fashioned Kodi way". Problem is those remote clients that depend on remote access to my Emby server, I can't very well uninstall Emby for Kodi on those.

 

Network issues are pretty much ruled out too since it happens on two physically different locations, both with local and remote clients.

 

At this point I'm out of ideas except that it must be a bug in Emby for Kodi itself, hence my plea that someone looks into that. But when the only developer maintaining it is "missing in action" it seems like a rather uphill path to get this fixed. Especially since I seem to be expected to fix this myself as this is a "community project" and I'm a part of that "community". That would be a rather daunting task for me since the last time I did any serious coding was too long ago and on a very different platform. :)

Link to comment
Share on other sites
chjohans

chjohans   32

Posted
  • Author
Posted (edited)

From you first post log

    Line 1166: 2019-10-03 21:41:22.950 T:9112   ERROR: Playlist Player: skipping unplayable item: 0, path [http://127.0.0.1:57578/emby/kodi/tvshows/153643/4736927/file.strm?KodiId=10745&Name=5x12+-+Ner+Tamid.mkv&Id=4736927]
    Line 2760: 2019-10-03 23:22:25.821 T:9112   ERROR: Playlist Player: skipping unplayable item: 0, path [http://127.0.0.1:57578/emby/kodi/tvshows/153643/4736927/file.strm?KodiId=10745&Name=5x12+-+Ner+Tamid.mkv&Id=4736927]
    Line 5229: 2019-10-04 13:03:14.961 T:9112   ERROR: Playlist Player: skipping unplayable item: 0, path [http://127.0.0.1:57578/emby/kodi/tvshows/153643/4789582/file.strm?KodiId=10746&Name=5x13+-+Leave+What+You+Don%27t.mkv&Id=4789582]
    Line 7416: 2019-10-04 17:11:28.351 T:9112   ERROR: Playlist Player: skipping unplayable item: 0, path [http://127.0.0.1:57578/emby/kodi/tvshows/153643/4789582/file.strm?KodiId=10746&Name=5x13+-+Leave+What+You+Don%27t.mkv&Id=4789582]
    Line 7622: 2019-10-04 17:12:21.150 T:9112   ERROR: Playlist Player: skipping unplayable item: 0, path [http://127.0.0.1:57578/emby/kodi/tvshows/153643/4789582/file.strm?KodiId=10746&Name=5x13+-+Leave+What+You+Don%27t.mkv&Id=4789582]
    Line 7801: 2019-10-04 17:13:12.327 T:9112   ERROR: Playlist Player: skipping unplayable item: 0, path [http://127.0.0.1:57578/emby/kodi/tvshows/153643/4789582/file.strm?KodiId=10746&Name=5x13+-+Leave+What+You+Don%27t.mkv&Id=4789582]
    Line 7922: 2019-10-04 17:13:40.290 T:9112   ERROR: Playlist Player: skipping unplayable item: 0, path [http://127.0.0.1:57578/emby/kodi/tvshows/153643/4789582/file.strm?KodiId=10746&Name=5x13+-+Leave+What+You+Don%27t.mkv&Id=4789582]
    Line 8484: 2019-10-04 17:18:27.479 T:9112   ERROR: Playlist Player: skipping unplayable item: 0, path [http://127.0.0.1:57578/emby/kodi/tvshows/153643/5089876/file.strm?KodiId=10747&Name=5x14+-+Today+and+Tomorrow.mkv&Id=5089876]
    Line 11018: 2019-10-04 22:10:46.851 T:9112   ERROR: Playlist Player: skipping unplayable item: 0, path [http://127.0.0.1:57578/emby/kodi/tvshows/153643/5089877/file.strm?KodiId=10748&Name=5x15+-+Channel+5.mkv&Id=5089877]
    Line 11170: 2019-10-04 22:12:40.116 T:9112   ERROR: Playlist Player: skipping unplayable item: 0, path [http://127.0.0.1:57578/emby/kodi/tvshows/153643/5089877/file.strm?KodiId=10748&Name=5x15+-+Channel+5.mkv&Id=5089877]
    Line 11399: 2019-10-04 22:13:22.718 T:9112   ERROR: Playlist Player: skipping unplayable item: 0, path [http://127.0.0.1:57578/emby/kodi/tvshows/153643/5089877/file.strm?KodiId=10748&Name=5x15+-+Channel+5.mkv&Id=5089877]
    Line 11502: 2019-10-04 22:13:45.650 T:4968   ERROR: CCurlFile::Open failed with code 0 for http://127.0.0.1:57578/emby/kodi/tvshows/153643/5089877/file.strm?KodiId=10748&Name=5x15+-+Channel+5.mkv&Id=5089877:
    Line 11503: 2019-10-04 22:13:45.652 T:4968   ERROR: XFILE::CFileCache::Open - failed to open source <http://127.0.0.1:57578/emby/kodi/tvshows/153643/5089877/file.strm?KodiId=10748&Name=5x15+-+Channel+5.mkv&Id=5089877>
    Line 11523: 2019-10-04 22:13:54.740 T:4968   ERROR: CCurlFile::Open failed with code 0 for http://127.0.0.1:57578/emby/kodi/tvshows/153643/5089877/file.strm?KodiId=10748&Name=5x15+-+Channel+5.mkv&Id=5089877:
    Line 11524: 2019-10-04 22:13:55.176 T:4968   ERROR: XFILE::CHTTPDirectory::GetDirectory - Unable to get http directory (http://127.0.0.1:57578/emby/kodi/tvshows/153643/5089877/file.strm?KodiId=10748&Name=5x15+-+Channel+5.mkv&Id=5089877)
    Line 11525: 2019-10-04 22:13:56.664 T:4968   ERROR: XFILE::CDirectory::GetDirectory - Error getting http://127.0.0.1:57578/emby/kodi/tvshows/153643/5089877/file.strm?KodiId=10748&Name=5x15+-+Channel+5.mkv&Id=5089877
    Line 11602: 2019-10-04 22:14:50.363 T:9112   ERROR: Playlist Player: skipping unplayable item: 0, path [http://127.0.0.1:57578/emby/kodi/tvshows/153643/5089877/file.strm?KodiId=10748&Name=5x15+-+Channel+5.mkv&Id=5089877]

Most of these actually worked, ignore the skipping unplayable item as that is not a fail from what I can see

    Line 11502: 2019-10-04 22:13:45.650 T:4968   ERROR: CCurlFile::Open failed with code 0 for http://127.0.0.1:57578/emby/kodi/tvshows/153643/5089877/file.strm?KodiId=10748&Name=5x15+-+Channel+5.mkv&Id=5089877:
    Line 11523: 2019-10-04 22:13:54.740 T:4968   ERROR: CCurlFile::Open failed with code 0 for http://127.0.0.1:57578/emby/kodi/tvshows/153643/5089877/file.strm?KodiId=10748&Name=5x15+-+Channel+5.mkv&Id=5089877:

These are the actual fails I think.

 

Can you confirm you had a bunch (11 or so) work and then two fails in the first post log?

 

Thanks for trying to help, much appreciated! :)

 

I can't be 100% sure since it's a while ago, but I wrote that I tried to restart the same stream 4 times in my post so it must have been 4 times.

 

But yes a few playbacks worked before the eror, but I'm not sure if it was as many as 11.

 

Those "unplayable items" should also play just fine, and in fact the same file that you list as playback error above ("5x15 - Channel 5.mkv" - S05E15 of "Fear the Walking Dead") is also listed as unplayable in the log above.

 

Just to confirm I did play all the files through the Chrome client just now and they all played just fine, including those listed as "unplayable" above.

Edited by chjohans
Link to comment
Share on other sites
TeamB

TeamB   2352

Posted
Posted (edited)

I am reasonable sure the issue is with the local http server the E4K add-on uses to work around the new Kodi 18 limitations about adding plugin links directly into the Kodi DB.

From the logs it looks like at some point the local http server can not be contacted by the local Kodi player.

The way this works is the internal db has a link to the local http server and the local server returns a strm file with the location of the actual file. However in the above log some of the local connections are failing.

I don't know why they are failing but on some systems and in your case it is happening a lot and on a lot of different systems.

One option for you if you really want to use E4K add-on is to try dynamic mode that skips the local Kodi DB, this might work better for you.

The other option is use DLNA or EmbyCon on Kodi.

Or just drop Kodi from your clients list and use one of the other Emby clients.

Edited by TeamB
  • Like 1
Link to comment
Share on other sites
chjohans

chjohans   32

Posted
  • Author
Posted

Is it direct playing through Emby Server? Or is Kodi playing directly to the file system?

 

Yes, on the same LAN as the Emby server too. I have remote clients too but the local ones fail as well. So let's keep it simple and concentrate on local playback, yes that is failing too.

Link to comment
Share on other sites
chjohans

chjohans   32

Posted
  • Author
Posted

I am reasonable sure the issue is with the local http server the E4K add-on uses to work around the new Kodi 18 limitations about adding plugin links directly into the Kodi DB.

 

From the logs it looks like at some point the local http server can not be contacted by the local Kodi player.

 

The way this works is the internal db has a link to the local http server and the local server returns a strm file with the location of the actual file. However in the above log some of the local connections are failing.

 

I don't know why they are failing but on some systems and in your case it is happening a lot and on a lot of different systems.

 

One option for you if you really want to use E4K add-on is to try dynamic mode that skips the local Kodi DB, this might work better for you.

 

The other option is use DLNA or EmbyCon on Kodi.

 

Or just drop Kodi from your clients list and use one of the other Emby clients.

 

Thanks, sounds like a reasonable explanation. Are you saying this is "unfixable", or would eg the developer of this addon be able to fix this?

 

Will look into the "dynamic mode" of E4K, I actually didn't know about that option so might give that a try. Or just skip Emby altogether, not using the local Kodi library has other implications - other addons depends on the local DB to do what they are supposed to do.

 

From what you write it sounds like Emby for Kodi is broken, with little or no hope to ever get fixed. Since I depend more on Kodi than on Emby I might have to skip Emby instead.

 

Or maybe use Emby for Kodi just to populate and keep the Kodi library in sync, and then use EmbyCon for playback. Then again Luke mentioned something you had discovered re having both installed at the same time, do you think what I suggest will have unwanted side effects?

Link to comment
Share on other sites
TeamB

TeamB   2352

Posted
Posted

Thanks, sounds like a reasonable explanation. Are you saying this is "unfixable", or would eg the developer of this addon be able to fix this?

 

Will look into the "dynamic mode" of E4K, I actually didn't know about that option so might give that a try. Or just skip Emby altogether, not using the local Kodi library has other implications - other addons depends on the local DB to do what they are supposed to do.

 

From what you write it sounds like Emby for Kodi is broken, with little or no hope to ever get fixed. Since I depend more on Kodi than on Emby I might have to skip Emby instead.

 

Or maybe use Emby for Kodi just to populate and keep the Kodi library in sync, and then use EmbyCon for playback. Then again Luke mentioned something you had discovered re having both installed at the same time, do you think what I suggest will have unwanted side effects?

Emby for Kodi is not broken in that it works most of the time for most people. For some reason it does not like your environment or setup.

 

You mention when it stops you need to restart Kodi to get it working again, or others have mentioned this, from this description it sounds like the internal HTTP server either locks, crashes or stops responding. This could be due to bugs in the code of the add-on or bugs in the code of the python HTTP server. Since this is running on the same server as the client it is local and is working some of the time it sounds like the HTTP server for whatever reason stops serving.

 

Could this be fixed, yeah potentially, if the root cause can be identified, the main problem is the people that can fix this can not reproduce it. It is very hard to fix an issue you can not actually see.

 

On running both add-ons side by side I dont know, I tested them a while ago and they worked fine next to each other but there was a recent report that said EmbyCon did not work with E4K installed. I have not tested this recently.

 

Yeah if you need the local Kodi DB fully populated with paths etc your only option is using Emby for Kodi or using Kodi the old way and pointing it directly at your files.

Link to comment
Share on other sites
chjohans

chjohans   32

Posted
  • Author
Posted

Ok, thanks again. I will test EmbyCon side-by-side with Emby for Kodi.

 

Yes, when playback starts to fail I have to restart Kodi again to get it to work. But the strange thing is, most of the time playback actually starts at the same time the error message that playback failed is shown. And when I close that message box playback is stopped. Based on this I had guessed it might be some sort of timing/timeout issue.

 

If your theory is correct, eg that the local web server for whatever reason stops serving, would playback at all be able to start like I describe above? In other words, what is the local web server being used for and how does it affect or interact with the playback of media files?

 

Do you think "Native" vs "Direct path" playback mode make any difference?

 

Then about this "dynamic" mode, I can't find any option to enable that. Is it something I would chose when I first install/configure Emby for Kodi? And if I understood correctly not only does this mode not use the local database for playback, but it's not populating the local database at all, right? If all this is correct, it pretty much sounds like EmbyCon, so what's the difference between the two then? And when using Emby in dynamic mode no views or widgets that would use the local DB would work, right?

 

Thanks again :)

Link to comment
Share on other sites
TeamB

TeamB   2352

Posted
Posted

I think if playback actually starts and the message pops up then playback is actually working, you are correct this throws a little bit of doubt on the fact the local http server is not working at all.

 

I think Native should help, if you switch to native make sure you do a DB refresh.

 

I think dynamic mode is controlled per library in the settings somewhere.

Link to comment
Share on other sites
horstepipe

horstepipe   356

Posted
Posted

From the logs it looks like at some point the local http server can not be contacted by the local Kodi player.

 

 

Could you please tell me the lines in the log about that behavior?

Link to comment
Share on other sites
fr0z3n

fr0z3n   20

Posted
Posted

Not sure if it helps but when the issue happens it is either:

 

issue 1 (no playback with error popup) or

 

issue 2 (background playback with error pop up and as soon as you click OK playback stops)

 

For both these issues I don't always have to reboot to fix.

 

Most times when issue 1 or 2 happens it will happen a few times in a row then on a subsequent playback attempt it will work. Just gotta persist.

 

But if I reboot after either issue 1 or 2 happens, the first playback attempt after a reboot works often.

Link to comment
Share on other sites
TeamB

TeamB   2352

Posted
Posted

Thanks

But there can’t be no relation to whether the Kodi webserver is enabled or disabled?

 

The HTTP server the add-on uses is not the internal Kodi one, they are not related.

 

Not sure if it helps but when the issue happens it is either:

 

issue 1 (no playback with error popup) or

 

issue 2 (background playback with error pop up and as soon as you click OK playback stops)

 

For both these issues I don't always have to reboot to fix.

 

Most times when issue 1 or 2 happens it will happen a few times in a row then on a subsequent playback attempt it will work. Just gotta persist.

 

But if I reboot after either issue 1 or 2 happens, the first playback attempt after a reboot works often.

 

Ok so it sounds like the internal http server is still working, and playback starts, I have no idea what the errors mean then or if they are even related to the issue you are seeing.

I dont know enough about the E4K add-on so not sure I can give any further insight.

 

I specifically wrote the EmbyCon add-on to be simpler and easier to write and maintain as I was not happy with the DB sync and hoops you had to jump though in code to get all that working.

 

Sorry guys, my only suggestion would be try to find something that works for you.

Link to comment
Share on other sites
horstepipe

horstepipe   356

Posted
Posted

The HTTP server the add-on uses is not the internal Kodi one, they are not related.

 

You’re absolutely sure about that? I’m asking because on startup wizard of E4K it suggests to enable Kodi’s webserver to allow artwork caching.

Link to comment
Share on other sites
chjohans

chjohans   32

Posted
  • Author
Posted

I actually haven't had the time to try this yet as I'm travelling this week and the next. So can only try this in about a week when I'm back home. Will post my findings here.

Link to comment
Share on other sites
rbronco21

rbronco21   11

Posted
Posted

It used to happen once and then the movie would always play on the second try. I haven't noticed the issue for the last few days.

  • Like 1
Link to comment
Share on other sites
Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...