Chdk for SX130 IS ? - page 22 - CHDK Releases - CHDK Forum
supplierdeeply

Chdk for SX130 IS ?

  • 1095 Replies
  • 258411 Views
Re: Chdk for SX130 IS ?
« Reply #210 on: 11 / February / 2011, 10:52:16 »
Advertisements
@achillies: I never had that problem, it must be because I delete the file "\ DCIM \ CANONMSC \ M0123.CTG" when I copy my photos on the pc. This file stores info of photos from memory.
At least I did not find anything last night.

*

Offline Pilda

  • *
  • 33
Re: Chdk for SX130 IS ?
« Reply #211 on: 11 / February / 2011, 14:10:23 »
Hi,
if I try to use bracketing with custom timer, camera always crash after second shot. I suppose that's because of the memory problem. I hope this great combination will work someday.

I also have often trouble with disappearing CHDK menu in alt mode.  When I active the menu, the menu appears just for a little while and then dissapear. I have to press a button to do it vissible again.

*

Offline achillies

  • ***
  • 227
  • SX130IS
Re: Chdk for SX130 IS ?
« Reply #212 on: 11 / February / 2011, 17:51:13 »
@SX130user - I can't reproduce it now.  It was probably because I was changing file extensions back and forth in the RAW menu trying to see the DNG files via USB (But there is no "DNG visable via USB" option in the misc menu, so I guess I was spinning my wheels.)

Hi,
if I try to use bracketing with custom timer, camera always crash after second shot. I suppose that's because of the memory problem. I hope this great combination will work someday.

I can not reproduce this.  If you can reproduce it regularly, what specific settings are you using? (eg. what bracketing values, and what timer settings).
« Last Edit: 11 / February / 2011, 18:11:53 by achillies »
Don't let the sands of time get in your lunch.

Re: Chdk for SX130 IS ?
« Reply #213 on: 11 / February / 2011, 19:27:29 »
Hi!
I'm very happy to say that I successfully tested the 'set_movie_status' command in script. It's nice to know that, couse on wiki it is said to be working only for  a720 & s3is. I used set_movie_status 1 and 2, so I can now pause video recording on sx 130:)

The testing script:
Code: [Select]
@title pauser

print "wait 5 s"
sleep 5000

print "start..."
click "shoot_full"

print "wait 2 s"
sleep 2000

s=get_movie_status
print "stat:",s

print "wait 2 s"
sleep 2000

print "pause?"
set_movie_status 1

print "wait 1 s"
sleep 1000

print "go ahead?"
set_movie_status 2

print "wait 2 s"
sleep 2000

print "end!"
click "shoot_full"

end

Althought it crashed twice, it usually works. Well - nothing's perfect!

EDIT - No... I tried now and it crashes much more times.... I don't know why. But seems to be working at all. I can't find any role. I can repeat this script five-six, maybe seven times and next time - crash. Crash can be also the first try. Or  secound. Or other random... Random number generator:D
« Last Edit: 11 / February / 2011, 19:40:04 by outslider »
if (2*b || !2*b) {
    cout<<question
}

Compile error: poor Yorick


*

Offline achillies

  • ***
  • 227
  • SX130IS
Re: Chdk for SX130 IS ?
« Reply #214 on: 11 / February / 2011, 21:27:53 »
I'm very happy to say that I successfully tested the 'set_movie_status' command in script. It's nice to know that, couse on wiki it is said to be working only for  a720 & s3is. I used set_movie_status 1 and 2, so I can now pause video recording on sx 130:)

I'm happy to hear it (because I'm sure I'll use it)!  I wouldn't keep hammering at scripting crashes too much right now though.  Quid is working on a hopefully more stable version, and after that's out, THEN, we can start worrying about script crashes. ;)
Don't let the sands of time get in your lunch.

*

Offline Pilda

  • *
  • 33
Re: Chdk for SX130 IS ?
« Reply #215 on: 12 / February / 2011, 02:46:28 »
I can not reproduce this.  If you can reproduce it regularly, what specific settings are you using? (eg. what bracketing values, and what timer settings).

It's really strange. It seems to be not regular. I tryied it a while ago and it worked quite well. Camera crashed only once from maybe 10 attempts.

I tryied just TV bracketing +/- 1 EV, with raw (all images). Timer settings was 3 sec, 3 images. But I am afraid it is not valuable information because it seems to be very irregular.

« Last Edit: 12 / February / 2011, 03:00:23 by Pilda »

Re: Chdk for SX130 IS ?
« Reply #216 on: 12 / February / 2011, 03:28:53 »
Hi!
Finally I could make some Tv bracketing pictures! I turned the RAW mode off, I think thats was the key (even if I specified in the exceptions, that no RAW format in continuous mode didnt help).
My next question is, is it possible to save these pictures, wtih the correct EXiF data? Because if I see well, all pictures are shown (saved) with same - first picture - settings. Thx.

*

Offline quid

  • **
  • 67
  • SX130IS
Re: Chdk for SX130 IS ?
« Reply #217 on: 12 / February / 2011, 04:03:14 »
@Plida: Disappearing menu is known problem of CHDK on new cameras. About bracketing: 3s delay is too small, on my camera saving to RAW is a little above 3s, and saving to DNG about 3.7s. But I didn't have any crash with smaller delay on clean start in Shooting Mode - camera just took next picture as soon as possible.

@CanonPeter: Currently on SX130 there is no information about overrides in Exif (or in MakerNotes like on other cameras with CHDK).


*

Offline Pilda

  • *
  • 33
Re: Chdk for SX130 IS ?
« Reply #218 on: 12 / February / 2011, 04:26:33 »
Quid:
aha, I thought the delay is only delay before the first photograph and then there is no delay. Now I am a bit cleverer. Thank you for the hint.

*

Offline quid

  • **
  • 67
  • SX130IS
Re: Chdk for SX130 IS ?
« Reply #219 on: 12 / February / 2011, 05:23:46 »
Thanks again for tests. Based on download counter of test version, I hoped for much larger response, but I hope that it was because OK was always on screen.

I've made a workaround for our memory problems - instead of loading CHDK on heap, I've loaded it into one of memory regions that looks unused.
Last version was testing if this 2MB memory block is not used, using debug code from the experimental alternate memory allocation thread, adjusted to use specific memory block instead of _exmem_alloc().

In this version CHDK is loaded into addres 0xF00000, and whole heap memory is available to camera. I know, that there is no way to prove, that this memory block is not used by Canon, and reyalp may never allow this code on CHDK SVN sever ;) , but I think that it's the only possibility to have a stable CHDK port for now - at least until we discover a better way.

Changelog:
- Workaround for memory problems
- Built with all default CHDK features





 

Related Topics