Transcoding options for Plex, Emby, Jellyfin

Suggestions
87

I made an account just to say that I would buy lifetime in a heartbeat if Infuse was somehow able to query Jellyfin to send it a transcoded feed - I often access my library out of home and so usually I can’t use infuse because I rip straight from the Blu-Ray and I don’t have enough upload bandwidth to view those files outside of home.

88

As you can see from this thread going back 2.5 years, this has been a long standing request. We’ll see if it ever makes it in the roadmap… still hoping :crossed_fingers:

Edit: Sorry the original request was posted in May 2019 so we’re looking at 6 years.

89

There are lots of Jellyfin clients that can already do this - not sure what Infuse’s specific bottleneck is for this sort of feature but it would be killer for me.

90

I moved your post to a currently running suggestion thread for this feature.

Don’t forget that you need to click the like button on the first post in this thread to show your support for this suggestion! :wink:

91

I’m not clear why this thread is being combined here. My understanding is that this topic is focused on supporting Infuse App / Client-Side transcoding selection settings (which still would be awesome to have). I feel too many nuanced issues are getting combined here.

However, this issue is related to simply investigating and supporting the correct JellyFin API such that JellyFin actual server (not app level) bandwidth limitation settings are adhered to.

For illustration purposes:

  • Current JellyFin remote bandwidth settings are set to 10mbps.
  • When media is played remotely on all other jellyfin apps, media is transcoded down to 10mbps as designed.
  • It’s believed that Infuse uses the wrong API such that it always plays media at original quality, ignoring server set bandwidth settings.

Hope this helps. For Jellyfin users we want this, please support the below thread:

Thanks!

92

correct, mods are confusing things and assuming they are the same, when they are not.

for jellyfin, i don’t believe people are asking for the infuse client to do any transcoding or offer any transcoding settings. jellyin server handles that, all infuse needs to do is tell jellyfin that it’s either local or remote, which it currently isn’t doing because the wrong API call is being used.

all this falls on deaf ears though as no-one are firecore is interested.

93

Plex is a similar situation – server side bandwidth limits can be set for remote connections which may trigger transcoding. (now finally with HEVC output)

Honestly I’d take any option (honor server limits or give client side settings) for transcoding. But after years of waiting, and seeing other fringe features added, I don’t think either will be considered.

94

Agreed. Server side transcode is what we need, and just have infuse play. This and multi-user have led me to using other options as the kids have limited profiles and use remotely.

95

It seems that there is absolutely no way to tell infuse that I want to use transcoding even if it’s otherwise direct playable? There seems to be a problem that the backing HDD is not fast enough, or something and playback keeps stopping due to it, but can be restarted immediately after but it will happen again and again.

This is a somewhat basic functionality that infuse seems to lack?

Diagnostics code: XMP2X

96

correct

97

Any chance to get transcoding? Remotely Watching / downloading 80GB movies is our of the picture for me on apple tv. Native emby/jellyfin clients are very bad and firecore is so good but is missing this one inportant for us users :sad_but_relieved_face:

98

Don’t forget that you need to click the like button on the first post in this thread to show your support for this suggestion! :wink:

100

While I understand the concept of “likes”, they don’t seem to have much correlation to which features are worked on. There are currently 10 feature requests with less likes than this one that are marked as “planned”. This one has been in the top 20 like-wise for several years now.

101

While number of likes for a suggestion is one consideration for priority of development there are many other factors that also come into play.

If all suggestions took say one hour to develop and implement then the number of likes would probably be the main deciding factor but different suggestions will take varying amounts of development time for programmers. If it’s estimated that internal development time would be several weeks then other suggestions that may be only a day or two would probably come first.

On top of this say you have a number of more detailed suggestions all with an estimated development time of say a week, then you have to look at which one do you have the best chance of not impacting other functions of the software. (Think about the wood puzzle game Jenga ) Then factor in which one will fit your long term development goals.

Then one of the biggest variables, compatibility with Apples guidelines and their operating system updates.

Many users forget that one of the biggest unknowns that devs have to deal with are bugs that creep in or are designed in by os changes or outside APIs will take priority in programming focus.

To be clear, I’m not a Firecore employee nor do I have inside info to what is on the big board there but I’ve been in the software development world and can say that until you’ve seen behind the curtain in the developers actual environment you don’t know what each new feature request may “really” entail.

So while sometimes the suggestions seem to take forever it still helps the devs to see which ones get more requests from the users by the number of likes for each suggestion. It only takes a second to click the like button on the first post.

102

I can appreciate everything you’ve said – I manage a development team myself. And at the end of the day this is Firecore’s product and already worth what I’ve paid for a lifetime license. However having looked at some of the API calls involved (for Jellyfin at least), I think this request is a lot more manageable that it appears, and would dramatically improve remote use – which is huge IMO. Considering the request was opened 6 years ago, I can only assume remote playback isn’t of interest. Or that everyone else is on symmetric gig fiber except me out here in the woods. :slight_smile:

103

I too looked at this and I think the API looks straightforward, but I don’t build Apple TV apps, so maybe there’s some gotchas there. That said this request and related topics have been posted in the forum several times over the years. Here are the threads I could find in chronological order:

Not sure how popular of a request this is compared to all the others, but I did look up one example, Multi-users/profiles:
September 2016: https://community.firecore.com/t/multi-users-profiles (261 likes for the first post, 671 likes within the thread)

Implementation aside, if you compare the two requests, looks like we’ve got another 3 years and 200 or so likes needed :wink:

104

We have really fast download speed but the upload speed is caped by the provider at a very low level. So streaming movies away from home is actually a problem sometimes, especially with high bitrate files :confused:

105

Same for downloading. I’d like to sync files for traveling but I would fit 2 movies on my ipad in original quality. Doesn’t make sense. Emby can download transcoded on the fly files but like I said emby client is bad and jellyfin even worse.

106

It’s a bit frustrating that this hasn’t been acknowledged at all by the developers.

There exists multiple Jellyfin clients on Apple Platforms that will play transcoded media, and in the case of Streamyfin, also download live-transcoded media - a feature that Jellyfin currently doesn’t even support!

These are people developing applications in their spare time with no budget at all. The API should be relatively straightforward to implement, so I am really wondering why we haven’t at least gotten an acknowledgement of the suggestion - considering it’s been active for 5 years now.

This is the one thing that’s stopping me from spending money on Firecore.

107

#preach