the sx10 porting thread

reyalp

14033

Re: the sx10 porting thread

« Reply #580 on: 26 / October / 2009, 00:59:24 »

Advertisements

In core/gui.c gui_draw_osd, at the very start this is a commented out call to gui_draw_debug_vals_osd

Uncomment that one, comment the other one, and it should draw on top of the menu. Not completely sure about recreview mode.

Logged

Don't forget what the H stands for.

hiker_jon

284

Re: the sx10 porting thread

« Reply #581 on: 26 / October / 2009, 12:21:55 »

Quote from: reyalp on 26 / October / 2009, 00:59:24

In core/gui.c gui_draw_osd, at the very start this is a commented out call to gui_draw_debug_vals_osd

Uncomment that one, comment the other one, and it should draw on top of the menu. Not completely sure about recreview mode.

That worked! (for menu, but it still doesn't show in recreview mode, so in this mode the value of playrec_mode is unknown).

If the camera starts up in play mode then playrec_mode = 0.
In record mode playrec_mode = 2.
If you hit menu in record mode playrec_mode = 4.
If you go back to play mode from record mode playrec_mode = 3.
If the lens retracts while in play mode playrec_mode stays at 3.
If you hit the movie record button in record mode playrec_mode briefly goes to 5 then back to 2.

Whatever playrec_mode is used for, it is more complicated than just a bit field to indicate play/record mode.

I am stuck on how to detect recreview mode.

Logged

hiker_jon

284

Re: the sx10 porting thread

« Reply #582 on: 26 / October / 2009, 13:31:59 »

One more observation on recreview mode.
Not even the <alt> text appears when in this mode, but the camera does go into alt mode (but not reliably) as can be checked by pressing alt then verify that the delete button is not recognized until alt is pressed a second time.

Jon

Logged

reyalp

14033

Re: the sx10 porting thread

« Reply #583 on: 29 / October / 2009, 23:51:28 »

Quote from: hiker_jon on 26 / October / 2009, 12:21:55

That worked! (for menu, but it still doesn't show in recreview mode, so in this mode the value of playrec_mode is unknown).

If the camera starts up in play mode then playrec_mode = 0.
In record mode playrec_mode = 2.
If you hit menu in record mode playrec_mode = 4.
If you go back to play mode from record mode playrec_mode = 3.
If the lens retracts while in play mode playrec_mode stays at 3.
If you hit the movie record button in record mode playrec_mode briefly goes to 5 then back to 2.

What happens if you open the menu in play mode ?

Also, by menu you mean the menu button menu, or the func menu ?

edit:
I think I've found the same variable on my camera (a540) and it does not change when you go into the menu in play mode.

It does go to 5 briefly when changing to movie mode with the dial.

« Last Edit: 30 / October / 2009, 00:48:36 by reyalp »

Logged

Don't forget what the H stands for.

hiker_jon

284

Re: the sx10 porting thread

« Reply #584 on: 30 / October / 2009, 04:27:31 »

Quote from: reyalp on 29 / October / 2009, 23:51:28

Quote from: hiker_jon on 26 / October / 2009, 12:21:55
That worked! (for menu, but it still doesn't show in recreview mode, so in this mode the value of playrec_mode is unknown).

If the camera starts up in play mode then playrec_mode = 0.
In record mode playrec_mode = 2.
If you hit menu in record mode playrec_mode = 4.
If you go back to play mode from record mode playrec_mode = 3.
If the lens retracts while in play mode playrec_mode stays at 3.
If you hit the movie record button in record mode playrec_mode briefly goes to 5 then back to 2.

What happens if you open the menu in play mode ?

Also, by menu you mean the menu button menu, or the func menu ?

edit:
I think I've found the same variable on my camera (a540) and it does not change when you go into the menu in play mode.

It does go to 5 briefly when changing to movie mode with the dial.

I meant press the menu button. Same as your a540 playrec_mode in my sx10 does not change in play mode when the menu button is pressed.

canon_menu_active detects menu press in play or record mode.

I am stumped by recreview hold. No chdk graphics appear. This is different than my other cameras (a590,a720).

Logged

reyalp

14033

Re: the sx10 porting thread

« Reply #585 on: 30 / October / 2009, 20:23:57 »

Quote from: hiker_jon on 30 / October / 2009, 04:27:31

I meant press the menu button. Same as your a540 playrec_mode in my sx10 does not change in play mode when the menu button is pressed.

canon_menu_active detects menu press in play or record mode.

So cameras that use playrec_mode should take 4 to mean record mode as well.

Quote

I am stumped by recreview hold. No chdk graphics appear. This is different than my other cameras (a590,a720).

Perhaps something else is preventing CHDK from drawing ? You can turning on an LED in the gui code that tests for recreview to see if it is set at that point. Or add something to the main spytask loop that makes the debug LED follow the state of the recreview variable.

Logged

Don't forget what the H stands for.

JoeMarfice2

Re: the sx10 porting thread

« Reply #586 on: 11 / January / 2010, 04:55:00 »

OK, I was able to follow the directions to build the bac pixel map (using the script) up until the BOLD TEXT below:

Quote from: fe50 on 20 / March / 2009, 16:37:57

- power your cam on, half-press the shutter to go to record mode
- press PRINT, then press FUNC/SET
- select "Load script from file", go 2 steps down to the TEST/ folder, press FUNC/SET
- select "BADPIXEL.LUA", press FUNC/SET
- start the script with the SHUTTER !
- wait until you see "press SET to save....." {THIS NEVER HAPPENED}
- press FUNC/SET to store the badpixel.bin automatically in the right place

- press PRINT to leave the <Alt> mode, press PRINT again to enter <Alt> mode
- press MENU, go to the "RAW parameters", enter it with FUNC/SET
- enable the settings "Save RAW" , "DNG format" and "DNG file extension"
- press PRINT to leave the <Alt> mode again

Now RAW saving in DNG format is enabled, transfer the DNG files with a card reader...

Instead of the screen displaying "press SET to save.....", it warns me "this will take a few seconds - don't panic!" (OK - good wait message

). Then, the blue Print-button LED flashes, the screen appears to take a photo, this process repeats, and ... the screen goes dark after 30 seconds or so. Tried pressing FUNC/SET at that point, and following the directions, but it didn't work.

So, I reset the power settings in the Canon menu so that my screen would stay active for 3 min (the maximum allowed). Repeated the process. After ~3 min the screen went dark...

Now, with an error message suggesting it will take "a few seconds", waiting over 3 minutes seems like something's gone wrong.

This time, after the 2 cycles through the auto-picture taking, I just went ahead and selected FUNC/SET. The screen now reads at the very bottom:
Create badpixel.bin < ALT >

Looks like it's doing something, but it never seems to finish.

Help?

Logged

fe50

3147
IXUS50 & 860, SX10 Star WARs-Star RAWs

Re: the sx10 porting thread

« Reply #587 on: 11 / January / 2010, 05:03:22 »

Sometimes the console screen may get overwritten/cleared, so you cant't see the "press SET to save....." message.

--> Just press FUNC/SET ~20 seconds after the 2nd flash of the blue print LED...
--> To see the console messages again (aka "refresh the console screen") you can also press the PRINT button twice.

Logged

-->FIRMWARE DUMPS<-- * Manual * Lua * me

JoeMarfice2

Re: the sx10 porting thread

« Reply #588 on: 12 / January / 2010, 15:47:34 »

Thanks, fe50, that worked! I'm in business with DNG raw files that can be read by actual programs!

Gripe, not aimed at anyone here: Why on earth the CHDK project would call their output files CRW, when they aren't consistent with standard Canon CRW files - according to what I've read and seen - is beyond me... No one outputs Word-like documents with a .txt extension. No one outputs .bmp image files that aren't bitmaps. These files should be .CR1, or .CRW_CHDK, or anything not already associated with an existing image file format.

Logged

sandeman

31

Re: the sx10 porting thread

« Reply #589 on: 12 / January / 2010, 16:02:38 »

Quote from: JoeMarfice2 on 12 / January / 2010, 15:47:34

Gripe, not aimed at anyone here: Why on earth the CHDK project would call their output files CRW, when they aren't consistent with standard Canon CRW files - according to what I've read and seen - is beyond me... No one outputs Word-like documents with a .txt extension. No one outputs .bmp image files that aren't bitmaps. These files should be .CR1, or .CRW_CHDK, or anything not already associated with an existing image file format.

Because there is no such thing as a fixed crw format. Nearly every camera has a different format. The programs you use have been programmed so they can read the files of (most) Canon cameras that natively support raw output. But this does not mean that these are in principle not different from the CHDK .crw files. The SX10 is just not implemented in these programs. When Canon brings out a new camera, it always takes a while before e.g. Photoshop can read the raw files.

Besides this, there are programs that can read the .crw files produced by CHDK on the SX10.

Edit: OK, let me rephrase this a bit: the crw format is standardized, but most programs need a camera profile in order to read the files from a specific camera.

« Last Edit: 12 / January / 2010, 16:18:01 by sandeman »

Logged