crop_rec on steroids: 3K, 4K, 1080p48, full-resolution LiveView

[a1ex]

The 7D issue does not apply here - on 7D, the issue is caused by the preview backend (and for the moment, I don't have any solution other than disabling the previews completely).

Here, the issue is my single-buffering experiment (which gives a little more memory for high-res modes, but apparently it doesn't play nice with high-FPS modes).

[pc_bel]

@beauchampy
I'm really interested in 192050p 3x3 mode and while I wait for a solution for the tearing issue, for me the solution is 1080p45 3x3 mode. Not same slowmotion like 50p but no tearing issue and continuous recording. Tested at ISO3200 and it works for me continuous!!!. Only framing is a little bit offset...
5Dmk3 113 Lexar 64Gb 1066x

[pc_bel]

Tested:
April3th build 1920x960 50p 3x3 mode NO TEARING ISSUE!!!! Continuous at ISO100 and 400. At ISO800 shorter recording times (aprox 20sec. for me).
5Dmk3 113 Lexar64Gb1066x

[hjfilmspeed]

So I can use a little education here. Sorry Im behind. If I get the:
ML ASSERT:
RAW_IS_IDLE
at mlv_lite.c:584 (measure_compression_ratio), task shoot_task
lv:1 mode:3
where the text appears on the screen, is this a crash? I have been assuming it is and pulling the battery. Should I be doing this?

[DeafEyeJedi]

Here's a 5D3.123 build from 2017-04-03 for those that want to try and confirm...

https://bitbucket.org/DeafEyeJedi/magic-lantern/downloads/magiclantern-crop_rec_4k_2017April03.5D3123.zip

[JackDaniel412]

Hello @a1ex , I ran the ROM1 test, no error found.
I updated ML to the April 10th, in debug section show this error



There is a way to fix it?

Thanks!

[a1ex]

is this a crash? I have been assuming it is and pulling the battery. Should I be doing this?

Yes, taking the battery out after a crash is what I always do.

Unfortunately, it doesn't appear to prevent Canon code from saving corrupted settings into the ROM. Still looking into it.

edit: opening the battery door seems to be interpreted as some sort of emergency shutdown, but a clean one - settings are saved into ROM, but ML shutdown hooks (e.g. saving ML config files) are not executed. But, if you somehow hold the battery door switch pressed, and just remove the battery, the ROM is not updated.

@JackDaniel412: asked and answered

[DeafEyeJedi]

Re: tearing I noticed this happening after the 2017-04-06 build and still persist with 2017-04-10 build as well when shooting in 1080p 3x3 45fps (50p Canon) and could this strange pattern of corrupted (plus dropped?) frames in several MLV's that spat out be related to the tearing at all?

Because my instincts are thinking that it may have started it after I had a bunch of random corrupted footage similar to the one below (is this what you were seeing also @beauchampy?) otherwise correct me if I'm wrong.

https://vimeo.com/212794399

Re: 2017-04-03 build I am now getting corrupted frames similar to the one above when shooting in 1080p 3x3 45p until I reduce the resolution down to 1920x960p which all seems fine.

Though on the older build I seem to be able to get clean recording w full 1920x1080p in 3x3 45fps which is rather confusing. Gonna need to take a step back and check again with all of this before I lose it for good. literally.

[beauchampy]

@beauchampy: known bug, but right now, figuring out how prevent the recent soft-bricks has a higher priority.

Until then, my advice would be to try the Apr03 or older builds (which are double-buffered, which avoids tearing, but Frozen LV is not working well, so recording times may be shorter).

Do not use Apr04.

Can confirm Apr03 build is working correctly. Thanks a1ex!

No problem buddy, you take your time. Thanks for all your hard work, these updates are amazing.

[jordanwalkert]

Hey a1ex,
With the latest build from April 10th (the one to ignore false warnings), I am still getting a message about the null bug. I have not run into any major issues or soft bricking, but I also do not have a backup or unaffected copy of my ROM from before the 4th. Am I screwed, any solution to this without a clean ROM from before?

[a1ex]

In many cases, I can infer the missing values from another ROMs (so it's not a very hard requirement).

BTW, your existing copy from ML/LOGS is likely to be a good one (as it's only re-created after a format).

[hjfilmspeed]

Yes, taking the battery out after a crash is what I always do.

Unfortunately, it doesn't appear to prevent Canon code from saving corrupted settings into the ROM. Still looking into it.

edit: opening the battery door seems to be interpreted as some sort of emergency shutdown, but a clean one - settings are saved into ROM, but ML shutdown hooks (e.g. saving ML config files) are not executed. But, if you somehow hold the battery door switch pressed, and just remove the battery, the ROM is not updated.

@a1ex Hmmmmm So if I mod the switch with say.... tape, I can pull battery with out afflicted ROM being saved?
Should I do this as a extra precaution when heavy testing?
Would this have adverse affects on Canon code being that its an "unsafe" battery pull at that point? 
So many questions sorry.
I suppose there is always a chance I might not even know that the ROM is affected and I could clean shutdown anyway. 

[Danne]

@Jordanwalkert
Did you save the roms from when installing the actual april 4th build? Those should be the last uncorrepted ones if so...
looong shot

[pc_bel]

More testing with april3th. 5Dmk3 113
1920x960 50p 3x3.
Now I'm recording continuous at ISO3200.
I'm a little confused... Maybe it depends on the detail level of the image?...

[giarcpnw]

I may have missed this but once you set the settings for 3k 1:1 crop, what's the diff between the regular record mode and then x5 crop mode? They seem the seem on preview but regular mode will record around 3072x1228 but x5 Crop just stops. Is it cranking the data rate or something?

And does FPS override make any difference in any of thi?

[pc_bel]

Now I've got two consecutive errors... Error 70, then I turn off camera. Next an  Error 80. Camera does not show live view after both errors. After a new reboot all is apparently ok...

[pc_bel]

Another issue in 1920x960 50p 3x3 is framing.

Here there is a composition comparing real image vs live view framing:
http://ovh.to/TpLuMh

[DeafEyeJedi]

Can anyone else confirm that it seems when you go into Full-res LiveView (it becomes 2+ stops brighter according to the LV as well as the ML histogram) than if in any other settings within crop mode from the latest experimental build?

If so, is this normal or a bug?

[a1ex]

Probably it's because of the shutter speed mapping from 1/4000 ... 1/30 to 1/15000 ... 1/FPS (also used on 4K half-fps).

Suggestions for a better (less confusing) implementation?

[goldenchild9to5]

Here is a quick test I did using 5D Mark III in 3k - 3:1 / Build April 10th latest one.  I just Love the images that I'm getting & specially the motion, the images speak for themselves even when youtube super compresses it.  Let me know what you guy's think. 

https://www.youtube.com/watch?v=OmxEjoruetw&feature=youtu.be

[Quentin]

When I find it, I am glad.
When I need it, I cant find it
Where is the menu option for setting the Preview ?
Thanks for your help

[D_Odell]

I tried today with April10th build. Since I normally shoot 1.85:1 I tried 3K 1:1 (2928 × 1580), ISO 640, shutter 1/50. But the cam can only record for 5 sec with 14 bit lossless. Is that normal? Or how to be able to record constantly with this resolution, if possible? CF card is Sandisk 160mb r/w. Thanks for al the heavy work and fun to reach new heights!

DNG: https://www.dropbox.com/s/tz79q88ozc8f5p4/M12-0944_000004.dng?dl=0

[Walter Schulz]

Bandwidth required:
2928 x 1580 x 24 (?) x 14 / 8 = 185 MByte/s

[D_Odell]

Bandwidth required:
2928 x 1580 x 24 (?) x 14 / 8 = 185 MByte/s

Correct 23.976. Normal I watch ML recommendation in menu, and with these settings says 101.8MB/s at 23.976.

[mageye]

Try recording at ISO100