Repository navigation
Replies: 4 comments 1 reply
|
Great write up and feature request. |
|
Thanks for the detailed write-up. It pointed straight at the problem, which turned out to be on Ether's side, not in PM4K or CoreELEC. What's happening. I read PM4K's playback code (plexnet in pannal/plex-for-kodi) to see exactly what it asks the server for:
Ether had no Fix (v0.3.3):
How it was checked. I replayed PM4K's exact request sequence against Ether with an HEVC + EAC3 MKV: the decision, then the direct-play Part with seeking (range requests), then |
|
I tested v0.3.3 (commit b72b51b) on my Ugoos AM6B (CoreELEC / PM4K 0.4.4) and have two major findings (full ether-support.zip attached): start.mkv works! If I uncheck Allow Direct Play in PM4K settings (forcing PM4K to use /video/:/transcode/universal/start.mkv), playback works immediately.Why default playback (Direct Play) still fails: Because v0.3.3 now enables Direct Play in /video/:/transcode/universal/decision for PM4K, PM4K tries to Direct Play by default instead of calling start.mkv. However, Kodi's requests to the Part URL return HTTP 404 in 0 ms (dbQueries: 0): 18:38:46.084Z: GET /video/:/transcode/universal/decision -> 200 OK 18:38:46.209Z–18:38:46.434Z: Kodi (client: plex) sends two HEAD requests and two GET requests to /library/parts/4000975460010001/1793816042/ -> all four return 404 (85 bytes, 0 ms, 0 dbQueries). It looks like either the Part key returned in the metadata/decision XML for PM4K is missing a trailing filename segment (ending in /1793816042/ instead of /1793816042/file.mkv), or Ether's router for /library/parts/:partId/:timestamp/ isn't matching a trailing slash or HEAD requests. |
|
Thanks for testing v0.3.3 so quickly, and for the support bundle. It showed the exact failing request. Good news first: Why direct play still failed. It's on Ether's side, and your second guess was right. PM4K builds the direct-play URL from the part key Ether sends,
So Kodi requests Fix (branch Until 0.3.4, your workaround of turning off Allow Direct Play in PM4K is the right one. After updating, direct play should start straight away with it back on. Let me know if it doesn't. |
Uh oh!
There was an error while loading. Please reload this page.
Hi,
First of all, thanks for developing Ether. It's a really interesting project.
I'm having a playback compatibility issue when using Ether with PM4K (Plex for Kodi) on a Ugoos Android TV box running CoreELEC.
My setup:
Ether: https://github.com/braedonsaunders/ether
PM4K: https://github.com/pannal/plex-for-kodi
CoreELEC: https://github.com/pannal/CoreELEC
Hardware: Ugoos box
Playback device: Kodi / PM4K
Ether works perfectly when accessed through the official Plex app on my Apple TV.
However, when accessing the same Ether server through PM4K on my Ugoos/CoreELEC box, playback doesn't work.
I've been advised that this could be related to a difference in how Ether delivers the video stream and how PM4K handles playback.
My understanding is that Ether is delivering an HLS stream, whereas PM4K/Kodi may be expecting a direct-play media file (such as an MKV), or may have limitations with the particular HLS streaming format being supplied.
Does Ether use HLS by default when communicating with Plex clients, and is there a way to offer a conventional direct-play stream instead?
Could there be an issue with the Plex client capability negotiation between Ether and PM4K?
Would it be possible to add an alternative playback method or stream format that is more compatible with Kodi/PM4K?
Is there a way to force Ether to provide a direct-play MKV (or another Kodi-compatible format) rather than HLS?
It would be fantastic to get Ether working with PM4K and CoreELEC, as this would open up compatibility with a lot of dedicated Kodi media-player setups.
Thanks!
All reactions