Dolby Vision now possible through MP4 Mux.

[deadchip12]

Does anyone using the Ugoos AM6B+ have a white banding issue in Saving Private Ryan @ 2h35m mark?

Can you provide a photo? I don't have the movie but I may try later.

[deadchip12]

My cmv4.0 source for this movie is MAX and not MA(movie anywhere)

Does it matter if I use a different source from yours and at the end it passes all the checks?

I compared the L1 plot of my Blue Beetles 2023 (source: MA) to the L1 plot of yours (source: MAX) and they were exactly the same, except for some numbers (red circles):

[LV8HD]

Hi everyone, some time ago I asked if anybody here knew how to change maxcll and maxfall values within the hevc stream itslef without the need to re-encode it. Well ,I've finally figured it out.
Thus, a question comes to my mind: how important are these values in the actual playblack? I've seen many movies having those values wrong and sometimes not having them at all.

[RESET_9999]

Does it matter if I use a different source from yours and at the end it passes all the checks?

no

[skull88]

Hi everyone, some time ago I asked if anybody here knew how to change maxcll and maxfall values within the hevc stream itslef without the need to re-encode it. Well ,I've finally figured it out.
Thus, a question comes to my mind: how important are these values in the actual playblack? I've seen many movies having those values wrong and sometimes not having them at all.

They don't matter for DV playback for sure, and possibly not in some contexts even for HDR fallback, as Paramount for example continues to not add MDL metadata for their UHD BDs. Curious what the method you figured out is, regardless, please share if you're willing to. Thank you kindly. Cheers.

[deadchip12]

If a movie is not in any of the red/green/yellow list in your spreadsheet, e. g. Creed III, does it mean this transfer process won't work or you haven't tested with that movie yet?

I haven't checked all the movies

Is there a way for me to check them myself or is it too complicated?

Just checked the first file (the higher bitrate one) and there's no Level4 line, along with these:
L5 Left offset: L5_is_missing_you_should_edit...
L5 Right offset: L5_is_missing_you_should_edit...
L5 Top offset: L5_is_missing_you_should_edit...
L5 Bottom offset: L5_is_missing_you_should_edit...

L4 is when I do P8 hybrid, it doesn't matter when you transfer 3-8-9 to a P7 rpu since they already have L4.
All iTunes webdl are missing L4 and L5

So, just to confirm: profile 8 itunes web-dl releases are now perfectly usable right? What about profile 5 itunes web-dl releases? Should I avoid them because of the color error (mentioned in your spreadsheet: color difference(orangish red) is caused by apple stupid static color reshaping in the RPU. Once removed (when converted to P8), the colors match.)?

Does it matter if I use a different source from yours and at the end it passes all the checks?

no

Sorry, by "all the checks" I only meant the checks I see at the end of the Transfer CMV4.0 bloc video tutorial. Are there other checks I should do, considering I'm using a difference source, like brightness difference, color error, etc.?

[RESET_9999]

So just to confirm: profile 8 itunes web-dl releases are now perfectly usable right? What about profile 5 itunes web-dl releases? Should I avoid them because of the color error (mentioned in your spreadsheet: color difference(orangish red) is caused by apple stupid static color reshaping in the RPU. Once removed (when converted to P8), the colors match.)?

the apple color reshaping metadata only applies to DV profile 5 playback. The dolby visions levels (1-2-3-4-5-6-8-9-11) are a different thing and are always the same regardless of the DV profile so yes, any cmv4.0 rpu can be transfered to a cmv2.9 rpu as long as they come from the same DV analysis (same L1/L2).

Is there a way for me to check them myself or is it too complicated?

just download the webdl and check if it's cmv4.0 and the same Level 1 as the bluray disc DV ?

Sorry, by "all the checks" I only meant the checks I see at the end of the Transfer CMV4.0 bloc video tutorial. Are there other checks I should do, considering I'm using a difference source, like brightness difference, color error, etc.?

all that matters is the metadata themselve. It can work only if they are the same

[deadchip12]

So just to confirm: profile 8 itunes web-dl releases are now perfectly usable right? What about profile 5 itunes web-dl releases? Should I avoid them because of the color error (mentioned in your spreadsheet: color difference(orangish red) is caused by apple stupid static color reshaping in the RPU. Once removed (when converted to P8), the colors match.)?

the apple color reshaping metadata only applies to DV profile 5 playback. The dolby visions levels (1-2-3-4-5-6-8-9-11) are a different thing and are always the same regardless of the DV profile so yes, any cmv4.0 rpu can be transfered to a cmv2.9 rpu as long as they come from the same DV analysis (same L1/L2).

Is there a way for me to check them myself or is it too complicated?

just download the webdl and check if it's cmv4.0 and the same Level 1 as the bluray disc DV ?

Sorry, by "all the checks" I only meant the checks I see at the end of the Transfer CMV4.0 bloc video tutorial. Are there other checks I should do, considering I'm using a difference source, like brightness difference, color error, etc.?

all that matters is the metadata themselve. It can work only if they are the same

Thanks again for all the explanation so far.

I'm checking frame difference for Blue Beetles 2023. Doing it manually by looking at random scene cuts in Avisynth+ and I'm seeing 0 frame difference. Yet the L1 plots between the original bluray and stream version are not in synced (ignore the red circles please). What could be the reason?

[RESET_9999]

as I said earlier, what matters is that your scene cuts match the BL. The framecount mismatch makes the graph look different.

[deadchip12]

as I said earlier, what matters is that your scene cuts match the BL. The framecount mismatch makes the graph look different.

Ok so I finished transferring cmv4.0 for Blue Beetles 2023 and am doing the final checks. The RPU_CMV4.0_L3L8L9_transfered.bin's L1 plot matches the original bluray file's. I exported the scene cuts using verify_sync2 file and am checking random frames at the beginning and the end of the final mkv file to make sure they are the first frames of a new shot. I found one that isn't: Frame 657. Frame 656 and 657 are still in the same shot. I checked randomly many other frames and they are all the first frame of a new shot. Why is this frame 657 not?
Edit: Found another one that is not the first frame: frame 5503. The similarity between this and frame 657 is that they both seem to be part of a very wide shot.
Also, some of the frames listed, e.g. 49, are from early in the movie and they are just part of a black screen sequence.

[RESET_9999]

Maybe automatic scene-cut detection? It happens sometimes, most of the time, a flash or fast movement can cause that and it doesn't really matter. I've seen this many times on retail RPU.

[deadchip12]

Why are some web releases cmv2.9 instead of cmv4.0 I wonder?

[RESET_9999]

most of the newer ones are 4.0 at least.

[deadchip12]

@RESET_9999 I'm testing Aquaman.and.the.Lost.Kingdom.2023 and during workflow 1-1 (inject RPU_CMV4.0_L3L8L9_transfered.bin to original bluray file) I get this missing L5 lines. Should I just press enter to skip?

[RESET_9999]

You can't skip it, this workflow was designed to always fix incorrect L5.
Just edit it to 0,0,0,0