Bug Reports against Recent Builds -- Report bugs here

  • 281 Replies
  • 50796 Views
  • Publish
    Confirmed: Reported bug is in script code, not build
    « Reply #10 on: 09 / January / 2008, 13:27:44 »
    Advertisements
    Hello,

    The bug that was causing the camera to crash and the script to be overwritten was in the script.

    In the dump_props subroutine, there is a print statement without an ending quotation mark (").

    This should probably still be looked at, however.  If this type of problem can cause data to be incorrectly written to the memory card, it could cause the file system to become corrupted, and photos and other data could be lost.

    Anyway, that's all for now.

    Thanks,

    Tom
    Tom Friend
    -- -----------
    Nikon Coolpix 990, Olympus C-8080WZ, Nikon D1, Canon S2 IS, Canon SD700

    *

    Offline a710is

    • ****
    • 250
    • A710 IS
  • Publish
    Re: Bug Reports against Recent Builds -- Report bugs here
    « Reply #11 on: 13 / April / 2008, 05:03:10 »
    gathering up some bugs for my A710 that aren't going away:
    ND filter option still not present although when it was present it worked
    ISO Market doesn't show anymore in video lately (it did in the past)

    and I believe ISO override should be possible considering that it seems to happen when letting go of the shutter.

    also optical zoom being disabled in video after going to digital zoom.

    *

    Offline fbonomi

    • ****
    • 469
    • A570IS SD1100/Ixus80
      • Francesco Bonomi
  • Publish
    Re: Bug Reports against Recent Builds -- Report bugs here
    « Reply #12 on: 17 / May / 2008, 02:55:48 »
    EDIT: I have to check this better first....

    Hi: I just ran into a simple problem:the PR_SCREEN.TXT file won't go over 65536 bytes.

    I saw this on In Allbest #48, I guess this will be similar in most builds...
    « Last Edit: 17 / May / 2008, 03:18:56 by fbonomi »

    *

    Offline PhyrePhoX

    • *****
    • 2253
    • make RAW not WAR
      • PhyreWorX
  • Publish
    Re: Bug Reports against Recent Builds -- Report bugs here
    « Reply #13 on: 29 / May / 2008, 18:38:41 »
    stickified.
    bugs should not neccessarily be reported in this thread here, but should at least contain the information that is summarized in the first post (some conventions when reporting a bug) if reported in a new thread (if possible, supply most important info also in the subject).
    there will be a dedicated bugtracker soon, patience is a virtue.


  • Publish
    Re: Bug Reports against Recent Builds -- Report bugs here
    « Reply #14 on: 08 / August / 2008, 17:08:50 »
    Hi all,
    Please, someone can restore the <[/color]-Back  function <ALT> <SET> [SCRIPT] mode( A720 camera ) is since the #51 that don't work  ;)
    Regards

  • Publish
    Re: Bug Reports against Recent Builds -- Report bugs here
    « Reply #15 on: 08 / August / 2008, 17:12:20 »
    Well I'm not good to use the forum ...... I want to say <- Back function.
    regards

    *

    Offline fe50

    • ******
    • 3033
    • IXUS50 & 860, SX10 Star WARs-Star RAWs
      • fe50
  • Publish
    Re: Bug Reports against Recent Builds -- Report bugs here
    « Reply #16 on: 08 / August / 2008, 17:31:30 »
    Hi zincopal,
    you can also edit your posts, use the "Modify" button in the upper right corner of your post.  ;)

    I'm not sure whether i understand you - do you mean the "<- back" entry in the script menu ?
    This will only work when you have entered the script menu from within the CHDK menu !
    If you enter the script menu directly by pressing SET/FUNC in <Alt> mode, you can leave it with the MENU button (and stay in <Alt> mode) or with PRINT (and leave also <Alt> mode).

  • Publish
    Re: Bug Reports against Recent Builds -- Report bugs here
    « Reply #17 on: 09 / August / 2008, 17:40:59 »
     Hi fe50,
    Many thanks fo Your reply, ( You, often peek me out of the troubles and I appreciate Your generosity but I would not impose on You and Your disponibility ) :).

    The little imperfection is in the  SET/FUNC in <Alt> mode( for the A720 release )
    Naturally I know how can solve the little problem,  but I would like that the CHDK should be perfect, the function actually exist and it is a pity that don't work, I hope only that in some next revision when someone not overburned of others interesting modifications found a little time for fix the little bug ::)
    Anyway I want to send You again my thanks
    Regards


    *

    Offline reyalp

    • ******
    • 9802
  • Publish
    Re: Bug Reports against Recent Builds -- Report bugs here
    « Reply #18 on: 11 / August / 2008, 19:48:52 »
    In both the current trunk and juciphox, on a540
    set subject distance override
    leave alt mode
    enable flash
    set mode to auto happens in several modes
    press half shoot
    -> ui freezes (sometimes all the menus/icons/histogram are shown, sometimes not)
    press half shoot again
    -> camera shuts down camera shuts down after being hung for a while (watchdog, I assume)

    I'll investigate after I get my current work tidied up.

    edit:
    sometimes shuts down with only one halfshoot.
    seems not to happen if zoomed (thx to hacki for the tip, may also affect ixus750)

    edit:
    appears to be in this loop
    Code: (c) [Select]
    void lens_set_focus_pos(long newpos)
    {
        _MoveFocusLensToDistance((short*)&newpos);
        while ((shooting_is_flash_ready()!=1) || (focus_busy));
    It also seems to be somewhat intermittent, possibly related to the subject it is trying to focus on.

    Turning off the flash or removing the shooting_is_flash_ready() part appears to make this go away, unless I'm getting caught by the random element.
    « Last Edit: 12 / August / 2008, 00:23:14 by reyalp »
    Don't forget what the H stands for.

    *

    Offline fudgey

    • *****
    • 1705
    • a570is
  • Publish
    Re: Bug Reports against Recent Builds -- Report bugs here
    « Reply #19 on: 12 / August / 2008, 06:45:44 »
    It also seems to be somewhat intermittent, possibly related to the subject it is trying to focus on.

    Turning off the flash or removing the shooting_is_flash_ready() part appears to make this go away, unless I'm getting caught by the random element.

    My first thought is that it's intermittent (also) because flash charging time varies, and that the problem is that CHDK stays in a loop waiting for the flash without letting the camera's software work it's magic, including watchdog resets.

    I don't know how often the camera resets its watchdog, so the phase of the reset period could also be a source of variation.

     

    Related Topics