Dump Submitted: Mississippi Burning 4K UHD (F6FE)

[rogueranger89]

MKB20_v77_MISSISSIPPI_BURNING_UHD_F6FE.tgz

[MrPenguin]

MKB20_v77_MISSISSIPPI_BURNING_UHD_F6FE.tgz

The latest KEYDB.cfg file contains this entry:

Code: Select all

0x797E9237C797FA8C320ED55C5F68710A9A47D257 = MISSISSIPPI BURNING UHD

Does copying this file into MakeMKV's data directory (i.e. where MakeMKV also writes its TGZ dump files) and restarting MakeMKV help?

[rogueranger89]

Promblem solved with the latest KeyDB.cfg
Worked fine for me now.
Thank you

[rogueranger89]

I'm having AV Sync issues with it, could that be an indicator that the key is not 100% correct or some other issue?

................
................
AV sync issue in stream 0 at 0:00:05.422 : secondary stream video frame timecode differs by -291.961ms
AV sync issue in stream 0 at 0:00:05.422 : too many video frames with invalid timecodes, future messages will be suppressed

[Woodstock]

Other issues than key. If the key were incorrect, you'd not be able to start the rip.

AV sync errors are often at places where pieces of the film are spliced together. MakeMKV tries to fix those, as the log shows. Did it create a file? How does the audio sound around the times shown?

[rogueranger89]

Yeah it spat out a normal MKV of the movie and the AV Issues did not really effect the outcome. The milliseconds that may or may not be there a not noticeable so everythings good.

[Woodstock]

Just be careful when you find something like a few anime titles I've had, where the AV offsets were like 30 seconds.

[quietvoid]

This title has authoring problems so the Dolby Vision might have issues on playback depending on how your device reacts.
Because the 2 videos have different timestamps, MakeMKV causes missing metadata for a lot of frames.