Messages

@Ilia3101

I've got many concert photos with blue/purple led light...Blue/Purple is the worst

Here's one example of Example :
https://drive.google.com/file/d/1vzKa3SS-ATFOof-zM1oqxwofxscwoIKR/view?usp=sharing

How it shows in google drive is not bad, but that's because I used a modified picture style preset on my camera with desaturation, apparently google drive reads these custom settings from the file and actually uses them, not bad.
If I open the file in Finder on MacOs, a standard picture style preset is used and you'll see your bad clipping.

I will look for more...

Not sure what you mean with your last question ?

Any idea of crop_mode2?

What works for me for crop_mode is to go to raw video menu tab and then inside raw video options I choose preview option -> real-time.
This gives me 5x zoom Canon liveview in the high resolution modes.
Now the only problem is framing, to check framing, use half-press on the shutter button. When doing half shutter press, you'll see the actual framing (although a bit slow fps).
You can even do half shutter once in a while, while recording, to check framing.

About question 1:
You need crop mode for that.
Enable the crop_rec module in the module tab.
When it is enabled there should be a crop_mode option in  the Raw video tab.
In the crop_mode menu, you can set your desired resolution (for example 2880 x 1200)
After that, you should be able to get the higher resolution in raw video menu (where you set resolution and aspect ratio etc.).
Note: the standard compressed 12 bit is not available with crop_rec module, you must select 14 bit compressed raw option in raw video menu.
BUT there is a way to get 12 bit compressed, but you have to select this option in the submenu (Q button) of Crop_rec menu.
It's all a bit fidly and not very intuitive, but once you know how it works all is fine 
Note 2:
FPS override and other options that mess with fps aren't available/working with crop_rec options. Crop_rec options have fixed fps.


Question 2:
For normal 720/60 you need to switch to NTSC in Canon video menu. (PAL setting gives you 720/50fps and NTSC setting gives you 720/60fps).
So not a magic lantern setting, but a setting in the normal Canon menu system (you must be in video mode to see video options in Canon menu).

Question 3:
No idea, I don't use LUT's

Yes it is.
In this post is a download link for a build for 6d with sd_uhs in it.

https://www.magiclantern.fm/forum/index.php?topic=15088.msg228879#msg228879

Can I return to firmware 1.1.6 from the newest one 1.1.9 ?

Never tried it myself but it should be possible, check out this topic for instructions
https://www.magiclantern.fm/forum/index.php?topic=18941.0

You must have the official canon firmware 1.1.6 upgrade file to be able to go back to 1.1.6.
As far as I know, it's not available anymore on Canon's website.
If you need it, it's on the nightly builds downloadpage for 6d.
https://web.archive.org/web/pel.hu/down/eos6d-v116-win.zip

Is there any difference for ML builds in cameras version-  6d (N) or 6d (WG) ? Any of these cameras can use ML builds?

Not sure, but as far as I know they run normal firmware.
So if they run on canon 6d firmware 1.1.6 you can use ML build for 6d.

In the last picture you uploaded, I notice the fps  = 24.833
That's not good, it should be 24.992 fps.

So my first guess is, you have some other magic lantern option enabled that messes with fps.

Do you have 'fps override' in use ?
Or maybe 'image fine-tuning' option ( shuttertime fine-tuning ) ?

The fps value in 2880x1200 should normally be 24.992 fps.

Also, try pressing the info button on the camera until you see ML overlays/information on screen. And use option 'ML Preview' option in raw video submenu. This way you can see a preview of your framing. Is this preview normal or also corrupt ?

Sorry to say,i almost got corruption frames in high resolution,not just got these at the beginning but all the time.I try to setup different version ML,and the problem doesn't disappear

Can you upload/share an example mlv file or frame, just a short clip with corrupted frames ?
That way we can see what's going on and how your corrupted frames look like.

Could have multiple causes, to name a few.
-The software you are using to view/edit the mlv's (is it up to date to handle lossless compression?)
-The focus box (white rectangle on your camera screen during liveview in 1x zoom mode) is not in the center. This causes corrupted frames where a large portion of the frame is stuck/frozen and not updated.

hey ,i sometimes get corrupted frames on 6D when i shot by 2480x1396 dual iso,or other high resolution,what is going wrong? when i get corruption frames,it said "data corruption at slot "number", frame "number" "

Yeah happens sometimes, 2480x1396 is at the edge of what is possible. Most of the times it work, sometimes you get 2 corrupted frames at the beginning.
The mlv clips are fine if I have that message, but if it stops recording earlier it's annoying.

I probably can make a preset that has some more headroom for the camera and will always work perfect, like 2400x1350 or something.

when I click SET button in the crop-rec menu

You need to press the "Q" button for the sub menu.
Edit: oh wait I didn't get it right:

You're right, the advanced menu is empty, I moved the interesting options to normal menu and removed the others.
Most of the others were used for eos-m, so not working or implemented for 6d.

IMPORTANT INFO:

Find out about a problem with the 2880x1200 at 25 fps preset.
If the foxus box is moved with the cursor arrows, you might get corrupted frames.
When the focus box is dead center, all works well. But if it is slightly moved around, it might cause corrupted frames.
You can see it in the behaviour of the real-time Canon live view. If your focus box is in a wrong place, liveview gets sluggish/jittery.
If you move the focus box around to a place where liveview is normal again, things are probably fine agian. (works for me).

Haven't noticed this behaviour at other presets.

Not sure for which camera you need it ?
For 6d you can find the latest complete build with sd_uhs module in this post:

https://www.magiclantern.fm/forum/index.php?topic=15088.msg229094#msg229094

What is the fastest your 6D can do with SD overclock? I have the Sandisk 170mb and it can only do around 60mb/s . I saw someone posted in facebook a 650D making around 90mb

With that card I would expect higher speeds possible. I have a 128GB Sandisk 170mb card and it does around ~80Mb/s with the 240Mhz option setting.

But at what resolution setting are you recording, you might be in a video mode that is not data heavy. Normal 1824x1026 video mode doesn't need more speed then ~60Mb/s. So could be that your card can handle more, but your resolution setting doesn't require more speed.

So far everything works as what you have mentioned. Just would like to ask, is the current build supporting h264 proxy recording? I'm experimenting the h264 proxy setting with 12bit lossless (SD overclock to 160mhz), and it crash with error 70. Just wanna know whether this is supposedly a usable setting, or just 6D limitation that can't handle this setting?

P/s: Just a wish request if you wouldn't mind, if possible to have 4k/5k timelapse video mode as currently have in EOS-M? That would be amazing!

Not sure about proxy recording, never used it. But I think it's made for dual card slot cameras like the 5d3. So raw recording on one card and proxy recording on the second card. So the error makes sense I guess (although it would be better if this option wasn't even available in the first place)

I didn't do anything with timelapse mode on the 6d yet, I use full resolution silent picture mode for that in combination with the intervaltimer.
At the moment if I have some time I rather see if I can get real-time preview and correct framing to work. Maybe in the future I'll look into timelapse options.

My main question is why is there less latitude in Davinci resolve working with dng lossless then there is with working with ACR with the dngs coming out of MLV app (the dngs coming from MLV app go into resolve too, for clarity)? I feel like I'm working on a raw photo when I work on a single frame in ACR but in Davinci it starts to fall apart or go haywire way faster.

Different raw editors gives different results. Resolve is about video so you get some different approaches to things. For video there always where Lift, gamma and gain.
Which is slightly different to photo where you have shadow, exposure and highlight.
So might take some practice to get used too and get good results.
Another thing is that resolve is made by blackmagic and probably fit best to their cameras and might not get most out of other camera brands.

Now I have some questions:

1) Horizontal max Res

The 2688 horizontal res limit in crop mode is hardware-related or is speed-related? Otherwise: is it possible - in liveview - to shoot continous RAW frames as in photo mode to get a full res video (even with low fps)?

2) Framing in Crop Mode

In crop mode the "problem" is framing

If RAW Video -> Preview is set to Real-time, framing is not accurate (Why?)

If RAW Video -> Preview is set to Framing, Framing is OK but not real time (and seems CPU intensive: if there's fast panning during recording, often recording stops...)

Wouldn't be possible to have a Crop Rec Mode with Real Time Liveview where the Exact Framing is showed in Overlay?
I mean: the liveview shows the whole scene (not cropped, not zoomed) and the crop is showed by a rectangle.
Wouldn't it be possible? Or the crop-mode is strictly related to zoom mode in the Liveview?

Thanks for all your work!

Question 1:
The 2688 pixelwide horizontal resolution is a default setting by Canon in 5x zoom on the 6d.
Alex found out how to adjust these default resolutions in 5x zoom a few years ago. Since then we have the crop_rec modules.
It is possible to adjust this 5x zoom resolution to full photo resolution at the cost of low fps (full resolution is about 4.5 fps).
Full resolution setting is very heavy in bitrate. A full resolution frame is about 25MB (lossless compressed 14 bit). So lossless 14 bit data stream is over 100MB/s.
It would probably work about right in 2fps.
For more practical use I made 2 high resolution low fps presets in the crop_rec module in the build you're using:
5120x2880 at 5 fps and 5120x2880 at 6 fps.
This way you get about 15 megapixel frames and the 5 fps setting gives you, with the current sd_uhs hack, almost about continuous recording.

Question 2:
Realtime framing is something which isn't figured out how it works, until a few weeks ago.
User theBilalFakhouri made some pretty good process on this recently.
Some camera's now have (almost) pixelperfect framing with real-time preview.
I have too read into this to see if it works the same for the 6d, it does seem to work different for 5d3 though.
So with the latest findings of theBilalFakhouri there might be a change to get better liveview on the 6d, but it will probably take some time 

I see I have missed some post in this topic since august 
I still will try to answer them 

Are you talking about 2.5k liveview or not? Because Canon mov files always looks like shit 

Compared to raw that is 

Does this liveview resolution change mean you can record 2.5k in h.264 ? What happens when you disable raw video and hit the record button, how does the canon mov file look.
Just curious
(Since raw is way too good to go back to h.264 compression  )

Wow, respect 

Everything I read about this thingy points to sloppy engineering.

Indeed, probably the most obvious reason.

But if the first firmware is gone...we will never know for sure.

Just wondering about what Walter says...the original firmware of the R5, say the version that's on the first batch out in the wild.
It's nowhere available for download I guess, since it's the original first version of the firmware.

So that means, if everybody does the update to the newer version, there might be a chance that nobody will ever find out how the 'temperature video locking' was controlled originally.
So maybe we never will know if Canon did the 8k videolocking on purpose and not for temperature or safety of the hardware...


So this whole new firmware update could also be used by Canon to get rid of some nasty evidence 

As far as I know, you can only get these sort of messed up liveview when crop_rec module is enabled and in use. You probably have a build where a crop_rec preset is enabled by default.
In magic-lantern menu goto the raw video menu tab and look if there is an option crop_rec and see if you can change it to "Off".
If this doesn't work, go to the module tab, disable the crop_rec.mo module and restart the camera. Everything should be normal then.

To be clear, this liveview is a side effect for getting higher resolution modes (cropped).
When you look into raw video submenu, you could also set Preview option to "ml preview" instead of liveview. I expect you get a low resolution liveview preview and can record in >HD resolution.

@theBilalFakhouri

For extreme high fps presets, it worked for me to set the following 4 register to value 1.
Liveview is gone when doing that, but the camera doesn't freeze (most of the times  )

C0F08184
C0F08188
C0F08194
C0F08198

I use this messy code to have set these registers to value 1 for presets >60fps, it's put in the same block of code where you override resolution and A and B timer registers etc.

Code Select Expand


//720P_HighFPS_6D
static inline uint32_t reg_override_720P_HighFPS_6D(uint32_t reg, uint32_t old_val)
{
if (CropReadoutPresetChoice_720P > 5 )
    {
        F08184 = 0x295;
        F08188 = 0x3be;
        F08194 = 0x1ef;
        F08198 = 0x3be;
    }
    else
    {
        F08184 = 0x0;
        F08188 = 0x0;
        F08194 = 0x0;
        F08198 = 0x0;
    }


       switch (reg)
       {

// fix for >60fps will destroy liveview
        case 0xC0F08184: return 0x296 - F08184;
        case 0xC0F08188: return 0x3bf - F08188;
        case 0xC0F08194: return 0x1f0 - F08194;
        case 0xC0F08198: return 0x3bf - F08198;


//           case 0xC0F06804: return 0x5be02a0 - SelectableResolutionFix + (((((Horizontal_Res_720P/3) - 2560)/4)/4)*4)  + ((((Vertical_Res_720P - 1440)/4)*4) << 16) ;

           case 0xC0F06804: return 0x5be02a0 - SelectableResolutionFix + (((((Horizontal_Res_720P/3) - 2560)/4)/4)*4)  + ((((Vertical_Res_720P - 1440)/4)*4) << 16) ;


           case 0xC0F06824: return 0x2b0 + (((Horizontal_Res_720P/3) - 2560)/4);
           case 0xC0F06828: return 0x2b0 + (((Horizontal_Res_720P/3) - 2560)/4);
           case 0xC0F0682C: return 0x2b0 + (((Horizontal_Res_720P/3) - 2560)/4);
           case 0xC0F06830: return 0x2b0 + (((Horizontal_Res_720P/3) - 2560)/4);

           case 0xC0F06010: return 0x2b5 + (((Horizontal_Res_720P/3) - 2560)/4);
           case 0xC0F06008: return 0x2b502b5 + (((Horizontal_Res_720P/3) - 2560)/4) + (((Horizontal_Res_720P - 2560)/4) << 16);/*  for dec 690*/
           case 0xC0F0600C: return 0x2b502b5 + (((Horizontal_Res_720P/3) - 2560)/4) + (((Horizontal_Res_720P - 2560)/4) << 16);

           case 0xC0F06014: return 0x603 + (((Vertical_Res_720P - 1440)/4)*4) + SafetyMargin_720P; /*  dec 1543*/

           case 0xC0F0713c: return 0x5b8 + (((Vertical_Res_720P - 1440)/4)*4) + Head_3_timer_offset_720P;        //5b8 works best for 5472
           case 0xC0F07150: return 0x5b8 + (((Vertical_Res_720P - 1440)/4)*4) + Head_4_timer_offset_720P;        //5b7 works best for 5472

       }

    return reg_override_bits(reg, old_val);
}


Already had the liveview fix with C0F38024 register in the latest 6d builds.
But there is indeed a certain limit I couldn't pass.
On 6d I could fix liveview for 2880x1200, but couldn't get it to work on higher resolutions then that, like 3072x1152.
It also has a minimum limit for vertical resolution, if I want to fix liveview with presets below a vertical resolution something about 960, it also doens't work.

Didn't know about the C0F383D4 and C0F383DC, so maybe messing with those I can stretch it a little.