Plugin paths supported?

[pünktchen 912]

@quickmic 
Does your addon support simple plugin paths for playback like EmbyCon does?

plugin://plugin.video.embycon/?item_id={ItemId}&mode=PLAY

I know i can use the addon webserver like this:

http://127.0.0.1:57578/embyvideodynamic-{ServerId}-{ItemId}-{ItemType}-{Name}.{Extension}

But that requires to know to many parameters beforehand, when i only have the itemId.

[quickmic 651]

On 8/26/2021 at 1:52 AM, pünktchen said:

@quickmic 
Does your addon support simple plugin paths for playback like EmbyCon does?

plugin://plugin.video.embycon/?item_id={ItemId}&mode=PLAY

I know i can use the addon webserver like this:

http://127.0.0.1:57578/embyvideodynamic-{ServerId}-{ItemId}-{ItemType}-{Name}.{Extension}

But that requires to know to many parameters beforehand, when i only have the itemId.

Well, you need the ServerID. It's mandatory due to multi-Emby-server-support.

The ServerID is NOT made up by next-gen plugin, it the real Emby-Server ID like: "2a38697ffc1b428b943aa1b6014e2263"

Also there are two options for remote content. One is the embyvideodynamic as you mentioned, the other one is embylivetv.

http://127.0.0.1:57578/embylivetv-{ServerID}-{ItemID}-stream.ts

For embyvideodynamic:

{ItemType} = "MusicVideo", "Movie", "Episode", "Video" etc

{Name} = Filename

{Extension} = mkv, mp4 etc.

{Filename} are not really critical. It's just used for connivance, you can also make that up like "blabla" as filename. (no special characters allowed, including spaces!)

{Extension} should at least indicate the content (Kodi uses the extensions to detect audio or video content. So it's critical NOT using mp3 if it's a video and vice versa.

It's not really critical to use mkv instead of mp4. Probably the Kodi OSD tags are not correct, but it will work anyway.

{ItemType} is used for identification. Actually dynamic content (this is all content received remotely from emby server via websocket) is checked if it's (already) synced to Kodi's DB.

If yes, next-gen pulls the metadata from Kodi DB (much faster). If it's not synced, next-gen queries Emby-server for metadata. If this info is not correct, worst case would be. next-gen pulls data from Emby server even it's already synced and actually no need for. (Slower). But it should work even it's not correct.

 

btw, what you hav ein mind?

VirtualTV is already supported by the latest experimental version.

Edited August 27 by quickmic

[pünktchen 912]

My plugin can also export stream links for playback of past and future programs as archive video (SimplePVR calls it catchup streams) to a channels.m3u. The stream links are urls with a placeholder for the "CatchupId" that is provided as part of the program from a xmltv file. I must admit i didn't try if the CatchupId accepts such a long parameter like the ones that are needed for your addon. I thought i would ask for a simpler method before i start to code.

The reason why i also write EmbyNextGen urls in the export function of my plugin is, with the channels.m3u of your addon users that have a live tv plugin in Emby and the same as a Kodi pvr addon, get duplicated channels.

[pünktchen 912]

@quickmic with some of your addon updates, the dynamic proxy urls have changed

from:

http://127.0.0.1:57578/embyvideodynamic-{ServerId}-{ItemId}-{ItemType}-{ItemName}.{FileExtension}

to:

http://127.0.0.1:57578/embyvideodynamic-{ServerId}-{ItemId}-{ItemType}-bc5ed8d67ac34d98745631hhb2158d7b12-8000507-h264-{ItemName}.{FileExtension}

What are those additional parameters?
Are really all those parameters needed that your addon works correctly? Right now your addon just throws an exception if only one parameter is missing in the query.
How often do you plan to change those urls? It makes it really hard for me to support your addon if such basic function changes often.

[quickmic 651]

Quote

How often do you plan to change those urls? It makes it really hard for me to support your addon if such basic function changes often.

Actually, yes they can change and have in one of the last betas. Actually it was not the intention as API usage.

I will add an api/url like Embycon. Mandatory data would be {ServerId} and  {ItemId} OR {MediasourceID}.

I cannot skip ServerId due to multi emby server support. The ItemId or MediasourceId is no longer unique in this case

 

At the moment, all parameters are mandatory, but some of the are not critical. You could make an assumption for :

 

e.g.
{ItemType} = movie
{ItemName} = unknown
{FileExtension} = mkv

[pünktchen 912]

1 hour ago, quickmic said:

I will add an api/url like Embycon. Mandatory data would be {ServerId} and  {ItemId} OR {MediasourceID}

That would be fantastic and would solve all problems. Preferable only ServerId and ItemId.

[quickmic 651]

I added the API support in the last experimental version.

 

If you want you can try or wait till beta is available.

command is:

RunPlugin(plugin://plugin.video.emby-next-gen?mode=play&server=2a38697ffc1b428b943aa1b6014e2263&item=123322)

case sensitive!

 

 

Edited November 15 by quickmic

[pünktchen 912]

Great! Will report back.

[pünktchen 912]

Working great. Thank you so much!