Messages

Yeah it's confirmed. The B timers are necessary for it to work. At the same time they are root cause of the "slowish" LCD.
Need to check what's going on or where the limits really are. I'm out too. Gonna pick it up again later.

Btw: my VM is up and running. Thx for assisting with zips.

Still no luck. That's strange. Maybe the fps timers? I see you got this included:

https://bitbucket.org/Dannephoto/magic-lantern/commits/fe375ba28b3a6602906e13c84d50561c1c8701a9?at=crop_rec_4k_mlv_lite_snd_sd_uhs_HDR_ext_all_bits

Height should be doable by adjusting additionally ADTG2 registers. Needs definitely some time. Guess it should suffice if you remerge 100D_merge_fw101 into crop_rec_4k branch  from ML repository and provide that zip here to find out what's wrong.

My working NB is dead. I took my HP 13" hackintosh and natively installed win7 again onto it to have something to play with - I yet have to setup my compiling environment.

Bad news:
1:1 modes cause headaches. one has to put a lot of more work / time / hunting into it for getting it to work.

good news:
I can also extend "Movie Crop mode" with same technique to round about 2450x1020 resolution. Importing clip into MLV App looks good. Didn't try to extend it more for now. Guess still good stuff achieved as we are able to extend width by a great margin.

Mystery:
autofocus puts the lcd / camera in some kind of "low fps" mode. Looks like 3 / 4 / 5 fps. crop_rec Builds from the experiments page don't have this. Guess you have a typo somewhere in fps-engio in your custom build. Strange thing: I can't replicate my achievements with the builds from experiments page. Your adtg gui module just can be enabled with them. Your build and the ones from experiments page differ in such a way that I can replicate always on your builds but never on the one from experiments page. Is it the latest comiits from 100D missing in crop_rec? a1ex can you please merge 100D into crop_rec again?

cool seems we can use this technique also for 1:1 modes (ofc wih other values) and scratch X5 mode. Quick test before battery went empty was 20xx * 1152 resolution but the top 1/10 of the image had dirty output

No preset. Manually adjusted each time. Presets can be done in crop_rec module or you modify the 5D3 ones in adtg_gui.c:

https://bitbucket.org/hudson/magic-lantern/src/f683753bc4e3f5ef05a8ac86cab32f751aa39db0/modules/adtg_gui/adtg_gui.c?at=iso-research&fileviewer=file-view-default#adtg_gui.c-1105

Dirty hack:

Code Select Expand


static int crop_mode_reg(int reg)
{
       return 0;
}

static int res3k_reg(int reg)
{
    if (regs[reg].dst == 0xC0F0)
    {
        switch (regs[reg].reg)
        {
            case 0x6804:                /* C0F06804 - raw resolution */
                return 0x4580311;       /* from 0x528011B -> 3072px in raw_rec */
            case 0x6824:
               return 0x4ca
           fill in rest as seen in my posted screenshot
          fill in rest as seen in my posted screenshot
         fill in rest as seen in my posted screenshot
        fill in rest as seen in my posted screenshot

        }
    }

    return 0;
}


You fill in all other cases as seen in my posted screenshot.
In adtg gui advanced submenu you select ""1:1 3K crop mode (5D3)" to set your "dirty" preset. Afterwards you can verify by selecting "overriden regs"

Yeah I am running your version atm. 100D even hangs if you follow other ppl's tuts for using adtg gui for e.g. we already hang when switching to play mode.

You do it this way:
Stills mode - turn adtg gui module on and enable "Digic Registers" as well as "Known regs". Take a photo in stills mode.
Turn off adtg gui module again or it will hang next
Switch to movie mode
Turn adtg gui module on again.
Switch to X5 zoom mode
Open ML menu and override registers as seen once done open CANON MENU.
Close CANON MENU again.
Switch to X5 zoom mode and be happy about and extended rsolution (width)
check / adjust  RAW Video resolution

Dunno if its my old branch you compiling off which causes these headaches or something else but 100D should hopefully soon become unified party member so we can compile from "offical" ML branches. Having to handle custom branches and always remerge my stuff is a pain - at least for me.

Check, managed to record another clip:
https://drive.google.com/file/d/1UjL9dTxwGxR5JuVbTCAR7_Ivgy4Pofuo/view?usp=sharing
https://drive.google.com/file/d/1JDtO_E2-tDyiYXI60j9FwU0sTOavD5D-/view?usp=sharing

[xx]

29xx (W) * 107x (H) in X5 zoom mode:
https://drive.google.com/file/d/14nFXHTKfLSTjWfgtPInJtPMu1pTIW3CO/view?usp=sharing

Take it with a grain of salt. Values just found by failing/ trying / hunting. I am getting too much (m)alloc errors with adtg gui enabled and only managed to record one clip earlier when I posted the screenshot. We could try to implement it for testing into crop_rec module though. Extending height is another story

Yes those! 

battery pull-outs rubbing my nerves:
https://drive.google.com/drive/folders/1qQ0SRRHxP3-u3k6iCi4r8Akhpc70gh53?usp=sharing

Will see if I can replicate again tomorrow and try to reach limits for 24fps. Maybe we will get lucky as 100D has some fps potential

Thanks!Liveview is totally uneditable atm on 100D. Hangs relatively fast.
Danne waiting for you. Maybe we can consider removing lines 861 as well as 874 too forget that
Thx in advance.

would it be sufficient to disable / commentout lines 862 / 863 as well as 875 / 876 ??
https://bitbucket.org/hudson/magic-lantern/src/f683753bc4e3f5ef05a8ac86cab32f751aa39db0/modules/adtg_gui/adtg_gui.c?at=iso-research&fileviewer=file-view-default#adtg_gui.c-862

Nevertheless Danne if you can modify the known regs above would be cool.

You would have to modify "Known regs" to adjust to my request starting here:
https://bitbucket.org/hudson/magic-lantern/src/f683753bc4e3f5ef05a8ac86cab32f751aa39db0/modules/adtg_gui/adtg_gui.c?at=iso-research&fileviewer=file-view-default#adtg_gui.c-31

Leave CMOS 1-7 values and replace all following to the ones a1ex uses for 5D3 in crop_rec branch. It should be like this:

Code Select Expand


static struct known_reg known_regs[] = {
    {DST_CMOS,      0, 0, "Analog ISO (most cameras)"},
    {DST_CMOS,      1, 0, "Vertical offset"},
    {DST_CMOS,      2, 0, "Horizontal offset / column skipping"},
    {DST_CMOS,      3, 0, "Analog ISO on 6D"},
    {DST_CMOS,      4, 0, "ISO-related?"},
    {DST_CMOS,      5, 0, "Fine vertical offset, black area maybe"},
    {DST_CMOS,      6, 0, "ISO 50 or timing related: FFF => darker image"},
    {DST_CMOS,      7, 0, "Looks like the cmos is dieing (g3gg0)"},
    {DST_ADTG, 0x8000, 0, "Causes interlacing (g3gg0)"},
    {DST_ADTG, 0x8806, 0, "Causes interlacing artifacts"},
    {DST_ADTG, 0x800C, 0, "Line skipping factor (2 = 1080p, 4 = 720p, 0 = zoom)"},
    {DST_ADTG, 0x805E, 1, "Shutter blanking for x5/x10 zoom"},
    {DST_ADTG, 0x8060, 1, "Shutter blanking for LiveView 1x"},
    {DST_ADTG, 0x8172, 1, "Line count to sample. same as video resolution (g3gg0)"},
    {DST_ADTG, 0x8178, 1, "dwSrFstAdtg1[4], Line count + 1"},
    {DST_ADTG, 0x8179, 1, "dwSrFstAdtg1[5]"},
    {DST_ADTG, 0x8196, 1, "dwSrFstAdtg1[2], Line count + 1"},
    {DST_ADTG, 0x8197, 1, "dwSrFstAdtg1[3]"},
    {DST_ADTG, 0x82F9, 1, "dwSrFstAdtg1 and FPS related"},
    {DST_ADTG, 0x82F3, 1, "Line count that gets darker (top optical black related)"},
    {DST_ADTG, 0x82F8, 1, "Line count"},
    {DST_ADTG, 0x8830, 0, "Only slightly changes the color of the image (g3gg0)"},
    {DST_ADTG, 0x8880, 0, "Black level (reference value for the feedback loop?)"},

    {DST_ADTG, 0x8882, 0, "ISO ADTG gain (per column, mod 4 or mod 8)"},
    {DST_ADTG, 0x8884, 0, "ISO ADTG gain (per column, mod 4 or mod 8)"},
    {DST_ADTG, 0x8886, 0, "ISO ADTG gain (per column, mod 4 or mod 8)"},
    {DST_ADTG, 0x8888, 0, "ISO ADTG gain (per column, mod 4 or mod 8)"},
    {0xC0F0,   0x6000, 0, "FPS register for confirming changes"},
    {0xC0F0,   0x6004, 0, "FPS related, SetHeadForReadout"},
    {0xC0F0,   0x6008, 0, "FPS register A"},
    {0xC0F0,   0x600C, 0, "FPS related"},
    {0xC0F0,   0x6010, 0, "FPS related"},
    {0xC0F0,   0x6014, 0, "FPS register B"},
    {0xC0F0,   0x6018, 0, "FPS related"},
    {0xC0F0,   0x601C, 0, "FPS related"},
    {0xC0F0,   0x6020, 0, "FPS related"},
    {0xC0F0,   0x6084, 0, "RAW first line|column. Column is / 2. 600D: 0x0001007E."},
    {0xC0F0,   0x6088, 0, "RAW last line|column. 600D: FHD 1182|1070, 3x 1048|1102, HD 720|1070"},

    {0xC0F0,   0x6800, 0, "RAW first line|column. Column is / 8 on 5D3 (parallel readout?)"},
    {0xC0F0,   0x6804, 0, "RAW last line|column. 5D3: f6e|2fe, first 1|18 => 5936x3950"},
    {0xC0F0,   0x6824, 0, " "},
    {0xC0F0,   0x6828, 0, " "},
    {0xC0F0,   0x682C, 0, " "},
    {0xC0F0,   0x6830, 0, " "},
   
    {0xc0f0,   0x7134, 0, "HEAD3 timer (start?)"},
    {0xc0f0,   0x7138, 0, "HEAD3 timer"},
    {0xc0f0,   0x713C, 0, "HEAD3 timer (ticks?)"},

    {0xc0f0,   0x7148, 0, "HEAD4 timer (start?)"},
    {0xc0f0,   0x714c, 0, "HEAD4 timer"},
    {0xc0f0,   0x7150, 0, "HEAD4 timer (ticks?)"},
};



Hope didn't forget one. You can check from crop_rec branch crop_rec.c and search through "0xC0f06", "0x8" for ADTG, "0xC0f07". Check also user mk1174 posts where he posts screenshots for 700D. I remember him stating ADTG2 82B6 is needed too. add that too and post the updated adtg module. I hope with the reduced list it will become easier for us to test and the "lockups" will be less.

Can someone please create a special version of adtg module containing a submenu "crop_rec REGS" which only contains all regs from crop_rec.c: CMOS1-7 / ADTG2[0x8xxx] / C0F060xxx / C0F068xxx / C0F07xxxx

Should be round about 50 regs maybe less maybe more. Guess also useful for other cams.
100D apparently locks up often while fiddling with the submenus. Have to take out battery often.

I managed to get 3520x1980 with some pinkish LCD preview at 3.5fps. Half of lcd was broken / dirty output. Didn't record any stuff. My personal interest is in FULLRES_LV. I remember a1ex stating 5D3 could do silent pictures with 1/8000 or faster ?! Maybe I remember wrong. Above request could help with fiddling. Danne seems to work on same....

My notebook charger is broken.Using wifes atm lefthanded and right hand is handicaped / broken + plastered (read: not finger nor arm)

Thanks. Tried Danne's and Works!

As I can't do myself atm:
can someone provide me a working build with adtg module included for 100D plz??

last one I used to compile should have been this:
https://bitbucket.org/nikfreak/magic-lantern/branch/isoresearch

Good job, Danne. Thank you.

as far as I remember at least mv1080crop could do ~45 fps:

// no need to cause confusions as recording speed cannot handle such high fps in crop mode
// (ZOOM || MV1080CROP ? 1288 : 1970)) <-- these are ok while not recording.

Just try the values 

if you guys have time and interest you may want to check my comments in fps-engio.c for the 100D. Maybe recording at higher fps in movie crop mode (~45fps) is now of interest due to higher write speeds??

someone able to recover the picture(s) posted by mk1174 here:
https://www.magiclantern.fm/forum/index.php?topic=19300.msg183290#msg183290

Atm it's blank for me.

offtopic Q: any chance for unlocking "AF microadjustment menu" for rebels like 100D? 

EDIT: wrong link posted.

That's correct one:
hint, hint...

Levas if the card is labelled 45Mb/s you alread reached max performance. You will need to get a faster one for e.g. Sandisk Extreme Pro

Crossing fingers for stability. Thanks for taking time to achieve this @a1ex. You're awesome.