Radarr and FileBot are both highly customizable when it comes to naming and organizing your media files. The FileBot format engine is programmable and can mimic any Radarr naming scheme to any degree of 1:1 accuracy. However, the examples below prioritize simplicity over 1:1 correctness.
It seems that Filebot's {hdr} binding gives different results than Radarr's {[MediaInfo VideoDynamicRangeType]} binding. If a file has both DV and HDR10, Filebot's {hdr} returns only DV, while Radarr returns DV HDR10. Is there any way to more closely replicate Radarr's behaviour?
brijazz wrote: ↑22 Feb 2025, 14:36
If a file has both DV and HDR10, Filebot's {hdr} returns only DV, while Radarr returns DV HDR10. Is there any way to more closely replicate Radarr's behaviour?
e.g. if hdr is Dolby Vision then print DV HDR10 instead:
Do you mean Dolby Vision with HDR10 fallback as opposed to just Dolby Vision? The code { hdr.replace('Dolby Vision':'DV HDR10') } simply replaces the text Dolby Vision with DV HDR10. No more. No less.
If you mean to add a DV+HDR10(Dolby Vision with HDR10 fallback) marker for files that have Dolby Vision with HDR10 fallback then see {hdr} binding for example code:
Yes - I'd love for the {hdr} binding (or some equivalent instruction) to be able to output "DV" if only DV is present and "DV HDR10" if both DV and HDR10 are present. I'll look at the second example you posted, that seems like it will do the trick.
Please read the 
Do you mean Dolby Vision with HDR10 fallback as opposed to just Dolby Vision? The code { hdr.replace('Dolby Vision':'DV HDR10') } simply replaces the text Dolby Vision with DV HDR10. No more. No less.