Crop mode recording (crop_rec.mo) (1:1, RAW/H.264, 25/30/50/60 fps)

[hyalinejim]

You are the man, a1ex! This is a great aid for getting precise rectilinear compositions at higher resolutions. Prior to this it was like trying to use a shift lens in the horizontally offset position. It's also a boon for those wishing to use anamorphics without one side being heavily vignetted.

[a1ex]

Ouch, not exactly the easiest workaround.

2nd thing i "noticed" is that 1:1 mode is extremely overexposed compared to 3x3

I've just found an overexposure bug when using FPS override (actual exposure time is incorrect, usually higher than expected). Were you using it when you had the issue?

[Quentin]

Thanks to all people that contribute.
Any recent build with the new crop developments ?
Thank you

[a1ex]

Just committed the centered 5x zoom, the overexposure fix, and some refactors to ease porting to other camera models. EOS M support is included too (thanks rbrune).

Test build coming after feedback from those who understand the code

[budafilms]

Great work my King! 

[nikfreak]

just discovered that you are reading out old hardcoded values for edmac_raw_slurp now automagically via the registers. Probably you will be using this technique and adding the skip values for centering x5-zoom on all cameras later, right?

[DeafEyeJedi]

just discovered that you are reading out old hardcoded values for edmac_raw_slurp now automagically via the registers. Probably you will be using this technique and adding the skip values for centering x5-zoom on all cameras later, right?

+1

[a1ex]

Right, this covers all video modes without having to hardcode them.

Still need one camera-specific constant: the multiplier for horizontal resolution (I guess it's number of columns read out in parallel, and I believe it's the same for all video modes). Known range: from 1 (500D) to 8 (5D3). Also, older cameras use 0xC0F0608[04] instead of 0xC0F0680[04].

[nikfreak]

static unsigned int crop_rec_init()
{
    if (is_camera("5D3",  "1.1.3") || is_camera("5D3", "1.2.3"))
    {
        /* same addresses on both 1.1.3 and 1.2.3 */
        CMOS_WRITE = 0x119CC;
        MEM_CMOS_WRITE = 0xE92D47F0;
       
        ADTG_WRITE = 0x11640;
        MEM_ADTG_WRITE = 0xE92D47F0;

typo or unique 5D3 thingie?

[a1ex]

Both functions happen to start with the same instruction. Didn't check other cameras.

[DeafEyeJedi]

Felt this was worth sharing.

[Quentin]

Does the latest NightBuild 18 Dec 2016, includes the new Crop mode ?

[Walter Schulz]

?
Latest Build date is 2016Dec03.

[Quentin]

Dunno, maybe was withdrawn. I downloaded it but didnt test it.

[Walter Schulz]

I doubt you downloaded something from the main branch. You should be able to determine the download link.
Something like
https://builds.magiclantern.fm/jenkins/job/<camera type>.<firmware version>/<build number>/artifact/platform/<camera type>.<firmware version>/magiclantern-Nightly.2016Dec18.<camera type><firmware version>.zip

[Quentin]

I have it handy.
If someone wants the today version, I dont mind sending it to him

[Walter Schulz]

I hope it was build after g3gg0 re-edited his changes ...

[Julien]

First, Big up to all developers and all ML community including @Hans_Punk, @Danne, @a1ex, and the rest.

Second point, sorry for my level in english. It's not as well as I want.

Third, I try 3x crop mode on my 700D/T5i Rebel and it works good.
My question or better my wish, is to know if it's possible to have a variable/graduate crop mode module with ML or may be to develop this kind of possibilities?

What I mean when I talk about graduate crop mode?
With ML, 3x crop mode transform a 5O mm F1.4 lens in 150 mm for the same aperture.
I need a smaller extensions/crops like 1.4x crop or 1.6x crop or 2x crop which become 70 mm , 80 mm or 100 mm with the same 1.4 aperture.
It's like extension tubes or extender teleconverter, but numericaly with less or without loss of light in high magnification and disfraction of lights.
In fact,
 - 50mm lens + 20mm extension tubes or 1.4 extender = 70mm
   70 x f/1.4 = 98 divided by 50mm = f/1.96

What kind of utilities can we have with a graduate crop mode (x1.4/x1.6/x2)?
For instance, I use B4 2/3'' Angénieux and Fujinon lens.
Both have analogic extender (x2). The M4/3's digital camera sensor is full covered. No problem with a  Panasonic GH4 for instance.
If I use this kind of lens with my Canon T5i/700D, the APS-C sensor is not ful covered. There are small vignetting.
I think the sensor could be all covered with x1.4 or x1.2 crop.

That's why I ask this kind of new features in the developement of Magic Lantern crop mod.
Do you think it coulb be possible?

Thanks for reading

[vstrglv]

I have tried to merge Unified into crop_rec branch but failed. There are many conflicts. It is very useful if somebody post a tutorial how to  merge Unified into crop_rec branch, because crop_rec.mo is very, very useful.

[Danne]

How are you merging? Source tree? Usually I create a branch of unified then I merge crop_rec into my branch through source tree.
If you,re on mac you could post your workflow descriptions, questions and findings here.
http://www.magiclantern.fm/forum/index.php?topic=16012.msg155422#msg155422

[dfort]

Looks like this worked for @vstrglv

Code: [Select]

hg update unified
hg pull
hg branch unified_crop_rec
hg merge crop_rec

[vstrglv]

Yes it works! Thanks to dfort. Tested on 5D3.113, OK until now.

[clement2]

Is there any chance I can get the latest build version with the last update crop mode module? I am idiot on programming. I am 5d3.113. thx.

[RenatoPhoto]

@ A1lex and Greg
Fantastic module!  I use it 99% of the time..  and thanks for providing it for 5D3-1.23 firmware.
Thanks for dedication and hard work.

[aschille84]

Yes it works! Thanks to dfort. Tested on 5D3.113, OK until now.

@vstrglv Care to share a test build? Still working with crop_rec and 10/12-bit?


Sent from my iPhone using Tapatalk