Bug Reports against Recent Builds -- Report bugs here - page 4 - CHDK Releases - CHDK Forum supplierdeeply

Bug Reports against Recent Builds -- Report bugs here

  • 281 Replies
  • 110299 Views
*

Offline reyalp

  • ******
  • 13719
Re: Bug Reports against Recent Builds -- Report bugs here
« Reply #30 on: 13 / August / 2008, 18:16:34 »
Advertisements
Code: (c) [Select]
_GetPropertyCase(PROPCASE_FLASH_MODE, &t, sizeof(&t));
 if ((t != 2) && shooting_in_progress() && shooting_is_flash())
    return ( _IsStrobeChargeCompleted());
 return 1;
However, it strikes me a bit odd that shooting_is_flash() checks PROPCASE_IS_FLASH_READY.

Surely one of those two things is misnamed ?
Don't forget what the H stands for.

*

Offline PhyrePhoX

  • *****
  • 2254
  • make RAW not WAR
    • PhyreWorX
Re: Bug Reports against Recent Builds -- Report bugs here
« Reply #31 on: 13 / August / 2008, 18:52:54 »
i fixed the adressed things, thanks for reporting.
btw some people in the past used the assembla bugtracker, maybe we could start using it more? this way it can be made sure that no bugs are lost and forgotten. you can post anonymously there or register for an account on assembla.com. maybe open a ticket there and also post in this thread to discuss about it?

*

Offline whoever

  • ****
  • 280
  • IXUS950
Re: Bug Reports against Recent Builds -- Report bugs here
« Reply #32 on: 14 / August / 2008, 04:00:18 »
However, it strikes me a bit odd that shooting_is_flash() checks PROPCASE_IS_FLASH_READY.

Surely one of those two things is misnamed ?

Yes, it is a misnomer. shooting_is_flash() returns the contents of PROPCASE_IS_FLASH_READY. The latter, updated on half-shutter after pre-metering (and that's when the "expo override" code of CaptSeq is executed), contains 1 if flash is going to be used and 0 otherwise.


*

Offline yvesson

  • ***
  • 209
  • A540 SX10IS
    • poll about some pics (not much serious) ^^
Re: Bug Reports against Recent Builds -- Report bugs here
« Reply #33 on: 14 / August / 2008, 10:56:07 »
Hej,
Not sure this is a CHDK thing, but on A540 with jucifer's builds, I noticed recently that when in manual mode, the screen doesn't go off when I put a plug in the "video in". It works normally in other modes, at least Av-Tv-auto. I have the auto build from 2 days ago.
I'm not sure where to post this sorry.


*

Offline PhyrePhoX

  • *****
  • 2254
  • make RAW not WAR
    • PhyreWorX
Re: Bug Reports against Recent Builds -- Report bugs here
« Reply #34 on: 14 / August / 2008, 10:59:56 »
well you can verify if it is a "chdk problem" if you try it without chdk. also, you can try a recent allbest build.

*

Offline yvesson

  • ***
  • 209
  • A540 SX10IS
    • poll about some pics (not much serious) ^^
Re: Bug Reports against Recent Builds -- Report bugs here
« Reply #35 on: 14 / August / 2008, 11:13:12 »
Hej,
Well my post was a bit stupid, forgot to say I can't reproduce it, it happens when using MD scripts but not all the time. So I wanted more to know if other people experienced this.

*

Offline fudgey

  • *****
  • 1705
  • a570is
Re: Bug Reports against Recent Builds -- Report bugs here
« Reply #36 on: 14 / August / 2008, 13:35:38 »
Well my post was a bit stupid, forgot to say I can't reproduce it, it happens when using MD scripts but not all the time. So I wanted more to know if other people experienced this.

I remember that it sometimes takes a bit time for LCD image to get back after unplugging the video plug (and this is probably even without CHDK)... maybe the same kind of behavior happens when plugging in as well if you do it during a script (for example during MD half-shoot)? I've always plugged in right before starting the script, because that way I don't make MD trigger by moving the camera...

*

Offline yvesson

  • ***
  • 209
  • A540 SX10IS
    • poll about some pics (not much serious) ^^
Re: Bug Reports against Recent Builds -- Report bugs here
« Reply #37 on: 14 / August / 2008, 16:00:57 »
Hej,
Yes seems you're right at least on that, fudgey, if I plug before I start the script, the screen goes off, but the other way round, it doesn't.
And it always happened at night when shooting lightnings or -like now- stars. Also another "problem", the leds near the viewfinder keep on blinking in these night MD situations.


*

Offline PhyrePhoX

  • *****
  • 2254
  • make RAW not WAR
    • PhyreWorX
Re: Bug Reports against Recent Builds -- Report bugs here
« Reply #38 on: 14 / August / 2008, 16:09:10 »
they blinkd during capturing, right?
and fudgey is probably right: the cam maybe doesnt detect the jack if it is in the middle of capturing (you cant even switch off the cam during that)

*

Offline yvesson

  • ***
  • 209
  • A540 SX10IS
    • poll about some pics (not much serious) ^^
Re: Bug Reports against Recent Builds -- Report bugs here
« Reply #39 on: 14 / August / 2008, 17:17:37 »
Hej,
Nope, all the time they blink (in fact one of them blinks, other one is on all the time), but only when MD at night I noticed, also the icon showing the cam is moving too much and will cause blur is there, though the cam is on a solid wall and thus not moving.
And about the screen, it can stay on for long minutes so I doubt it could be capturing or half shoot for all this time.

 

Related Topics