Managed to get a bunch of corrupted files on my 5D2

[jpegmasterjesse]

Running one of rdc's newer builds, with dual_iso.mo

haven't had any huge problems so far, not sure what was different this time. It was casual/fun stuff, nothing of huge consequence, but if anyone with savvy wants to take a look feel free, and much appreciated:

https://drive.google.com/open?id=1ci26Yy1wfPr4thvxE04OPSx2pnjvb6k1

[reddeercity]

1st: use the latest build , your are using

Code: [Select]

Built on 2019-06-21
you should be using 2019Jul15.5D2212.zip ,

2nd: Dual Video ISO should be only used in Manual Mode not Auto or Tv , Av etc. .... and so on ......
below shows what you had set the camera mode to Auto , Tv & Av

Code: [Select]

bv.av = 0
bv.tv = 112
bv.iso = 72
bv.auto = 1You need 2 ISO's Base & Recover , usually 100-ISO with 800-ISO as the recover .

The ASSERT00.LOG , tell what happen. you had a problem with the bit reduction .

Code: [Select]

ML ASSERT:
raw_info.bits_per_pixel == bpp
at ../../src/raw.c:2372 (raw_lv_request_bpp)
and that's confirmed with the corrupted mlv file , check the black level and it's reported as 1193 instead of 448 for 12bit .
I can go on and on ,  so to reduce the chance of corrupted mlv file's and camera lockup ,
use only in Manual Mode with Dual Video ISO & only load the module you are using .
I only load: 5D2_212.sym , dual_iso.mo & mlv_rec.mo , that's it .
no need to load ETTR.mo , use the technique not the module - the more module you load cause extra load on the system = problem.
Keep it simple , and by the way this is very bleeding edge stuff so you can expect the unexpected .