i’m using Infuse to connect to a jellyfin server using direct mode.
i have jellyfin set to limit the bitrate to 8Mbps for remote connections.
when i use Infuse remotely, jellyfin is not recognising that it’s a remote connect so no bitrate limit happens. i’ve sent to the logs to a jellyfin dev and they advised
interpreting the logs as Infuse directly accessing the media, perhaps via the "download" endpoint instead of the playback endpoints. This means there are no checks for "locality", no application of bit rate controls, no checks for client compatibility and transcoding.
can someone at Infuse advise if this is the case?
when using swiftin it does correctly flag that it’s remote and jellyfin applies the bitrate limit, so this would suggest that Infuse is doing something different when connecting to the server.
that setting doesn’t need infuse to support transcoding, it only needs to tell jellyfin it’s accessing remotely by using the correct endpoint.
jellyfin does the transcoding if it knows the client is conenecting remotely. infuse is not using the correct endpoint according to jellyfin dev so it thinks infuse is a local connection, possibly because it’s using the download endpoint when it should be using the appropriate playback endpoints.
considering the thread you linked to is 5 years old i wouldn’t hold any breath on seeing anything happen with regard to that.
the infuse app is essentially useless for remote conections.
Very curious on the response here. Ideal state would be for Infuse to support custom transcoding/quality settings but at the very least, it should support JellyFin server-level forced bandwidth settings that are set at the user or global level.
yes, i’m not sure @james has understood what is being reported here.
the post is not asking to have client side transcoding, it’s about server-side locality based forced transcoding.
from what the jellyfin devs suggest infuse is not using the correct endpoint for playback - if it was then the server-side transcoding would work as expected.
In some testing SwiftFin (also doesn’t support client side transcoding settings) does, however, adhere to server-side bandwidth settings.
Streamyfin does as well (but also supports client side transcoding settings).
Love Infuse and been using it for years but this is an important functionality for me. Because of this, I don’t use Infuse remotely nor recommend it for other remote users.
You probably could get a good number of new subs indirectly from existing users pushing to sign up for Infuse.
Hey @james -
Apologies to pester but would you mind given us your view on this? I feel it’s less of a transcoding overall and more of which api is called. Although I mostly have no idea what I’m talking about in terms of the technical integration but I would assume it’s easier to support server level bandwidth restrictions than app-level custom transcoding settings.
Would love your take on this. Thank you!
the jellyfin dev suggest that the download endpoint is being used rather than the playback endpoint, as the download endpoint would, obviously, not require any remote playback transcoding to take place as jellyfin is being told it’s downloading rather than playing.
it should be using the playback endpoint, which would then allow jellyfin to apply any service side bandwidth limiations as required - it would not require infuse to do anything.
i’m willing to be the “go between” between the jellyfin dev i was speaking to and infuse, but for that to happen i need some contribution from infuse and the will to get this working as it should be.
to re-iterate, we are NOT talking about infuse client-side transcoding, we are talking about infuse using the correct jellyfin endpoint so that server side bitrate limiting can be applied based on whether the client is internal or external to the server.
this isn’t happening, in the opinion of the jellyfin dev, because infuse is using the wrong endpoint - their suggestion being that infuse is probably sing the download endpoint rather than the playback endpoint.
you haven’t answered the question yet though, so not sure why you’d move it to suggestions.
i have asked several times now to confirm what endpoint you are using for jellyfin direct mode to initiate playback.
at ths point i am not asking you to do anything other than answer the question posted.
to confirm, i’m not asking you to add support for client based transcoding (which is what you incorrectly assumed at the start of the thread).
so to confirm what this thread is asking, what endpoint are you using to initiate playback for jellyfin direct mode - “playback” or “download”? if you are already using the “playback” endpoint then infuse is already doing what it should do and i can go back to the jellfin dev to advise.
