Jump to content

Emby for Kodi - Yatse & Stream


inkubux

Recommended Posts

inkubux

Hi,

 

I'm using the new Emby for kodi plugin and I love it :).

 

The only issue I have when I want to use Yatse to "share" the video with other upnp, or android video player. The link sent from Kodi is something like this:

 

http://[iP]/vfs/emby/[mediaid]  (something a long the lines).

 

since I share this link with external applications they fail to play because of the link.

 

A one point when the plugin was in it's "infancy" a couple of weeks ago this link was either a samba share or an http link to the Emby media so it worked.

 

I was just wondering if there is a way to have a direct url / link when using the Kodi API for other apps ? but keeping the Virtual url inside Kodi ? this would be best of both world

 

 

I know I could use the Emby android client To watch or share locally on my Tablet. The Android client is not stable enough anyway.

 

I rather use Yatse since I has all the remote (keyboard, remote etc.) Kodi features. It just make more sense for may setup to only use one App instead of 2.

 

But that's not the point of this small bug. 

 

 

Thanks a lot for your help

Edited by inkubux
Link to comment
Share on other sites

scalda

This is because the Addon no longer puts the smb direct path in the database, so YatseApplication doesn't know what to do with the path that the Addon provides.

 

I use YatseApplication aswell so I just tried this and also fails here

Link to comment
Share on other sites

xnappo

Correct - we will consider having a hybrid approach to this so that both direct path access and transcoding can work after our 1.0 release.  

 

Go vote for this issue on the Trello board to get the priority up:

https://trello.com/c/jCBVwx1M/81-cache-playback-path-to-local-kodi-db-for-faster-playback-start

 

Note that for your request - only proposed solution #1 would work, you might post a link to this thread in the comment.  We cannot 'keep the virtual URL inside the addon' because we can't intercept the play command to detect the network situation if the direct path is there.  It is either one way or the other.

Edited by xnappo
Link to comment
Share on other sites

inkubux

Correct - we will consider having a hybrid approach to this so that both direct path access and transcoding can work after our 1.0 release.  

 

Go vote for this issue on the Trello board to get the priority up:

https://trello.com/c/jCBVwx1M/81-cache-playback-path-to-local-kodi-db-for-faster-playback-start

 

Note that for your request - only proposed solution #1 would work, you might post a link to this thread in the comment.  We cannot 'keep the virtual URL inside the addon' because we can't intercept the play command to detect the network situation if the direct path is there.  It is either one way or the other.

 

Thanks I added my vote, but unfortunately I can't add a comment in Trello (I just created a brand new Account).

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...