ixus90/sd790 IS porting

Nitek

My cam crashed while i was trying different iso-values, but alle the other stuff i tried worked.

Nitek

blubbi
DNG works fine here.

How did you get the badpixel-script working? I keeps telling me i have to run it in record mode...

edit:
Now it started (don't realy know why now), but it didn't save the badpixel.bin file...

sharky

if it says 'run this script again', then something went wrong (it does two shoots, and both badpixel counts should match). if it goes OK, then you have to press 'set' for it to write the badpixel list.

blubbi

Nitek

blubbi
DNG works fine here.

How did you get the badpixel-script working? I keeps telling me i have to run it in record mode...

edit:
Now it started (don't realy know why now), but it didn't save the badpixel.bin file...

Pushing SET didn't help.
I looked at the card on my PC and there was a bad_tmp.bin (or some similar name) on the card.
Renamed it, and everything worked.

I don't know why the script does't rename the file itself.

Thougth there are many scripts which do not work correct on my ixus.
(Motion detection, Intervalometer.... http://crteknologies.free.fr/wiki/doku.php/photo:chdk-scripts )

Kind regards
blubbi

hairyfoote

reyalp
Most (all ?) of the IXUS/SD series don't have a real adjustable aperture, so CHDK can't add aperture override. The aperture is entirely dependent on zoom. CHDK can allow control of the ND filter.

I know this doesn't particularly apply to the development. But, how can you go about changing the DOF if you can't override the aperture? As far as I know, using the ND filter would have no way of doing this. Would I have to mess with the Subject Distance values? Or is there no way to manually change the DOF?

Thanks

sharky

No.

no variable DOF.

buy a professional camera 😀

hairyfoote

Haha. Alright, thanks for clearing that up!

PhyrePhoX

or use zoom.

hairyfoote

Has anyone else had trouble with running scripts? I tried running 3 different motion detection scripts, and only 1 actually ran but it wasn't able to actually "detect" anything. I even played with the settings to make sure I didn't have a value wrong, but it still didn't work. Although I was able to get a Time Lapse script to work.

Do these scripts need to be adapted for the ixus90? Or do these script problems relate to the current working build of CHDK on our ixus90?

Is there any noticeable difference between Average and RAWconv for the bad pixel setting?

sharky

Judging from your story, there may be a problem in finding the correct 'live image' buffer on the ixus90. Do this histograms work ? They use the same data I think..

sharky

Also, since the 'mode' wheel is not working, maybe some scripts depend on running in the correct mode.

You probably have to power down, set the correct mode, then power up to change mode, am I right ?

hairyfoote

Well, the histogram graph will show up on the display. But the graph never changes even if I meter to different lighting conditions and such. So i'm guessing that means the "live" part doesn't work. Correct? Is there anything else I can test this with to be sure of that.

Yeah, most of them require at least M mode. And that's what I pretty much always keep it set as.

Nitek

sharky
Also, since the 'mode' wheel is not working, maybe some scripts depend on running in the correct mode.

You probably have to power down, set the correct mode, then power up to change mode, am I right ?

The wheel changes to between Auto, Manual, Digital Macro, Color Swap... Changing between picture and movie mode is done by a slider.

sharky

Well, the histogram graph will show up on the display. But the graph never changes

Mkay, that's bad.

I will check the ROM to see if the live buffer is somewhere different than in the ixus85. In fact, maybe the original poster had it all right and I have to revert some of the code back to his code.

The wheel changes to between Auto, Manual, Digital Macro, Color Swap... Changing between picture and movie mode is done by a slider.

I see. I thought the wheel did picture/movie mode. Maybe its a simple fix somewhere. I will take a look at this some time soon.

cheers,
Sharky

Nitek

Some things are strange:
- the cam allways powers up in play mode (no big problem though)
- sometimes it doesn't show the chdk-osd (except of the boot-splash) and ignores the overrides
- sometimes the osd disappears when changing vom play to record (pushing the trigger) and ignores the overrides
- overriding iso crashes the cam when taking a photo: live view continous for 1 or 2 seconds, then the cam turns off

hairyfoote

I have experienced many of those same symptoms, especially when it ignores the overrides. I haven't been able to do anything that consistently reproduces the problem so I don't know what may be causing it. It just seems like totally random timing.

For the OSD, the battery icon and histogram show perfect all the time (however the histogram doesn't actually "work" like it should). Also, if I selected to not show the boot splash screen, it seemed like the OSD would never show up.

scruss

Many thanks to all the developers. I now have my SD790 writing 15MB DNG files.

Crono

scruss
Many thanks to all the developers. I now have my SD790 writing 15MB DNG files.

How? My DNG files seems corrupted (purple lines and garbage).

Thanks to all the people involved in porting CHDK to IXUS90IS!!!

scruss

Crono
How? My DNG files seems corrupted (purple lines and garbage).

Dunno. They look okay to me. Photoshop didn't like them, but Gimp RAW handled them fine.

cliff

Well I tried it today and although it is a work in progress looks great,
thanks to the developers and hope to see a fully working version soon.

Hadn't tried gimp on the raw files will try that
rgds,
Cliff

« Previous Page Next Page »