2024-01-31, 04:23 PM
(2024-01-31, 02:44 PM)tmsrxzar Wrote:(2024-01-31, 01:17 PM)slippyC Wrote: I don't think having to remove ffmpeg to keep it from transcoding is a good option.
the simplest solution to never transcoding is to use a client that supports everything, all my clients 'direct play' everything, the ones that wouldn't got returned
the issue here is that you want to run on a server that can't transcode AND a client that doesn't support your media
convert your media ahead of time or upgrade 'something' in your setup, being a media server jellyfin's ability to transcode to clients is at least 1/3 it's entire point of existing
Well if they are going to force you to transcode then why have the option in the first place? It wouldn't happen to be because they know that the server isn't always going to run on a beast system? Like I said, this would probably run on a Pi and would be a cool little server setup for a media server. You need to take your fanboy rose colored glasses off and see that it's an actual issue. It is a deficiency in the way the software works. If they want to force you to transcode then don't have the setting to disable it.
I'm COMPLETELY fine with everything not being compatible. What I'm not ok with is having the feature to disable something, yet it doesn't disable it.
Number two, I can not control what format a "Live Stream" is in. All of my local media is compatible with directplay(or at least that I'm aware of and if it wasn't that is on me). The only option is basically not use "Live Streaming". That knocks off half of the use of the server. So what now, use multiple apps or just use some other single app solution like Kodi? If that's the case, then why the hell even use Jellyfin?
If I was using a m3u based IPTV app and my device didn't support the codec what would it do? It just wouldn't play the thing.
And that is fine.
If they want to force transcoding then remove the feature to disable it.
It's really just that simple...
I suspect that isn't what they want though, since the setting was initially put in there. And...that get's back to there being a problem with the software and it not following the actual settings "they" implemented.