Jump to content


Photo

Emby External Player Launcher

Emby External Player Launcher EmbyExternalPlayerLauncher E2PL MPC-HC external external player

  • Please log in to reply
75 replies to this topic

#61 Elegant OFFLINE  

Elegant

    Advanced Member

  • Members
  • 32 posts
  • Local time: 01:09 AM

Posted 16 December 2018 - 01:44 AM

The Emby External Player Launcher, if I set the address to use the SSL port (443) it will fail to connect (see attached). If I access Emby using the same address and port in the web browser, I have no issues and the certificate is trusted per my previous post.

Attached Files


Edited by Elegant, 16 December 2018 - 01:45 AM.


#62 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 140179 posts
  • Local time: 01:09 AM

Posted 16 December 2018 - 02:21 AM

Ok, I'm not familiar enough with this , but first things being first, are you able to use https with Emby apps?



#63 KMBanana OFFLINE  

KMBanana

    Advanced Member

  • Members
  • 134 posts
  • Local time: 01:09 AM

Posted 16 December 2018 - 02:28 AM

Is there a need for https with this app?  You need to be on the same machine or LAN as the Emby server for it to work in the first place.  



#64 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 140179 posts
  • Local time: 01:09 AM

Posted 16 December 2018 - 03:01 AM

Right, probably not.



#65 Elegant OFFLINE  

Elegant

    Advanced Member

  • Members
  • 32 posts
  • Local time: 01:09 AM

Posted 16 December 2018 - 03:02 AM

@Luke I never had to download an Emby app previously. Downloading Emby Theatres actually taught me what the issue was. I noticed that using emby.svc.example.com:443 did not work here either BUT I did notice the example at the bottom of Emby Theatre (192.168.1.100 or https://myserver.com). So I tried using https://emby.svc.example.com instead which works. The key was putting https:// in the address bar. Thanks!


Edited by Elegant, 16 December 2018 - 03:02 AM.


#66 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 140179 posts
  • Local time: 01:09 AM

Posted 16 December 2018 - 03:25 AM

Thanks for the feedback.



#67 Bloodred OFFLINE  

Bloodred

    Advanced Member

  • Members
  • 52 posts
  • Local time: 09:09 AM

Posted 17 December 2018 - 06:57 PM

I'm glad you got it working! It makes a lot of sense actually for "https://" to be required there since the client wouldn't really have any way to know that it should be trying to establish an encrypted connection, so I guess it was just using regular HTTP over port 443 which obviously wouldn't work if your proxy expected HTTPS. I should've thought of that. Anyway, good thing you could solve the problem and thanks for posting the solution.



#68 fyngd OFFLINE  

fyngd

    Member

  • Members
  • 12 posts
  • Local time: 02:09 PM

Posted 14 March 2019 - 10:40 PM

2019-03-15 10:38:38,753 [1  ] INFO  EmbyExternalPlayerLauncher.Program - Emby External Player Launcher is starting.

2019-03-15 10:38:39,136 [1  ] INFO  EmbyExternalPlayerLauncher.ServerConnect.AutoConnector - Connecting to Emby Server...
2019-03-15 10:38:40,869 [5  ] INFO  EmbyExternalPlayerLauncher.ServerConnect.EmbyPlayerConnector - Connected to Emby server at http://192.168.1.8:8096
2019-03-15 10:38:40,904 [9  ] ERROR EmbyExternalPlayerLauncher.ServerConnect.Logging.EmbyLogger - Error connecting to ws://192.168.1.8:8096/emby/embywebsocket?api_key=373cf605e5ba48fb9a4b881bdafc9422&deviceId=E2PL-admin@Ning
System.PlatformNotSupportedException: 此平台不支持 WebSocket 协议。
   在 System.Net.WebSockets.ClientWebSocket..ctor()
   在 Emby.ApiClient.WebSocket.NativeClientWebSocket..ctor(ILogger logger)
   在 Emby.ApiClient.WebSocket.ClientWebSocketFactory.CreateWebSocket(ILogger logger)
   在 Emby.ApiClient.WebSocket.ClientWebSocketFactory.CreateWebSocket()
   在 Emby.ApiClient.ApiClient.<EnsureConnectionAsync>d__296.MoveNext()


#69 Elegant OFFLINE  

Elegant

    Advanced Member

  • Members
  • 32 posts
  • Local time: 01:09 AM

Posted 13 July 2019 - 01:42 PM

Just noticed that it seems to fail if using LDAP for authentication. Tested with one user using LDAP and another without. Would it be possible to have support added? Thanks!



#70 Bloodred OFFLINE  

Bloodred

    Advanced Member

  • Members
  • 52 posts
  • Local time: 09:09 AM

Posted 21 July 2019 - 01:48 PM

Hello! I'm afraid I've never personally used LDAP and don't know much about it. I assume it's something you configure on the Emby server, right? The authentication is handled by the Emby client library and E2PL only really provides the user name and password. I can have a look at it, but I'm not sure I'll be able to do anything about it.

 

Is this something which used to work in the past but no longer works since a server update or something like that? It's possible that something changed in the server API too.



#71 Elegant OFFLINE  

Elegant

    Advanced Member

  • Members
  • 32 posts
  • Local time: 01:09 AM

Posted 21 July 2019 - 08:47 PM

It may be related to the server API per @Luke's comments in the LDAP Plugin thread. My credentials work fine in other tools/plugins such as Emby for Kodi but this specific one is giving me trouble when authentication is changed to LDAP in Emby. Thanks!



#72 saltywatermelonsoda OFFLINE  

saltywatermelonsoda

    Newbie

  • Members
  • 2 posts
  • Local time: 08:09 AM

Posted 22 September 2019 - 04:36 AM

is E2PL still being actively developed? basic functionality of playing videos with MPC-HC (1.8.7) still works, but

  • Automatic viewing progress synchronization
  • Resuming in-progress videos
  • Remote control

are now broken.

 

the log shows this error:
 

 

2019-09-20 22:09:28,494 [9  ] INFO  EmbyExternalPlayerLauncher.ServerConnect.EmbyPlayerConnector - Playing "XYZ" from "F:\Movies\1080p\XYZ.mp4"
2019-09-20 22:09:30,515 [22 ] ERROR EmbyExternalPlayerLauncher.Players.MpcHc.MpcHcWebAdapter - Could not get player status.

 

I'm running the latest versions of Emby Server (4.2.1.0), MPC-HC (1.8.7) and E2PL.

 

Thanks!



#73 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 140179 posts
  • Local time: 01:09 AM

Posted 22 September 2019 - 11:59 AM

By now it might need an update.

#74 Bloodred OFFLINE  

Bloodred

    Advanced Member

  • Members
  • 52 posts
  • Local time: 09:09 AM

Posted 23 September 2019 - 08:08 AM

Hello! Apologies for the late reply, my free time was limited lately as I have a few other things keeping me busy.
 
@Elegant - in regards to LDAP not working, what you've found is sadly correct, the problem is the fact that there have been API changes on the server side which don't seem to have been carried over to the client library I'm using in E2PL, I don't think there's much I can do about it from the E2PL code itself, unless the library gets updated and the new version remains compatible with what E2PL is using. For my own Emby server, I decided a while ago to stop updating it (on 3.5.2.0) because I assumed API changes would indeed appear at one point, as they actually have. I don't know if downgrading is possibly an option for you or not, but I guess LDAP might work with an older server version, before the API changes. Again, I don't use LDAP myself though.

@Luke, the library seems to have been last updated 2 years ago, at least there isn't a newer NuGet package that I can see (I'm looking here: https://www.nuget.or...wser.ApiClient/). Will this library ever be updated again, or is it deprecated/abandoned at this point?

 

@saltywatermelonsoda, for that issue I actually have some good news. I have encountered it myself since I use the same version of MPC-HC, along with another issue which sometimes prevented proper progress tracking. This happens because the web server in newer versions of MPC-HC seems to behave differently. One problem is that it's very slow to respond sometimes, so the request from E2PL times out and as such it cannot get the status, as if the player wasn't running. You can already mitigate this by setting the timeout in E2PL to a larger value, such as 10s (so 10000ms in the config). There's another problem with the newer version of MPC-HC sometimes intermittently returning player stopped status when it's not actually stopped, seems to happen sometimes when loading videos or changing refresh rate. I have a new version which tries to address this problem and I will release it in the following days.

 

There are some other issues which I believe might be related to API changes too (live progress updates during playback don't always work properly anymore, but progress should be corrected when you close MPC-HC), not sure whether I'll be able to fix those. Increasing the timeout and the upcoming version should fix some of the functionality, though.



#75 saltywatermelonsoda OFFLINE  

saltywatermelonsoda

    Newbie

  • Members
  • 2 posts
  • Local time: 08:09 AM

Posted 23 September 2019 - 01:38 PM

There's another problem with the newer version of MPC-HC sometimes intermittently returning player stopped status when it's not actually stopped, seems to happen sometimes when loading videos or changing refresh rate. I have a new version which tries to address this problem and I will release it in the following days.

 

 

Thanks Bloodred! think this is also what is happening on my side, except it happens every time with every video i've tried so far. the emby actvity log shows these events on the dashboard (always exactly on the 60s mark):

 

saltywatermelonsoda is playing XYZ.mp4 on E2PL

9/23/2019, 7:15:37 pm
saltywatermelonsoda has finished playing XYZ.mp4 on E2PL
9/23/2019, 7:16:37 pm

 

increasing the timeout to 10000ms and more hasn't changed anything, so i'll keep an eye out for the update.

 

thank you so much for keeping E2PL alive!



#76 Bloodred OFFLINE  

Bloodred

    Advanced Member

  • Members
  • 52 posts
  • Local time: 09:09 AM

Posted 26 September 2019 - 11:03 AM

Here we go, I've released E2PL v1.1.1.0. It's available on the releases page on GitHub:

https://github.com/r...uncher/releases

 

This version brings updates to how MPC-HC status is interpreted and should fix issues with MPC-HC 1.8.7 (and other newer versions). Since these newer versions of MPC-HC sometimes seem to respond very slowly to requests (I don't know why exactly, though it could be happening during refresh rate changes or such), I still recommend increasing the request timeout in the E2PL settings as well. I've set it to 10s on my system and this has cleared up timeout issues in my case. Since different systems may behave differently, the 10s isn't a value set in stone and if you're getting unexpected timeouts in the E2PL log you can try tweaking this value further. Do note that it is possible/normal to sometimes get a timeout when MPC-HC actually finishes playback and closes automatically or if the player is closed intentionally, that's not a problem.


  • saltywatermelonsoda likes this





Also tagged with one or more of these keywords: Emby External Player Launcher, EmbyExternalPlayerLauncher, E2PL, MPC-HC, external, external player

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users