Jump to content

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


quickmic

Recommended Posts

quickmic
42 minutes ago, Gepelmario said:

It only happens with 4k H265 Files files. I forgot to post this info, 

i tried many 4k files.

Same result

I assume, this is the input content. Have you transcoded to h264 or h265 (output)?

Actually, I tried several files, not able to reproduce the issue. Also I rule out srt subtiles involed due to its external type.

Currently, I'm in doubt that the issue is related to h265 or h264. Can you send me the emby-xxxxxxxxxx.db from Kodi. With this db file I could check the type of the subtitles.

Edited by quickmic
Link to comment
Share on other sites

Gepelmario
21 minutes ago, quickmic said:

I assume, this is the input content. Have you transcoded to h264 or h265 (output)?

Actually, I tried several files, not able to reproduce the issue. Also I rule out srt subtiles involed due external injected.

Currently, I'm in doubt that the issue is related to h265 or h264. Can you send me the emby-xxxxxxxxxx.db from Kodi. With this db file I could check the type of the subtitles.

You are correct 

H265 and H264  are the input contents. I transcoded to H264  as output.

I also tried some other H264 Files with srt subtitles. Same Error

The Subtiles are SRT Format before the MUX into the MKV Container. 

The Files are running great in chrome or the emby android tv app. 

 

 

Edited by Gepelmario
Link to comment
Share on other sites

2 hours ago, quickmic said:

I've send you a test version. I hope it fixes the issue. btw, it has nothing todo with recording. The problem is, the seasoninfo is empty on recorded files. Actually this could happen anywhere not only on recordings.

Now it's added season "0" if no info received by Emby server.

Season "0" is usually the indicator for "Specials" in TV shows.

Installed and the recordings do appear while Kodi is open but only one of them has the recording visible to play. The other three are still empty.

The one that is visible has more info in the tvshow.nfo than the other three recordings.

Should Emby create season 0 folders for recordings without season and episode info? The recordings are  now recording in the main tv show folder.

Capture_818.jpg

Capture_819.jpg

Capture_820.jpg

kodi.log tvshow Expeditie Robinson 2021_09_05_20_01_00.nfo tvshow Heel Holland Bakt Nog een keer 2021_09_05_20_30_00.nfo tvshow Kopen zonder kijken 2021_09_05_20_30_00.nfo tvshow Steenrijk, Straatarm België 2021_09_05_20_30_00.nfo

  • Like 1
Link to comment
Share on other sites

quickmic
32 minutes ago, heula said:

When I try to play the recordings that are available but are still recording than  Kodi crashes.

kodi.log 131.22 kB · 0 downloads kodi.old.log 109.32 kB · 0 downloads

I assume nfs://192.168.1.157/volume4/Mannenseries//Breaking Bad/Season 3/Breaking Bad - 03x09 - Kafkaesque.mkv or nfs://192.168.1.157/volume4/Recordings/Oh, Wat Een Jaar!/Oh, wat een jaar! 2021_09_04_20_00_00.ts was the file to be played. If so and Kodi crashes, there is nothing the plugin could do here. It's a native file, Kodi fully controls playback for native files.

btw, "old" content will not be fixed without a database resync. New recordings should have the season info 0 and should be visible. Probably there are additional info missing... I'll check the other issues tomorrow.

Edited by quickmic
Link to comment
Share on other sites

11 minutes ago, quickmic said:

I assume nfs://192.168.1.157/volume4/Mannenseries//Breaking Bad/Season 3/Breaking Bad - 03x09 - Kafkaesque.mkv or nfs://192.168.1.157/volume4/Recordings/Oh, Wat Een Jaar!/Oh, wat een jaar! 2021_09_04_20_00_00.ts was the file to be played. If so and Kodi crashes, there is nothing the plugin could do here. It's a native file, Kodi fully controls playback for native files.

btw, "old" content will not be fixed without a database resync. New recordings should have the season info 0 and should be visible. Probably there are additional info missing... I'll check the other issues tomorrow.

I posted the wrong Kodi log files. These are the correct ones.

kodi.log kodi.old.log kodi_crashlog-19.1 Git_20210508-85e05228b4-20210905-215129.dmp kodi_stacktrace-19.1 Git_20210508-85e05228b4-20210905-215129.txt

Link to comment
Share on other sites

LichenKing

Most recent test build broke ISO playback again.

  1. "Select Source Media" selection dialog appears more than once back to back when selecting item in Kodi.
  2. Playback always fails.
  • Like 1
Link to comment
Share on other sites

zanlation

When I enable cinema mode the play-back of videos fails. I am using the latest emby-next-gen. embruary skin and emby server versions.

Edited by zanlation
add skin
  • Like 1
Link to comment
Share on other sites

quickmic
6 hours ago, LichenKing said:

Most recent test build broke ISO playback again.

  1. "Select Source Media" selection dialog appears more than once back to back when selecting item in Kodi.
  2. Playback always fails.

Thanks for reporting, I'll fix it in next version.

Link to comment
Share on other sites

quickmic
1 hour ago, zanlation said:

When I enable cinema mode the play-back of videos fails. I am using the latest emby-next-gen. embruary skin and emby server versions.

Please send me a kodi.log

I performed a test and it's working fine here.

Link to comment
Share on other sites

zanlation
1 hour ago, quickmic said:

Please send me a kodi.log

I performed a test and it's working fine here.

I just sent you a message with a kodi.log file.

Link to comment
Share on other sites

zanlation
1 hour ago, zanlation said:

I just sent you a message with a kodi.log file.

If I enable cinema mode in the embraury skin options with an intro video, the movie will start playing. However its plays the intro twice - as its is also playing the server option too.

Link to comment
Share on other sites

quickmic
1 hour ago, zanlation said:

If I enable cinema mode in the embraury skin options with an intro video, the movie will start playing. However its plays the intro twice - as its is also playing the server option too.

Thanks for the log, I see there an issue reported but not sure if it's related to the cinnema mode problem.

Could be also based on you Emby Server settings.

1.jpg

Link to comment
Share on other sites

quickmic
2 hours ago, zanlation said:

I just sent you a message with a kodi.log file.

From your log:

CCurlFile::Open failed with code 0 for http://127.0.0.1:57578/mnt/b2e773f9-8493-42a3-91ef-bd9a7ef78fbf/INTROS/ShieldTV/NOONAN%20CINEMAS%20INTRO%204K.mp4:

This file crashed the player. I've no idea where it's coming from. Sounds like a native file malformed to addon-mode-prefix. I assume the file is located here:

/mnt/b2e773f9-8493-42a3-91ef-bd9a7ef78fbf/INTROS/ShieldTV/NOONAN%20CINEMAS%20INTRO%204K.mp4

Obviously it an intro/trailer, can you post additional information about it?

Link to comment
Share on other sites

DiscoDuck79

@quickmicI've had issues with the Websockets failing and that the syncing has been somewhat unstable, I've sporadically lost the ability to send test messages from the server etc.

Now I've enabled Settings/Services/Control - Allow remote control from applications on other systems and now it's more or less flawless with the sync. Changes applied on the Emby server is reflected very quick on the kodi client and same goes the other way.

However....

When I try to zero the resume position on an episode from kodi this happens.

1: Zero set the resume position on the episode from the menu. Episode is removed from the In progress list in Kodi - nothing happens in Emby, I.E it remains at the current progress.

2: Restart Kodi, navigate to emby-next-gen "In Progress Episodes" - folder is empty

3: On the Emby server, resume playback for a couple of seconds on the episode

4: Now the episode becomes visible at step 2, after a skin reload the episode is listed as In Progress but without the progress bar visible.

In the Emby log this happens when I mark an episode as watched and unwatched

Spoiler

2021-09-06 10:03:04.095 Info Server: http/1.1 POST http://192.168.10.20:8096/emby/Users/fa6e4844c67e4b68baecd354362b7ed2/PlayedItems/233275. UserAgent: Kodi/6.0.6
2021-09-06 10:03:04.101 Info Server: http/1.1 Response 200 to 192.168.10.60. Time: 7ms. http://192.168.10.20:8096/emby/Users/fa6e4844c67e4b68baecd354362b7ed2/PlayedItems/233275
2021-09-06 10:03:16.628 Info Server: http/1.1 Response 200 to 192.168.10.60. Time: 2ms. http://192.168.10.20:8096/emby/Items/229167/Images/Primary/0?=da82751e2945212b9a6543357451f541&EnableImageEnhancers=True
2021-09-06 10:03:17.483 Info Server: http/1.1 DELETE http://192.168.10.20:8096/emby/Users/fa6e4844c67e4b68baecd354362b7ed2/PlayedItems/233275. UserAgent: Kodi/6.0.6

Here I've initiated playback, skipped ahead and stopped. Then I've tried to zero set the resume position from kodi, but nothing is received on the Emby server. After the below timestamps there's no references to POST, DELETE or 233275 so I think nothing is received on the Emby server. I've tried with both Embuary and Estuary and the results are the same.

Spoiler

2021-09-06 10:16:43.386 Info Server: http/1.1 Response 206 to 192.168.10.60. Time: 1183ms. http://192.168.10.20:8096/emby/videos/233275/stream?static=true&MediaSourceId=5cd123f1c22413fb64740eb0c8966822&PlaySessionId=d3af717ae6724046a9e4f59a8929f8e8&DeviceId=4b7ae7be-aa4f-40a4-a08f-75c7663a5245&=NameOfTheEpisode.mkv
2021-09-06 10:16:43.387 Info Server: http/1.1 Response 206 to 192.168.10.60. Time: 2156ms. http://192.168.10.20:8096/emby/videos/233275/stream?static=true&MediaSourceId=5cd123f1c22413fb64740eb0c8966822&PlaySessionId=d3af717ae6724046a9e4f59a8929f8e8&DeviceId=4b7ae7be-aa4f-40a4-a08f-75c7663a5245&=NameOfTheEpisode.mkv
2021-09-06 10:16:43.388 Info Server: http/1.1 GET http://192.168.10.20:8096/emby/videos/233275/stream?static=true&MediaSourceId=5cd123f1c22413fb64740eb0c8966822&PlaySessionId=d3af717ae6724046a9e4f59a8929f8e8&DeviceId=4b7ae7be-aa4f-40a4-a08f-75c7663a5245&=NameOfTheEpisode.mkv. Accept=*/*, Accept-Charset=UTF-8,*;q=0.8, Accept-Encoding=deflate, gzip, Host=192.168.10.20:8096, Range=bytes=5769-, User-Agent=Kodi/19.1 (X11; Linux aarch64) CoreELEC/19.2 App_Bitness/32 Version/19.1-(19.1.0)-Git:e1d5be86494746261b701a8c9dae796cfcbcd42e
2021-09-06 10:16:44.877 Info Server: http/1.1 POST http://192.168.10.20:8096/emby/Sessions/Playing/Progress?CanSeek=True&QueueableMediaTypes=Video%2CAudio&IsPaused=False&ItemId=233275&Type=episode&MediaSourceId=5cd123f1c22413fb64740eb0c8966822&PositionTicks=5500000&RunTimeTicks=50206401367&VolumeLevel=100&IsMuted=False&PlaySessionId=d3af717ae6724046a9e4f59a8929f8e8. UserAgent: Kodi/6.0.6
2021-09-06 10:16:44.878 Info Server: http/1.1 POST http://192.168.10.20:8096/emby/Sessions/Playing?CanSeek=True&QueueableMediaTypes=Video%2CAudio&IsPaused=False&ItemId=233275&Type=episode&MediaSourceId=5cd123f1c22413fb64740eb0c8966822&PositionTicks=5500000&RunTimeTicks=50206401367&VolumeLevel=100&IsMuted=False&PlaySessionId=d3af717ae6724046a9e4f59a8929f8e8. UserAgent: Kodi/6.0.6
2021-09-06 10:16:44.878 Debug SqliteItemRepository: Public GetItemLinks
2021-09-06 10:16:44.880 Info SessionManager: Playback start reported by app Kodi 6.0.6 playing NameOfTheEpisode. Started at 550 ms
2021-09-06 10:16:58.484 Info Server: http/1.1 POST http://192.168.10.20:8096/emby/Sessions/Playing/Stopped?CanSeek=True&QueueableMediaTypes=Video%2CAudio&IsPaused=False&ItemId=233275&Type=episode&MediaSourceId=5cd123f1c22413fb64740eb0c8966822&PositionTicks=6096650390&RunTimeTicks=50206401367&VolumeLevel=100&IsMuted=False&PlaySessionId=d3af717ae6724046a9e4f59a8929f8e8. UserAgent: Kodi/6.0.6
2021-09-06 10:16:58.485 Debug App: ReportPlaybackStopped PlaySessionId: d3af717ae6724046a9e4f59a8929f8e8
2021-09-06 10:16:58.486 Info SessionManager: Playback stopped reported by app Kodi 6.0.6 playing NameOfTheEpisode. Stopped at 609665 ms
2021-09-06 10:16:58.491 Info Server: http/1.1 Response 204 to 192.168.10.60. Time: 7ms. http://192.168.10.20:8096/emby/Sessions/Playing/Stopped?CanSeek=True&QueueableMediaTypes=Video%2CAudio&IsPaused=False&ItemId=233275&Type=episode&MediaSourceId=5cd123f1c22413fb64740eb0c8966822&PositionTicks=6096650390&RunTimeTicks=50206401367&VolumeLevel=100&IsMuted=False&PlaySessionId=d3af717ae6724046a9e4f59a8929f8e8

In the kodi log all I see is: CPythonInvoker(190, /storage/.kodi/addons/script.embuary.helper/plugin.py): script successfully run

when I try to zero the position.

It's not the end of the world, it can easily be done by marking the episode as watched/unwatched to reset the state but it's always nice when workarounds aren't needed.

  • Like 1
Link to comment
Share on other sites

quickmic
1 hour ago, DiscoDuck79 said:

@quickmicI've had issues with the Websockets failing and that the syncing has been somewhat unstable, I've sporadically lost the ability to send test messages from the server etc.

Now I've enabled Settings/Services/Control - Allow remote control from applications on other systems and now it's more or less flawless with the sync. Changes applied on the Emby server is reflected very quick on the kodi client and same goes the other way.

However....

When I try to zero the resume position on an episode from kodi this happens.

1: Zero set the resume position on the episode from the menu. Episode is removed from the In progress list in Kodi - nothing happens in Emby, I.E it remains at the current progress.

2: Restart Kodi, navigate to emby-next-gen "In Progress Episodes" - folder is empty

3: On the Emby server, resume playback for a couple of seconds on the episode

4: Now the episode becomes visible at step 2, after a skin reload the episode is listed as In Progress but without the progress bar visible.

In the Emby log this happens when I mark an episode as watched and unwatched

  Reveal hidden contents

2021-09-06 10:03:04.095 Info Server: http/1.1 POST http://192.168.10.20:8096/emby/Users/fa6e4844c67e4b68baecd354362b7ed2/PlayedItems/233275. UserAgent: Kodi/6.0.6
2021-09-06 10:03:04.101 Info Server: http/1.1 Response 200 to 192.168.10.60. Time: 7ms. http://192.168.10.20:8096/emby/Users/fa6e4844c67e4b68baecd354362b7ed2/PlayedItems/233275
2021-09-06 10:03:16.628 Info Server: http/1.1 Response 200 to 192.168.10.60. Time: 2ms. http://192.168.10.20:8096/emby/Items/229167/Images/Primary/0?=da82751e2945212b9a6543357451f541&EnableImageEnhancers=True
2021-09-06 10:03:17.483 Info Server: http/1.1 DELETE http://192.168.10.20:8096/emby/Users/fa6e4844c67e4b68baecd354362b7ed2/PlayedItems/233275. UserAgent: Kodi/6.0.6

Here I've initiated playback, skipped ahead and stopped. Then I've tried to zero set the resume position from kodi, but nothing is received on the Emby server. After the below timestamps there's no references to POST, DELETE or 233275 so I think nothing is received on the Emby server. I've tried with both Embuary and Estuary and the results are the same.

  Reveal hidden contents

2021-09-06 10:16:43.386 Info Server: http/1.1 Response 206 to 192.168.10.60. Time: 1183ms. http://192.168.10.20:8096/emby/videos/233275/stream?static=true&MediaSourceId=5cd123f1c22413fb64740eb0c8966822&PlaySessionId=d3af717ae6724046a9e4f59a8929f8e8&DeviceId=4b7ae7be-aa4f-40a4-a08f-75c7663a5245&=NameOfTheEpisode.mkv
2021-09-06 10:16:43.387 Info Server: http/1.1 Response 206 to 192.168.10.60. Time: 2156ms. http://192.168.10.20:8096/emby/videos/233275/stream?static=true&MediaSourceId=5cd123f1c22413fb64740eb0c8966822&PlaySessionId=d3af717ae6724046a9e4f59a8929f8e8&DeviceId=4b7ae7be-aa4f-40a4-a08f-75c7663a5245&=NameOfTheEpisode.mkv
2021-09-06 10:16:43.388 Info Server: http/1.1 GET http://192.168.10.20:8096/emby/videos/233275/stream?static=true&MediaSourceId=5cd123f1c22413fb64740eb0c8966822&PlaySessionId=d3af717ae6724046a9e4f59a8929f8e8&DeviceId=4b7ae7be-aa4f-40a4-a08f-75c7663a5245&=NameOfTheEpisode.mkv. Accept=*/*, Accept-Charset=UTF-8,*;q=0.8, Accept-Encoding=deflate, gzip, Host=192.168.10.20:8096, Range=bytes=5769-, User-Agent=Kodi/19.1 (X11; Linux aarch64) CoreELEC/19.2 App_Bitness/32 Version/19.1-(19.1.0)-Git:e1d5be86494746261b701a8c9dae796cfcbcd42e
2021-09-06 10:16:44.877 Info Server: http/1.1 POST http://192.168.10.20:8096/emby/Sessions/Playing/Progress?CanSeek=True&QueueableMediaTypes=Video%2CAudio&IsPaused=False&ItemId=233275&Type=episode&MediaSourceId=5cd123f1c22413fb64740eb0c8966822&PositionTicks=5500000&RunTimeTicks=50206401367&VolumeLevel=100&IsMuted=False&PlaySessionId=d3af717ae6724046a9e4f59a8929f8e8. UserAgent: Kodi/6.0.6
2021-09-06 10:16:44.878 Info Server: http/1.1 POST http://192.168.10.20:8096/emby/Sessions/Playing?CanSeek=True&QueueableMediaTypes=Video%2CAudio&IsPaused=False&ItemId=233275&Type=episode&MediaSourceId=5cd123f1c22413fb64740eb0c8966822&PositionTicks=5500000&RunTimeTicks=50206401367&VolumeLevel=100&IsMuted=False&PlaySessionId=d3af717ae6724046a9e4f59a8929f8e8. UserAgent: Kodi/6.0.6
2021-09-06 10:16:44.878 Debug SqliteItemRepository: Public GetItemLinks
2021-09-06 10:16:44.880 Info SessionManager: Playback start reported by app Kodi 6.0.6 playing NameOfTheEpisode. Started at 550 ms
2021-09-06 10:16:58.484 Info Server: http/1.1 POST http://192.168.10.20:8096/emby/Sessions/Playing/Stopped?CanSeek=True&QueueableMediaTypes=Video%2CAudio&IsPaused=False&ItemId=233275&Type=episode&MediaSourceId=5cd123f1c22413fb64740eb0c8966822&PositionTicks=6096650390&RunTimeTicks=50206401367&VolumeLevel=100&IsMuted=False&PlaySessionId=d3af717ae6724046a9e4f59a8929f8e8. UserAgent: Kodi/6.0.6
2021-09-06 10:16:58.485 Debug App: ReportPlaybackStopped PlaySessionId: d3af717ae6724046a9e4f59a8929f8e8
2021-09-06 10:16:58.486 Info SessionManager: Playback stopped reported by app Kodi 6.0.6 playing NameOfTheEpisode. Stopped at 609665 ms
2021-09-06 10:16:58.491 Info Server: http/1.1 Response 204 to 192.168.10.60. Time: 7ms. http://192.168.10.20:8096/emby/Sessions/Playing/Stopped?CanSeek=True&QueueableMediaTypes=Video%2CAudio&IsPaused=False&ItemId=233275&Type=episode&MediaSourceId=5cd123f1c22413fb64740eb0c8966822&PositionTicks=6096650390&RunTimeTicks=50206401367&VolumeLevel=100&IsMuted=False&PlaySessionId=d3af717ae6724046a9e4f59a8929f8e8

In the kodi log all I see is: CPythonInvoker(190, /storage/.kodi/addons/script.embuary.helper/plugin.py): script successfully run

when I try to zero the position.

It's not the end of the world, it can easily be done by marking the episode as watched/unwatched to reset the state but it's always nice when workarounds aren't needed.

Currently the reset position is not reported at all from plugin to emby server. The plugin can only deal with info reported by Kodi (callbacks).

btw, this callback funtion is the same as used for "marked as watched/unwatched". In case of a position reset just item ID is reported, that's it.

Based on this limited info it could be any change. The plugin only knows that something has changed for this item.

Problem is, I don't know under which circumstances the callback is fired. If I capture every item callback and forward to Emby server as a refesh command, this could easily escalade and overload the plugin or server or just have a performance impact.

As mentioend before same callback is used for watched/unwatched but in this case, Kodi sends the info what has changed (additional parameter "playcout" is included in the callback info).

So this is straight forward for watched/unwached but not for resume reset playposition.

btw, this is also the reason why "add to favorites" is add into emby option menu and you cannot use the native Kodi option for it. Changes in native Kodi favorites are not reported at all to plugins.

Callbacks in general are not very well designed in Kodi but that's the way it is.

 

Edited by quickmic
  • Thanks 1
Link to comment
Share on other sites

DiscoDuck79
1 hour ago, quickmic said:

Currently the reset position is not reported at all from plugin to emby server. The plugin can only deal with info reported by Kodi (callbacks).

btw, this callback funtion is the same as used for "marked as watched/unwatched". In case of a position reset just item ID is reported, that's it.

Based on this limited info it could be any change. The plugin only knows that something has changed for this item.

Problem is, I don't know under which circumstances the callback is fired. If I capture every item callback and forward to Emby server as a refesh command, this could easily escalade and overload the plugin or server or just have a performance impact.

As mentioend before same callback is used for watched/unwatched but in this case, Kodi sends the info what has changed (additional parameter "playcout" is included in the callback info).

So this is straight forward for watched/unwached but not for resume reset playposition.

btw, this is also the reason why "add to favorites" is add into emby option menu and you cannot use the native Kodi option for it. Changes in native Kodi favorites are not reported at all to plugins.

Callbacks in general are not very well designed in Kodi but that's the way it is.

 

Excellent explanation!

  • Like 1
Link to comment
Share on other sites

quickmic

New version available:

6.0.6 build 24 (ex2)

- local trailers support for cinema mode and library sync
- minor sync fixes
- iso selection fixed

 

 

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

quickmic

@all

I think this could be the next beta version.

Please report all issues, I also perform continue testing...

 

  • Like 1
  • Thanks 1
Link to comment
Share on other sites

BaukeZwart
20 minutes ago, quickmic said:

@all

I think this could be the next beta version.

Please report all issues, I also perform continue testing...

 

I have send you a PM with log this morning, I couldn't see anything suspicious in the log but will test with the latest build and report back. 

  • Like 1
Link to comment
Share on other sites

BaukeZwart

I'm still having issues with syncing to always on devices.
Last night I watched and deleted a few episodes after watch on the Shield, On the Fire TV all those episodes where still shown as unwatched.

Also during the night a new episode was added to Emby, on both the Shield and Fire TV that episode didn't show until I restarted the the E4K plugin.
This was with 6.0.6 build 24 (ex2) on both devices.

Edit: it looks like these sync fails only happen when the device is on but not used for some time. The Shield is connected wired, the stick wireless. I will check Emby during the day see if it keep seeing both devices as connected. 

Edited by BaukeZwart
  • Like 1
  • Agree 1
Link to comment
Share on other sites

quickmic
16 minutes ago, BaukeZwart said:

I'm still having issues with syncing to always on devices.
Last night I watched and deleted a few episodes after watch on the Shield, On the Fire TV all those episodes where still shown as unwatched.

Also during the night a new episode was added to Emby, on both the Shield and Fire TV that episode didn't show until I restarted the the E4K plugin.
This was with 6.0.6 build 24 (ex2) on both devices.

Edit: it looks like these sync fails only happen when the device is on but not used for some time. The Shield is connected wired, the stick wireless. I will check Emby during the day see if it keep seeing both devices as connected. 

I'm checking that, I think the websocket connection still needs some improvements.

  • Thanks 1
Link to comment
Share on other sites

BaukeZwart

Already both devices are no longer listed as active devices in Emby.
Thats about 25 minutes after the last check.

I never checked this before, not sure if that's normal behaviour.

Edit: would it be possible for E4K to send a heartbeat periodically to tell Emby it's still alive?

Edited by BaukeZwart
Link to comment
Share on other sites

DiscoDuck79

I'm experience similar issues as @BaukeZwart

Scenario 1:

Emby-next-gen set to "Enable new content" as active. During playback of TV using Tvheadend client (NOT connected to Emby server) a file is added to the Emby server, I can see this in the log of kodi as well that data is received. Playback is stopped, no changes are visible on the kodi screen (see note after Scenario 4). I then initiate playback of a file stored at the Emby server, once running I stop the playback. Now kodi starts to update and I get notifications of added content.

 

Scenario 2:

Emby-next-gen set to "Enable new content" NOT active, same procedure as above but then the new content will not be added.

 

Scenario 3:

Emby-next-gen set to "Enable new content" as active. Emby server not displaying the kodi client as active device and kodi sitting at the home menu. New content is added.

 

Scenario 4:

Emby-next-gen set to "Enable new content" NOT active. Emby server not displaying the kodi client as active device and kodi sitting at the home menu. New content is NOT added.

NOTE: The new content is actually added, but not "loaded" or how to say. I can see that the file has changed, but the icon changes from a episode poster to the series poster and the file information isn't updated - it looks like kodi is aware that there has been a change, but it's not loading the changes.

 

 - If the Enable new content isn't activated it seems to prevent all content to be properly added, not only prevent popups.

- As per the "Enable new content" description Live TV from e.g. TVH should still get popups if there's new content (although I'm happy that it's not), something probably isn't right - see below issue.

 

I watch regular TV on my kodi client using TVH client (TVH server is a separate server on my LAN and not connected to Emby), I stop the TV playback and play something from the Emby server. Stop the Emby stream and start "normal" TV again, now the Emby server restarts playback on the server of the item I just played from there although TV is being broadcasted onto my screen, but on the server control panel it indicates playback of the recently stopped episode. This is new since next-gen V6.

Link to comment
Share on other sites

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
×
×
  • Create New...