There may be 2 reasons why Avatar is transcoding.
One is that it uses the PGS subtitle format that is not supported on that TV but for most renderers that should not prevent it from playing and I don't think UMS will decide to transcode because of this.
The other reason is it uses the TrueHD audio format that is not listed as supported in the manual so has not been added to the conf.
Try playing from the #--TRANSCODE--# folder and choose "No transcoding" to see if the TV will actually play this properly. If it does then I can tweak the conf to add those formats.
(if you do not see it, enable "show the #--Transcode--# folder" in the GUI on the navigation tab, in the web GUI it is in the "virtual folders/files" section)
Your network speed to your router probably won't be the speed to the TV as manufacturers won't use expensive Gigabit ports on TVs so will be limited to far less than 100Mb/s depending on how much money they want to save on the port. For a wired connection 17.664 Mb/s is much better than the 2mb's on wifi but still seems slow. Maybe something is interfering with the speed test on your computer or your TV is just not responding quick enough to the ping.
A better way to measure the speed will be if there is an app on the TV to do it but not sure there is any available. If there is a web browser on the TV then you could use OpenSpeedTest running on your computer to do it. More info in this
video. This should give you a better idea if the measurement in UMS is wrong.
I don't have a graphics card that is able to do encoding so I don't exactly know what settings to use but try one of these.
I'm guessing you will need to use "h264_nvenc" for "AVC/H.264 GPU encoding acceleration method"
- Clipboard Image (4).jpg (128.04 KiB) Viewed 3417 times
and make sure GPU acceleration is turned on (it shows it off in your settings)
- Clipboard Image (5).jpg (13.92 KiB) Viewed 3417 times
Another thing I just remembered is setting the max speed to 0 would break all the web settings due to a bug.
I don't know exactly which version this appeared but I found it while testing the V14 beta a while ago and I don't think the fix got included into the main branch.
From what I remember it would prevent the web settings to actually load your settings and would not save if you change anything.
Just in case set this back to 90 in the old GUI if you are using a wired connection, or 30 is recommended on wifi.