www.makemkv.com

x800, Chromecast and C8 images are the only devices that don't show any issue with this pattern. Your oppo should look the same, curious about ATV...

All the image are from a device connected to the C2
C8 pic is from plex internal player. (C8 is no longer calibrated and probably over track)

Took me forever to get some ok (not fully representative of what I see) shots with my old iPhoneX (RAW -> JPG):
https://slow.pics/c/7Nmrryfs
- atv22-inf752-E7.JPG: Using Infuse 7.5.2 (auto), ATV4K 2022 with LG OLED E7
- oppo-E7.JPG: Oppo player accessing pattern file over SMB, LG OLED E7 (nice to know it supports P8)

I think that Infuse and/or ATV processing lacks proper colour space conversion between P8 and P5 (expected), initial quick observations without reading yet the S&M page. A thorough analysis requires reading & understanding that link as well checking the on screen image not the camera shots.

- Top row edge rectangle different circle colours
- Surrounding rectangles different colours
- Colour space conversion, red row has a solid 1/3 patch in red
- 3rd row of rectangles different colours
- Y Low, Cr low clipped

PS: the S&M pdf says no DoVi test patterns, how did that multi pattern become DoVi P8 ?

interesting, thanks man.
crazy how every device behaves differently, even in TV-LED when the TV is supposed to do everything.

^^^ I wouldn’t call my camera shots anything worth much until I have a better capture device, learn the test pattern and check everything with my Oppo, which as we know can set to either player or TV led. That brings me to an earlier Q I had, what “device” do you use to capture screenshots in your media chain ?

I wonder how do any of those color space conversion and other differences contribute to when watching a converted UHD rip P7 (Mel) to P8 (dovi_tool) to Infuse (ATV P5 or P8). I did process few scenes from two movies, it’s hard subjectively to find anything that stands out unless one can take screenshots or quickly switch between Oppo & ATV (which is like 15s…)

aboulfad wrote: Mon Apr 24, 2023 11:27 am what “device” do you use to capture screenshots in your media chain ?

with a DLSR camera, you can lock the auto-exposure and all the other settings.

did a bunch of comparisons this way on my youtube channel.

RESET_9999 wrote: Mon Apr 24, 2023 12:13 pm with a DLSR camera, you can lock the auto-exposure and all the other settings.
did a bunch of comparisons this way on my youtube channel.

Thank you, I thought you had an HDR capable capture device I'll borrow a DSLR & try. My 2017 LG E7 internal player didn't play that pattern in DoVI P8 (mp4->HDR, ts->spinning wheel), that could have been another source.

aboulfad wrote: Mon Apr 24, 2023 12:38 pm
Thank you, I thought you had an HDR capable capture device I'll borrow a DSLR & try. My 2017 LG E7 internal player didn't play that pattern in DoVI P8 (mp4->HDR, ts->spinning wheel), that could have been another source.

I you mean how to capture the PQ signal of a device? Sure, you can do that with any capture card but you're testing the player LLDV this way.
TV-LED cannot be captured since the final PQ image is generated by the TV and not the player.

The shield red push and other content have been tested this way in this thread a while ago( with the shogun atomos). I don't think the multi-pattern ever been tested this way though.

Hello everybody!!! mp4muxer.exe New version, I make commands:
C:\Users\Legosoff>"C:\Program Files\Dolby Media Encoder\resources\dee\mp4muxer.exe" --input-file C:\Users\CinemaHD\Desktop\SUPER_8.hevc --dv-profile 8 --dv-bl-compatible-id 1 --hvc1flag --input-file C:\Users\CinemaHD\Desktop\English.aac --media-lang eng --track-name R5 --input-file C:\Users\CinemaHD\Desktop\Russian.aac --media-lang rus --track-name Original --input-file C:\Users\CinemaHD\Desktop\subtitles.xml --media-lang rus --track-name R5 --cover-art C:\Users\CinemaHD\Desktop\cover.png --output-file C:\temp\out.mp4
mp4muxer.exe: ERROR: Images specified with unsupported file format. Images only supported for CFF (.uvu) files.

help:
--mux-flags arg Set the multiplexer flags.
--frag-flags arg Set the fragmentation flags.
--track-flags arg Set the track header flags.
--output-file arg Specify the output file.
--output-format arg Specify the output file format.
--dash-profile arg Specify the MPEG DASH profile.
--hls-profile arg Specify the HLS profile.
--validate arg Verify conformance to the output format.
--overwrite Overwrite the output file even if it already exists
--hvc1flag Set the HEVC track's sample entry name to 'hvc1'
--dvh1flag Set the DoVi track's sample entry name to 'dvh1'
--avc3flag Set the AVC track's sample entry name to 'avc3'
--ps-present-flag Set the parameter sets ( AVC: sps/pps; HEVC: vps/sps/pps) present in the sample and
sample entry.
--ps-only-sample-entry-flag Set the parameter sets ( AVC: sps/pps; HEVC: vps/sps/pps) only present in the sample
entry.
--input-file arg Specify the input elementary stream file or directory.
--input-format arg Specify the format of the input elementary stream file or directory.
--media-lang arg Set the 3-letter media language of the media.
--ref-flag Set the reference flag to the input ES file for segment alignment checking.
--track-name arg Set the value for the 'name' field in the `hdlr' box.
--track-groupid arg Set the alternate_group field in the `tkhd' box.
--track-tsoffset arg Set relative time offset of a single track.
--tt-sample-interval arg Set the time interval between subtitle samples, in milliseconds.
--log-file arg Set the log file
--uv-apid arg Set the APID.
--uv-profile arg Set the DECE profile.
--uv-movie-md arg Add DECE required metadata XML file.
--uv-opt-movie-md arg Add DECE optional metadata XML file.
--uv-metadata-images arg Specify a list of image files referenced within the metadata.
--cover-art arg Set the cover art image.
--enc-key arg Set the encryption key in either the base64 or hex format.
--drm-data-file arg Add a DRM data set from a file.
--uv-bloc arg Set the Base Location in an UltraViolet file.
--uv-purl arg Set the Purchase Location in an UltraViolet file.
--mpeg4-brand arg Specify the ISO base media file format brand in a format as follows (ABCD[:v]).
--mpeg4-comp-brand arg Specify the ISO base media file format compatible brand(s), comma separated, in a format
as follows: (ABCD,EDFG).
--license-file arg Specify a license file
--help Print general help information
--morehelp arg Print detailed help information on a specific option.
--progress Display a progress meter
--version Print the version information and exit.
--id3-blob arg Set the contents of the ID32 box.
--itunes-blob arg Set the contents of the udta.meta box.
--threegp-blob arg Set the contents of the 3GPP metadata boxes.
--dv-profile arg Set the Dolby Vision profile.
--dv-bl-compatible-id arg Set the Dolby Vision base layer compatible ID, if the profile index is 8, this option
must be set by user.
--ac4-bitrate arg Set the ac4 bitrate value.
--ac4-br-precision arg Set the ac4 bitrate precision value.

I need a poster picture, why is the picture refused --cover-art C:\Users\CinemaHD\Desktop\cover.png?

legosoff wrote:Hello everybody!!!
mp4muxer.exe: ERROR: Images specified with unsupported file format. Images only supported for CFF (.uvu) files.

I need a poster picture, why is the picture refused --cover-art C:\Users\CinemaHD\Desktop\cover.png?

Error message is your answer, .png is NOT a supported file format

Different image format and still an error, where can I find CFF (.uvu)?

legosoff wrote:Different image format and still an error, where can I find CFF (.uvu)?

Try googling it

spl147 wrote: Tue Apr 25, 2023 12:07 pm

legosoff wrote:Different image format and still an error, where can I find CFF (.uvu)?

Try googling it

https://www.uvcentral.com/files/CFFMedi ... -1.1r1.pdf I did so and everything correct, it not clear.

I got a problem with script to mux a ts file.
this ts file

HDR Format : Dolby Vision, Version 1.0, dvhe.08.06, BL+RPU, HDR10 compatible / SMPTE ST 2086, HDR10 compatible
Code ID : 36

the code id 36 , won`t get work in Windows computer. only the code id dvhe, dvh1 and some else.

to get id dvhe, I use the mp4muxerNEW with

./mp4muxerNEW -i D:\DV\20000_P8.hevc --dv-profile 8 --dv-bl-compatible-id 1 -o D:\DV\20000_P8.mp4

so, if there is another way to get the dvhe flag?
cause I found some DoVi demo videos are ts file with dvhe, such as LG Amaze Dolby Vision UHD 4K Demo.ts

HDR Format : Dolby Vision, Version 1.0, dvhe.05.09, BL+RPU
Code ID : dvhe
Code ID/info : High Efficiency Video Coding with Dolby Vision

qq1649536801 wrote: Wed Apr 26, 2023 9:01 am I got a problem with script to mux a ts file.

If you have a file that can't be muxed in tsmuxer, you should open a ticket here: https://github.com/justdan96/tsMuxer/issues

RESET_9999 wrote: Wed Apr 26, 2023 2:09 pm

qq1649536801 wrote: Wed Apr 26, 2023 9:01 am I got a problem with script to mux a ts file.

If you have a file that can't be muxed in tsmuxer, you should open a ticket here: https://github.com/justdan96/tsMuxer/issues

sorry to bother you, I found it`s my mistake. only mp4 file can make the codec id "dvhe".
just like the files in your "Dolby Vision Stuff" and "RPU and FEL test", some test video file are marked "NEWER TV" and "OLDER TV", both of them are mp4 files.
the codec ID of "NEWER TV“ mp4 file is dvh1, and the older one is dvhe.

so, I want to ask you : how did you mux those newer and older mp4 files.
Thanks for your work and everything you did in this posting!!! your scripts make me know a lot things od dolby vision.