Thanks I’ll pass this on!
1 Like
Still incorrect for 4K HDR movies (HDR10, disc rips, no Dolby Vision).
Edit: 1080p Blu-ray rips are the same as 4K HDR. TrueHD is off, dts formats have 2147483647.
Movies with TrueHD & AC3 audio tracks look “odd.” No 2147483647, but the bitrate for TrueHD seems off: requiredBandwidths="293,286,270,245,219,194,43,1 The AC3 audio track is correctly listed with 640 for all values.
Movies with dts-HD & dts audio tracks have 2147483647 for the overall bandwidth and the dts-HD MA & dts 5.1 (lossy) audio tracks: requiredBandwidths="2147483647,2147483647,2147483647,2147483647,2147483647,2147483647,2147483647,567779"
Deep Analysis was also not performed on some movies. Still looking for a pattern for that.
Anna (TrueHD audio):
Anna.zip (15.1 KB)
Jurassic Park III (dts-HD audio):
JurassicParkIII.zip (12.0 KB)
1 Like
1.24.1.4931 fixed the problem with TrueHD & dts/dts-HD audio bandwidths.
Everything looks good in my libraries.
You’ll see deepAnalysisVersion="6" in the XML when the analysis re-runs.
Thanks for fixing this.
1 Like
This was fixed the day after I updated to 1.24.1.493 (with deep analysis=6), but it seems to be broken again. My TrueHD required bandwidths are too low and the video bandwidths include the HD audio/FLAC bitrate, which increases the required bitrate of the video). Only the lossy audio tracks look correct.
This is for the entire library, not just newly added items.
1 Like
Can you share any examples?
I can later today.
I just noticed this isn’t tagged as windows-server, so I might raise a separate issue, as that’s what I’m running on. I had the same issues covered in this thread though.
1 Like
I’ll add the tag. I’m almost certain it’s a cross-platform thing.
In V for Vendetta (4K HDR10), you can see the the TrueHD “requiredBandwidths” don’t make sense (much like FordGuy61’s post above). The HEVC bitrate is actually the sum of the HEVC video and the TrueHD audio bitrates. The HEVC “requiredBandwidths” also has some higher values than the file “requiredBandwidths”, which doesn’t make sense.
You can also see in the 1080p version that, while the FLAC “requiredBandwidths” values make sense, the h264 “bitrate” is the sum of the actual h264 bitrate and the FLAC bitrate. The h264 “requiredBandwidths” values make sense though.
In Arrival (4k HDR10), you can see that the DTS-HD “requiredBandwidths” are correct, but the bitrate is set to the core 1536kbps value. This also adds the DTS-HD bitrate to the actual HEVC bitrate for an incorrect HEVC bitrate value. The “requiredBandwidths” values do seem to make sense for all the tracks though.
Examples.zip (4.2 KB)
1 Like
Agreed. TrueHD analysis still seems off - that’s way low. I’ll check some of mine.
Huh.
The overall file bitrate seems right. It matches ((size/duration)*8).
I wonder if the per-track bitrate values aren’t really averages. Maybe it’s an ffprobe result or something. I’m curious to extract some individual tracks to do the same ((size/duration)*8) math on them.
Or if they are averages, maybe there’s something like Simpson’s Paradox going on to explain why they can’t be summed.
It seems that the deep analysis isn’t always being performed on all files. It also seems to change (revert?) if a manual “Analyze” is performed.
The biggest inconsistencies I see are with my multiple version movies, as typically one version reports the correct values, but the other doesn’t.
It’s there a way to trigger files so that the nightly runs deep analysis on them? I just want my bandwidth reported correctly so remote playback decisions are accurate.
I haven’t noticed this. Can you describe the steps to reproduce?
Interesting, I’ll test this.
Deep Analysis can be initiated from the CLI:
./Plex\ Media\ Scanner --analyze-deeply -x --item 35193
I was aware of the manual CLI Deep Analysis. So there’s no way to put an item on the “to-do” list other than remove and add?
As far as reproducing the Analyze issue, just select “Analyze” from the “More” (three vertical dots) menu and look at the XML. Here is one of mine before (Deep_Analysis.txt) and after (Manual_Analyze.txt)
Deep_Analysis.txt (6.4 KB)
Manual_Analyze.txt (6.4 KB)
Note the ‘bitrate’ value of the video has increased (for both versions) to include the lossless audio bitrate. The required bandwidths haven’t changed, but this value is what I see on my dashboard, so I assume that’s what’s being used to determine it’s bitrate. This is also what I see when I first add video with lossless audio prior to deep analysis being run.
I’m curious about how scheduled tasks work too. I’m not aware of any way to inspect or interact with scheduled tasks.
If manual Analyze is producing incorrect results and un-doing the work of Deep Analysis, that sounds like a bug to me. I’ll try to reproduce.
@FlaTechNole21 did you see this?
Others are reporting that it has addressed the 2147483647 issue for them. I haven’t tested.
Yes, I did and was thinking about trying it out. Maybe this weekend when I have time.
1 Like
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
