SD990 - page 11 - DryOS Development - CHDK Forum
« previous next »
Pages: 1 ... 6 7 8 9 10 [11] 12 13 14 15 16 ... 21   Go Down

SD990

  • 206 Replies
  • 98158 Views
*

Offline i5xswipe

  • *
  • 3
Re: SD990
« Reply #100 on: 14 / April / 2009, 19:01:32 »
Advertisements
I still feel like an idiot with CHDK, most of the talk around here just confuses the hell out of me, which is frustrating because I like to think I'm an advance tech geek, maybe it's all the unfamiliar camera terminology!

I appreciate all the hard work you've put in reyalp, can't wait to see the final product, I hope it to be a sweet product, with all the best scripts et al bundled together ready to go!

i5xSwipe
Logged
*

Offline reyalp

  • ******
  • 14128
Re: SD990
« Reply #101 on: 15 / April / 2009, 01:23:30 »
Quote from: i5xswipe on 14 / April / 2009, 19:01:32
I appreciate all the hard work you've put in reyalp, can't wait to see the final product, I hope it to be a sweet product, with all the best scripts et al bundled together ready to go!
It will be like any other CHDK build.

I've finally got some time to work on it again, so here's a new build.
main changes:
- optical zoom in video. No mute yet and the zoom motor is really loud!
- workaround for fast click of full shoot. The workaround will only be used if sv or tv override is in effect. Note, whitebalance appears to be different with or without the workaround. Also, I'm not sure if it works right with flash or not. However, tv/sv overrides with automatic flash don't make much sense anyway.
- adjusted fl_tbl
- tweaked battery high/low values. Note, these are stored in cfg, so unless you reset your cfg you won't see any change.
- enabled scripted LED support

I've also included (#ifdef'd out, under the define CAPTSEQ_MSG_LOG) some code for recording the sequence of values the main loop of capt_seq_task pulls from the message queue. This is messy and won't go into the trunk, but maybe someone will find it useful. Note, this will hang you cam in movie mode.

attached are patch and full build.
Logged
Don't forget what the H stands for.
*

Offline hnikesch

  • **
  • 75
Re: SD990
« Reply #102 on: 15 / April / 2009, 22:01:42 »
I will give new build a try, last build worked for the stuff I need.  I leave it running,  Added some display items, also use bracketing, custom auto iso, user menu, and a little RAW
Logged
It is better to burn a roll of film than curse the darkness Equip, S100 w/CHDK, SD900 w/CHDK, SD990 w/CHDK & Pentax K2000, Pentax Kr
Flickr:
*

Offline reyalp

  • ******
  • 14128
Re: SD990
« Reply #103 on: 18 / April / 2009, 03:01:10 »
beta version is merged into the trunk. This will appear on the autobuild server soon, and be functionally the same as the last build I posted here.
Logged
Don't forget what the H stands for.
*

Offline nabeshin

  • *
  • 3
Re: SD990
« Reply #104 on: 18 / April / 2009, 13:59:03 »
Quote from: speedfreak on 03 / April / 2009, 11:31:06
Quite interesting. What kind of software did you use to get this improved results over JPEG?
I always process DNG on Adobe Camera Raw over PS Elements, and Photomatix Pro when HDR.
Noise is a pity, but it can be eliminated via plugins.
Greetings
Logged
*

Offline reyalp

  • ******
  • 14128
Re: SD990
« Reply #105 on: 18 / April / 2009, 16:47:05 »
A quick and dirty timelapse I took the other day http://www.youtube.com/watch?v=6XlZkYThklI#hd

custom lua script loosely based on http://chdk.setepontos.com/index.php/topic,2589.0.html
Logged
Don't forget what the H stands for.
*

Offline reyalp

  • ******
  • 14128
Re: SD990 ISO override limt/bug
« Reply #106 on: 20 / April / 2009, 02:37:24 »
ISO override from the CHDK menu or script appears to only go up to effectively 800, despite showing ISO 1600 (or whatever) in the UI and exif.

The override definitely does change the ISO in the 80-800 range, but everything higher than 800 looks exactly the same.

A manual mode shot with the same settings and ISO 1600 is much more exposed.

I haven't tried comparing raws yet, but that's next.
Logged
Don't forget what the H stands for.
*

Offline reyalp

  • ******
  • 14128
Re: SD990
« Reply #107 on: 21 / April / 2009, 01:55:18 »
Updated in trunk (get it from the autobuild server http://mighty-hoernsche.de/)

Jogdial support. This means you can script the jogdial, and it'd disabled when you are in alt mode
Power up to shoot mode: just hold the power button down a bit longer

edit:
and now video quality control. I just blindly modeled it off the SX10 stuff (thanks ewavr  :xmas) so I'm not sure if the numbers are right, but it seems to work.
« Last Edit: 21 / April / 2009, 03:50:22 by reyalp »
Logged
Don't forget what the H stands for.
*

Offline kic

  • *
  • 3
Re: SD990
« Reply #108 on: 22 / April / 2009, 18:24:47 »
Hey together,

first of all - great job... I admire you guys doing all that complicated work. Thanks for porting it to the SD990.

Today I got my SD990/IXUS980 and I downloaded the beta version to try it out. I split the SDHC card (32GB), first partition 200MB FAT16, second partition the rest FAT32. DISKBOOT.BIN/PS.FI2 on the first partition, CHDK on the second, big one. Since I did not find a way to switch the camera on in play mode, I decided to do the BOOTDISK method by editing partition one. This worked, the cam boots into CHDK. It also stores pictures although the SDHC card is switched to LOCK (of course, otherwise it would not boot).

BUT - these pictures are all stored on the first, small FAT16 partition, nothing on the big FAT32 partition. Why? It must recognize the FAT32 because there is the CHDK file structure and I guess it would not work without this. I can press the direct print button to get into ALT mode, go through the menu... I didn't try mode, but definitely, pictures and movies go to the small partition.

Is this my fault? I cannot find any more hints about that.

Thanks a lot anyway, this is a great thing.

Torben
Logged
*

Offline reyalp

  • ******
  • 14128
Re: SD990
« Reply #109 on: 22 / April / 2009, 22:13:07 »
kic:
I'm not sure why the pictures would be stored on the first partition.  When CHDK loads, it should autodetect the larger partition and switch to that. I know this worked with the 8gig card I had set up. I used various linux tools to partition it, as described on the wiki.

You should also be able to load directly from a FAT32 card (or partition) using the "firmware update" method.

Did you use the build from http://mighty-hoernsche.de/ or one of the old ones attache to this forum ?

FWIW, diskboot.bin is only used for the autoboot method, and PS.FI2 is used for the "firm update" method. Each one is a complete copy of the CHDK executable, in slightly different formats. the CHDK directory structure should go on the big partitition.
Logged
Don't forget what the H stands for.
Pages: 1 ... 6 7 8 9 10 [11] 12 13 14 15 16 ... 21   Go Up
« previous next »
 

Related Topics


SimplePortal © 2008-2014, SimplePortal