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

[pünktchen 1251]

3 hours ago, pünktchen said:

As a general rule, you should never assign parent images via your addon. This is all done by the Kodi skins

 

[Andy2k 60]

3 hours ago, quickmic said:

ImageTagsMappings = {
    "Series": (('Primary', 'poster'), ("Art", 'clearart'), ("Banner", 'banner'), ("Disc", 'discart'), ("Logo", 'clearlogo'), ("Thumb", 'thumb'), ("Thumb", 'landscape'), ("Backdrop", 'fanart'), ('Primary', 'thumb'), ("Backdrop", 'landscape')),
    "Season": (('Primary', 'poster'), ("Art", 'clearart'), ("Banner", 'banner'), ("Disc", 'discart'), ("Logo", 'clearlogo'), ("Thumb", 'thumb'), ('SeriesPrimary', 'poster'), ("ParentThumb", 'thumb'), ("Primary", 'thumb'), ("ParentLogo", 'clearlogo'), ("ParentBackdrop", 'fanart')),
    "Episode": (("Primary", 'thumb'), ("Backdrop", 'fanart'), ("ParentThumb", 'fanart'), ("ParentBackdrop", 'fanart')),
    "Movie": (('Primary', 'poster'), ("Art", 'clearart'), ("Banner", 'banner'), ("Disc", 'discart'), ("Logo", 'clearlogo'), ("Thumb", 'thumb'), ("Thumb", 'landscape'), ("Backdrop", 'fanart'), ('Primary', 'thumb')),
    "BoxSet": (('Primary', 'poster'), ("Art", 'clearart'), ("Banner", 'banner'), ("Disc", 'discart'), ("Logo", 'clearlogo'), ("Thumb", 'thumb'), ("Thumb", 'landscape'), ("Backdrop", 'fanart'), ('Primary', 'thumb')),
    "Video": (('Primary', 'poster'), ("Art", 'clearart'), ("Banner", 'banner'), ("Disc", 'discart'), ("Logo", 'clearlogo'), ("Thumb", 'thumb'), ("Backdrop", 'fanart'), ('Primary', 'thumb')),
    "MusicArtist": (('Primary', 'thumb'), ('Primary', 'poster'), ("Art", 'clearart'), ("Banner", 'banner'), ("Disc", 'discart'), ("Logo", 'clearlogo'), ("Thumb", 'thumb'), ("Backdrop", 'fanart'), ('Primary', 'thumb')),
    "MusicAlbum": (('Primary', 'thumb'), ('Primary', 'poster'), ("Art", 'clearart'), ("Banner", 'banner'), ("Disc", 'discart'), ("Logo", 'clearlogo'), ("Thumb", 'thumb'), ("Backdrop", 'fanart'), ("ParentThumb", 'thumb'), ("Primary", 'thumb'), ("ParentLogo" ,'clearlogo'), ("ParentBackdrop", 'fanart'), ("AlbumArtists", 'poster'), ("AlbumArtists", 'thumb'), ("AlbumArtists", 'fanart'), ("ArtistItems", 'poster'), ("ArtistItems", 'thumb'), ("ArtistItems", 'fanart')),
    "Audio": (('Primary', 'thumb'), ('Primary', 'poster'), ("Art", 'clearart'), ("Banner", 'banner'), ("Disc", 'discart'), ("Logo", 'clearlogo'), ("Thumb", 'thumb'), ("Backdrop", 'fanart'), ('AlbumPrimary', 'poster'), ("ParentThumb", 'thumb'), ("Primary", 'thumb'), ("ParentLogo", 'clearlogo'), ("ParentBackdrop", 'fanart'), ("AlbumArtists", 'poster'), ("AlbumArtists", 'thumb'), ("AlbumArtists", 'fanart'), ("ArtistItems", 'poster'), ("ArtistItems", 'thumb'), ("ArtistItems", 'fanart')),
    "MusicVideo": (('Primary', 'poster'), ("Art", 'clearart'), ("Banner", 'banner'), ("Disc", 'discart'), ("Logo", 'clearlogo'), ("Thumb", 'thumb'), ("Backdrop", 'fanart'), ('Primary', 'thumb')),
    "Photo": (('Primary', 'poster'), ("Art", 'clearart'), ("Banner", 'banner'), ("Disc", 'discart'), ("Logo", 'clearlogo'), ("Thumb", 'thumb'), ("Backdrop", 'fanart'), ('Primary', 'thumb')),
    "PhotoAlbum": (('Primary', 'poster'), ("Art", 'clearart'), ("Banner", 'banner'), ("Disc", 'discart'), ("Logo", 'clearlogo'), ("Thumb", 'thumb'), ("Backdrop", 'fanart'), ('Primary', 'thumb')),
    "Folder": (('Primary', 'poster'), ("Art", 'clearart'), ("Banner", 'banner'), ("Disc", 'discart'), ("Logo", 'clearlogo'), ("Thumb", 'thumb'), ("Backdrop", 'fanart'), ('Primary', 'thumb')),
    "TvChannel": (('Primary', 'poster'), ("Art", 'clearart'), ("Banner", 'banner'), ("Disc", 'discart'), ("Logo", 'clearlogo'), ("Thumb", 'thumb'), ("Backdrop", 'fanart'), ('Primary', 'thumb')),
    "Trailer": (('Primary', 'poster'), ("Art", 'clearart'), ("Banner", 'banner'), ("Disc", 'discart'), ("Logo", 'clearlogo'), ("Thumb", 'thumb'), ("Thumb", 'landscape'), ("Backdrop", 'fanart'), ('Primary', 'thumb'))
}

I tested it also on Estuary (with another db reset), works like it should.

 

3 hours ago, quickmic said:

 

 

[quickmic 1330]

7 hours ago, pünktchen said:

 

I'll test that too.

[quickmic 1330]

7 hours ago, pünktchen said:

As a general rule, you should never assign parent images via your addon. This is all done by the Kodi skins

 

I performed another test.

What you say is valid for Embuary but not for e.g. Esturay mod v2.

EM2 don't respects the fallbacks therefore I cannot remove the poster assignment in general and also not the parent fallbacks assigned via plugin.

So the last mapping table (with removed poster artwork) is not valid for all skins.

The situation is: Stock Estuary requires no posters assigned for episodes and estuary mod v2 does.

So I'll keep the mapping table from the 7.8.2 (and the option) but I'll "invert" the poster assignment option. So default will be no posters with an opt-in poster assignment.

OR

I'll remove all parent fallbacks etc and another table for assignment (via plugin option) for all "non" standard assignments. Maybe this is the way to go.

Fact is, the default skin should be correct without any adjustments in the plugin's config menu.

 

to all: Feel free to perform additional tests and let me know if more changes are required.

Next table will be:

ImageTagsMappings = {
    "Series": (('Primary', 'poster'), ("Art", 'clearart'), ("Banner", 'banner'), ("Disc", 'discart'), ("Logo", 'clearlogo'), ("Thumb", 'thumb'), ("Thumb", 'landscape'), ("Backdrop", 'fanart'), ('Primary', 'thumb'), ("Backdrop", 'landscape')),
    "Season": (('Primary', 'poster'), ("Art", 'clearart'), ("Banner", 'banner'), ("Disc", 'discart'), ("Logo", 'clearlogo'), ("Thumb", 'thumb'), ('SeriesPrimary', 'poster'), ("ParentThumb", 'thumb'), ("Primary", 'thumb'), ("ParentLogo", 'clearlogo'), ("ParentBackdrop", 'fanart')),
    "Episode": (('Primary', 'thumb'), ('Primary', 'landscape'), ("Art", 'clearart'), ("Banner", 'banner'), ("Disc", 'discart'), ("Logo", 'clearlogo'), ("Thumb", 'thumb'), ("Backdrop", 'fanart'), ("ParentThumb", 'thumb'), ("Primary", 'thumb'), ("ParentLogo", 'clearlogo'), ("ParentBackdrop", 'fanart')),
    "Movie": (('Primary', 'poster'), ("Art", 'clearart'), ("Banner", 'banner'), ("Disc", 'discart'), ("Logo", 'clearlogo'), ("Thumb", 'thumb'), ("Thumb", 'landscape'), ("Backdrop", 'fanart'), ('Primary', 'thumb')),
    "BoxSet": (('Primary', 'poster'), ("Art", 'clearart'), ("Banner", 'banner'), ("Disc", 'discart'), ("Logo", 'clearlogo'), ("Thumb", 'thumb'), ("Thumb", 'landscape'), ("Backdrop", 'fanart'), ('Primary', 'thumb')),
    "Video": (('Primary', 'poster'), ("Art", 'clearart'), ("Banner", 'banner'), ("Disc", 'discart'), ("Logo", 'clearlogo'), ("Thumb", 'thumb'), ("Backdrop", 'fanart'), ('Primary', 'thumb')),
    "MusicArtist": (('Primary', 'thumb'), ('Primary', 'poster'), ("Art", 'clearart'), ("Banner", 'banner'), ("Disc", 'discart'), ("Logo", 'clearlogo'), ("Thumb", 'thumb'), ("Backdrop", 'fanart'), ('Primary', 'thumb')),
    "MusicAlbum": (('Primary', 'thumb'), ('Primary', 'poster'), ("Art", 'clearart'), ("Banner", 'banner'), ("Disc", 'discart'), ("Logo", 'clearlogo'), ("Thumb", 'thumb'), ("Backdrop", 'fanart'), ("ParentThumb", 'thumb'), ("Primary", 'thumb'), ("ParentLogo" ,'clearlogo'), ("ParentBackdrop", 'fanart'), ("AlbumArtists", 'poster'), ("AlbumArtists", 'thumb'), ("AlbumArtists", 'fanart'), ("ArtistItems", 'poster'), ("ArtistItems", 'thumb'), ("ArtistItems", 'fanart')),
    "Audio": (('Primary', 'thumb'), ('Primary', 'poster'), ("Art", 'clearart'), ("Banner", 'banner'), ("Disc", 'discart'), ("Logo", 'clearlogo'), ("Thumb", 'thumb'), ("Backdrop", 'fanart'), ('AlbumPrimary', 'poster'), ("ParentThumb", 'thumb'), ("Primary", 'thumb'), ("ParentLogo", 'clearlogo'), ("ParentBackdrop", 'fanart'), ("AlbumArtists", 'poster'), ("AlbumArtists", 'thumb'), ("AlbumArtists", 'fanart'), ("ArtistItems", 'poster'), ("ArtistItems", 'thumb'), ("ArtistItems", 'fanart')),
    "MusicVideo": (('Primary', 'poster'), ("Art", 'clearart'), ("Banner", 'banner'), ("Disc", 'discart'), ("Logo", 'clearlogo'), ("Thumb", 'thumb'), ("Backdrop", 'fanart'), ('Primary', 'thumb')),
    "Photo": (('Primary', 'poster'), ("Art", 'clearart'), ("Banner", 'banner'), ("Disc", 'discart'), ("Logo", 'clearlogo'), ("Thumb", 'thumb'), ("Backdrop", 'fanart'), ('Primary', 'thumb')),
    "PhotoAlbum": (('Primary', 'poster'), ("Art", 'clearart'), ("Banner", 'banner'), ("Disc", 'discart'), ("Logo", 'clearlogo'), ("Thumb", 'thumb'), ("Backdrop", 'fanart'), ('Primary', 'thumb')),
    "Folder": (('Primary', 'poster'), ("Art", 'clearart'), ("Banner", 'banner'), ("Disc", 'discart'), ("Logo", 'clearlogo'), ("Thumb", 'thumb'), ("Backdrop", 'fanart'), ('Primary', 'thumb')),
    "TvChannel": (('Primary', 'poster'), ("Art", 'clearart'), ("Banner", 'banner'), ("Disc", 'discart'), ("Logo", 'clearlogo'), ("Thumb", 'thumb'), ("Backdrop", 'fanart'), ('Primary', 'thumb')),
    "Trailer": (('Primary', 'poster'), ("Art", 'clearart'), ("Banner", 'banner'), ("Disc", 'discart'), ("Logo", 'clearlogo'), ("Thumb", 'thumb'), ("Thumb", 'landscape'), ("Backdrop", 'fanart'), ('Primary', 'thumb'))
}

 

And optional assignment for:

('SeriesPrimary', 'poster')

 

Edited September 19, 2022 by quickmic

[quickmic 1330]

https://kodi.wiki/view/Artwork_types

"3 Artwork Usage Chart"

Quote

Artwork is skin dependant and skinners are free to use artwork how and where they choose. Some skins may conform with the following, others may not.

...and that's the problem. Skinners are not always respect the "standard". It would be too easy, grrrr

Edited September 19, 2022 by quickmic

[Seger 110]

Hey, in the last test I noticed that deleting and adding databases is often only triggered after a restart. When resetting, the file "MyVideos119" or the thumbnail folder also remains and is overwritten again later when adding. I am currently testing the scheme again.

Thanks Seger

 

[heula 189]

With the latest version(s) I needed to do a full database reset and now I see Emby coverart and it is not enabled in the next gen settings.

I use the coverart from Kodi.

 

Thanks

[pünktchen 1251]

1 hour ago, quickmic said:

...and that's the problem. Skinners are not always respect the "standard". It would be too easy, grrrr

Oh i think they are respecting the standard, but they do not always use all available possibilities. But that should be not your problem imho.

[quickmic 1330]

2 hours ago, heula said:

With the latest version(s) I needed to do a full database reset and now I see Emby coverart and it is not enabled in the next gen settings.

I use the coverart from Kodi.

 

Thanks

I'll check it, could be a bug.

[Seger 110]

Of good order, the 7.8.2 scheme works fine under Embuary.

Somehow the "next" doesn't quite want to let me go. I watched some episodes of a series yesterday via an Emby client and after finishing the episode, Emby and Embuary list the "next" section in position 1, but my test custom widget "next", which points to the Emby Next Gen, didn't update it. If I then start the episode again from Kodi, it is also positioned correctly in Kodi. Once I have a log I will post it as usual, just overwrote some through the other tests.

[Seger 110]

When testing the scheme and the individual widgets, the box crashed several times, maybe there is something else than the Embuary Widget problem.

I manually reset the nodes, as it no longer happened automatically, then restarted and restarted the loop.

After a successful kodi start, I created a widget via a custom entry: Base->Addon Emby-Next-Gen "next" to test the system for heart and kidneys. so via addon/widget then started a sequence and caused the crash. Could be the widget problem from Embuary, but could also be something else. Attached are 2 logs to take a look.

kodi.old.log kodi.log

[Seger 110]

Attached perhaps again a video of what causes my knot in the head. As 3 different "next" nodes:

1 Embuary, immediately takes over the right sequence after a short playback and the last played sequence jumps to the front

2 Custome Node (libary)

3 Nex-Gen-Addon

- with variant 2 and 3 does not jump to the front and there is no synchronisation with the server either, at least not after a short playback time. I don't know, maybe the video will help to untie my knot :-).

[smernt 9]

Hey, I keep having an issue with playback, it seems to happen most often with shorter episodes, such as kids shows <10mins long.

Sometimes it can happen on the first episode I play, other times its after a couple of episodes have played back to back, but eventually the audio cuts out, and then the video gets really choppy before freezing completely, though if subtitles are on they'll keep playing. At that point it becomes very difficult to stop playback or even close out of kodi for maybe 1-2 minutes, until it eventually lets me force close the app. I can then re-open the app and play the same files again without issue, but it eventually happens with another file, and the cycle repeats.

I've attached a log which I grabbed straight after a crash happened, just in case that's useful. From a quick look at it myself, there's a lot of this around the time the crash happens: 
 

2022-09-18 09:56:01.247 T:6427    ERROR <general>: CAEStreamInfo::GetDuration - invalid stream type
2022-09-18 09:56:01.248 T:6427  WARNING <general>: Skipped 21 duplicate messages..
2022-09-18 09:56:01.248 T:6427  WARNING <general>: ActiveAE - large audio sync error: -14263.344117

But it's definitely not an issue with the files, because I can re-open Kodi and play that same file again and it works fine, and the issue doesn't happen at all in the official emby app...

 

kodi.log

Edited September 19, 2022 by smernt

[quickmic 1330]

6 hours ago, Seger said:

Attached perhaps again a video of what causes my knot in the head. As 3 different "next" nodes:

1 Embuary, immediately takes over the right sequence after a short playback and the last played sequence jumps to the front

2 Custome Node (libary)

3 Nex-Gen-Addon

- with variant 2 and 3 does not jump to the front and there is no synchronisation with the server either, at least not after a short playback time. I don't know, maybe the video will help to untie my knot :-).

2022-09-19-13-20-07.avi

2 & 3. I assume you used for 3 the synced node (for "addon" node selection). Ergo they are identical nodes.

Now it's hard to explain... The addon node uses caches from the next-gen-plugin queries.

Technically the addon-mode node uses a detour via next-gen plugin. Dont' use it, it's just an extra layer and redirecting to the same node and makes no sense in this case. Addon mode nodes makes only sense for dynamic nodes (cause they are not "directly" available for Kodi ). Really hard to explain.

I try, forget about all plugins related stuff. Kodi nodes are files and located in ...kodi/userdata/library/

It's a file telling Kodi what to show. It's related to Kodi's internal database and has nothing todo with the plugin at this point.

So the node is just a file (with commands), and the difference between 2 & 3 is just how you call this file.

2: Kodi access the file directly and loads the view.

3: Kodi query's the plugin and the plugin redirects to the same (node) file. (That's the detour). -> Please don't ask why they are available if it's redirecting to the same node file. That's even more difficult to explain, but there are reasons.

Dynamic nodes includes not synced content to Kodi's database (or the query is not possible via Kodi's database, but let's skip that for the moment). Ergo, not synced content cannot be queried via Kodi's database, and comes directly from Emby server (therefore it's slow).

 

Back to your observation. 2 & 3 are identical, but looks the Kodi query is faster in one node than the other OR the detour via plugin uses the plugin's query cache. Even it is, it should be correct in both cases. The cache for queries is cleared under some circumstances. I stop here explaining that, but I'll review it. Maybe a bug, but I don't think so. Maybe just delayed, however.

Let's go back to 1 & 2

Embuary uses realtime query to Kodi's database, therefore it's always "correct" but there is a price to pay.

Embuary doesn't use Kodi's internal functions (the nodes/node files) for views. It uses jsonRPC calls which are by design not the fastest (another detour).

So the way to got is let Kodi build the view by it's internal functions, ergo the node file.

To make this even more clear, each Kodi widget/list view is based on those files (even with stock installation). -> Not 100% correct, but close enough for my point.

 

So the final question is, why doesn't refresh the "custom" node file as fast and there are several explanations. Is it incorrect or is it just slower.

Both cases is something to review VERY VERY deeply. Is it skin related. I know, you use Embuary but this is not a proper test. Such questions are not easy to answer. Could be everything, e.g. the skin is not triggering the refresh. The helper is not triggering the refresh. The refresh was triggered, but delayed. And a million more.

However, I'll review it.

 

Sorry for the long answer, but this is not a black or white matter.

 

Therefore I recommend tests with stock skin. This is a dedicated testcase, or at least some else lightweight skin. Especially NOT using Embuary for such plugin tests. This skin has a million of extra layers, and nobody will know who causes an issue.

I know you want everything perfect for Embuary, but I will not debug this skin. I debug plugin issues, and for some cases artwork review for some skins.

If it's an actual plugin issue, test it and report it but not with Embuary.

Don't get me wrong, I'm not saying it's not a plugin issue but there is no way to review it without reviewing the Embuary skin as well and that's not what I'm gonna do.

I'll check the issue with a simple skin, if I find something than it's confirmed, otherwise not.

Edited September 19, 2022 by quickmic

[quickmic 1330]

4 hours ago, smernt said:

Hey, I keep having an issue with playback, it seems to happen most often with shorter episodes, such as kids shows <10mins long.

Sometimes it can happen on the first episode I play, other times its after a couple of episodes have played back to back, but eventually the audio cuts out, and then the video gets really choppy before freezing completely, though if subtitles are on they'll keep playing. At that point it becomes very difficult to stop playback or even close out of kodi for maybe 1-2 minutes, until it eventually lets me force close the app. I can then re-open the app and play the same files again without issue, but it eventually happens with another file, and the cycle repeats.

I've attached a log which I grabbed straight after a crash happened, just in case that's useful. From a quick look at it myself, there's a lot of this around the time the crash happens: 
 

2022-09-18 09:56:01.247 T:6427    ERROR <general>: CAEStreamInfo::GetDuration - invalid stream type
2022-09-18 09:56:01.248 T:6427  WARNING <general>: Skipped 21 duplicate messages..
2022-09-18 09:56:01.248 T:6427  WARNING <general>: ActiveAE - large audio sync error: -14263.344117

But it's definitely not an issue with the files, because I can re-open Kodi and play that same file again and it works fine, and the issue doesn't happen at all in the official emby app...

 

kodi.log 1.18 MB · 0 downloads

Kodi bug, not plugin related.

Lot's of Kodi bug reports related to this matter. Just google.

Edited September 19, 2022 by quickmic

[Seger 110]

thanks for the really detailed answer, i will expand my test scenario to the standard skin in the future.

Thank you

Seger

 

[embyL0VER 70]

Good afternoon to all. @quickmic I just want to try the next up widget in Estuary but I can't figure out how to edit widgets in this skin. (This skin is maeh) sry.

But what I see is the node for in progress movies or series, is updating the data quite instantly (I have changed the node to the one from emby-next-gen). Only the next-up episode node seems not to update. But yeah I only can test this node with embuary as I have said, cause I don't get how to modify the Estuary standard skin. 

[quickmic 1330]

2 minutes ago, embyL0VER said:

Good afternoon to all. @quickmic I just want to try the next up widget in Estuary but I can't figure out how to edit widgets in this skin. (This skin is maeh) sry.

But what I see is the node for in progress movies or series, is updating the data quite instantly (I have changed the node to the one from emby-next-gen). Only the next-up episode node seems not to update. But yeah I only can test this node with embuary as I have said, cause I don't get how to modify the Estuary standard skin.

Stock estuary skin cannot be customized. Use estuary mod v2 (kodi nerds repo). You will see zero difference by default settings, but fully adjustable.

Too all: Please don't drop skin related questions, issues etc in this thread. This is a bug report/support thread for next-gen plugin not a skin mod thread.

btw, same for Kodi bugs.

[embyL0VER 70]

Ah this explains a lot. Thank you for the hint and sry for asking skin related thing indirectly, will install it and test again.

EDIT: Well what a Skin-Setup....

Anyway I have checked the next-up widget in Estuary-Mod2.

The standard next-up episode widget coming with the skin (I assume it is from skin helper) is also refreshing instantly after ending an episode and showing the next one. I assume same approach like the embuary widget with rpc-calls.

However the emby-next-gen "next up episode" widget doesn't refresh instantly to the next episode after watching the one before. But it refreshes the progress bar of a running episode if you pause/stop them. 

Edited September 19, 2022 by embyL0VER

[quickmic 1330]

22 hours ago, pünktchen said:

Oh i think they are respecting the standard, but they do not always use all available possibilities. But that should be not your problem imho.

I performed a test with just the "standard" artwork assignment. This will break the dynamic nodes, cause there is no lookup/fallback possible due to content is not synced. So this no go

I will use to the assignment from 7.8.2 but with inverted "option".

[quickmic 1330]

19 hours ago, Seger said:

Attached perhaps again a video of what causes my knot in the head. As 3 different "next" nodes:

1 Embuary, immediately takes over the right sequence after a short playback and the last played sequence jumps to the front

2 Custome Node (libary)

3 Nex-Gen-Addon

- with variant 2 and 3 does not jump to the front and there is no synchronisation with the server either, at least not after a short playback time. I don't know, maybe the video will help to untie my knot :-).

2022-09-19-13-20-07.avi

I checked and I think next-gen node is "correct" and matching Emby server and the skins's (helper) is not.

Please don't take for granted, that the Skin nodes are always "right". Approach is, nodes should match Emby server.

Let me know, if this answers your question.

 

nextup3-2022-09-20_08.56.15.mkv

[Seger 110]

12 hours ago, quickmic said:

Ich habe nachgesehen und denke, dass der Knoten der nächsten Generation "richtig" ist und der Emby-Server und die Skins (Helfer) nicht übereinstimmen.

Bitte gehen Sie nicht davon aus, dass die Skin-Knoten immer "richtig" sind. Der Ansatz ist, dass die Knoten mit dem Emby-Server übereinstimmen sollten.

Lassen Sie mich wissen, ob dies Ihre Frage beantwortet.

 

nextup3-2022-09-20_08.56.15.mkv 9,71 MB · 1 herunterladen

Isn't it the other way round? "Next Up" is the node of the skin, the lower one is surely that of next-gen-addon or what have you included above?

[quickmic 1330]

9 hours ago, Seger said:

Isn't it the other way round? "Next Up" is the node of the skin, the lower one is surely that of next-gen-addon or what have you included above?

Right, I also call next-gen's node as next-up (it's it's internal id), what you see is just a label.

In the video it's called "next episodes".

[quickmic 1330]

4 minutes ago, quickmic said:

Right, I also call next-gen's node as next-up (it's it's internal id), what you see is just a label.

In the video it's called "next episodes".

You mean the next-up from skin is "correct"? Well, there is also no right or wrong. They work differently, and next-gen's node is exactly doing what Emby-server shows under next-up. Therefore it should match the dynamic node (data comes directly from Emby server).

The difference is, Emby server and also next-gen's node updates the order when finished watching, while skin's node updates even if an episode is just in progress and not fully played.

Edited September 21, 2022 by quickmic

[Seger 110]

44 minutes ago, quickmic said:

The difference is, Emby server and also next-gen's node updates the order when finished watching, while skin's node updates even if an episode is just in progress and not fully played.

Now we have it my friend, exactly the explanation was missing in my head, that's why the sorting is also different, thank you!!!! In the end, both only work with different conditions. Is it possible to set in the addon that the update is also updated after the short view? If not, I think this could also be a future request in the Emby Core team.