Feature Request Generated, a <@&823677075751043102> will review soon. Only Votes cast on the features site will count.
#Support Dolby Vision Profile Metadata
versed jewelBOT
remote schooner
Most used DV profil :
Profil 5 > used by streaming source, DV without HDR fallback (No tonemaping support in plex so can only be watched on a DV compatible device)
Profil 7 > Used in BD, DV + HDR fallback, some release also merge DV metadata to an existing HDR file to create them (Plex handle tonemaping, can be watched on any device)
To correctly id them without running mediainfo you can get that from filename if using trash guides renaming :
Profil 7 should be DV HDR,DV HDR10 or DV HDR10Plus
Profil 5 should be DV alone
you may also find them in PMM :
For profil 7 with plex builder, search HDR true and filters has_dolby_vision
For profil 5 with plex builder, search HDR false and filters has_dolby_vision
serene notch
Hi there!
Couple of things I'd like to add - quick overview first:
- Profile 7 > UHD BluRay (mediainfo: dvhe.07.xx)
- Profile 5 > WEB-DL (mediainfo: dvhe.05.xx)
- Profile 8 > WEB-DL w/ HDR fallback or UHD BluRay P7 to P8 conversion (mediainfo: dvhe.08.xx)
you may also find them in PMM :
For profil 7 with plex builder, search HDR true and filters has_dolby_vision
For profil 5 with plex builder, search HDR false and filters has_dolby_vision
That's not entirely accurate. HDR=true and has_dolby_vision must return profile 7 and 8 since both profiles have HDR fallback.
Profile 8, btw there's a ton out there by now, usually is a hybrid WEB-DL DV w/ HDR fallback. Also, there's tools out there to convert an UHD BluRay P7 to P8 (FEL is discarded), which is why you find more and more x265 UHD BluRay encodes w/ DV (P8) & HDR.
An accurate way to differentiate between 5, 7 and 8 w/ PMM does not exist at the moment.
More so, trash guide's naming scheme will not prevent having Profile 8 files mislabeled - e.g.:
- filename after renaming: Movie (year) WEBDL-2160p DV h265
- DV profile running the file through mediainfo: dvhe.08.06 > Profile 8
That's not the fault of anybody or any tool, rather a good example of what a mess the whole Dolby Vision landscape still is.
OP mentioned device compatibility. This is very understandable, since DV playback across devices still is an absolute mess. Some work better, some worse. Some play back P8 w/o any problems, some don't or - even worse - force TVs in DV-mode but don't pick up the DV metadata (aka fake Dolby Vision, the PLEX app is know for that...). Lot's of devices don't support P7 (the Shield does w/ Maven's Kodi-Build, Apple TV does not, ...). There's loads of discussion around this topic. Just scratching the surface here.
Long story short: The only precise way to differentiate the DV profiles is to really filter by D O V I Profile
Needless to say that I support the feature request 😄
remote schooner
My bad mixed profil 7 and 8
I don't think any plex app support P7 so that leave only P5 and P8 that you can already filter.
serene notch
I don't think that everyone uses the native PLEX app and unfortunately you're still missing the point... 🙂 OP talks device compatibility and therefore it adds value being able to differentiate between 5, 7 and 8. Say you want to apply the 4K HDR overlay to Profile 7 files since you know that your devices do not support Profile 7 playback but Profile 8 plays fine. I don't see another way to properly differentiate aside from D O V I Profile. The request itself is valid, if Sohjiro and team ever deem it necessary to add as a feature is another point, of course.
solemn condor
we actually do have ways of pulling in DOVI Profile with plexapi. We have talked about it and very well might be in 1.20
The issue is just how to differentiate the different profiles
via overlays
serene notch
Heya, that sounds great! Looking forward to 1.20 🙂
Maybe a thought on how to differentiate the profiles. Don't know if it helps or can be implemented. Today we have use_dv: true/false. How about differentiating by template variables in order to be able to choose how/what PMM should do overlay-wise?
use_dv7: true/false-> true (default): apply DV overlay; false: apply HDR overlay (since there's a HDR fallback)use_dv8: true/false-> true (default): apply DV overlay; false: apply HDR overlay (since there's a HDR fallback)use_dv5: true/false-> true (default): apply DV overlay; false: do not apply any overlay (since there's no HDR fallback)
(I need to think about it further if controlling Profile 5 adds any value. Since there's no fallback one could make the case that Profile 5 should always have the DV overlay applied. No option to control overlay behavior required, right?)
Users that don't care, could still have use_dv: true/false to control DV overlays as per 1.19
Another way could be to only add a "5", "7", "8" to the overlay picture. Or some sort of clue as to what DV Profile the file has. It can probably done nicely, I guess. And then have a template variable to control whether or not the overlay should also show DV profile info.
- true: Use overlay w/ profile information
- false (default): Use already existing overlays - no changes required
Just back on the envelope kind a thoughts. Let me know what you think or what might be feasible to do. Happy to further exchange thoughts on that topic 🙂
sinful mica
found my way to this thread and just wanted to say i'm looking forward to this potentially being in 1.20 🙂