IXUS 105 / SD1300 IS porting thread - page 75 - DryOS Development - CHDK Forum  

IXUS 105 / SD1300 IS porting thread

  • 772 Replies
  • 236926 Views
Re: IXUS 105 / SD1300 IS porting thread
« Reply #740 on: 11 / November / 2012, 19:36:32 »
Advertisements
Some more info: fw 1.00d, no palette specified in platform_camera.h so using default palette1.

*

Offline nafraf

  • *****
  • 1308
Re: IXUS 105 / SD1300 IS porting thread
« Reply #741 on: 12 / November / 2012, 05:33:21 »
@casrap
Thanks for the report.

I'll use your movie_rec.c to port the same function in 100b and 100c.  I'll post the patches in a couple of days.

About the colors, I think that is better to change the palette ;)

Re: IXUS 105 / SD1300 IS porting thread
« Reply #742 on: 12 / November / 2012, 05:56:39 »
AFAIK changing the palette does not change the available colors, it only changes the selection from those colors for chdks output?

Re: IXUS 105 / SD1300 IS porting thread
« Reply #743 on: 12 / November / 2012, 09:46:12 »
AFAIK changing the palette does not change the available colors, it only changes the selection from those colors for chdks output?
Correct.  The choice of palette determines how CHDK maps the colors it wants to the camera's 256 byte array of values that hold the camera colors.   Unfortunately,  Canon changes that array between different modes (shooting, playback, menu, etc) so selecting a nice mapping in playback does not guarantee good looking colors in shooting mode.   

Some of the more recent cameas have an option to overwrite unused values in the playback and record palettes so that nice colors can be selected.
Ported :   A1200    SD940   G10    Powershot N    G16


Re: IXUS 105 / SD1300 IS porting thread
« Reply #744 on: 16 / November / 2012, 15:30:13 »
Hi all,

during last days we were testing FW v 1.0b.
camera working with prepared CHDK patch version.

@nafraf - thank you

A495, IXUS 105

Re: IXUS 105 / SD1300 IS porting thread
« Reply #745 on: 23 / November / 2012, 06:55:31 »
I found a bug that disables all overrides; when you select a self timer few of the overrides work and after one shot none of the overrides work. I fixed the bug, and nafraf kindly cleaned it up, ported it to 100b and will post the update to the autobuild svn and/or will ask for testers for the 100b version.

*

Offline nafraf

  • *****
  • 1308
Re: IXUS 105 / SD1300 IS porting thread
« Reply #746 on: 12 / December / 2014, 08:39:46 »
Patch to remove KEY_POWER from KEY_MASK0, bug reported here.

*

Offline koshy

  • *****
  • 1096
Re: IXUS 105 / SD1300 IS porting thread
« Reply #747 on: 14 / December / 2014, 21:07:45 »
Patch to remove KEY_POWER from KEY_MASK0, bug reported here.
Tested to be working fine. Play is ALT key now and I can power the cam off while in ALT mode. Thanks.
Koshy had a little ELPH which wasn't white as snow but everywhere that Koshy went the ELPH was sure to go. (actually an SD, but that detail ruins the rhyme...)


*

Offline nafraf

  • *****
  • 1308
Re: IXUS 105 / SD1300 IS porting thread
« Reply #748 on: 15 / December / 2014, 06:15:08 »
Thanks. Changes committed to trunk, changeset 3800

*

Offline reyalp

  • ******
  • 14079
Re: IXUS 105 / SD1300 IS porting thread
« Reply #749 on: 08 / June / 2016, 15:47:37 »
Replying to post from the chdkptp thread, because this is almost certainly a porting issue:
in Full zoom: no distortions via chdkptp client, but distorted using init_usb_capture(1,0,0); and shoot();
Cam Model is IXUS 105.

This first image is taken using chdkptp client (remote shoot), exhibiting no distortion, the second has (note the bent edges).

I use a java library to take photos (relevant lines:https://github.com/acamilo/CHDK-PTP-Java/blob/master/src/main/java/chdk/ptp/java/camera/AbstractCamera.java#L389).
Why are the images distorted and what to do against it ?
What does your client do better ?

The difference is  almost certainly related to the method used to set zoom rather than the client. The chdkptp GUI just sends click('zoom_in') or click('zoom_out') for each button press. Using script set_zoom lets you go directly to a specific zoom point, but in some ports the camera doesn't update it's distortion correction settings.

It is possible we can adjust the port to make set_zoom behave correctly.

Please post your canon firmware version. If no one else beats me to it, I'll try to post a test build in the next few days.
Don't forget what the H stands for.

 

Related Topics