Hello,
i’m having a black screen on chrome (different OS, different PC).
Tested with 1080P or 4K HDR file => same result, sound is ok, but black screen
Fixed by changing
uncheck: “Use alternate streaming protocol for video playback” - found in Settings > Web Player > Debug
small feedback here with the common lookups from here, all fine with the 1.41.1.9065 build
tested in Browser, all transcoded fine with hevc and colors all matched 
about DVR recordings with enabled encoding … weird result 
4 testruns with the same broadcast
h264_NO > no transcode, direct …
hevc_99, 50, 1 … while 99 (Standard) should be highest, result
hevc_50 had ~ 15 mbit, hevc_99 ~ 10 mbit, hevc_01 ~ 8 mbit
if this scale using a CBR value … cant follow it
just as feedback about recording setting
@alturismo do you still have the logs from your experiment?
What that setting does depends on your hw device. If your device supports rate control it scales between the high and low bitrates for the resolution. If it does not it scales between qscale values of 15 and 25.
as i dont know which specific one, here is the package
cant follow the rule actually, either way … its a weird result to me
if bitrate is taken for recordings (cbr i assume) then the results should be different, if qscale is taken … also, at least in my logic.
now i see plex setting
01 > lowest
99 > medium
50 > highest
but even lowest 01 is more then factor 2 from source in size, almost factor 2 in bitrate, not a issue to me … just wonders me what setting you use as its not the expected result (to me )
but im encoding after my comcut seperately anyway, so not my intention, but i guess there will be more questions coming up with these results …
I’m not sure if this is related to the preview build or not, but I have a HDHR EXTEND, but I do not use the built in Transcoder, I use tdarr to reencode the MPEG2 to HEVC, and then I send a scan request to Plex after the file is converted from .ts to .mkv. Plex identifies the new file properly, but it does not analyze the new mkv file for ads automatically. I always have to click analyze afterwards. Should it not automatically scan for ads ? I do have ad detection turned on for the library. It does properly detect ads before it is re-encoded to HEVC.
Hopefully they will add “Generate Ad Detection Markers” in the Library settings like we have for Detecting intros and credit markers.
that’s already there, which is why I’m noting that it isn’t working…
I actually think that was included with the preview build from the start, at least based on folks responses in this thread while testing.
@vertigo235 I have no idea why that would happen, i’ll add it to the known issues list
So I’m getting the “Chrome Manifest” error with HEVC but it’s really odd.
v130.0.6723.19 with File #1 works perfectly fine.
v130.0.6723.19 with File #1 fails immediately with “Error code: s4032 (Manifest)”
Same Chrome version on both machines. Same Chrome flags related to video on both machines. Only difference is one is LAN and one is WAN.
Both machines have similar AMD iGPUs and currently running v24.9.1 drivers.
@Kermee which pms build are you using?
@alturismo I attempted to reproduce your results and found that 99 resulted in 20Mbps, 50 resulted in 15 mbps and 0 resulted in 8mbps. Can you re-try your 99 test?
yep, tested again, i guess i know where the issue is, interlaced (real) is causing differences, depending on encoding.
now it worked out as expected (at least in your setting), ~ 10, 15, 20 mbit … which are way too high btw for 1080 broadcasts, you have ~ 4 - 12 mbit h264 1080 live … so hevc should be way lower, personal oppinion.
here the output mediainfos from these 3 files
test2.txt (12,3 KB)
here the mediainfos from today morning incl. original (h264)
test1.txt (12,8 KB)
but i guess where the differences came from, wrong interpreted interlace … once correctly encoded to 25p, 2 x wrong encoded fps, thats where the diff came from.
so overall, most common it should be ok, i would think about your start / end bitrates …
Maybe that’s the issue then? But it is generated when DVR Recordings are added, I know that much.
@vertigo235 I have been unable to replicate markers not being generated for hevc dvr transcodes and have found no where in the code which would affect that setting. have you been able to repeat this behavior multiple times?
It looks like it might be related to plex thinking it is a new file.
ie. Adding new media to the library, does not trigger ad marker creation as it is added, and there appears to be no setting to enable this?
I can’t do DVR Transcodes, that was another thing I asked about earlier, my HDHR identifies as an HDHR Extend, and plex only allows me to use the suboptimal built in encoder.
And yes it seems to happen every time.
Keep in mind, that I am transcoding the MPEG2 .ts file into HEVC .mkv file, outside of plex. The new file is identified after scan, but it doesn’t trigger ad markers immediately. This is my issue.
