G7 X porting thread

  • 109 Replies
  • 36520 Views
*

Offline reyalp

  • ******
  • 10701
  • Publish
    Re: G7 X porting thread
    « Reply #100 on: 17 / April / 2017, 00:56:40 »
    Advertisements
    Updated with build r4797 in the usual posts:

    100b https://chdk.setepontos.com/index.php?topic=12692.msg131767#msg131767
    100c https://chdk.setepontos.com/index.php?topic=12692.msg131768#msg131768
    100d https://chdk.setepontos.com/index.php?topic=12692.msg127047#msg127047


    The main change is that raw buffers should now be correct in most cases (technical details). This means you can use CHDK raw in many cases where the Canon firmware does not allow Canon raw: With digital zoom, in Auto mode, with "my colors", etc. Of course,  the visual effects apply only to the jpeg.

    CHDK raw is also now disabled in some modes where it known to be non-functional: HDR, "handheld night scene" and "hybrid auto".
    Don't forget what the H stands for.

    *

    Offline reyalp

    • ******
    • 10701
  • Publish
    Re: G7 X porting thread
    « Reply #101 on: 07 / May / 2017, 03:07:42 »
    Updated with build r4805 in the usual posts:

    100b https://chdk.setepontos.com/index.php?topic=12692.msg131767#msg131767
    100c https://chdk.setepontos.com/index.php?topic=12692.msg131768#msg131768
    100d https://chdk.setepontos.com/index.php?topic=12692.msg127047#msg127047

    Added workaround for some UHS cards not using full speed under CHDK technical details. I suspect this may fix occasional boot problems, but haven't used it enough to be sure.
    Don't forget what the H stands for.

    *

    Offline reyalp

    • ******
    • 10701
  • Publish
    Re: G7 X porting thread
    « Reply #102 on: 11 / June / 2017, 20:45:31 »
    Builds for 100b and 100d are now available from the trunk autobuild http://mighty-hoernsche.de/trunk/

    The test build for 100c is still waiting for feedback.
    Don't forget what the H stands for.

  • Publish
    Re: G7 X porting thread
    « Reply #103 on: 14 / June / 2017, 01:43:04 »
    Thank you for all your great work!

    My Camera: G7X 100d

    On May 5, 2017 I downloaded and began testing g7x-100d-1.5.0-4805-full-prealpha
    I only tested the following:
    • Override Tv - LongExp
    • Override Av
    • Override ISO
    • Dark Frame Subtraction
    • Bracketing in Continuous Mode
    • interval.bas script

    After learning the fundamentals and trying out many of the successful techniques I use for astrophotography using Magic Lantern on an SL1, I found everything to be fully functional except for Dark Frame Subtraction. No matter what I set it to [off,on,auto] it is always enabled in my camera.

    I tried downloading and using the meteor2.lua script, but it, too, failed to turn off Dark Frame Subtraction.

    On May 13 I downloaded and installed g7x-100d-1.5.0-4827-full_ALPHA, but it has the same behavior.

    Specifically, any long shutter speed (5+ seconds in my testing), whether initiated using a CHDK override or a native camera setting, in or out of a script, is followed immediately by a "Busy" for an amount of time about equal to the shutter speed. I have tried any number of different combinations of the features noted above, as well as shooting RAW, JPEG or RAW+JPEG, but nothing causes Dark Frame Subtraction to be turned off.

    Just reporting a suspected bug.  All the other features make it a great tool for me. 
    Thanks again


    *

    Offline reyalp

    • ******
    • 10701
  • Publish
    Re: G7 X porting thread
    « Reply #104 on: 14 / June / 2017, 17:02:12 »
    After learning the fundamentals and trying out many of the successful techniques I use for astrophotography using Magic Lantern on an SL1, I found everything to be fully functional except for Dark Frame Subtraction. No matter what I set it to [off,on,auto] it is always enabled in my camera.

    I tried downloading and using the meteor2.lua script, but it, too, failed to turn off Dark Frame Subtraction.
    Thanks for testing and reporting. As mentioned in notes, dark frame control is not implemented yet in this port.

    In my experience, the Canon firmware only enables exposures longer than 30s, not 5s. This could depend on ISO or shooting mode, I typically use M and ISO 800 or less.

    If you do know settings that trigger it for exposures around 5s, let me know because it will make it easier for me to develop a fix.
    Don't forget what the H stands for.

  • Publish
    Re: G7 X porting thread
    « Reply #105 on: 14 / June / 2017, 17:20:31 »
    In  sx60hs Canon enables darkframe for any exposure of more than 1 second as far as I can tell.

    *

    Offline reyalp

    • ******
    • 10701
  • Publish
    Re: G7 X porting thread
    « Reply #106 on: 14 / June / 2017, 17:45:11 »
    In  sx60hs Canon enables darkframe for any exposure of more than 1 second as far as I can tell.
    Yes, the small sensor powershots usually do it somewhere around 1-3 seconds. On g7x, I know I've taken a lot of 30s shots without it, but it might depend on settings. The Canon manual is very non-specific, it just says that processing time may be required for longer exposures.
    Don't forget what the H stands for.

  • Publish
    Re: G7 X porting thread
    « Reply #107 on: 25 / June / 2017, 21:31:22 »
    Dark Frame Subtraction test results:

    Using g7x-100d-1.5.0-4827-full_ALPHA.
    The only CHDK feature I enabled was "Override TV, LongExp".
    All other settings were established using the Canon menus.
    I tested in both P and M modes.  ISO seems to be the only driving factor.
    Using times in whole seconds only, these are the times at which Dark Frame Subtraction began.  Times less than those shown did not cause Dark Frame Subtraction.

    ISO - Time in seconds
    125 - 36
    200 - 36
    400 - 36
    800 - 18
    1600 - 5
    3200 - 5
    6400 - 5
    12800 - 5

    I hope this is helpful.
    As always, thank you for your efforts.


    *

    Offline reyalp

    • ******
    • 10701
  • Publish
    Re: G7 X porting thread
    « Reply #108 on: 02 / July / 2017, 02:50:14 »
    Dark Frame Subtraction test results:
    Thanks, that was very helpful. I added dark frame control support in build 4841.

    In my testing, I found sensor temperature was factor too, I had to use 20 seconds to be sure to get a dark frame at ISO3200, but after it ran for a while it was triggered at shorter times.
    Don't forget what the H stands for.

  • Publish
    Re: G7 X porting thread
    « Reply #109 on: 03 / July / 2017, 00:43:17 »
    Thanks for (letting me turn off) Dark Frame Subtraction! That was really fast.
    I have not tested it extensively, but it works on a few simple tests. I look forward to using it out in the field on the next new moon.
    « Last Edit: 03 / July / 2017, 00:49:58 by mbf_az »

     

    Related Topics