A495 porting thread

  • 346 Replies
  • 46803 Views
  • Publish
    Re: A495 porting thread
    « Reply #310 on: 03 / July / 2011, 13:51:26 »
    Advertisements

    I'm not entirely sure what constant bit rate does


    Keeps the bitrate constant !

    Which means that if the scene becomes more detailed and/or there is increased movement, the frame-compression will have to be increased and video quality will therefore be reduced

    *

    Offline philmoz

    • *****
    • 2936
      • Photos
  • Publish
    Re: A495 porting thread
    « Reply #311 on: 03 / July / 2011, 15:54:42 »
    If you're referring to the override to select 'Super Fine' JPEG compression this isn't enabled for the A495.
    If I follow this thread correctly,  this is an issue with jpeg's and not video ?  It seems to have started with video and transitioned.

    @philmoz :  I assume the is an issue with a #define in platform_camera.h ?  Is so, which one ?   The problem with that file is that there doesn't seem to be a way to know if something is missing - it doesn't look like every parameter is either #define of #undef.


    JPEG quality override is enabled by adding
        #define CAM_QUALITY_OVERRIDE            1
    to platform_camera.h

    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)

    *

    Offline reyalp

    • ******
    • 9865
  • Publish
    Re: A495 porting thread
    « Reply #312 on: 03 / July / 2011, 16:02:29 »
    @philmoz :  I assume the is an issue with a #define in platform_camera.h ?  Is so, which one ?   The problem with that file is that there doesn't seem to be a way to know if something is missing - it doesn't look like every parameter is either #define of #undef.

    include/camera.h should be the master list, with a define/undef for anything that might appear in platform_camera.h, plus a descriptive comment.

    *should* being the operative word ;)
    Don't forget what the H stands for.

  • Publish
    Re: A495 porting thread
    « Reply #313 on: 03 / July / 2011, 16:52:16 »
    If you're referring to the override to select 'Super Fine' JPEG compression this isn't enabled for the A495.
    If I follow this thread correctly,  this is an issue with jpeg's and not video ?  It seems to have started with video and transitioned.

    @philmoz :  I assume the is an issue with a #define in platform_camera.h ?  Is so, which one ?   The problem with that file is that there doesn't seem to be a way to know if something is missing - it doesn't look like every parameter is either #define of #undef.


    JPEG quality override is enabled by adding
        #define CAM_QUALITY_OVERRIDE            1
    to platform_camera.h

    Phil.

    @philmoz :  are you going to post a patch ?


    *

    Offline philmoz

    • *****
    • 2936
      • Photos
  • Publish
    Re: A495 porting thread
    « Reply #314 on: 03 / July / 2011, 18:21:42 »
    @philmoz :  I assume the is an issue with a #define in platform_camera.h ?  Is so, which one ?   The problem with that file is that there doesn't seem to be a way to know if something is missing - it doesn't look like every parameter is either #define of #undef.

    include/camera.h should be the master list, with a define/undef for anything that might appear in platform_camera.h, plus a descriptive comment.

    *should* being the operative word ;)

    There's an '#undef' in camera.h; but the comment leaves a bit to be desired.

    I'll post a patch for the A495 and update the comment in camera.h later - unless waterwingz beats me to it.

    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: A495 porting thread
    « Reply #315 on: 04 / July / 2011, 00:30:09 »
    unless waterwingz beats me to it.
    I'm on vacation this week - laptop only, no build machine with me. :P

  • Publish
    Re: A495 porting thread
    « Reply #316 on: 06 / July / 2011, 16:11:16 »
    OK! I have some news:
    How the camera detects that a card was inserted??

    Today I was experimenting with a 2GB kingston microSD with the adapter. But, when I turn the camera on in playback mode and without the card in the adapter, it says "Memory card error" & "Card locked" both with the adapter locked and unlocked.

    When I take the adapter out, the camera detects correctly that there's no card inserted.

    Does this information helps with my 16GB card issue?
    Anyone else had this problem too?

    Thanks!

  • Publish
    Re: A495 porting thread
    « Reply #317 on: 10 / July / 2011, 09:12:13 »
    For the Aussie members. Dick Smith are selling Canon A495 for $68.00.

    I purchased two and used CameraVersion13-sfx to read the version number from a photo.

    Both read version 100 on the exif data.

    I purchased my first Canon A495 about two months ago. That version reads 100 as well.

    I have read through the posts in this thread, which is the best A495 CHDK to use with a version 100?


    *

    Offline whim

    • ******
    • 2013
    • A495/590/620/630 ixus70/115/220/230/300/870 S95
  • Publish
    Re: A495 porting thread
    « Reply #318 on: 10 / July / 2011, 09:52:49 »
    Quote
    I purchased two and used CameraVersion13-sfx to read the version number from a photo.

    Both read version 100 on the exif data.

    Use CameraVersion13's button "Phil's site" to browse to the exiftools site, download the Windows Executable (currently 8.60) and update (just drop 'exiftool(-k).exe' in the directory with CameraVersion13.exe and restart)

    hth,

    wim

    PS above tested to work on a JPG from A495 / 100e
    « Last Edit: 10 / July / 2011, 10:00:11 by whim »

  • Publish
    Re: A495 porting thread
    « Reply #319 on: 10 / July / 2011, 11:00:08 »
    @whim,

    Installed exiftool

    Scrolling in main page

    Firmware Revision 1.00 rev 6.00 displayed.

     

    Related Topics