The background to these Qs is the is ongoing discussion over at avsforum with the HDR support in madvr, in particular the new cli tool for offline analysis of a film. This doesn't seem to play entirely nicely with the use of BD folder rips and it's not clear whether it is one or all of MC, LAV splitter or madMeasureHDR that is causing the measurement data to not be used reliably. There is some detail in the posts around
https://www.avsforum.com/forum/24-digital-hi-end-projectors-3-000-usd-msrp/2954506-improving-madvr-hdr-sdr-mapping-projector.html#post57030428 but basically
- measurements generated by live playback => a measurement file in the BDMV/PLAYLIST directory named after the stream containing the main film
- measurements generated by offline analysis of index.bdmv => a measurement file named after index.bdmv
The measurement data is not used when you play the film in MC in either case. What does seem to work reliably is described in
https://www.avsforum.com/forum/24-digital-hi-end-projectors-3-000-usd-msrp/2954506-improving-madvr-hdr-sdr-mapping-projector.html#post57030670i.e.
- use madMeasureHDR.exe to analyse the index.bdmv
- play the index.bdmv in jriver to work out which playlist entry is the main film (which is now easy because a measurements file is dumped there)
- copy index.bdmv.measurements to PLAYLIST/<streamname>.measurements (overwriting the generated mpls.measurements file)
Now for the questions....
1) any plans to add support for this tool in a similar fashion to audio analysis? it would be a nice option
2) is it possible to get this working reliably with BD folder rips? madshi suggests he is just using whatever LAV Splitter Source tells him the file is.
btw, and as a minor curiosity, I noticed that the MC library entry points at index.bluray;1 which does not exist, the actual file is index.bdmv, and if I edit it to point at index.bdmv then it reverts it immediately to index.bluray;1 . Why does it do this?