in jellyfin my server is reporting “The source file is entirely compatible with this client and the session is receiving the file without modifications.” even when i’ve set playback on the phone from original to 720p 2Mbps (the original is 4K 25Mbps)
I’d expect infuse to send a request to jellyfin to transcode at the server-side and then send the transcoded file to infuse, however it looks like the transcoding is happening on the device? is this correct? if it is then this is terrible implementation.
I have a jellyfin server capable of hardware transcoding and that’s where i want the transcoding to happen.
You can open the HUD to view details about the actual video/audio streams that are playing in Infuse. This will allow you to confirm whether transcoding is active or not.
We can try and look quirks with the dashboard reporting on the server.
This screenshot is from a 4K Atmos sample, so you can clearly see that transcoding is active.
indeed, but jellyfin is not reporting it as being transcoded, it reports it as being direct played, so clearly there is an issue somewhere.
I believe this is linked to the fundamental issues in the way that infuse connects to jellyfin.
i had previously reported that infuse always tells JF that it’s local even when it’s not, resulting in server side transcoding not happening when jellying sees the client as being remote.
this issue is almost certainly related to that - and JF support had suggested that you are using the wrong endpoint to trigger playback.
I’ve been dreaming of transcode options in Infuse for years, but now that it’s here I seem to have issues.
Basically I have two Emby servers, each setup with (NVIDIA) hardware transcoding which works reliably (locally and remote) via Emby apps and Web. I have plenty of outbound from each server (300-500Mbps) and can direct play anything reliably. Yet transcoding in Infuse seems to work maybe 1 out of 100 tries. When it fails I see this:
Even though I see Emby fire up an ffmpeg transcoder and from the logs that seems normal/healthy. On the Infuse end I just get the spinner until that error message.
During the (very) rare event that choosing a transcode option “works”, it also seems odd. On the Emby side it appears to be direct playing:
And on the Infuse end the “stream speed” seems to confirm this even though the “video” section seems to think it’s the 1280p 1Mbps requested. (this is after it’s been playing a while, so I’m thinking it’s past the initial buffering?)
After playing with it further, it seems to be certain titles that have the 1 in 100 success rate (although there seem to be a lot). Haven’t been able to figure out the pattern yet though (DV, HDR, etc) With anything that does work, I still see direct play on the Emby side.
Yes, I notice that as well (direct play showing in Jellyfin as well), although it definitely seems to “work” more reliably than Emby. Should probably test the outbound bandwidth of the stream to see if it’s truly transcoding, although it would be quite odd to report directly play if it was.
