supplierdeeply

SX40HS porting thread

  • 258 Replies
  • 63282 Views
*

Offline dvip

  • ****
  • 451
Re: SX40HS porting thread
« Reply #250 on: 24 / March / 2013, 12:47:54 »
Advertisements
Something interesting, both the SX40HS and the SX50HS share the same sensor, but in platform_camera.h I found a different values for CAM_RAW_ROWS.

// SX50HS:
// Sensor size, DNG image size & cropping
#define CAM_RAW_ROWPIX    4176  // Found @0xff1ae73c
#define CAM_RAW_ROWS      3062   // Found @0xff1ae748

// SX40HS:
// Sensor size, DNG image size & cropping
#define CAM_RAW_ROWPIX    4176  // Found @0xff18e050
#define CAM_RAW_ROWS       3060  // Found @0xff18e05c



Re: SX40HS porting thread
« Reply #251 on: 29 / March / 2013, 13:08:55 »
Hi Dave,
I was sent to this discussion as it relates to Stick... I have used it to load CHDK using my Mac onto a 32GB SD card with no problems. I have a 128GB SDXC card from Lexar Professional, and Stick doesn't see a card available when it is in the drive. I assume that the 128GB isn't supported by Stick. Is there a way to get it set up to process that size of card?

Thanks
Colin.

*

Offline dvip

  • ****
  • 451
Re: SX40HS porting thread
« Reply #252 on: 04 / April / 2013, 19:14:43 »

*

Offline dvip

  • ****
  • 451
Re: SX40HS porting thread
« Reply #253 on: 01 / May / 2013, 10:47:37 »
While on shooting mode I notice that the Canon menu overlaps chdk's menu.
I use the user menu and I don't notice this much there, but yesterday
I went back to the full chdk menu and could not even read
well some on the menu options, especially on the right part of the screen.
I don't remember this happening before, but then again, I've been using the user menu for a while now.



*

Offline zeno

  • *****
  • 884
Re: SX40HS porting thread
« Reply #254 on: 01 / May / 2013, 13:06:26 »
@londonroadhog

apologies Coln - only just seen your post. STICK can deal with 128GB cards if you edit the stick.properties file (with any text editor) and add/amend the line
   maxsize=130000
If you make it 128000 it still might not work, some 128Gb cards are actually slightly bigger.

Some users have reported problems with some card readers - I'm investigating.
A570, S100, Ixus 127
Author of ASSIST, STICK, WASP, ACID, SDMInst, LICKS, WICKS, MacBoot, UBDB, CFGEdit

*

Offline philmoz

  • *****
  • 3070
    • Photos
Re: SX40HS porting thread
« Reply #255 on: 01 / May / 2013, 16:03:48 »
While on shooting mode I notice that the Canon menu overlaps chdk's menu.
I use the user menu and I don't notice this much there, but yesterday
I went back to the full chdk menu and could not even read
well some on the menu options, especially on the right part of the screen.
I don't remember this happening before, but then again, I've been using the user menu for a while now.

Can you post an image showing the problem.

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 dvip

  • ****
  • 451
Re: SX40HS porting thread
« Reply #256 on: 01 / May / 2013, 18:36:52 »
Hi Phil, here is the image.
Notice how the flash icon... on the right, makes it hard to read the menu.


*

Offline philmoz

  • *****
  • 3070
    • Photos
Re: SX40HS porting thread
« Reply #257 on: 02 / May / 2013, 04:13:27 »
Hi Phil, here is the image.
Notice how the flash icon... on the right, makes it hard to read the menu.

Strange - I've not had that problem, and I can't reproduce it.

What mode do you have the camera in, and what are the Canon menu settings?

It's not likely that much can be done about it - other than to avoid the mode/setting that causes the problem.

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 dvip

  • ****
  • 451
Re: SX40HS porting thread
« Reply #258 on: 03 / May / 2013, 14:47:00 »
It looks like the problem occurs when a TV Ev step value of 10 or slower is used.
It might have something to do with the screen's refresh rate when using a slow TV value.

 

Related Topics