the sx10 porting thread

reyalp

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.

hiker_jon

reyalp
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.

hiker_jon

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

reyalp

hiker_jon
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.

hiker_jon

reyalp

hiker_jon
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).

reyalp

hiker_jon
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.

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.

fe50

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.

sandeman

[unknown]
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.

fe50

@JoeMarfice2
as sandeman already said - CRW is "a kind of" standard used by Canon (Canon RaW) for older RAW images, there's also the newer .CR2 RAW image format. Canon didn't publish official papers for those formats...
There are also dozends of other RAW image "file formats" out there, that's why Adobe created the DNG format...
--> http://en.wikipedia.org/wiki/Raw_image_format
--> http://en.wikipedia.org/wiki/Digital_Negative_%28file_format%29

If you don't like .CRW, so you can choose another filename extension in the CHDK RAW menu.

reyalp

sandeman

[unknown]
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.

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.

This is not true (edit: or I should say, not the whole picture). CRW and CR2 are Canon formats with a well defined specific technical specification. CHDK does not implement either of these formats, and CHDK "CRW" files are just a sensor dump which has no relation to the canon format.

CHDK uses the CRW extension because it is recognized by the canon firmware, which makes some things like transferring over USB more convenient. You can choose other extensions if you like.

Here's some notes on how the prefix/extension chosen interact with the canon firmware:
https://chdk.setepontos.com/d/2045/1

edit to add:
It is unfortunate that the CHDK non-format has become confused with the canon format. It would have been better to define an actual, easily identifiable format from the start. Oh well, see sig 😉

whim

So, just like I said, the CHDK project "CRW" files aren't consistent with standard Canon CRW files, and that's just plain dumb.

I wouldn't call going for maximum possible saving speed dumb, it's nice to have a choice between
max speed and max compatibility.

wim

reyalp

[unknown]
So, just like I said, the CHDK project "CRW" files aren't consistent with standard Canon CRW files, and that's just plain dumb.

The part of the post you didn't quote explained why that extension was chosen... and you are still free to use other extensions.

JoeMarfice

(I'm the same user as JoeMarfice2, BTW)

OK, I missed the part where whim & reyalp said that (if I'm putting it all together right) the files won't be saved as quickly with a less ambiguous file extension than "crw". It is then a very unfortunate choice, instead of just dumb. Maybe the best choice, but if so, that's still unfortunate, because it's ambiguous.

The whole purpose of file extensions is to eliminate ambiguity: to enable applications and the OS to "know" which files they can use, and how.

whim

@JoeMarfice

Somehow, i still have the impression you missed the point ... the only available choices available for raw (or anything
that needs to able to be transferred over USB) are .JPG, .CRW, .CR2, THM, WAV (see link in #591)
And the same argument of possible confusion can be made for all of them, so what choice would you favour / have
favoured ?

wim

PS that reminds me i still forgot to sue M$ for stealing my name as an extension 😉

hasitha

Guys is there a way to use 8gb card with CHDk for sx10 ?

fe50

Hello & welcome, hasitha !

hasitha
Guys is there a way to use 8gb card with CHDk for sx10 ?

Yes - it's the same as on the most/all the other cameras with SDHC support...

* https://chdk.setepontos.com/d/2468/126 (general info)
* https://chdk.setepontos.com/d/2468/450 (in the camera)
* https://chdk.setepontos.com/d/3910/7 (with SDM installer)

lienso

Hi,

I am trying to fix a particular bug in SX20IS port - the main CHDK menu does not go away. It seems that the problem is in the address of RefreshPhysicalScreen and/or enabled_refresh_physical_screen (the second is, obviously, easy if you know the first.) I have dumps of SX10 ans SX20 and trying to look for similar calls between those (SX10 is presumably working fine). No luck so far.

Can anybody give a tip how the RefreshPhysicalScreen can be located, e.g. how was it achieved in SX10?

Regards in advance.

lehoangtn

I switch my camera on in display mode, and press FUNC./SET + DISP (third)= I see these things:

Canon PowerShot SX10 IS
P-ID: 318D PAL D

#Page1
Firmware Ver: GM1.01B
E18
Nov 13 2008 09:03:39

#page2
Adj Ver.019.013
UsmSweepFregError
2010.07.16 11:05:35

#page3
Adj Ver.019.013
Total shoot: 14081
Zoom Retry count: 65
Mecha Condition: x00010000

I can't CHDK for my camera. Although, I do its step by step on userguide. Could you help me to fixed this problem, please.

reyalp

lehoangtn
I can't CHDK for my camera. Although, I do its step by step on userguide. Could you help me to fixed this problem, please.

You need to be more specific. Saying you "do its step by step on userguide" doesn't help. The SX10 port works, so you've done something wrong. If you want help finding what you did wrong, you need to explain clearly which steps you did and what the results were.

vtysh

I have an issue. I am using chdk for firmware version 1.00c.

Sometimes when i turn on the camera directly to the shooting mode the lens become move forward as usual and i see "canon" typed on display. The canon screen may be shown for around 15-20 seconds and then camera turns off itself without moving lens back. Or it may hang so i need to move out batteries and put again.

But if i turn on the camera in picture viewing mode first and then switch to shooting mode i didn't notice this issue.

I suppose that it may be e18 error issue also and there are not enough power to turn on camera in shooting mode.

Can anybody clear my doubts? Is it camera issue or chdk issue?

Upd:
Just got the same behaviour in viewing mode. I turned on the camera in viewing mode and it hangs on canon screen. Then screen switched off automatically and camera doesn't react on any button until i remove batteries and put again. So e18 error shouldn't be the reason in this case. Can anybody help?

« Previous Page Next Page »