EOS M3 porting [M3] [EOS_M3]

Ant

c_joergAs @reyalp describes in Reply #81, the propcases for Sv is still wrong.

There were some changes in propcases since Reply #81.
Tv sholuld be ok.
For Sv try this build.

CHDK-M3-101a-r34.zip

666.62KB

c_joerg

No sv doesnâ€™t work 🙁
But the focal length is still OK. At this time, I used my adapted EF-S 10-18 on 10mm and 18mm.
And the values in the log file are correct. Great job!!! 😀 😀
Where does this information come from?

rawopint.xlsx

15.66KB

Ant

c_joerg
No sv doesnâ€™t work 🙁

Now PROPCASE_SV and PROPCASE_SV_MARKET are equal to G7X.
You better should ask reyalp about it.

All that I found in firmware according Sv is:

loc_FC099EDE
      LDRSH.W R0, [SP,#0x20+var_18]
      MOVS    R2, #2
      ADD     R1, SP, #0x20+var_1C
      STR     R0, [R4,#(dword_1258EC - 0x1258E0)]
      MOVS    R0, #0xFF
      BL      GetPropertyCase_NOEP
      LSLS    R0, R0, #0x1F
      BEQ     loc_FC099EF6
      ADR     R0, aErrorGetsvresult ; "\n\rError : GetSvResult"
      B       loc_FC099F0C
; ---------------------------------------------------------------------------

loc_FC099EF6
      MOVS    R2, #2
      LDRSH.W R0, [SP,#0x20+var_1C]
      MOV     R1, SP
      STR     R0, [R4,#(dword_1258F0 - 0x1258E0)]
      LSLS    R0, R2, #7
      BL      GetPropertyCase_NOEP
      LSLS    R0, R0, #0x1F
      BEQ     loc_FC099F16
      ADR     R0, aErrorGetsvfixresult ; "\n\rError : GetSvFixResult"

Where does this information come from?

Which information?

c_joerg

Ant
Which information?

The focal length?

Ant

Previously I was using modified function EFLensComGetFocalLength, because M3 firmware doesn't contain GetLensCurrentFocalLength function.

But it's present in M10 firmware. So now I use the function equal to one of subfunction called from GetLensCurrentFocalLength on M10.

c_joerg

Whatâ€™s about the ISO Base?
https://chdk.setepontos.com/d/12170
Is the ISO Base 200?

Ant

it looks like

reyalp

Ant
it looks like

It's confusing, but the script tells you what it *should* be, not what it is.

However, camera.h defaults to 200 for DryOS >= 49, so it should be OK.

Another thing to check would be the market to real conversion factors. (SV96_MARKET_OFFSET, ISO_MARKET_TO*, ISO_REAL_TO*)

These can be found by comparing the market and real values after setting ISO in the UI and half pressing. See core/shooting.c for how they are defined and used.

Now PROPCASE_SV and PROPCASE_SV_MARKET are equal to G7X.

Did you verify that the values look like SV96 values?

srsa_4c

FWIW, market and real ISO seems to be equal on the m10.

c_joerg

srsa_4c
FWIW, market and real ISO seems to be equal on the m10.

Could you try to run rawopint on the M10, just a couple of shoot, and post the log fileâ€¦.

srsa_4c

c_joerg
Could you try to run rawopint on the M10, just a couple of shoot, and post the log fileâ€¦.

Are you looking for something specific (such as script setup / scene type), or just some random shots? Please head over to the m10 thread with the answer (this is off-topic here).

reyalp

srsa_4c
FWIW, market and real ISO seems to be equal on the m10.

If they are equal, the defines should be like G7X, not the defaults like the M3 port.

c_joerg

reyalp
The SV propcases should be pretty easy to identify and verify. When you set the ISO to a specific setting in the UI, they will change, and SV_MARKET should be the APEX96 value of the set ISO. The SV value will be similar, either identical or offset by some mostly fixed APEX96 value. The difference between SV and SV_MARKET needs to be found and set in platform_camera.h if it isn't the default.

DELTA_SV can be found in camera auto ISO mode, where SV_MARKET + DELTA_SV should equal APEX96 of the camera chosen ISO value. The SV_MARKET in this case will be the CAM_MARKET_ISO_BASE value, which might also need to be overridden.

Not sure if I really understood the whole stuffâ€¦
I did some testing with ISO settings in the Canon user interface (UI)
I set ISO in Tv Mode to ISO100, ISO200, ISO400, ISO800 and ISO1600.

press("shoot_half")
repeat
   sleep(10)
until get_shooting() == true
sv96_prop = get_prop(props.SV)
sv96_get  = get_sv96()
release("shoot_half")

print("sv96_prop:",sv96_prop,"/",sv96_to_iso(sv96_prop),"; sv96_get:",sv96_get,"/",sv96_to_iso(sv96_get))

Update:
Iâ€™m a little bit confused:
For ISO100 I got SV96=480 and not 412 difference 68
For ISO200 I got SV96=576 and not 508 difference 68
For ISO400 I got SV96=672 and not 604 difference 68
Is this a mismatch?

Update 2
This is the same difference (+1) which I see in the rawopint log fileâ€¦

srsa_4c

c_joerg
For ISO100 I got SV96=480 and not 412 difference 68
For ISO200 I got SV96=576 and not 508 difference 68
For ISO400 I got SV96=672 and not 604 difference 68

If you can compile CHDK (with this, for example), add the following lines to platform/m3/platform_camera.h and make a build:

    // "real" to "market" conversion definitions
    #define SV96_MARKET_OFFSET                  0
    #define ISO_MARKET_TO_REAL_MULT             1
    #define ISO_MARKET_TO_REAL_SHIFT            0
    #define ISO_MARKET_TO_REAL_ROUND            0
    #define ISO_REAL_TO_MARKET_MULT             1
    #define ISO_REAL_TO_MARKET_SHIFT            0
    #define ISO_REAL_TO_MARKET_ROUND            0

c_joerg

srsa_4c
If you can compile CHDK (with this, for example)

Thanks. I havenâ€™t compiled CHDK before, but I will go into it. But it will take some timeâ€¦
What is the correct value for ISO100? Sv96=412? my S110 delivers 411â€¦

Ant

srsa_4cadd the following lines to platform/m3/platform_camera.h and make a build

Done.

CHDK-M3-101a-r35.zip

666.61KB

c_joerg

Ant

srsa_4cadd the following lines to platform/m3/platform_camera.h and make a build

Done.

Should something change with the run?
I got the same sv96 values.
I looked into shooting.c. The result is exact log2(iso/3.125)*96+0.5)

Ant

c_joergShould something change with the run?

no more Sv related warnings in RAWOPINT.CSV

c_joerg

Ant
no more Sv related warnings in RAWOPINT.CSV

No warnings anymore 😁 😁 😁ïŠ ïŠ
But why I got on my S110 and G1x on ISO100 sv96=411 and on the M3 sv96=480?

Update:
The black_level=127 from Reply #80 has changed to black_level=511 in Reply #259 (like on the G1x), But Iâ€™m not sure whyâ€¦

Ant

c_joergBut why I got on my S110 and G1x on ISO100 sv96=411 and on the M3 sv96=480?

and on the M10 sv96=480 too

c_joergThe black_level=127 from Reply #80 has changed to black_level=511 in Reply #259 (like on the G1x), But Iâ€™m not sure whyâ€¦

Because it was long time ago, when CAM_SENSOR_BITS_PER_PIXEL was not corrected.

« Previous Page Next Page »