DirectPlay Doesnt work. Transcoding does #93
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I have a really weird issue.
Got this set up and working in browser and using the native web player in the jellyfin app. In the admin dashboard I can see these streams are transcoding. They playback and work without much juddering.
However, anything that can direct play
Jellyfin Windows App
Jellyfin for WebOS
Jellyfin Android app when set to the integrated player (ExoPlayer)
When i try and start these streams they endlessly buffer before giving a stream error and exiting.
WebOS also won't load the guide that works fine in the browser
Error log
In the logs, the stream path starts with
http://172.20.13.1:8096
:Some HTTP traffic seems to target
http://jellyfin.server.com
:Is this address and port reachable from the client? If not, configure your Jellyfin networking correctly in the Admin Dashboard under
Advanced
>Networking
>Firewall and Proxy Settings
>Published Server URIs
.For example:
Jellyfin is behind a reverse proxy with SSL offloading, does this adding need http requests to work?
-------- Original Message --------
On 28 Mar 2024, 15:04, Kevin Jilissen wrote:
Configure it with
all=https://....
if your reverse proxy uses SSL.changed that - error now shows same but with the
https://
pathnot sure if it helps, but direct play for normal media files hosted on my fileserver has always worked
Also, if it was networking, wouldnt the same issue happen when transcoding files?
UPDATE:
Changing the advanced networking broke transcoded streams as well
Update 2
I disabled the all=https://jellyfin.server.com in order to get transcoded playback to work again.
Thought i would add the logs from a stream that works - the only difference is its being transcoded now as im using the browser on the same device that wont work above
most of these logs are about the ffmpeg transcode itself, but nevertheless - playback is flawless and works without issue but only when iptv is transcoded - this is baffling to me. No other files on the server do this, and the fact it works on the same device when watched through a browser is so weird. Sadly I cant use this as a workaround for devices like smart TV's
Some observations:
all=https://
did fix your networking, as now the restream is actually opened using direct play:all=https://
, so somewhere is still something tricky going on in your networking setup.HLS
:19dc465fb0/app/src/main/java/org/jellyfin/mobile/player/queue/QueueManager.kt (L221)
This appears to be an app bug, possibly also in the Windows and WebOS clients.
Related issue: https://github.com/jellyfin/jellyfin-android/issues/1277
Ah, interesting, I didnt spot that, good to know. If the playback not starting for directplay was FFMPEG related, any reason that the Networking change also broke transcoded streams?
The jellyfin host can ping and resolve
jellyfin.server.com
so im guessing its ffmpeg having the https specifically causing the issue.For Clarity, the issue is also present on Jellyfin for WebOS (The LG Homebrew channels installation)
Thanks