Jump to content

embyforkodi (next-gen) 10.X.X support

quickmic

By quickmic
in Emby For Kodi Next Gen

 Share
Go to solution Solved by quickmic,

Recommended Posts

quickmic

quickmic 1703

Posted
  • Author
Posted (edited)
3 hours ago, DarWun said:

Stupid question. But how do I force an update of the sources.xml file? I've done testing over the last few days that added and removed path locations from the libraries. But the source.xml file is dated three days prior. It doesn't seem to get updated as I make changes. The optional paths aren't listed in the file even though they are set in the library.

Edited to add: I deleted the sources.xml file expecting that Kodi would recreate it on the next startup. It did not. I then did an E4K database reset. After doing that and adding the libraries, the sources.xml file was created. But what I'm seeing in it does not reflect path locations set for my libraries in Emby. the "nfs:..." optional location I added for the movie library is not shown at all.

image.png.154ecbdb04297a9640fd120b86899068.png 

 

kodi.log 7.25 MB · 0 downloads

Your observation is absolutely correct. The plugin doesn't delete the sources, there is no need for. It just adds additional records if they don't exist and only on factory resets.

Additional paths are usually used for playing not Emby related content -> native Kodi content. If I would rebuild the sources from scratch, people will (and have) complained about that.

I still need the "invalid" sources.xml for review (including your custom records, braking the playback).

btw, I see an issue in you last uploaded kodi.log. I assume it's a log from stock .29 plugin? I'll check and fix it, seems to be related to transcoding.

Edited by quickmic
  • Like 1
quickmic

quickmic 1703

Posted
  • Author
Posted

New PUBLIC TESTING version available 10.0.30:

Delta changelog 10.0.29 -> 10.0.30

fix transcoding playback

alienchen

alienchen 1

Posted
Posted

I hope to limit the length of continue watching.

Continue watching sync takes several seconds

DarWun

DarWun 349

Posted
Posted (edited)
17 hours ago, quickmic said:

I still need the "invalid" sources.xml for review (including your custom records, braking the playback).

btw, I see an issue in you last uploaded kodi.log. I assume it's a log from stock .29 plugin? I'll check and fix it, seems to be related to transcoding.

Thanks for explaining that. The image of the sources.xml file I provided in my last post is from the broken playback attempt. I was confused by the fact that I wasn't actually seeing a "nfs"\\..." source item in the sources.xml file even though it was specified for the library of the media file that failed to play. I'll provide the actual log when I get home from work later tonight.

As to your quest about which version of the plugin the last kodi.log I provided is linked to. You are correct. It is a log from the stock E4K .29 plugin. I'll update to .30 before doing any additional testing.

Edited by DarWun
quickmic

quickmic 1703

Posted
  • Author
Posted
On 6/9/2024 at 6:39 PM, Kyrunner said:

I think so up next was working fine Pryor   To.  .29  only way it works now is if I use dynamic which I have never had to.

I checked, works fine on my setup. Can you please confirm it's not working.

quickmic

quickmic 1703

Posted
  • Author
Posted
13 hours ago, alienchen said:

I hope to limit the length of continue watching.

Continue watching sync takes several seconds

It's instant on my setup. Dynamic and synced. Please elaborate.

quickmic

quickmic 1703

Posted
  • Author
Posted (edited)

10.0.30 is now tagged as beta

Edited by quickmic
quickmic

quickmic 1703

Posted
  • Author
Posted (edited)

fyi

10.0.30 has a connection issue, when using suburls: "http://blabla/suburl/emby"

I'll fix it in next version.

thx @toomanynightsfor testing.

Edited by quickmic
DarWun

DarWun 349

Posted
Posted (edited)
On 6/12/2024 at 11:36 PM, quickmic said:

I still need the "invalid" sources.xml for review (including your custom records, braking the playback).

btw, I see an issue in you last uploaded kodi.log. I assume it's a log from stock .29 plugin? I'll check and fix it, seems to be related to transcoding.

"Invalid" sources.xml file attached (E4K .30). Debug Kodi.log attached from playback attempt (She-Hulk - S01E01).

Library path location settings:

image.png.7ad5955467a1786ce6ed44e317feb013.png

sources.xml kodi.log

Edited by DarWun
quickmic

quickmic 1703

Posted
  • Author
Posted (edited)
11 hours ago, DarWun said:

"Invalid" sources.xml file attached (E4K .30). Debug Kodi.log attached from playback attempt (She-Hulk - S01E01).

Library path location settings:

image.png.7ad5955467a1786ce6ed44e317feb013.png

sources.xml 1.16 kB · 0 downloads kodi.log 7.82 MB · 0 downloads

 

I used your sources.xml and a similar library. Still no issue on my setup, playback is flawless.

 

 

nfs2.png

 

Also I performed a test on windows, everything fine.

Another test with a TV-Shows, also fine.

I compared my (working) Kodi log with yours line by line. The only difference, you get timeouts while mine is perfect.

At the moment I have no idea what's wrong/different on your setup and I cannot reproduce it.

Also no idea why this should only happen on > .25

As mentioned, the next step would be testing with your server. I'm running out of options here on my setup.

 

btw, I review again your emby server log (the .27 part only): 

2024-06-07 17:41:36.001 Info Server: http/1.1 Response 200 to host2. Time: 2ms. POST http://192.168.0.13:8096/emby/Sync/Data?X-Emby-Client=Emby for Windows&X-Emby-Device-Name=DARWUN-PC&X-Emby-Device-Id=YjVTdvDbFxfYvfGIbmhC7BONQNxmnOSBrFWIjGZlvU&X-Emby-Client-Version=1.1.566.0&X-Emby-Token=x_secret4_x&reqformat=json
2024-06-07 17:44:27.417 Info Server: http/1.1 POST http://192.168.0.13:8096/Sessions/Capabilities/Full. Source Ip: host1, UserAgent: Emby for Kodi Next Gen/10.0.27
2024-06-07 17:44:27.436 Info Server: http/1.1 Response 204 to host1. Time: 18ms. POST http://192.168.0.13:8096/Sessions/Capabilities/Full
2024-06-07 17:44:28.060 Info CoverArt: image enhance of Movies took 0.000 seconds.
2024-06-07 17:44:28.762 Info CoverArt: image enhance of Collections took 0.000 seconds.
2024-06-07 17:44:29.434 Info CoverArt: image enhance of TV took 0.000 seconds.
2024-06-07 17:44:30.070 Info CoverArt: image enhance of Music took 0.000 seconds.
2024-06-07 17:46:21.568 Info App: Saving playlist file /volume1/Shares/Music/Playlists/HDHomeRun Digital Antenna.wpl
2024-06-07 17:46:36.011 Info Server: http/1.1 POST http://192.168.0.13:8096/Sessions/Capabilities/Full. Source Ip: host1, UserAgent: Emby for Kodi Next Gen/10.0.27
2024-06-07 17:46:36.012 Info Server: http/1.1 Response 204 to host1. Time: 1ms. POST http://192.168.0.13:8096/Sessions/Capabilities/Full
2024-06-07 17:46:36.699 Info CoverArt: image enhance of Movies took 0.000 seconds.
2024-06-07 17:46:37.337 Info CoverArt: image enhance of Collections took 0.000 seconds.
2024-06-07 17:46:38.325 Info CoverArt: image enhance of TV took 0.000 seconds.
2024-06-07 17:46:38.941 Info CoverArt: image enhance of Music took 0.000 seconds.
2024-06-07 17:51:38.914 Info Server: http/1.1 HEAD http://192.168.0.13:8096/videos/791666/stream. Source Ip: host1, Connection=keep-alive, Host=host3, User-Agent=Emby for Kodi Next Gen/10.0.27, Accept-Charset=utf-8, Accept-Encoding=gzip, Authorization=Emby Client="Emby for Kodi Next Gen", Device="Kodi%20%28LibreELEC%29", DeviceId="a5782669-e4a5-448c-80fa-8c12a10e9011", Version="10.0.27", Emby UserId="830506f670cb492593df1dc39c976875", Content-Type=application/json; charset=utf-8, Content-Length=121, X-Emby-Token=x_secret3_x
2024-06-07 17:51:38.925 Info Server: http/1.1 Response 200 to host1. Time: 11ms. HEAD http://192.168.0.13:8096/videos/791666/stream
2024-06-07 17:54:14.036 Info Server: http/1.1 POST http://192.168.0.13:8096/Sessions/Capabilities/Full. Source Ip: host1, UserAgent: Emby for Kodi Next Gen/10.0.27
2024-06-07 17:54:14.038 Info Server: http/1.1 Response 204 to host1. Time: 1ms. POST http://192.168.0.13:8096/Sessions/Capabilities/Full
2024-06-07 17:54:57.170 Info Server: http/1.1 POST http://192.168.0.13:8096/emby/Sessions/a079a66674632022c818826ce74723ba/Playing?ItemIds=791666&PlayCommand=PlayNow&X-Emby-Client=Emby Web&X-Emby-Device-Name=Chrome Windows&X-Emby-Device-Id=84499b7f-450a-4b5d-9bf6-cf655ec509c6&X-Emby-Client-Version=4.9.0.23&X-Emby-Token=x_secret1_x&X-Emby-Language=en-us. Source Ip: host2, UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36 Edg/125.0.0.0
2024-06-07 17:54:57.210 Info Server: http/1.1 Response 204 to host2. Time: 40ms. POST http://192.168.0.13:8096/emby/Sessions/a079a66674632022c818826ce74723ba/Playing?ItemIds=791666&PlayCommand=PlayNow&X-Emby-Client=Emby Web&X-Emby-Device-Name=Chrome Windows&X-Emby-Device-Id=84499b7f-450a-4b5d-9bf6-cf655ec509c6&X-Emby-Client-Version=4.9.0.23&X-Emby-Token=x_secret1_x&X-Emby-Language=en-us
2024-06-07 17:54:57.380 Info Server: http/1.1 HEAD http://192.168.0.13:8096/videos/791666/stream. Source Ip: host1, Connection=keep-alive, Host=host3, User-Agent=Emby for Kodi Next Gen/10.0.27, Accept-Charset=utf-8, Accept-Encoding=gzip, Authorization=Emby Client="Emby for Kodi Next Gen", Device="Kodi%20%28LibreELEC%29", DeviceId="a5782669-e4a5-448c-80fa-8c12a10e9011", Version="10.0.27", Emby UserId="830506f670cb492593df1dc39c976875", Content-Type=application/json; charset=utf-8, Content-Length=121, X-Emby-Token=x_secret3_x
2024-06-07 17:54:57.383 Info Server: http/1.1 Response 200 to host1. Time: 3ms. HEAD http://192.168.0.13:8096/videos/791666/stream
2024-06-07 17:57:04.702 Info Server: http/1.1 POST http://192.168.0.13:8096/Sessions/Capabilities/Full. Source Ip: host1, UserAgent: Emby for Kodi Next Gen/10.0.27
2024-06-07 17:57:04.704 Info Server: http/1.1 Response 204 to host1. Time: 1ms. POST http://192.168.0.13:8096/Sessions/Capabilities/Full
2024-06-07 17:57:52.001 Info Server: http/1.1 HEAD http://192.168.0.13:8096/videos/982864/stream. Source Ip: host1, Connection=keep-alive, Host=host3, User-Agent=Emby for Kodi Next Gen/10.0.27, Accept-Charset=utf-8, Accept-Encoding=gzip, Authorization=Emby Client="Emby for Kodi Next Gen", Device="Kodi%20%28LibreELEC%29", DeviceId="a5782669-e4a5-448c-80fa-8c12a10e9011", Version="10.0.27", Emby UserId="830506f670cb492593df1dc39c976875", Content-Type=application/json; charset=utf-8, Content-Length=121, X-Emby-Token=x_secret3_x
2024-06-07 17:57:52.003 Info Server: http/1.1 Response 200 to host1. Time: 3ms. HEAD http://192.168.0.13:8096/videos/982864/stream
2024-06-07 17:59:39.926 Info Server: http/1.1 POST http://192.168.0.13:8096/emby/Sessions/a079a66674632022c818826ce74723ba/Command?X-Emby-Client=Emby Web&X-Emby-Device-Name=Chrome Windows&X-Emby-Device-Id=84499b7f-450a-4b5d-9bf6-cf655ec509c6&X-Emby-Client-Version=4.9.0.23&X-Emby-Token=x_secret1_x&X-Emby-Language=en-us&reqformat=json. Source Ip: host2, UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36 Edg/125.0.0.0
2024-06-07 17:59:39.950 Info Server: http/1.1 Response 204 to host2. Time: 24ms. POST http://192.168.0.13:8096/emby/Sessions/a079a66674632022c818826ce74723ba/Command?X-Emby-Client=Emby Web&X-Emby-Device-Name=Chrome Windows&X-Emby-Device-Id=84499b7f-450a-4b5d-9bf6-cf655ec509c6&X-Emby-Client-Version=4.9.0.23&X-Emby-Token=x_secret1_x&X-Emby-Language=en-us&reqformat=json

Beside the DNS names (which sounds kind of odd) -> host1, host2 etc. did you really send remote commands to the via WebUi -> "PlayNow"

EDIT:

I found one http issue, not sure if related to your problem. I'll try to fix it in next version.

 

 

 

Edited by quickmic
  • Like 1
quickmic

quickmic 1703

Posted
  • Author
Posted (edited)

New BETA version available 10.0.31:

Delta changelog 10.0.30 -> 10.0.31

fix connection issues with SubUrl connection strings (also fixes websocket issues behind proxies)
fix wrong subtitle index
fix http head requests

Comment:

resync is required to fix subtitle issues

@DarWunThis version might fixes the playback issue you have. If so, remote content was affected. The HEAD requests had a bug and its used to verify remote content.

Edited by quickmic
  • Thanks 2
DarWun

DarWun 349

Posted
Posted (edited)
6 hours ago, quickmic said:

New BETA version available 10.0.31:

@DarWunThis version might fixes the playback issue you have. If so, remote content was affected. The HEAD requests had a bug and its used to verify remote content.

It did indeed fix the issue I was having. Thanks @quickmic!

Let me know if you want me to do any additional testing. I'm not sure why Emby is considering my content as "remote". It is all on my local network devices with remote access completely disabled (or so i thought).

Edited by DarWun
  • Like 1
quickmic

quickmic 1703

Posted
  • Author
Posted

fyi

I found a bug in realtime library updates. In some scenarios the update is infinitely paused. Will be fixed in next version.

OpenHT

OpenHT 8

Posted
Posted (edited)

Hi!

There seems to be a DNS lookup issue after you rewrote the "http communication with the emby server" class (v10.0.31) :

Currently, every single http(s) request to the emby server also does a DNS/hostname lookup of the emby server. This means that an initial sync will lookup the hostname of the emby server several hundred or even thousand times. Also, if you watch something every time progress update (~5sec) will further increase the total DNS requests.

 

That's not good and depending on OS and DNS configuration could potentially slow down the initial sync significantly or in the worst case your IP could be blocked when using an external DNS provider or something like pi-hole directly. Thanks!

Edited by OpenHT
quickmic

quickmic 1703

Posted
  • Author
Posted
24 minutes ago, OpenHT said:

Hi!

There seems to be a DNS lookup issue after you rewrote the "http communication with the emby server" class (v10.0.31) :

Currently, every single http(s) request to the emby server also does a DNS/hostname lookup of the emby server. This means that an initial sync will lookup the hostname of the emby server several hundred or even thousand times. Also, if you watch something every time progress update (~5sec) will further increase the total DNS requests.

 

That's not good and depending on OS and DNS configuration could potentially slow down the initial sync significantly or in the worst case your IP could be blocked when using an external DNS provider or something like pi-hole directly. Thanks!

Ok, I'll check. Actually keep-alive is set in HTTP headers and Emby respects that (I tested that very carefully). Especially the init sync re-uses the connection.

Do you use an proxy? I changed my apache settings "KeepAliveTimeout=15" due to ping is send every 10 seconds and drops the connection by apache (default is 5 seconds). I could also increase the ping rate.

This was also an "issue" in older versions, but I never realized it as I was not digging into that matter. However, just a performance issue in this case, doesn't explain the DNS requests.

 

supermood

supermood 71

Posted
Posted

good day. I guess it's not the usual behavior that I have to restart every time I watched something and then want to watch something else? after reboot it works great. but pressing something else I says playback failed. 

ive turned off sync while playback (as recommended) and I think I'm 100% on standard settings 

should I send a log? here? mans thanks and best,

 

OpenHT

OpenHT 8

Posted
Posted
2 hours ago, quickmic said:

Do you use an proxy? I changed my apache settings "KeepAliveTimeout=15" due to ping is send every 10 seconds and drops the connection by apache (default is 5 seconds). I could also increase the ping rate.

This was also an "issue" in older versions, but I never realized it as I was not digging into that matter. However, just a performance issue in this case, doesn't explain the DNS requests.

 

Yes, I'm using a NGINX reverse proxy in front of my EMBY server but to be absolutely sure that it's not the proxy's fault I've setup a new instance which directly connects to the EMBY server on port 8096.

Result is the same, even without a proxy the initial sync does hundreds of EMBY server hostname lookups and so does every "ping" request: 

2024-06-17 22:07:34.277 T:501882   debug <general>: EMBY.emby.http: [ http ] Method: POST / Handler: System/Ping / Params: {} / Binary: True / ConnectionString:  / CloseConnection: False / RequestHeader: {}
2024-06-17 22:07:34.277 T:501882   debug <general>: EMBY.emby.http: Socket MAIN closed
2024-06-17 22:07:34.277 T:501882   debug <general>: Emby.helper.utils: get_url_info: ConnectionString='http://emby.xxx.xxx:8096/' Scheme='http' Hostname='emby.xxx.xxx' SubUrl='/' Port='8096'
2024-06-17 22:07:34.307 T:501882   debug <general>: EMBY.emby.http: Socket MAIN opened
2024-06-17 22:07:39.364 T:501886   debug <general>: EMBY.emby.emby: Websocket Pong received

2024-06-17 22:07:44.341 T:501882   debug <general>: EMBY.emby.http: [ http ] Method: POST / Handler: System/Ping / Params: {} / Binary: True / ConnectionString:  / CloseConnection: False / RequestHeader: {}
2024-06-17 22:07:44.341 T:501882   debug <general>: EMBY.emby.http: Socket MAIN closed
2024-06-17 22:07:44.341 T:501882   debug <general>: Emby.helper.utils: get_url_info: ConnectionString='http://emby.xxx.xxx:8096/' Scheme='http' Hostname='emby.xxx.xxx' SubUrl='/' Port='8096'
2024-06-17 22:07:44.373 T:501882   debug <general>: EMBY.emby.http: Socket MAIN opened
2024-06-17 22:07:49.429 T:501886   debug <general>: EMBY.emby.emby: Websocket Pong received

  

Jun 17 22:07:24 dnsmasq[102]: query[A] emby.xxx.xxx from 127.0.0.1
Jun 17 22:07:24 dnsmasq[102]: query[A] emby.xxx.xxx from 127.0.0.1
Jun 17 22:07:34 dnsmasq[102]: query[A] emby.xxx.xxx from 127.0.0.1
Jun 17 22:07:34 dnsmasq[102]: query[A] emby.xxx.xxx from 127.0.0.1
Jun 17 22:07:44 dnsmasq[102]: query[A] emby.xxx.xxx from 127.0.0.1
Jun 17 22:07:44 dnsmasq[102]: query[A] emby.xxx.xxx from 127.0.0.1
Jun 17 22:07:54 dnsmasq[102]: query[A] emby.xxx.xxx from 127.0.0.1
Jun 17 22:07:54 dnsmasq[102]: query[A] emby.xxx.xxx from 127.0.0.1
obituary

obituary 6

Posted
Posted 
2024-06-17 19:13:15.728 T:87712    info <general>: Skipped 1 duplicate messages..
2024-06-17 19:13:15.728 T:87712    info <general>: EMBY.hooks.webservice: No Emby servers found, timeout query
2024-06-17 19:13:20.432 T:19464    info <general>: Skipped 2 duplicate messages..
2024-06-17 19:13:20.432 T:19464   error <general>: EXCEPTION Thrown (PythonToCppException) : -->Python callback/script returned the following error<--
                                                    - NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS!
                                                   Error Type: <class 'IndexError'>
                                                   Error Contents: list index out of range
                                                   Traceback (most recent call last):
                                                     File "C:\Users\itsame\AppData\Roaming\Kodi\addons\plugin.service.emby-next-gen\dialogs\servermanual.py", line 55, in onClick
                                                       Scheme, Hostname, Port, SubUrl = utils.get_url_info(server)
                                                     File "C:\Users\itsame\AppData\Roaming\Kodi\addons\plugin.service.emby-next-gen\helper\utils.py", line 538, in get_url_info
                                                       Hostname = Temp[1][2:].split("?", 1)[0].split("/", 1)[0]
                                                   IndexError: list index out of range
                                                   -->End of Python script error report<--

I'm seeing this now on the latest version when trying to add a server. I'm adding using an IP address 192.168.2.160 with port 8096. I'm seeing this happen on all clients I've tried (Shield, windows text box).

obituary

obituary 6

Posted
Posted
23 minutes ago, obituary said: 
2024-06-17 19:13:15.728 T:87712    info <general>: Skipped 1 duplicate messages..
2024-06-17 19:13:15.728 T:87712    info <general>: EMBY.hooks.webservice: No Emby servers found, timeout query
2024-06-17 19:13:20.432 T:19464    info <general>: Skipped 2 duplicate messages..
2024-06-17 19:13:20.432 T:19464   error <general>: EXCEPTION Thrown (PythonToCppException) : -->Python callback/script returned the following error<--
                                                    - NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS!
                                                   Error Type: <class 'IndexError'>
                                                   Error Contents: list index out of range
                                                   Traceback (most recent call last):
                                                     File "C:\Users\itsame\AppData\Roaming\Kodi\addons\plugin.service.emby-next-gen\dialogs\servermanual.py", line 55, in onClick
                                                       Scheme, Hostname, Port, SubUrl = utils.get_url_info(server)
                                                     File "C:\Users\itsame\AppData\Roaming\Kodi\addons\plugin.service.emby-next-gen\helper\utils.py", line 538, in get_url_info
                                                       Hostname = Temp[1][2:].split("?", 1)[0].split("/", 1)[0]
                                                   IndexError: list index out of range
                                                   -->End of Python script error report<--

I'm seeing this now on the latest version when trying to add a server. I'm adding using an IP address 192.168.2.160 with port 8096. I'm seeing this happen on all clients I've tried (Shield, windows text box).

Apparently you are now expecting a protocol (http:// or https://) at the front of the connection string where previously you weren't.

You might want to take a hint from the port numbers like what was happening previously. I think the breaking change was in utils.py in this commit:

https://github.com/MediaBrowser/plugin.video.emby/commit/490ac0beb929e14f38bfded0b0d18ce87ab72c96

  • Like 1
quickmic

quickmic 1703

Posted
  • Author
Posted
51 minutes ago, obituary said:

Apparently you are now expecting a protocol (http:// or https://) at the front of the connection string where previously you weren't.

You might want to take a hint from the port numbers like what was happening previously. I think the breaking change was in utils.py in this commit:

https://github.com/MediaBrowser/plugin.video.emby/commit/490ac0beb929e14f38bfded0b0d18ce87ab72c96

Yes, correct. Actually I didn't though people not using the scheme prefix. However, I'll add a fix in next version.

quickmic

quickmic 1703

Posted
  • Author
Posted (edited)
7 hours ago, OpenHT said: 
Jun 17 22:07:24 dnsmasq[102]: query[A] emby.xxx.xxx from 127.0.0.1
Jun 17 22:07:24 dnsmasq[102]: query[A] emby.xxx.xxx from 127.0.0.1
Jun 17 22:07:34 dnsmasq[102]: query[A] emby.xxx.xxx from 127.0.0.1
Jun 17 22:07:34 dnsmasq[102]: query[A] emby.xxx.xxx from 127.0.0.1
Jun 17 22:07:44 dnsmasq[102]: query[A] emby.xxx.xxx from 127.0.0.1
Jun 17 22:07:44 dnsmasq[102]: query[A] emby.xxx.xxx from 127.0.0.1
Jun 17 22:07:54 dnsmasq[102]: query[A] emby.xxx.xxx from 127.0.0.1
Jun 17 22:07:54 dnsmasq[102]: query[A] emby.xxx.xxx from 127.0.0.1

Agreed, but that's what I mentioned. The interval of the DNS queries is 10 seconds (the ping interval), which means  the connection drops and is re-established every 10 seconds.

The 2 dns queries actually makes sense. One for the main connection and one for the async commands connection. As mentioned, I could lower the ping interval but I try to avoid that. Actually there are HTTP header parameters available to change the keep-alive timeouts, but never worked in my setup. I'll review it again...

So I think the DNS lookups are correct, but the connection shouldn't drop after 5 seconds.

 

Edited by quickmic
quickmic

quickmic 1703

Posted
  • Author
Posted (edited)
9 hours ago, supermood said:

good day. I guess it's not the usual behavior that I have to restart every time I watched something and then want to watch something else? after reboot it works great. but pressing something else I says playback failed. 

ive turned off sync while playback (as recommended) and I think I'm 100% on standard settings 

should I send a log? here? mans thanks and best,

 

Yes please, send me a kodi.log for review. btw, which version? 10.0.31?

Edited by quickmic
  • Like 1
monkeylove

monkeylove 11

Posted
Posted

Some new things I discovered:

When I use another app to add metadata (like TinyMediaManager) to newly added videos and set Emby to use only local metadata, I have to turn off the Emby server first before adding new videos, because Emby will still create .nfo files for them, and the addon in Kodi will pick them up. The result is that I see two entries for each of the newly added videos, one with no metadata yet and another with the metadata.

I experimented by updating from the stable version of the addon to the beta version, but after a while the setting option in the context menu of the addon disappeared. When I uninstalled the addon completely to start all over, after rebooting the player and reloading Kodi, the addon would still load, which means it's still there. It persisted even after I restored a backup (using the backup addon from the Kodi library). I ended up deleting the Kodi data from the apps settings to start with a fresh copy of Kodi, and then reconfigure Kodi and reinstall the Emby addon, etc.

 

Andy2k

Andy2k 75

Posted
Posted

Hi quickmic, there is another bug in the last E4K 10.x versions we had before iirc in the 8.x and 9.x tree. I use beta server 4.9.0.24.

 

Playing a local file from outside the the emby / Kodi database (non synced content) from eg a network share or local folder defined in souces.xml breaks progress updates on all synced contend i play after this till i restart Kodi.

 

 

quickmic

quickmic 1703

Posted
  • Author
Posted
1 hour ago, Andy2k said:

Hi quickmic, there is another bug in the last E4K 10.x versions we had before iirc in the 8.x and 9.x tree. I use beta server 4.9.0.24.

 

Playing a local file from outside the the emby / Kodi database (non synced content) from eg a network share or local folder defined in souces.xml breaks progress updates on all synced contend i play after this till i restart Kodi.

 

 

Tested and not reproducible with .31.

I need a log or exact instructions how to trigger the issue. Maybe both :)

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing
×
×
  • Create New...