PowerShot SX220 HS - Porting Thread - page 21 - General Discussion and Assistance - CHDK Forum  

PowerShot SX220 HS - Porting Thread

  • 563 Replies
  • 183262 Views
*

Offline philmoz

  • *****
  • 3445
    • Photos
Re: PowerShot SX220 HS - Porting Thread
« Reply #200 on: 25 / June / 2011, 09:20:43 »
Advertisements
Code: [Select]
#define ASPECT_GRID_XCORRECTION(x)  ( (((x)<<3)/8)+60  )

(((x)<<3)/8) == (x)

Phil.
CHDK ports:
  sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
  g12 (1.00c, 1.00e, 1.00f & 1.00g)
  sx130is (1.01d & 1.01f)
  ixus310hs (1.00a & 1.01a)
  sx40hs (1.00d, 1.00g & 1.00i)
  g1x (1.00e, 1.00f & 1.00g)
  g5x (1.00c, 1.01a, 1.01b)
  g7x2 (1.01a, 1.01b, 1.10b)

*

Offline funnel

  • ****
  • 349
Re: PowerShot SX220 HS - Porting Thread
« Reply #201 on: 25 / June / 2011, 09:58:27 »
Code: [Select]
(((x)<<3)/8) == (x)Thanks, I just left what was in the other port. I'll change it to avoid the unneeded calculations.
« Last Edit: 25 / June / 2011, 10:00:35 by funnel »

*

Offline whim

  • ******
  • 2046
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: PowerShot SX220 HS - Porting Thread
« Reply #202 on: 25 / June / 2011, 10:01:10 »
@funnel

Spotted an error in Makefile: you appear to support 2 separate firmwares (as in: platform/sub has
separate dirs for 100a and 101a) but still have "cp" lines in Makefile for sx220.
IMHO you can just remove lines 477-480.

BTW, I have beefed up Makefile syntax checking in CHDK-Shell 3.28, instead of silently crashing
it will now at least report the first offending line in cases like this.

cheers,

wim


*

Offline funnel

  • ****
  • 349
Re: PowerShot SX220 HS - Porting Thread
« Reply #203 on: 25 / June / 2011, 10:17:53 »
Thanks. I couldn't figure out why it was crashing.


*

Offline Tiz

  • *
  • 29
Re: PowerShot SX220 HS - Porting Thread
« Reply #204 on: 26 / June / 2011, 17:10:54 »
@funnel

I just registered in order to say: Thank you very much! Your great work is highly appreciated.

CHDK works great for me. In particular, fine detail (grass, trees) comes out much better in DNG mode.

Also the histo and the zebra are really nice.

The only thing, I am not entirely happy with is the video mode of the camera. There is too much noise reduction (destruction of fine details). I am wondering whether it is possible to increase the video quality.

*

Offline funnel

  • ****
  • 349
Re: PowerShot SX220 HS - Porting Thread
« Reply #205 on: 26 / June / 2011, 18:25:53 »
You can try the video quality override. I don't see much difference when using it though, just a bigger file. If you want I can send you a build with native calls enabled if you want to play with changing the iso, shutter speed and aperture in video mode with a lua script.

Most of the time I just use the original 720p mode and I like it.

*

Offline Tiz

  • *
  • 29
Re: PowerShot SX220 HS - Porting Thread
« Reply #206 on: 27 / June / 2011, 00:34:47 »
I think the bitrate is just fine. The noise reduction seems to be the problem. I do not know, however, whether it is possible to control this via CHDK.

*

Offline funnel

  • ****
  • 349
Re: PowerShot SX220 HS - Porting Thread
« Reply #207 on: 27 / June / 2011, 03:33:15 »
You can also try to bump up the sharpness in custom colors to see if it makes any difference.


Re: PowerShot SX220 HS - Porting Thread
« Reply #208 on: 27 / June / 2011, 04:54:20 »
I think the bitrate is just fine. The noise reduction seems to be the problem. I do not know, however, whether it is possible to control this via CHDK.

That noise reduction must be applied in the processing of the image, it isn't like long exposure noise reduction ("black frame"). I don't imagine an easy way through CHDK to skip that part of the image processing (but I don't know the inners of CHDK and the camera itself...).

As funnel said increasing sharpness should help, and I think increasing bitrate should help too (at least it won't hurt ;) ).

Saludos!

Re: PowerShot SX220 HS - Porting Thread
« Reply #209 on: 27 / June / 2011, 07:08:15 »
Great news, I found a way to solve the AF Scan crash. I used DoAFLock() instead of MakeAFScan(). I was experimenting with UnlockAF after MakeAFScan to see what happens and tried also DoAFLock and found it. Look like it has the same functionality and doesn't crash when zooming.

thanks for notify me in the Ixus 1000 thread.I get no notify about that, so i only today take a look whats new.

and its a really great new.
Your fix work on Ixus 1000 too great, i get no crash.

I dont know, if chdk change to use the new command or should the address for makeafscan set to DoAFLock to work with newest chdk source ?

thats the code i test.

void other_kbd_process(){
 int key;
#if CAM_AF_SCAN_DURING_VIDEO_RECORD

 if (movie_status==VIDEO_RECORD_IN_PROGRESS) {
  if (kbd_is_key_clicked(conf.video_af_key)) DoAFLock();
 }

#endif

its great to have refocus button working, because without button focus adjust is very slow.
last thing i miss is change exposure during record.
have you done some tesst, or better idea ?

I get the idea to try out a brute force method during video record.in the keyboard task loop, i try to set always the  EV value.maybe that help ?
Ixus 1000 HS

 

Related Topics