supplierdeeply

SX30 IS porting thread

  • 109 Replies
  • 14817 Views
*

Offline philmoz

  • *****
  • 2936
    • Photos
  • Publish
    Re: SX30 IS porting thread
    « Reply #40 on: 02 / December / 2010, 04:26:04 »
    Advertisements
    Many of the SX30 property constants are different from what is currently in propset3.h.

    If I add a conditional section based on the camera it messes up the creation of propset3.lua.

    Is there anything planned to handle this?

    Regards,
    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)

  • Publish
    Re: SX30 IS porting thread
    « Reply #41 on: 02 / December / 2010, 05:18:49 »
    This makes sense. I guess you plan to combine and convert them on the PC ?

    Yes.

    I may have a problem correcting vignetting and barrel distortion because the strips are each side of centre.
    I assume lens corrections are normally computed radially about the centre.

    Quote
    horizontal (with the normal landscape camera orientation) strips should be much simpler than vertical ones

    Think about it .. they have to be vertical to make a panorama.
    The camera will be mounted vertically.

    Quote
    since you can just write() a continuous chunk.

    Yes, this is working and passes the Adobe DNG test.
    A fullsize image is fine, the strip has the wrong colours.

    Very strange.
    Not sure if it is the header information or the (temporary) reverse-bytes expecting to start at a particular memory location.

    Incidentally, using one header file for all the shots means the thumbnails will not be correct.
    If allowed by the DNG standard, I may decide not to have a thumbnail.
    For testing, reversing bytes just once is useful because the JPG displays the location and size of the  stripe.
    « Last Edit: 02 / December / 2010, 05:23:55 by Microfunguy »

    *

    Offline philmoz

    • *****
    • 2936
      • Photos
  • Publish
    Re: SX30 IS porting thread
    « Reply #42 on: 02 / December / 2010, 05:43:27 »
    A fullsize image is fine, the strip has the wrong colours.

    Make sure your strip starts on an even row and is an even number of rows high. The sensor layout alternates each row so if you start on an odd row you will confuse the hell out of the de-mosaicing algorithm.

    Regards,
    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)

  • Publish
    Re: SX30 IS porting thread
    « Reply #43 on: 02 / December / 2010, 06:41:42 »
    Make sure your strip starts on an even row and is an even number of rows high.

    Yes, that is working fine now.


    David


    *

    Offline whoever

    • ****
    • 280
    • IXUS950
  • Publish
    Re: SX30 IS porting thread
    « Reply #44 on: 02 / December / 2010, 06:45:50 »
    I may have a problem correcting vignetting and barrel distortion because the strips are each side of centre.
    I assume lens corrections are normally computed radially about the centre.
    Yes, but not necessarily about the image center. In particular, DNG 1.3 opcodes for geometric and vignetting corrections allow you to specify the location of optical center in the image.
    Quote
    If allowed by the DNG standard, I may decide not to have a thumbnail.
    Thumbs are "recommended", but not required by the standard. Note that, if you remove them, you need to change the DNG structure, as in this case the main raw image goes into IFD0, rather than the thumb.

  • Publish
    Re: SX30 IS porting thread
    « Reply #45 on: 02 / December / 2010, 06:54:22 »
    (I guess this should be a separate topic but too late now)


    DNG 1.3 opcodes for geometric and vignetting corrections allow you to specify the location of optical center in the image.

    Surely the 'optical centre' will be outside each image strip ?

    Quote
    in this case the main raw image goes into IFD0, rather than the thumb.

    Thanks, I will look into that.

    *

    Offline whoever

    • ****
    • 280
    • IXUS950
  • Publish
    Re: SX30 IS porting thread
    « Reply #46 on: 02 / December / 2010, 07:02:23 »
    (I guess this should be a separate topic but too late now)
    I believe one can still split it.

    Quote
    Surely the 'optical centre' will be outside each image strip ?
    The specs don't explicitly require it to be inside the image -- one can try and see if dng_validate swallows it.

    *

    Offline whoever

    • ****
    • 280
    • IXUS950
  • Publish
    Re: SX30 IS porting thread
    « Reply #47 on: 02 / December / 2010, 14:01:28 »
    Quote
    one can try and see if dng_validate swallows it.
    Just tried. It doesn't. Says "Error: File format is invalid". ACR doesn't like it either. Out of luck, that is.


    *

    Offline pixeldoc2000

    • ****
    • 355
    • IXUS900Ti 1.00C, IXUS300HS 1.00D
      • pixel::doc homebase
  • Publish
    Re: SX30 IS porting thread
    « Reply #48 on: 02 / December / 2010, 14:21:48 »
    @philmoz

    Please share your source with us. This may help other (me) ;)
    I recomment put it on github.com ...

  • Publish
    Re: SX30 IS porting thread
    « Reply #49 on: 02 / December / 2010, 18:20:17 »
    Just tried. It doesn't. Says "Error: File format is invalid". ACR doesn't like it either. Out of luck, that is.

    OK, thanks.

    Anyway, even if the format was valid you would still need an application that supported that operation.
    I will just hope that stitching software will make the unsymmetrical corrections.

    I now have it working without a thumbnail.
    It is accepted by RawTherapee and IrfanView (and of course dng_validate except for the time format).

    IrfanView reported image size is half the correct value, maybe because I do not include EXIF information.


     

    Related Topics