change the container to TS:
https://github.com/justdan96/tsMuxer/releases
Correct, P5 uses BL+RPU with a different color space than HDR10 (IPT), hence the colors are off and there's no HDR10 fallback.DolbyVisionFTW wrote: ↑Mon Jan 03, 2022 1:55 amP5 (always single layer) = none-tonemapped DV base layer(green and purple colours) + dynamic metadata in RPU.WaynosDaBoss wrote: ↑Sun Jan 02, 2022 9:53 pmFrom what I have read so far it would appear dual layer files which use profile 7 are able to fall back to standard HRD10 and ignore the metadata but as this file is profile 5 single layer this is not possible.
Does anyone know if this file type should be supported or not or if I should just forget about the DV content and try to play standard HDR10 files instead or do I just have a bit of an oddball file here?
https://web.archive.org/web/20200929014 ... _09_16.pdf
Within the Dolby Vision context, a profile 5 bitstream must use perceptual quantization with reshaping for EOTF; uses Dolby Vision proprietary IPT color space for color primaries and color matrix; uses full range for range; and uses center-left siting for chroma sample location.
Dolby Vision proprietary IPT color space is similar to BT.2100 ICtCp, where I is similar to I, P similar to Cp, and T similar to Ct.
Cool, I will give that a try.RESET_9999 wrote: ↑Mon Jan 03, 2022 2:24 amchange the container to TS:
https://github.com/justdan96/tsMuxer/releases
It indeed looks like crapRESET_9999 wrote: ↑Wed Dec 29, 2021 4:17 pm@all
I was testing some hdr10 patterns converted to DV and look what happen on the Shield/X700/C8 with this P8 pattern : https://slow.pics/c/tnFWN04T (there's definitely something wrong with P8/P7 DV on the shield)
Re-did the FEL test files as well, hopefully, they work better on different devices...
https://drive.google.com/drive/u/1/fold ... V0E3VVkhiC
Awesome! This worked perfectly and is super easy to just quickly remux into a TS file without extracting anything! Quick question, is it preferable to use TS over M2TS?RESET_9999 wrote: ↑Mon Jan 03, 2022 2:24 amchange the container to TS:
https://github.com/justdan96/tsMuxer/releases
Don't think you can do that.Pixels wrote: ↑Mon Jan 03, 2022 6:06 pmI have a laptop that only supports P5 DV in mp4, so I've managed to convert P8 input file into P5, this in turn triggered DV but the video is stuttering. PS: I've tried mp4muxer & Tsmuxer, problem seems the only video player that could trigger DV in my laptop
Can someone help through this..
From my understanding (someone let me know if wrong) you're only losing the color enhancements + efficiency of the Dolby proprietary color space from p5 - this would mainly be seen on future displays capable of 12bit but possibly could be more banding (technically, not meant obviously or egregiously) or artifacts like that sort when using HDR10 base video vs native p5 one on displays now?
If the DV and HDR10 files are from the same release time and group you're often good to go
That only ever happened to me when trying to make base layer encoded FEL p7 file, it meant stuff is messed up/input was bad.darex wrote: ↑Thu Jan 13, 2022 8:49 amI'm having issues with mp4muxer that started recently.
All of a sudden it will not create a valid output file.
It is always 0kB and exits in 10-20 seconds.
I can see that it is using the disk and CPU for that time but then it just stops.
There is no error message and the files used as input have previously worked.
Anyone run into this before?
Whoops! Should be fixed in https://github.com/quietvoid/dovi_tool/ ... 23ccb277fb.RESET_9999 wrote: ↑Fri Jan 14, 2022 12:17 am@quietvoid, I wasn't able to generate dv from madvr with the latest version of your tool. it kept complaining about --json not an acceptable argument for madvr files