Issue with Remuxing on New Jellyfin

[RestaurantMarsupial]

Hello, not quite sure how to title this. Not fully certain if it really a "bug" or just me misunderstanding how Jellyfin works. I'm also not really sure if this is new to the updated Jellyfin or if it's just an intermittent issue and I'm noticing it now.

I've just updated to the new Jellyfin (10.11.0). My setup is basically that I just have files on my computer, and I run them on the Jellyfin app on my SmartTV connected via Wi-Fi (I've checked multiple times and I consistently get ~200Mbps download, so I think that should be fine). 

For a while, I thought I understood that Jellyfin won't play movies with certain audio formats, so I Remux them myself to change them to a 640Kbps AC3 format. However, I've noticed now that movies I WOULD expect to play "direct" (and have in the past... not the exact same files/movies but what to my understanding are essentially the same) play "Remuxing on the fly" (Dashboard info says: Remuxing
The media is in an incompatible file container (MKV, AVI, WMV, etc) but both the video stream and audio stream are compatible with the device. The media will be repackaged losslessly on the fly before being sent to the device. Remux uses very little processing power with a completely lossless media quality."). This would be fine but it seems extremely unstable/laggy on my end. The playback info says both audio and video are being streamed "direct". 

So my question is about what determines why files are played like this. I am almost 100% certain I have previously played .mkv files and had them streamed "directly" as opposed to remuxed (I'll keep looking and see if any currently play like this). Is this some setting I've changed that I haven't understood? Or, alternatively - is there some way to get these files to play smoothly and well even if they are remuxing - that would be a completely suitable alternative as well. I just watched something that said it was remuxing, but it played... OKish. It was smooth once it got going but was unstable - it crashed towards the end of the film and it seemed it would crash about 50/50 when I tried to fast forward or rewind the movie. I've noticed when I am playing something remuxed like this the disk the film is on will have very high usage, so presumably that is something to do with it. 

Also noticed it can take up a lot of room on my C:\ drive (the drive Jellyfin itself is installed on).

I can post logs if you tell me which ones are needed. 

Thanks in advance for any help!

EDIT: Just searching around I found a git post that I believe explains my issue: https://github.com/jellyfin/jellyfin-webos/issues/310

So seems as though I simply have to downgrade? I guess this issue is the cause of all my trouble so it is known about?

[ArneR]

Hi, first of all I want to extend my thanks, you worded this issue better than I would have been able to.

You are correct that this issue of remuxing is indeed caused in 10.11.0, when in 10.10.7 the media played fine.
I spun up a second docker instance on my Truenas Scale server manually pulling 10.10.7 and used the corresponding version of Jellyfin-Tizen and all was well. Jellyfin says the media is fully compatible and is being served without modification.

I don't understand why 10.11.0 behaves this way, or whether the fault lies in the server or the client, but I'd truly like it if I were able to actually disable remuxing as it messes with my anamorphic 576p content that played completely fine on the previous version.
A workaround I found for my anamorphic mkvs is to go to users and disable the following setting: "Allow video playback that requires transcoding".

Strangely enough, unchecking "Allow video playback that requires conversion without re-encoding" does nothing to stop it remuxing, so that have to mean something else then, I don't know.

Due to a bug in the normal build of Jellyfin-Tizen I have to use the 10.11.z build for it to launch and not hang on the splash screen, otherwise I would be stuck on the 10.10.7/10.10.z build, which has it's own issues playing content from a server running 10.11.0.

TLR 10.11.0 is not fit for production, and should not have been released in it's current state.