ML aperture info

Issue #274 resolved
Former user created an issue

ML aperture info don't match canon's info. When i zoom in to 55mm aperture changes from 3.5 to 5.6 and ML info stills showing 3.5, which ir wrong. Lens EF-S18-55mm f/3.5-5.6.

Comments (18)

  1. Former user Account Deleted

    I have the same issue using the kit lens (Canon EF-S 18-55mm f/3.5-5.6 IS) with the Canon EOS 550D/Rebel T2i/Kiss X4.

    Screenshot from latest Magic Lantern (changeset a127fa4f9ac4): Magic Lantern and Canon info on aperture different

    P.S.: The missing shutter info may be caused by issue #312

    Martin M.

  2. Former user Account Deleted

    I have this one too! wouldn't be much of a problem if I knew wich info was right.

  3. Former user Account Deleted

    Yes, with latest audio mon build. It looks the same as in the screenshot, aperture in ML doesn't go below 4. But it changes to 5.6 correctly when zooming.

  4. Former user Account Deleted

    Maybe some cameras use sligtly different codes for aperture. My kit lens goes from 3.5 to 5.6 when zooming (both on Canon and ML displays).

    What model do you have? 550D, T2i or kiss x4?

  5. Former user Account Deleted

    ML also teased me a few times by showing that aperture on my kit lens was 1.2 :) But I don't remember now, maybe that was on some other buid.

  6. Former user Account Deleted

    I have the same issue. kit lens shows 4.0 in ML when aperture is set to 3.5 50mm f1.8 shows 2.0 aperture in ML when it is set to 1.8. canon 50mm-250mm shows correct aperture in ML when set to 4.0.

    With all lenses there are some aperture values in between that don't match:

    • canon --> ML 2.2 --> 2.5 2.5 --> 2.8 2.8 --> 2.8 3.2 --> 3.5 3.5 --> 4.0 4.0 --> 4.0 4.5 --> 4.5 5.0 --> 5.6 5.6 --> 5.6 6.3 --> 6.7 7.1 --> 8.0 8.0 --> 8.0 etc.
  7. totriz

    that last post was mine. formatting the SD card and clearing the settings on the camera does not fix the issue. when changing the aperture from ML menu fewer values are selectable: 2.0 2.8 4.0 5.6 8.0 11 16.0 22.0

  8. totriz

    yes, I have tried all the latest builds, same problem. maybe I'll try going back and see if it worked fine in an older build.

    my camera is the US rebel T2i if it makes any difference...

  9. Alex

    I use the european model (550D). It is possible that other models use slightly different aperture codes.

    You can try enabling Spy PROP (in Debug menu) and look at the values of PROP_APERTURE (0x80000006). ML uses the following table:

    // aperture*10
    static const int values_aperture[] = {0,12,13,14,16,18,20,25,28,35,40,45,56,67,80,95,110,130,160,190,220,270,320,380,450};
    static const int codes_aperture[] =  {0,12,14,16,18,20,24,28,32,36,40,44,48,52,56,60, 64, 68, 72, 76, 80, 84, 88, 92, 96};
    

    Note that codes displayed by "Spy prop" are in hex, and the ones in the table are in decimal.

    If you can check the values from this table on your camera (and tell me the differences), that would be great.

    Example: when Canon display shows f1.8, the code should be 20 = 0x14, so the value displayed by "Spy prop" should be 14.

  10. totriz

    these are the values I get @ 0x80000006 for each f-stop:

    • 1.8 - 15
    • 2.0 - 18
    • 2.2 - 1b
    • 2.5 - 1d
    • 2.8 - 20
    • 3.2 - 23
    • 3.5 - 25
    • 4.0 - 28
    • 4.5 - 2b
    • 5.0 - 2d
    • 5.6 - 30
    • 6.3 - 33
    • 7.1 - 35
    • 8.0 - 38
    • 9.0 - 3b
    • 10 - 3d
    • 11 - 40
    • 13 - 43
    • 14 - 45
    • 16 - 48
    • 18 - 4b
    • 20 - 4d
    • 22 - 50
  11. Alex

    Found the problem: it happens if you have set 1/3EV step size. I have 0.5EV steps, that's why I've got different numbers. Will be fixed.

  12. Log in to comment