Q80D (2024) Transcoding Unnecessarily

[IndicatorFluid 5]

Hi, @SamES

I have another "unnecessary transcoding" issue. This happens with both h264 and h265 4096x2160 files, but not 3840x2160.

I've already tried:

• playing the same files from USB - works OK, and both files go without issues
• playing via DLNA - works OK, and both files go as above which is strange on second thought because I can't see h265 in the mp4 in DLNA profile for the Samsung Smart TV
• updating the TV app to beta 1.8.8  (was 1.8.0 from the Tizen store) - no help
• deactivating transcoding completely in Server -> User settings - works OK again, both files go on the TV but then there'll be a problem on mobile phones, I guess

TV specs (QE65Q80DAT) indicate it should play 4096x2160 files OK which I guess gets confirmed by playing it by different methods.

I'm assuming from the ffmpeg log that the reason for transcoding is the size alone. By "working via DLNA" I mean there's no ffmpeg log for these sessions. The same applies to the deactivated transcoding option.

The server is 4.8.8.0 running on MacOS 12.7.6 Monterey.

It is not a huge issue, it's not a deal breaker and I'm still going to go with the Premiere option for other features anyway. Just my i5 4th gen can only do h264 transcoding so I'm wondering if there's something I can do, encode it (in HandBrake) in a different way or set something else I haven't tried yet. I can always go with 3840 size which is not trigging transcoding BTW, the same settings just scaled down to 3840x2160.

ffmpeg-transcode-23b45996-a07b-48af-9e6b-3b9e59cb1fff_1_h265-4096x2160.txt ffmpeg-transcode-def4edf7-7528-491b-b8de-33741a57e77d_1_for_h264-4096x2160.txt

[IndicatorFluid 5]

Sorry for another post, it seems I can't edit my own post. The Samsung firmware version is 1120

[SamES 962]

Yes, some models now support 4096 for some formats on 4K TV's.  I'll have to try and find the simplest logic to support this.  

[Luke 38863]

@IndicatorFluidare you still seeing this with Emby Server 4.8.10? If so then please attach an ffmpeg log based on that as well as the corresponding main emby server log file. Thanks.

[IndicatorFluid 5]

@LukeHi!

Yes, it still does it. Here are files. This is not tested on the same files as before, can't find them anymore I'm just avoiding 4096 wide files these days, they are just not worth the hassle, but I've found one to test it

I'm not sure now if I still have the same Samsung app version, though. It may have expired and I may have had replaced it with the Tizen store one, whatever they have now on the list.

For some reason there are two embyserver logs for today. Both attached.

embyserver.txt embyserver-63872026794.txt hardware_detection-63872026901.txt ffmpeg-transcode-834a0c0c-fdd5-44e0-b209-25fedd3a7a46_1.txt

[visproduction 208]

Quote

TV specs (QE65Q80DAT) indicate it should play 4096x2160 files OK which I guess gets confirmed by playing it by different methods.

That TV model shows up online as having only 3840x2160 resolution.  Perhaps any playback of 4096 width has to be upconverted.  The fact that it plays back 4K with 4096 width is nice, but it is not apparently the native resolution of that TV.  Perhaps that explains the transcoding issues for 4096 widths.

[FrostByte 5202]

It's only being transcoded though because that's what the app is requesting from the server.  The test was when IndicatorFluid turns off transcoding at the server it plays fine with direct play.  He also tested via usb and played it with the TVs internal video player just fine.  So, the TV can handle it.

Looking at the charts on the Samsung devs page what he needs is for the app not to request a transcode for all 2024 STANDARD and PREMIUM model groups when the resolution is 4096x2160.  For all 2024 BASIC model groups the app should still request a transcode when playing that resolution.  Otherwise, he needs to keep flipping the transcode setting on the server if he wants it to direct play.

Here's a link to the 2024 sets and the resolutions they support:

https://developer.samsung.com/smarttv/develop/specifications/media-specifications/2024-tv-video-specifications.html

 

 

Edited January 9 by FrostByte

[visproduction 208]

IF,
That Samsung TV native resolution is 3840x2160.  I think it upconverts to play back 4096 width and that may be why it triggers a transcoding.  Your spec that says it plays back the 4096 is correct.  But that does not mean the native pixel count is 4096.

see: https://www.displayspecifications.com/en/model/bc6c3971

[SamES 962]

It can do 4096, but the client is limiting it to 3840 in some cases. It should be fixed in the next release

[IndicatorFluid 5]

My words exactly, FrostByte. Even if the TV can't actually display 4096x2160 it clearly can handle it, maybe by downsizing it on the fly – it doesn't mater. Actually I attached a screenshot of the relevant  table and I'm pretty sure the TV I have is the PREMIUM model.

Unfortunately I can't locate it on this list of Samsung models classification. This TV was bought in Currys and I guess they have their own model numbers so people can't just compare their offer with competition too easily or, they just get their TVs on  special order from Samsung and Samsung is so ashamed of these models that they don't even mention them

Jokes aside I'm assuming it's Q80D model and as such it should be a PREMIUM type. @visproductioncould you point me to any source stating otherwise?

[IndicatorFluid 5]

Thanks visproduction.

[FrostByte 5202]

I can see that the TV may be down scaling it automatically, but still if the app can be changed to not trigger a transcode that would be best.  I would much rather have a downscale done at the TV than a transcode by the server if possible.

[Luke 38863]

Please try the new 1.9.6. It should be resolved on the local network with the quality setting set to auto.

[IndicatorFluid 5]

@LukeI'd like to confirm that after updating the TV app to 1.9.6 from USB stick the same 4096x2160 file didn't trigger transcoding and just played on TV. No ffmpeg log was generated, the server log attached, the end of the log is relevant.

Now, on a side note, the quality of the image was terrible, it seems that the TV has problems with the file, but this is in no way emby's fault or flaw. It's possible that the file is faulty (I lost my good files I used originally to test the playback). so I hope to create proper 4096x2160 files coded with ffmpeg software and intel's hardware engine and see which one the TV handles better.

Thank you for the update of the TV app guys. Good job! I hope Samsung Okays it soon for distribution because I think the sideloaded app disappears after some time, doesn't it?

embyserver.txt

[FrostByte 5202]

54 minutes ago, IndicatorFluid said:

 

 hope Samsung Okays it soon for distribution because I think the sideloaded app disappears after some time, doesn't it?

 

It doesn't really disappear; it's more of a 30-day time bomb which gets inserted at compilation.  If Samsung doesn't approve it and get it uploaded in 30 days, then you will have to look for a newer usb version.  Or, when it expires just go back to the store version at that time and wait for Samsung to approve the update.