Transcoder not working with x265

Not sure to follow you.
How is that linked to my CPU/GPU when I am transcoding H.265 for months without any issue and it is working fine using 1.24.2.4973 but not with 1.24.3.5033.

I understand that I can work with encoding upfront, but what bother me is that it was working fine (and it still working fine with 1.24.2) but the 1.24.3 just break it. I mean, the CPU/GPU is still the same, only the plex version differ.

Got it, thanks for the input then.
Maybe @ChuckPa can elaborate on this, I am kinda scared to not being able to update my Plex ever again to keep the transcoding working. I mean, I don’t understand how a software update can break the fact that my hardware is able to handle this transcoding.

@NohTow

You have , as you are aware, a DS218+.

The DS218+ is equipped with the Intel J3355 CPU

Sep 19, 2021 14:15:59.889 [0x7f62b39bcb38] INFO - Plex Media Server v1.24.3.5033-757abe6b4 - Synology DS218+ x86_64 - build: linux-x86_64 synology-dsm7 - GMT 02:00
Sep 19, 2021 14:15:59.890 [0x7f62b39bcb38] INFO - Linux version: DSM 7.0.41890-0, language: en-US
Sep 19, 2021 14:15:59.890 [0x7f62b39bcb38] INFO - Processor Intel(R) Celeron(R) CPU J3355 @ 2.00GHz
Sep 19, 2021 14:15:59.890 [0x7f62b39bcb38] INFO - Compiler is - Clang 11.0.1 (https://plex.tv e0c29d5827bc4eaaa2ceb882cbeed224b0960173)
Sep 19, 2021 14:15:59.890 [0x7f62b39bcb38] INFO - /volume1/@appstore/PlexMediaServer/Plex Media Server

The Plex NAS Compatibility guide clearly shows the CPU is not capable of transcoding 4K HDR (UHD).

The fundamental difference between the J3355 CPU and the J3455 CPU is that 2160p HEVC HDR capability. Otherwise, the two are the same processor.

Please refer to the long-standing Plex NAS Compatibility guide.

The video you provided is HEVC MAIN 10 (HDR).

“HEVC MAIN” is SDR (aka 8-bit) and within the capability of the J3355 CPU
“HEVC MAIN 10” is HDR (aka 10-bit) and not within its capabilities.

Since your source was downloaded, is it entirely possible the quality was increased without your knowledge ?

HEVC MAIN 10 is not HDR, it’s only the encoding profile. HEVC MAIN 10 can be 8 or 10 bit and can be either SDR or HDR. High Efficiency Video Coding - Wikipedia

Furthermore the integrated graphics on the J3355 are capable of both decoding up to HEVC 10 bit and encoding HEVC 8 bit. It is the same integrated graphics that the J3455 features with a clock speed difference of about 50Mhz Intel HD Graphics 500 (cpu-monkey.com)

I’m not trying to be combative but it seems like this may be a genuine issue.

There were no transcoder changes whatsoever in those two versions.

This is why I am looking at media and not Plex.

mediainfo is telling:

MAIN 10 profile,
10 bit depth.
YUV encoding.

If nothing changed, what changed? :thinking:

General
Unique ID                                : 91096247821023430021208912674033525891 (0x44887FC84B1492CC858BFC3247CC6483)
Complete name                            : New.Girl.S03E21.Big.News.1080p.AMZN.Webrip.x265.10bit.EAC3.5.1.VOSTFR-NoTag.mkv
Format                                   : Matroska
Format version                           : Version 4
File size                                : 509 MiB
Duration                                 : 21 min 43 s
Overall bit rate                         : 3 274 kb/s
Encoded date                             : UTC 2021-05-09 16:27:21
Writing application                      : mkvmerge v56.1.0 ('My Friend') 64-bit
Writing library                          : libebml v1.4.2 + libmatroska v1.6.4 / Lavf58.29.100

Video
ID                                       : 1
Format                                   : HEVC
Format/Info                              : High Efficiency Video Coding
Format profile                           : Main 10@L4@Main
Codec ID                                 : V_MPEGH/ISO/HEVC
Duration                                 : 21 min 43 s
Bit rate                                 : 2 631 kb/s
Width                                    : 1 920 pixels
Height                                   : 1 080 pixels
Display aspect ratio                     : 16:9
Frame rate mode                          : Constant
Frame rate                               : 23.976 (24000/1001) FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 10 bits
Bits/(Pixel*Frame)                       : 0.053
Stream size                              : 409 MiB (80%)
Writing library                          : x265 3.2+35-acc5d16999e2:[Windows][GCC 9.2.1][64 bit] 10bit

I am going to dig deep into this.

I’ll try to get some exclusive time on the machines in the lab to investigate.

I will keep everyone advised.

Until then, please stay at 1.22.3.4973

Hello @ChuckPa,

As you said,

If nothing changed, what changed? :thinking:

That is basically my point here. I am 100% positive that this file (and others I can provide) were transcoded just fine before the update and are now working again. (using 1.22.3)
I mean, files did not change at all (I am manually handling them), the only thing that changed was Plex version, that is why I am looking at Plex and not media.

As an hint coming from someone who did not check the code at all, these files did struggle a bit some weeks ago, but unchecking the disable video stream transcoding box made them work flawlessly. Also, the issue was occurring only when subtitles were on and they forced the transcoding even on players that were direct playing the file when no subtitles was on. Maybe the problem comes from something related.

Again, even with the box checked and subtitles on, the file was playing. It just buffered from time to time. I prefer to have the choice of letting it buffer rather than just having a plain “no you can’t watch this file” message that I can not go around.

I can provide more of these files for debugging purpose if needed. I am just not too comfortable putting these links here, is there another way to send it to you ?

Sorry for the double post but, do we have any update on this @ChuckPa ?

The 1.24.3 is now pushed on the regular download link and PMS is asking me to do the upgrade.
Is it fixed or should I not do the update ?
Thanks.

Hi @ChuckPa
chiming in on thread, as I’m also experiencing a similar issue with transcoding x265 files which were playing fine on Samsung TV prior to 1.24.3.5033. Can play the same file via Plex Desktop.

Have since performed a clean uninstall and reinstall from Ver 1.18 > 1.23.6.488 > 1.24.2.4973 but the reverting and slow upgrade does not appear to have cleared the transcoding x265 files issue… so rather stuck

Plex Media Server v1.24.2.4973-2b1b51db9 - Synology DS2415+ x86_64 - build: linux-x86_64 synology - GMT 11:00
Linux version: DSM 6.2.4.25556-2, language: en-US
Processor Intel(R) Atom™ CPU C2538 @ 2.40GHz
TV Model: QA65Q7FAM, AVPlay version: 1.0, Tizen version: 3, Package version: 5.10.0
recently

Bro I love you, 3 days of scrapping reddit, plex forums and my error logs trying router resets and server reinstalls and it was the cinema trailers the whole time. Thank you thank you thank you. LEGEND. For reference it was any TV outside my local network. If my TV was on lan direct stream and transcodes worked fine but if i hotspotted my tv to external network nothing would play at all. turned off trailers and restarted the app and boom all good.

Tried all the recommendations but did not seem to improve the situation.
Disabled trailers (refreshed metadata), turned off any setting pertaining to subtitles, set CPU to “make it hurt” - reverted all of these except trailers, cos I didn’t want those anyway.

Then under language set subtitle mode to manually AND unticking " Enable local network discovery (GDM)" under Network and it seemed to fix the issue.

Validated a couple of times by toggling the network setting on/off attempting to root cause but then situation became unexplainable / illogical - becuase after the third time of reapplying / reverting the settings, the X265 files still played successfully.

Have also since upgraded to the latest version of plex, and still able to play X265 files. Absoulutely illogical but at least the issue has cleared for me.

Hope this helps someone…

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.