12-bit (and 10-bit) RAW video development discussion

[yourboylloyd]

I know that this sounds crazy, but is 8bit RAW possible? Sorry if I sound like a noob.

The best feature of shooting RAW on my 5D2 is the aspect ratio control. I can use a lot more of the sensor than shooting in H.264 allows me to. Shooting in 3:2 and 4:3 allows me more creative control in shooting for instagram/facebook because of the larger vertical resolution these sites are intended for. It also helps when shooting anamorphic because of the 1.33x horizontal squeeze!

If 8-bit raw sounds too weird, then is there a possible way to control aspect ratio when recording in H.264?

[ItsMeLenny]

I know that this sounds crazy, but is 8bit RAW possible? Sorry if I sound like a noob.

The best feature of shooting RAW on my 5D2 is the aspect ratio control. I can use a lot more of the sensor than shooting in H.264 allows me to. Shooting in 3:2 and 4:3 allows me more creative control in shooting for instagram/facebook because of the larger vertical resolution these sites are intended for. It also helps when shooting anamorphic because of the 1.33x horizontal squeeze!

If 8-bit raw sounds too weird, then is there a possible way to control aspect ratio when recording in H.264?

You won't get any benefit from it, the size is pretty much the same as 10 and 12 bit.
Plus I would assume it would result in banding.

[TrEK]

Hello friends
I see that its available new verision on 10/12 bit ML RAW for Canon 5dmk2 and Canon 5dmk3
Latest Build (2019-03-24 09:58)

But where i can watch differencess with previous version ?
thank

[scrax]

Hello friends
I see that its available new verision on 10/12 bit ML RAW for Canon 5dmk2 and Canon 5dmk3
Latest Build (2019-03-24 09:58)

But where i can watch differencess with previous version ?
thank

after the links to download for each camera there is a link to the bitbucket commits, just check the date to see what's new from the previous version you are using

[reddeercity]

No not for 5D2 , there no updated commits for "magiclantern-raw_video_10bit_12bit.2019Mar24.5D2212"
the latest is 2018-09-26 , so I'm not sure what has changed .

[TrEK]

No not for 5D2 , there no updated commits for "magiclantern-raw_video_10bit_12bit.2019Mar24.5D2212"
the latest is 2018-09-26 , so I'm not sure what has changed .

[

[a1ex]

The only change is reply #1823 (that is, compiling from other branch on newer models; no changes on the repository). Apparently it fixes some null pointer errors on Rebel cameras (that for some reason I could never reproduce).

I doubt they changed anything on 5D2/3, but I do not use these builds, so... YMMV.

[TrEK]

after the links to download for each camera there is a link to the bitbucket commits, just check the date to see what's new from the previous version you are using

friend ... i can not understand.
my current version on Canon 5dmk3 -2018.Oct.10




but now is available - 2019.Mar.24


where on this link i can see difference between current and new versions ?

[scrax]

friend ... i can not understand.
my current version on Canon 5dmk3 -2018.Oct.10




but now is available - 2019.Mar.24


where on this link i can see difference between current and new versions ?

Alex already answered, there are small changes only for other models, but if you look on the linked pages you should see that last commit (or last changes) is 26 september 2018  and since you version is older it already has all the commits, none new so nothing changed in the code

[reddeercity]

The only change is reply #1823 (that is, compiling from other branch on newer models; no changes on the repository). Apparently it fixes some null pointer errors on Rebel cameras (that for some reason I could never reproduce).
I doubt they changed anything on 5D2/3, but I do not use these builds, so... YMMV.

Everything is ok on 5D2 , I can't see anything that different .
tested mlv_lite  & mlv_rec , but mlv_rec is much faster on the 5D2 then mlv_lite .
Mainly because of the different liveview preview & no "Kill Liveview Overlays" like "mlv_rec"
which give about 10MB/s more write speed , best I can do is around 65 MB/s on MLV_lite
On mlv_rec I can get around 75 MB/s write speed .
would be nice to have "Kill Liveview Over lays" in mlv_lite the same as mlv_rec.

edit: tried h264 proxy , started to record a h264 .mov ( had the h264 overlay stuff)
but after a few second the liveview froze , had to do a battery pull .
check the CF card , had a h264.mov there about 18 second clip & the start of a mlv file with "0" data
so it kind of worked just didn't save the raw steam data , I may look in to this at a much later date .

[domo94]

7D 10-12 bit Mar.2.2019 Build

Had an entire video be corrupted.

I'm still managing the best types of shooting settings.





Shooting 60fps, 1600x408, 10 bit raw.

Hacked Preview output into a Feelworld Monitor.

Anybody need some tests?

[TrEK]

Alex already answered, there are small changes only for other models, but if you look on the linked pages you should see that last commit (or last changes) is 26 september 2018  and since you version is older it already has all the commits, none new so nothing changed in the code

thank you for answer
but do u know if will improve any new changes for canon 5dmk2/3 in new versions of ML 10/12 bit ?
and tell me pls how i can filter branch with change only for canon 5dmk2/3 or watch it in tree-list

[zcream]

Yes, works for me on 50D . I can zoom in, and record 2000x1078 rav video , zoom out and record 1584x1056 , both 12bit uncompressed and 24fps.
See screenshot of damaged frame - each zoomed clip has two damged frames at the beginnig, frame 002 and 003.
Magnification (5x 10x) is without pink hue, I have had using another build.

Any idea why 50d is not capable of 2.5k in zoom mode? Isn't the chipset similar to 7d and 5d2?

Sent from my Redmi 4A using Tapatalk

[Dionisgr]

On my Canon 650d, this firmware does not start With standard optics just a black screen, and with manual optics writes an error idle: stack overflow: free=0 used=160 and then does not start!

[dfort]

@Dionisgr - Which build? Open the autoexec.bin file with a text editor and you should see the changeset and who compiled it.

[Dionisgr]

That's what it says at the beginning of the file!

Magic Lantern raw_video_10bit_12bit.2019Mar24.650D104
Camera   : 650D
Firmware : 104
Changeset: d318f774b24e+94a19d94813f+ (raw_video_10bit_12bit)
Built on : 2019-03-24 10:05:06 by jenkins@nightly

[dfort]

@Dionisgr - Finally got back to this. I reported a problem back in Reply #1821 and a1ex made a "temporary fix" meaning the changes were not committed and pushed. If you look at the changeset: d318f774b24e+94a19d94813f+ the plus sign between two changeset hashes are an indication that there was a merge and the trailing plus sign shows that there were some other changes. If you look at the autoexec.bin file in a text editor you'll also see a rather long "diff" which can be used to patch the source code.

There's more work to be done on the raw_video_10bit_12bit branches so I would recommend using one of the crop_rec_4k branches instead. You can record 10/12bit on the 650D with those branches.

[a1ex]

That means, whatever caused the error... will remain a mystery. For example, should I consider merging that fix (new-dryos-task-hooks) into mainline, or not yet?

If the issue can be reproduced, the contents of the ML/SETTINGS directory might be enough to trigger it (possibly on other camera models as well, not just on 650D).

Otherwise, the above-mentioned build boots just fine in QEMU, but that's pretty much all I could test.

[dfort]

@Dionisgr - If you're still following this please post the contents of your ML/SETTINGS and I'll try to reproduce the error on my 700D.

In addition I posted a new-dryos-task-hooks build for the 650D on my downloads page. Appreciate it if you could try it out and post your findings on the pull request.

@a1ex - Isn't the problem with new-dryos-task-hooks is that it breaks the 500D and possibly some of the other older cameras?

[a1ex]

To my knowledge, new-dryos-task-hooks doesn't break anything (besides the above report, which is uncertain), but I didn't run extensive tests either. It should actually fix all these "null pointer" errors on various models, and these changes are compatible with all future models (including M50).

So, after QEMU, it would be the next candidate for merging into mainline, as long as it doesn't break things.

Not sure what you are talking about, regarding 500D.

[dfort]

Not sure what you are talking about, regarding 500D.

This:
https://bitbucket.org/hudson/magic-lantern/pull-requests/672/dryos-task-hooks-for-newer-cameras-6d-70d/diff#comment-48243615

[a1ex]

That should have been fixed in 0391160.

[dfort]

...should I consider merging that fix (new-dryos-task-hooks) into mainline, or not yet?

Yes, please. In addition to fixing the "null pointer" issues it is needed for the EOSM2, 1300D and probably some other ports in progress. It would be good to propagate new-dryos-task-hooks throughout the various development branches.

[Dionisgr]

@dfort @a1ex The link shows all the files in the ML folder https://drive.google.com/drive/folders/1VC4LqKf-IOwIzUBu5L3bSqMNo_TVeYgc?usp=sharing

[a1ex]

Could not reproduce; it boots just fine in QEMU.

However, you have loaded quite a few modules (some for still photos, others for video); maybe one of them is causing the issue. Delete the SETTINGS directory to start with a fresh configuration; then you'll be able to narrow down and figure out what module is causing the issue.

Was this configuration working with some older build? If yes, which one?