A4000IS porting thread

waterwingz

12132

Re: A4000IS porting thread

« Reply #130 on: 29 / June / 2013, 09:30:19 »

Advertisements

Quote from: Mulledy on 29 / June / 2013, 09:07:09

It just looks like it needs a litttle tweeking.

I just downloaded the script from this forum thread, loaded on my camera and ran it. No tweaking needed. Did you download the one I attached and simply move it to the camera or did you open it with something first?

Quote

I did find that there is a script called interval.lua that essentially does the same thing ( more or less).

Yea - the one I posted is a cut & paste from that one. I inserted a startup delay and changed the shooting to work with minimal delay between shots. I also added code to switch the camera to shooting mode if you accidentally start the script while in playback mode.

« Last Edit: 29 / June / 2013, 09:36:06 by waterwingz »

Logged

Ported : A1200 SD940 G10 Powershot N G16

Mulledy

Re: A4000IS porting thread

« Reply #131 on: 29 / June / 2013, 16:29:44 »

CHDK and Extend.lua are loaded and now working properly. Thanks you all!!!

Logged

waterwingz

12132

Re: A4000IS porting thread

« Reply #132 on: 29 / June / 2013, 16:42:24 »

Quote from: Mulledy on 29 / June / 2013, 16:29:44

CHDK and Extend.lua are loaded and now working properly. Thanks you all!!!

Here's a little reward for your hard work. I took a few minutes and updated the script. Now it allows you to change both the startup delay and the delay time between shots. It also prints out what it is doing on the LCD display.

extend2.lua (0.42 kB - downloaded 23 times.)

Logged

Ported : A1200 SD940 G10 Powershot N G16

Mulledy

Re: A4000IS porting thread

« Reply #133 on: 29 / June / 2013, 20:52:00 »

Loaded and works perfectly!!! I could't be happier. Thank you, Thank you, Thank you!!!!

Logged

Mulledy

Re: A4000IS porting thread

« Reply #134 on: 29 / June / 2013, 20:56:16 »

As a side note (anybody), are the scripts universal across all models of Canon? Or are they written specifically to work with the model/firmware/CHDK version. I know, that's a dumb question, but I'm a "rookie". And I'm really not that technically savvy.

Joe

Logged

waterwingz

12132

Re: A4000IS porting thread

« Reply #135 on: 29 / June / 2013, 21:20:46 »

Quote from: Mulledy on 29 / June / 2013, 20:56:16

As a side note (anybody), are the scripts universal across all models of Canon? Or are they written specifically to work with the model/firmware/CHDK version. I know, that's a dumb question, but I'm a "rookie". And I'm really not that technically savvy.

Not a dumb question at all. In the early days of CHDK (circa 2007-2009) most scripts were specific to particular camera model as the used simulated button presses to force required camera functions. In the following years, much of that was replaced with setting propset values directly. However, those tended to be specific to when the camera was released.

Wind to clock forward to today and its very possible to write scripts (in Lua) that will work on any camera. But there are a lot of older scripts posted on the forum and wiki so beware when downloading.

Logged

Ported : A1200 SD940 G10 Powershot N G16

eponymous

38
Canon A4000

A4000IS intervalometer scripts creating bad images

« Reply #136 on: 30 / June / 2013, 17:46:57 »

I'm using a new A4000 for doing some pole aerial photography (PAP). What I'm finding is that no matter which of a variety of intervalometer scripts I use, I get a majority of images that are incomplete. That is, the camera takes about ½ to ⅓ of a good picture and then the rest is either gray or consists of bands of another snap and then gray. I think it has something to do with the motion of the camera on the end of the pole. If I simply hold the camera in my hands while the intervalometer script is running, almost all the images come out ok.

In contrast, if I set up the camera to use its normal delay before starting and then multiple-image mode, everything is fine, so it appears that the camera is capable of doing what's needed, but that there's a bug somewhere in CHDK that prevents that from happening while the script is running.

(I searched the forum, but didn't find anything relevant.)

Logged

John

waterwingz

12132

Re: A4000IS intervalometer scripts creating bad images

« Reply #137 on: 30 / June / 2013, 17:52:20 »

Quote from: eponymous on 30 / June / 2013, 17:46:57

What I'm finding is that no matter which of a variety of intervalometer scripts I use, I get a majority of images that are incomplete.

Please post an intervalometer script that does this - either as a link to the exact script or as an attachment to your response to this message.

Logged

Ported : A1200 SD940 G10 Powershot N G16

srsa_4c

4451

Re: A4000IS porting thread

« Reply #138 on: 30 / June / 2013, 18:11:01 »

Seems like more and more users are experiencing JPEG corruption, which is probably connected to the use of EXMEM. (Tip: search this thread for "exmem" in print view)

@rkomar, if you're reading this: can you give details about available free memory in your EXMEM-less build? (play mode, record mode, movie mode)? If there's enough memory, we should disable EXMEM for this model.

@eponymous
Which is your camera's firmware version?

Logged

rkomar

Re: A4000IS porting thread

« Reply #139 on: 30 / June / 2013, 21:11:05 »

Not sure if I'm doing this the right way, but when I go into <Alt>Misc Stuff->Show Memory Info when I'm in shooting mode I see 655712 bytes free, in playback mode I see 653072 bytes free, and when I hold down the record button and start recording video, I see 654672 bytes free. So, there doesn't seem to be much difference between them. CHDK size is 139692 bytes at offset 0x157ca4.

I've been running EXMEM-less for a few months now, and haven't had any JPEG corruption, and also haven't noticed any instabilities, although I also hadn't done any video recording until this test.

Logged