Messages

If you enable in Av/Tv modes, couldn't you apply the maths from a fixed (user set) aperture/shutter?

well we can't change aperture in TV and shutter in Av (fighting with Canon) !

definitely I left this idea until there will be some clear and realizable algorithm

now I have to fix 5D3 lag, add EC curve, round ISO values, maybe option to attach main dial and speed dial to some conf value

User should be able to control DOF while having the shutter/ISO curves respond accordingly.
User adjusts shutter and other curves respond.

well this is very hard to implement, you have to define all dependencies, I don't really know how to do that
if you will do some research, some excel file with graphs, it can be our starting point
for now I don't care about DOF and shutter, I only use setting in the first post
I don't know if I should implement 2 point curve

Note:  line 317
Should read the opposite way,

thanks I will switch it

2 is good.  More is always better 

have you idea how it can be done? what menu gui

EC=0  get 0

it should be 1

you find it!
https://bitbucket.org/hudson/magic-lantern/pull-request/180/autoexpo-working-on-5d3/

Camera freezes as chris_overseas notes above when "Lock ISO & AV" is set to off.

will be fixed as soon as possible
I don't know what is not working

Can we stop it using digital ISOs?  Confine it to ISO 100, 200, 400, 800, etc.

not yet, I will add a option
for now you can use round values at eg. at 3 + 1 EVpBV (APEX theory)

EC adjustment will be very handy. 

I will add it

This way I can lock aperture to f/2.8 most times (sharpest for lens and reasonable DOF), but the option to adjust aperture to f/1.4 for low light situations

well this is in todo list, you want two point curve

For me this seems like the almost-perfect 'auto' shooting control.
It's like a real 'P' where you actually program what you want the camera to do depending on the light.

definitely, this is meant as perfect auto exposure algorithm
I never have to set my exposure

It takes some playing with to figure out initially what settings are going to work for particular situations, so I imagine you will get a lot of 'how do I use this' from people that don't have the patience to play with it for a while after which it makes total sense.

true, maybe some video tutorial where will be explained, basic of exposure, APEX system and finally Auto exposure module (curves, ranges, limits)
this is warning for people that don't understand what auto expo do, please play with it for weeks before asking

I also don't understand why someone would need it to work in anything by Manual mode

agree

Now you did mention Exposure Compensation in the first post and I would love to see this

I have already think of it and I have some idea
another case - I need shoot low light scenes underexposed as they are (it can be done by setting minimum shutter value, but it is not cleanest sollution)
so EC will be just next curve
I will add
    EC value (which will constantly decrease or increase EC curve)
    EC range (min - max)
    EC curve (at BV +/- EV per BV)

thanks for feedback

I have to go now to the airport to pick up Nanomad and Audionout and others...

G3GGo is from Germany and A1ex I think form Romania (not sure), Nanomad from Italia, Audionut dont know
we should make some ML party and find BV value on 5D3!

[some detailed instructions]

it's easy, you don't have to be a programmer

some detailed instructions
turn you camera on
set M mode
go to mem_spy settings in debug menu
set look for int16 (maybe int8), halshutter related on, range of adress 0x0 - 0x20 000, changes 20 - 300, other options should be turned off
turn mem_spy on
wait 10s and go to info screen (dont press halfshutter)
hold halfshutter until you find correct value
20x changes scene brightness
some variables will occur
look at the values in every third column how they react on scene brightness
if you have some suspicious, look at the exposure compensation and analyze what values have 0EV +1EV -1EV

if you will testing for long time some variables will hide, that's max 300 changes limit, in other word if you 300x changes you exposure our variable will hide (~ 2 changes in second on 5D2)

on 5D2 and 5D3


look at these images should get 1EV and your value 2049 or -1EV value 2047

Then I turn on module ON and press the LV button to go to life View.

no LV! How do you figure that?

I need to aim at bright light and press the half shutter, then put cap on and press half shutter.

turn mem_spy ON, wait 10s, hold halfshutter and watch what it changing, still hold halfshutter don't unpress it until you find correct value

How many memory locations should I find?  I assume that the mem locations are like 2d2cc?

as I said

set setting - halshutter related on, look for int16, range of adress 0x0 - 0x20 000, changes 20 - 300

Then there is two colums of numbers and a mem location, then two colums.

addr TAB num of changes TAB value

good luck!

https://maps.google.com/maps?saddr=Prague,+Czech+Republic&daddr=Quito+Ecuador&hl=en&sll=37.0625,-95.677068&sspn=57.249013,73.652344&oq=Pragu&mra=ls&t=m&z=3

Code Select Expand

We could not calculate directions between Prague, Czech Republic and Quito Canton, Ecuador.

it's all?

not yet, bv value isn't found on 5D3

You can lend me your 5D3 and I will find it

see first updated post

https://www.google.cz/search?q=dual+iso

http://www.magiclantern.fm/forum/index.php?topic=7208.0

nanomad try this https://bitbucket.org/hudson/magic-lantern/pull-request/174/mem_spy-module
set setting - halshutter related on, look for int16, range of adress 0x0 - 0x20 000, changes 20 - 300
switch to M mode, turn on mem_spy, make sure that you have metering off (dont press halfshutter)
go to info screen, wait at least for 5s (during this time changed values become hide)
turn on metering (hold halfshutter) and 20x change you scene exposure (aim at bright scene, then on dark, then on bright...)
some vars will occur, watch them how react on scene brightness

send my you gmail account via PM, I give you a write access.

I will be for devs only, but I dont have any idea how to ensure that.
Read the whole thread on bitbucket (eg. porting flexinfo on 5D2 was a coincidence that I found something undone).
It will be very useful, imagine that you want to implement something, but you dont have time to do that, so thats why.
Maybe it shold be somewhere on Bitbucket where contributes only devs.

I'm afraid ML user that write into the list "port raw dual iso 500fps". Probably it should be for devs only. I hope we will realize it some way!

I'm asking you if you can establish this task list topic in general develop discussion and make it sticky

What we should do to revert it? Do you want some help?

devs have write access
https://docs.google.com/document/d/19XsIAn4pxZ5xCBW5CQrsPP-bSoup87GLQ7CHzebBYFI/edit?usp=sharing

Please make one board for modules only (except raw* modules).

some workroom, maybe some fruits

Does it have to ...I'm hoping for .... I want to... I also want to... it really needs to... audio needs to...

g3gg0 please implement 500fps to raw_rec I really need that feature to capture my breakfast also I need sound recording if something horrible will happend
but seriously - one more reason why dont share unfinished features

help is always appreciated in this project - why ask?

well I have some ideas to raw_rec, but now I have to do some other part of ML, I will message you when I will be ready

nice, soon I'm going to port it on 5D2. Maybe if you will reach some milestone?
I want to solve the CF speed issue.
What is the write speed CF+SD? 100+?
Do you want some help with coding?