Messages

Would it be possible to program one of the 'lesser used' buttons (by my day to day use at least) like the DoF preview button, to quickly set 1 out of 3 (Shutter, Fstop, ISO) and have the other two variables 'auto expose' using the same projected graph, based off the 1 constant you set?

well this is most requested feature, firstly this has to be implemented: http://www.magiclantern.fm/forum/index.php?topic=7816

Autoexposure hasnt worked on 600D for awhile now

should work on 600D
http://nanomad.magiclantern.fm/jenkins/features.html

you can cache hack and take over the copyolcdata function and read out its parameters then send it on its way? Somehow this is done for the cmos/adtg functions?

could please you send me some hints how to do it?

A1ex could you please send your script, that generates this API from comments? I would like to make ML modules API.

and what about button assigment? like the canon info screen?
You can select items and invoke custom callback function and give a pressed key as arg0.¨
http://www.magiclantern.fm/forum/index.php?topic=7816.0

nice, and do you have idea for movie mode? Sound, buffer, time etc?
For custom content we can use flexinfo?

nice UI, but I want to solve how to show both helps (.help, .help2) and warnings at same time
sometimes I have to turn on LV or switch something on/off to hide warnings and show .help2 which is in many cases important to see
any ideas?

I will analyze these curves to better understand how to use this algorithm.

well now autoexpo is little complicated, this is a prototype, it will be simplified soon I hope

No, they look ok.  EC also works but the shutter is stubborn.

well could you try press shutter half way and remember what values it set, and goto the autoexpo menu and compare with values at the cyan linem, does it match?

Would it possible to add this as an easy option?

not now, my goal for now is finding a brightness sensors

so your photos are underexposed?
there can be conflict with other features, not fixed yet
and what the graph looks like?

I tried gdb_add_watchpoint into copyOlcDataToStorage func and to jump table, but it wasn't triggered.

or you can cache hack and take over the copyolcdata function and read out its parameters then send it on its way?

well this is too hard for me, I take a look at cache hack functions

what GDB?

maybe we can use mem_spy but where it can be stored? what address?

not triggered anywhere

Code Select Expand

ADD             R0, SP, #0xC ; jumptable FF8A02B0 case 59
STMIA           R0, {R4,R5,R9}
ADD             R0, SP, #0xC
BL              sub_FF9D65B0 ; copyOlcDataToStorage

https://docs.google.com/document/d/1T6QhhzOc0Nf0fc8XOpuYgD2JenfVEoRGTJd2aT9T2qs/edit

Well I need some help with reverse engineering.
I want to find brightness sensors in viewfinder.
If we found it we can implement ETTR in shooting mode or "auto exposure compensation" as I call it. I will describe it later.

There is a few ways how to find it. I choose debug flag.
After some research with nanomad I found that AE_VALUE is probably set in function copyOlcDataToStorage.
Nanomad says that function copies computed AE_VALUE from Toshiba MCU.
So my first step is find the address from is the data copied. I tried to set debug flag here, but it doest work, my flag wasn't triggered. There is some reasons why:
I spy wrong address (maybe I have ROM image wrong loaded)
AE_VALUE is set somewhere else
g3gg0 iirc some cameras permanently cleared the ICACHE in PwrMgr task, not sure if this is the case on 5D2

So please could anybody spy this?

Code Select Expand


LDRB            R0, [R8,#2]      ; R8 is what we need
STRB            R0, [R9,#0x1D]   ; 0x1D is struct offset of AE_VALUE

use this https://bitbucket.org/hudson/magic-lantern/pull-request/193/debugger-module

Talking of that, another request: Please also mark the currently/last measured bv with a vertical bar in the graph so one can instantly see what the resulting av/tv/iso _right_now_ are w/o any further hassle :-)

already done

I'm going to vacation, I will be left for 14 days. See later.

Btw here is the patched version:
https://bitbucket.org/pravdomil/magic-lantern-hack/commits/0352dd9cf59c8968f1a25727b878a1bd109218b5

bad news
https://bitbucket.org/hudson/magic-lantern/commits/d34836ca7e44028ea7019cbff3a2ca5ae29f22cb

I originally wanted to implement it in the autoiso module, but since your autoexpo now has ec on m and only in m can modify both shutter & iso imho it makes sense to implement it here and leave the autoiso module to good ol' Tv/Av.

Agree, autoiso by a1ex was experimental feature.

Pravdomil, I've got a request that imho is important for action flash shooting

I was shotting with flash more then 4 years ago, I have no flash now. And I prefer shooting without it.
Sorry, I will not be the one who does it.

The reason just I don't do this myself is that I first wanted to discuss the idea and also see if you'd add it yourself since you're a much, much better programmer as I am and can implement these curve modifications while I'd probably fail at it :-o

When I came to ML I don't know much about C, so try it, make pull req and I will give you some hints if I can.
Maybe some other dev will join 1%?

@Audionut
I understand now, but I have no idea how to implemented in C yet

I'm waiting for merging with offic repo but devs have a vacation time?

next update https://bitbucket.org/hudson/magic-lantern/pull-request/196/autoexpo-update/commits

Request this on as default.

done default lens av = this lens

I have implemented min ISO & min AV & EC changes.
I tried to implement min TV relation but it doesn't make sense for me, could you please post some example?
Above that I want to have same TV on and set min TV without changing other variables.

[-]

Can you determine the max Av of a lens?  Currently with -EC, Av max doesn't respect lens limit.

turn on lens AV

Same TV relations (it works both ways)

Code Select Expand

if you increase ISO min => move EC curve and ISO curve to the right, also decrease AV max
if you increase AV min  => move EC curve and ISO curve to the left
if you increase EC      => move EC curve and ISO curve to the left, also decrease AV max
if you increase ISO max => move EC curve and ISO curve to the left ??
if you increase TV min  => decrease AV to AV min if not possible move EC curve and ISO curve to the left ??

agree?

well I could implement it to autoexpo module
http://www.magiclantern.fm/forum/index.php?topic=7208.0
there will be an option to attach camera buttons to specific function (eg. min AV)
and on 5D2 we have rear dial and speed dial and ae lock free in M mode

Díky

Maybe a found out relations between our properties.

Code Select Expand

iso_min => ec_off & iso_off & av_max
av_min  => ec_off & iso_off
ec      => ec_off & iso_off & av_max
tv_min  => ec_off & iso_off

iso_max => ec_off & iso_off ??

agree?