3K/UHD 5D2 Raw development and Other Digic IV Cams

[aprofiti]

CMOS[2] should center it , check photo mode and see what it is.
I check to see by refreshing liveview with the half shutter button 
Seems the image is always right justified , and it can only be moved to the left from what I seen on 5d2 .

Found CMOS[4] is responsible for horizontal position on 50D, that's why i wasn't noticing any change in value while checking cmos[2]

Strange thing: after poking around cmos registers set to found what said above, for uknow reason now I get automatic centered image while entering liveview and setting full width:

Code: [Select]

Previuous automatic value:
CMOS[4] = 484
Centered Full Wide:
CMOS[4] = 404
Another Value fond early while logging photo mode, but not sure about
CMOS[4] = 40c


That expected , did you try and rec a .mlv file ? Looks like a image dump
more then likely the pink lower bar with not be in the raw video
It was the same for the 5D2

First attempt result in a standard 2000x1079 mlv video....
Discovered that to increase image size while recording, I have to manually increase resolution in movie Tab -> raw video

Max available is 3520 which give a almost good video of 3520x1078 (a couple of vertical dark lines as wrote defore) from a dump of 4768x1078

Is this how is suppose to do or I'm missing something?
@reddeercity Mlv_lite and crop_rec doesn't compile for 50D in Crop_Rec-4k-5d2-magic-lantern_redercit_buffer_a1ex-code-10-22-2018

[reddeercity]

Hi Reddeercity,
The squeezed mode is interesting. I'm thinking about use it in fullhd+ like (1920 x 360 up to 2400 x 432) at a high frame rate like 72 to optimise aliasing.
With an offset of 1 line in height every 1/72 second, we can reconstruct with dual-iso a good fullhd+ (1920x1080 up to 2400x1296 fps24 ) ?
I know we need to adapt mlv_dump or mlv_app to take in account the height shift but do you think it's doable in crop.c ?
Here is a schema to explain my thoughts :

Interesting idea ,
but 1280x434 is the max resolution I can go at Hi-Frame rate e.g. 72 (FYI - max frame rate to date is 82.5fps @ 1280x722 un-squeezed)

This the Hi-Frame rate limitations squeezed :
1888x704 @ 48fps
1600x500 @ 62.5fps
1280x434 @ 82.5fps

[reddeercity]

Found CMOS[4] is responsible for horizontal position on 50D ......
Strange thing: .... now I get automatic centered image while entering liveview and setting full width:

Code: [Select]

Previuous automatic value:
CMOS[4] = 484
Centered Full Wide:
CMOS[4] = 404
Another Value fond early while logging photo mode, but not sure about
CMOS[4] = 40c
Great , good to know it may help other d4 cams

First attempt .... mlv video....
Discovered that to increase image size ...... increase resolution in movie Tab -> raw video
Max available is 3520 which give a almost good video of 3520x1078 (a couple of vertical dark lines as wrote defore) from a dump of 4768x1078
Is this how is suppose to do or I'm missing something?

No,  I forgot to add the extended resolutions to the source (3008, 3840,4096 & 5632) -- sorry
Add that to mlv_rec.c @ line 136 e.g. like this

Code: [Select]

static uint32_t resolution_presets_x[] = {  640,  960,  1280,  1600,  1920,  2240,  2560,  2880, 3008,  3200,  3520, 3840, 4096, 5632 };
#define  RESOLUTION_CHOICES_X CHOICES(     "640","960","1280","1600","1920","2240","2560","2880","3008","3200","3520",3840","4096","5632")Even though your 50d can't  do 5632 it will go to the  next max. available size to you

@reddeercity Mlv_lite and crop_rec doesn't compile for 50D in Crop_Rec-4k-5d2-magic-lantern_redercit_buffer_a1ex-code-10-22-2018

I know mlv_lite didn't but wasn't sure about crop_rec  , I meaning to look in to it .
I can't even remember what error there where for mlv_lite , I need sound & HDMI support so I just kept with mlv_rec .
mlv_lite doesn't work very well with HDMI and there no sound surport in the 4K branch yet for 5D2 in mlv_lite
but I guess for the 50d there's no sound recording so you my have too look in to it your self , I my not get to it for a long time.

It took waza57 some time to get the crop_rec to work with the 5d2 , I would need to see the errors to understand
why it's not compiling .

[ilia3101]

1888x704 @ 48fps

Very nice!!! (edit: before I somehow missed that you got that resolution despite looking at the images 🤦)

Is it possible to disable the squeeze and have that same resolution without it?

Sorry if my spam is getting annoying, but is it possible to get higher vertical than the 2880x1080 preset if you lower the fps? Something like 2880x1200 at 21fps

[reddeercity]

Is it possible to disable the squeeze and have that same resolution without it?

No, at 48fps the max vertical is 704 , maybe 750
The nice think about the 5D2  with 3x5 , there no more aliasing and moire then you see in 3x3
plus at 48fps the frames are cleaner I think , good enough for smooth slow-mo @ 24fps

......  but is it possible to get higher vertical than the 2880x1080 preset if you lower the fps? Something like 2880x1200 at 21fps

In crop_mode I'm planning on 3008x1200 @ 24fps , it's almost there got sidetrack by the 4k vertical compressed height dev.
currently I have 2712x1200 @ 23.976fps & 2560x1200 @ 23.976fps
I'm also thinking of adding some square presets , 2144x1330 , 2144x1586 & 2144x1842(maybe) currently there are at 9.9fps but hope to get 24

[reddeercity]

I got (compressed vertical) 4416x1608 @ 23.98 working (A.R. 2.74:1) , would this resolution be useful ?
Or I can go to 4250x1722 @ 23.976 (A.R. 2.46:1) , I'm still keeping 3840x1872 (A.R. 2.05:1) & 4096x1776 (A.R. 2.30:1) @ 24fps
I just don't want too many presets or I can have both . **Note these are un-compressed vertical resolution**

[Danne]

No 2.35:1 preset?
By the way. Are you getting any real-time preview on any of your squeezed presets or are all of them 'framing' preview based?

[ilia3101]

No, at 48fps the max vertical is 704 , maybe 750

I didn't mean unsqueezed equivalent of 1880x704, I meant just 1880x704 but not squeezed, so basically a wide aspect ratio. 1880x704 matches pretty well to 2.67 if it were 3x3.

Would that be possible?

The nice think about the 5D2  with 3x5 , there no more aliasing and moire then you see in 3x3

There's got to be some difference, so I would use the 3x3 just to be safe as I like wide aspect ratios anyway.

I'm planning on 3008x1200 @ 24fps , it's almost there got sidetrack by the 4k vertical compressed height dev.
currently I have 2712x1200 @ 23.976fps & 2560x1200 @ 23.976fps
I'm also thinking of adding some square presets , 2144x1330 , 2144x1586 & 2144x1842(maybe) currently there are at 9.9fps but hope to get 24

This is good news! I tried changing fps override timers in the 2880x1080 build in first post, also the registers crop_rec lets you change, but it seems locked to height 1080. Guess I'd need to use whatever branch you are using to actually come up with these values. The name of it is not coming to my head right now.

[masc]

I got (compressed vertical) 4416x1608 @ 23.98 working (A.R. 2.74:1) , would this resolution be useful ?
Or I can go to 4250x1722 @ 23.976 (A.R. 2.46:1) , I'm still keeping 3840x1872 (A.R. 2.05:1) & 4096x1776 (A.R. 2.30:1) @ 24fps
I just don't want too many presets or I can have both . **Note these are un-compressed vertical resolution**

That all sounds so promising! The release date for all this will be a perfect day!
If I think about what I use most, then this should be A.R.s between 16:9 and 2.35:1. But maybe 2.74:1 is useful for someone out there...

[Igor_Braun]

let's send from each person one good of the place where he lives to Reddeercity? =) hehe.. That's absolutely incredible.

I absolutely agree with Masc about 16:9 and 2.35:1

[aprofiti]

I'm trying to get full heigth from vanilla 5x just like a1ex and reddeercity already did, but doesen't appears to extend image stright off like previous full width experiment.

I'm getting that pink bottom like this and can't get clean image like this by just increasing Timer B and Head timers.

[reddeercity]

I'm trying to get full heigth from vanilla 5x just like a1ex and reddeercity already did,
but doesen't appears to extend image stright off like previous full width experiment.

I'm getting that pink bottom like this and can't get clean image like this by just increasing Timer B and Head timers.

That's a CMOS[1] adjustment (Vertical Offset) & Head Timers c0f0713c & c0f07150 (vertical window size for liveview)
not sure if these are the same in 50d . I get this for time to time also but sometimes refreshing liveview fixes it (half shutter)
Good that you posted , I'm currently working on those square presets for 24p (2144x1586)
Got it work at 2144x1448 @ 23.976 ( I wanted some tall 4/3 preset - I like that look)
So I took that experiment  and built around it , getting these extended height can be difficult .

Here a procedure I use to get extended height in 5x zoom(2144x1586) on 5d2 (default 2144x1074)
1-Slow Timer'B" down to 9.98 fps (C0F06014: 0xEDC)
2-Adjust Raw Height C0F06088: 0x66A04BA (1586x2144) we read it as 2144x1586
3-Adjust the Vertical Liveview window (head timers) C0F0713C from 0x476 -> 0x676  & C0F07150 from 0x49C -> 0x69C
Need to do so math for the C0F07150 head timers e.g. 0x49c=1180 vertical default for 5d2 (1074) we need 1586+52(OB offset)=1638
0x69c=1692 , C0F0713C 0x476=1142 (default) need 1586+52(OB offset)=1638  0x676=1654 more then we need but I think you get I the idea .
4-CMOS[1] Vertical Offset adjustment , 0xE6A (default)  change to 0xBOD (just need to play around cmos[1] trial & error)
5-Increase frame rate , c0f06014 0xEDC to 0x4something etc...

That's the basics , adjust slowly -- if you flip thought the adjustments too fast you can either lockup the cam or loose the image (liveview turns black)
At best most or this is just trial & error plus a few lucky breaks 
 
Edit: Are you using the 50d 10-12bit build from the experimental download page
or did you use a build compiled from my source file with the add parts (redirect buffer for extended res.) for 50d ?

[reddeercity]

Still adjust different presets , trying to get more height in the 2k range
Figured out 2400x1330 @ 23.976fps real time color preview (same as canon preview) while recording raw video
record times are short , about 20 seconds at the moment (I haven't starting on Over Clocking the CF card Bus yet that's next)




You may wonder what the last three reg's are for , they are for the liveview preview while recording instead of a frozen liveview
c0f08184 = preview height,  I set this to the raw height +52 (the OB area)  0x467(1127)=>0x56a(1386)
c0f08188 = preview width , I set this to the total raw width+(OB Area 160) 0x907(2311)=>0xa07(2567)
c0f08518 = both preview height & width 0x4670907->0x56a0a07 ( 1127x2311)->(1386x2567) and of course we read this as 2567x1386   

[benoit]

Figured out 2400x1330 @ 23.976fps real time color preview (same as canon preview) while recording raw video

Great Reddeercity, "color realtime preview" I can't believe it ! the wimps will be glad when you release it !
Can't wait the date ! 

[aprofiti]

That's a CMOS[1] adjustment (Vertical Offset) & Head Timers c0f0713c & c0f07150 (vertical window size for liveview)
not sure if these are the same in 50d

Not quite sure abut CMOS[1] on 50D... his default value is 0x1 and doesn't seems to change from photo mode.
Tryed to increase by little steps but no feedback from LV image.

Instead CMOS[5] looks more interesting, because it's default value is 0x628 after switching to 5x mode and increasing to 0x629 will move image up, decreasing will move image down till image get duplicated/distorted.

Unfortunately small modifications from that value doesn't cover pink are with valid data, just transalate sensor image in upper area untill it gets white...
Didn't tryed increasing/decreasing by larger value, but if this is what you get from CMOS[1] on 5d2, maybe is what I'm looking for.

Here a procedure I use to get extended height in 5x zoom(2144x1586) on 5d2 (default 2144x1074)
1-Slow Timer'B" down to 9.98 fps (C0F06014: 0xEDC)
2-Adjust Raw Height C0F06088: 0x66A04BA (1586x2144) we read it as 2144x1586
3-Adjust the Vertical Liveview window (head timers) C0F0713C from 0x476 -> 0x676  & C0F07150 from 0x49C -> 0x69C
Need to do so math for the C0F07150 head timers e.g. 0x49c=1180 vertical default for 5d2 (1074) we need 1586+52(OB offset)=1638
0x69c=1692 , C0F0713C 0x476=1142 (default) need 1586+52(OB offset)=1638  0x676=1654 more then we need but I think you get I the idea .
4-CMOS[1] Vertical Offset adjustment , 0xE6A (default)  change to 0xBOD (just need to play around cmos[1] trial & error)
5-Increase frame rate , c0f06014 0xEDC to 0x4something etc...

Yes, basically it's what I'm doing, except for CMOS. From photo mode 0xc0f06088 = c9d09bb, 0xc0f06014 = c9c and 0xc0f06008 = 4f504f5

Noticed that timers appears to have a little overhead based from math you pointed to me before, should I try to reduce timer and resolution (to mach cr2 and reduce black area) later when I get Full Resolution working?

That's the basics , adjust slowly -- if you flip thought the adjustments too fast you can either lockup the cam or loose the image (liveview turns black)
At best most or this is just trial & error plus a few lucky breaks 

Cycling through video mode will usually help to get LV working when gets completely dark.

Edit: Are you using the 50d 10-12bit build from the experimental download page
or did you use a build compiled from my source file with the add parts (redirect buffer for extended res.) for 50d ?

I'm using your source files with the addittion of 50D's stubs for CONFIG_EDMAC_RAW_PATCH support.
I still need to recompile with what you told me before to add extendeds resolutions.

[ilia3101]

@reddeercity are you using the iso-research branch with adtg gui module to come up with these settings? I'm wanting to try... I see you posting screenshots of your settings which seem like a good starting point.

Also have you been able to create any presets (that can be selected in crop_rec menu) since that time Danne tried to put it in crop_rec.c?

I have been reading the code and competely confused how a preset is added to the menu. Why can't it just be a struct with some values...

[reddeercity]

@Ilia3101 I'm working on the code , lots of parts to deal with .
if you what to try , use the build on the first page of this thread then
download the ADTG_GUI.mo from https://builds.magiclantern.fm/modules.html
that's the one I use . Only load mlv_rec.mo & adtg_gui.mo -- Do Not load the crop_rec.mo

[reddeercity]

Can somebody check this please , I'm not sure about the "case cmos_new[1]:"
not sure if I need to add it here or somewhere else
I'm using waza57 crop_rec source 5d2_crop_rec.c
Starting at Line 1508 of crop_rec.c is where I made the changes , I'm using the values from this post here

Code: [Select]

static inline uint32_t reg_override_zoom_fps(uint32_t reg, uint32_t old_val)
{
    /* attempt to reconfigure the x5 zoom at the FPS selected in Canon menu */
    if (is_5D2)
    {
     int timerA = 679 ;         //waza57 good values for 23.976: 804- 1245  and 807 - 1237
     int timerB = 1471 ;     
     int a = reg_override_fps_nocheck(reg, timerA, timerB, old_val);
        if (a) return a;
           switch (reg)
            {
                /* raw resolution (end line/column) */
                /* X: (3072+140)/8 + 0x17, adjusted for 3072 in raw_rec */
               
                case cmos_new[1]:
                    return (old_val & 0x0000000) + 0xb0d  ;

                case 0xC0F06084:
                    return (old_val & 0x0000000)  ;
               
                case 0xC0F06088:
                    //return (old_val & 0xFFFF0000) + 0x630 ;
                    return (old_val & 0x00000000) + 0x56a053a;   //0x4b00648 or origin value chang nothing

                 /* HEAD3 timer */
                case 0xC0F0713c:
                    return 0x566 + YRES_DELTA + delta_head3;

                /* HEAD4 timer */
                case 0xC0F07150:
                    return 0x58c + YRES_DELTA + delta_head4;

                case 0xC0F08184:
                    return (old_val & 0x0000000) + 0x56a ;

                case 0xC0F08188:
                    return (old_val & 0x0000000) + 0xa07 ;

                case 0xC0F08518:
                     return (old_val & 0x0000000) + 0x56a0a07 ;                   
            }
Here Line-594 there's a cmos[1] change , I thinking that's where I should put the new cmos[1] value

Code: [Select]

  if (is_5D2)
                {
                cmos_new[1] = PACK12(42,57);//0xB0D;    /* pink highlights without this */
                cmos_new[2] = 0x10E;    /* read every column, centered crop */     //waza57 cmos 6
                break;


Edit: I updated my source with the 50d stubs for "CONFIG_EDMAC_RAW_PATCH" support
Crop_Rec-4k-5d2-50d-magic-lantern_1-9-2019.zip

[theBilalFakhouri]

Figured out 2400x1330 @ 23.976fps real time color preview (same as canon preview) while recording raw video

You may wonder what the last three reg's are for , they are for the liveview preview while recording instead of a frozen liveview
c0f08184 = preview height,  I set this to the raw height +52 (the OB area)  0x467(1127)=>0x56a(1386)
c0f08188 = preview width , I set this to the total raw width+(OB Area 160) 0x907(2311)=>0xa07(2567)
c0f08518 = both preview height & width 0x4670907->0x56a0a07 ( 1127x2311)->(1386x2567) and of course we read this as 2567x1386   

This is great! Do you mean also the real-time preview now is uncropped ? It shows the entire frame in real-time?

[reddeercity]

This is great! Do you mean also the real-time preview now is uncropped ?

Yes , until recording raw , then just like the default crop_mode it center crops
but I never tried with the overlays enabled as I have "kill overlays on recording"
in mlv_rec , get me a extra 25% write speed .
So it may with overlays  I'll check next time I have it loaded up.
Here I posted a iPhone video or the lcd screen showing the Liveview as I record 2400x1200 @ 23.976fps .

I know before with default crop_mode (2144x1074) if you press half shutter , you get a color preview with correct full framing
while recording , so I'm not sure it there's ML code that does the resizing or if it's a reg , maybe in the "preview regs"

[Danne]

Still adjust different presets , trying to get more height in the 2k range
Figured out 2400x1330 @ 23.976fps real time color preview (same as canon preview) while recording raw video
record times are short , about 20 seconds at the moment (I haven't starting on Over Clocking the CF card Bus yet that's next)




You may wonder what the last three reg's are for , they are for the liveview preview while recording instead of a frozen liveview
c0f08184 = preview height,  I set this to the raw height +52 (the OB area)  0x467(1127)=>0x56a(1386)
c0f08188 = preview width , I set this to the total raw width+(OB Area 160) 0x907(2311)=>0xa07(2567)
c0f08518 = both preview height & width 0x4670907->0x56a0a07 ( 1127x2311)->(1386x2567) and of course we read this as 2567x1386   

Are these the complete set of registers changed? Could you recheck if any setting is missed when selecting overridden regs only?

[ilia3101]

@reddeercity Is it techninally possible to get slow motion 48+ fps in crop mode? If I were to copy your slow motion registers while in 5x would it be effective? Or does that need something completely different


@a1ex We have been discussing with Danne about making presets for crop_rec out of the sets of registers that reddeercity has been finding. It seems really difficult, can there not be a way to just have them in some c structs/arrays?

soething like

Code: [Select]

preset_struct presets[ ] =
{
    {
        .name = "preset1",
        .num_registers = 2,
        .registers = {register1, value1, register2, value2}
    },
    {
         .name = "preset2",
...


[reddeercity]

@reddeercity Is it techninally possible to get slow motion 48+ fps in crop mode? If I were to copy your slow motion registers while in 5x would it be effective?
Or does that need something completely different

Yes needs something different, 48fps is dependent on line skipping & vertical compressed (3x5) which only work will in 3x3
you can force line skipping  in 3x crop but can't produce a useable image (being trying for 2 weeks now)
The best to hope for in crop mode would be a very small crop window e.g. 1280x430 (crop factor of about 4.5 which I have no interest in)
The simple fact that the sensor is very slow (96MP/s) kept it from any meaning full resolutions & or hi-frame rate .
This is a fact that can't be changed at present , Overclocking the sensor frequency would be the only way (24->32 maybe ?)
a1ex would the only one that would know for sure.
But you got to ask yourself , is worth it ? there would need to be more voltage among other variable (just like overcocking PC CPU)
Can it handle it or will it burn up ?

But you can certainly explore the possible , All my note are here on my thread .

..... discussing with Danne about making presets for crop_rec out of the sets of registers that reddeercity has been finding.
It seems really difficult, .....

No it not difficult , I got it figured out just been too busy to finish coding it .
D4 cams work a little different then d5 cams in crop_rec . (this is no small thing , it took @waza57 some time to get it to work , more then a mirror hack)
beside that , I not very impressed with 4k compressed vertical (4096x590)
It seems to produce more artifact then standard 3x3 (1856x1248)  , I guess because of the different pixel binding then d5 -- it's worst then d5 cams .
So I guess just because you can implement something doesn't mean you should . 
I'm looking at this from a video production side (that why I won't have anything that doesn't record @ 24fps - besides Full Res (5632x3755@4.5fps)
I'm re-evaluating all my presets , sorry for the delay but life come first 
As this part of the development is coming to a close for the 5D2 , other d4 cams with users need to catch up on there own (I'll still help where I can).

After I finish the crop_rec for the 5d2 , I'll spend my time now on overclocking CF card bus & Lossless compression .
I know the limitations of the sensor now  , I pushed it as far as it can go (I can see a cam upgrade for me in the future maybe 5d3 or 5d4)

[ilia3101]

Yes needs something different, 48fps is dependent on line skipping & vertical compressed (3x5) which only work will in 3x3
you can force line skipping  in 3x crop but can't produce a useable image (being trying for 2 weeks now)
The best to hope for in crop mode would be a very small crop window e.g. 1280x430 (crop factor of about 4.5 which I have no interest in)
The simple fact that the sensor is very slow (96MP/s) kept it from any meaning full resolutions & or hi-frame rate .

Assuming 96 is a reachable limit, here's what we would be able to get at 60fps:

Aspect	Max resolution
2.67:1	2064x774
2.35:1	1936x824
16:9	1680x945

This sounds really appealing if possible to me. I'm sure it's probably not possible to reach that limit so perfectly, but those resolutions might be doable at something lower like 50fps.

But you can certainly explore the possible , All my note are here on my thread .

What you have been doing is definitely very helpful.

No it not difficult , I got it figured out just been too busy to finish coding it .
D4 cams work a little different then d5 cams in crop_rec . (this is no small thing , it took @waza57 some time to get it to work , more then a mirror hack)

It is difficult to understand though, I still have no clue how to make presets.

I'm looking at this from a video production side (that why I won't have anything that doesn't record @ 24fps - besides Full Res (5632x3755@4.5fps)

I would personally like to make lower fps ones just for higher, but not full, resolution recording. It works if there's no speech or fast movement.

I'm re-evaluating all my presets , sorry for the delay but life come first 

Understandable

After I finish the crop_rec for the 5d2 , I'll spend my time now on overclocking CF card bus & Lossless compression .

Any of those two things would be AMAZING 😍

I know the limitations of the sensor now  , I pushed it as far as it can go (I can see a cam upgrade for me in the future maybe 5d3 or 5d4)

You definitely deserve the upgrade.

I am starting not to want to upgrade ever though, 5D mark 2 is too much fun. How endlessly can the 11 year old camera be pushed?

[70MM13]

I pushed it as far as it can go (I can see a cam upgrade for me in the future maybe 5d3 or 5d4)

get the 5D4!!!  let's not wait until it is 11 years old before it is supported!
you're the man to make it happen!