Developer-friendly / experimental branch (dataghost)

philmoz

arne182

So is there a way to force the flash to fire anyway in auto mode? In the other modes you can use the canon options to force flash but in auto that feature is not available. That is why it is important that it works on Auto mode.

Yes, it's called P mode 😀
AUTO means simply that, the camera makes all the decisions for you.
If you want to take control of the camera you have to switch to P or one of the creative modes.

CHDK menues yes, I am using 1386 from the autobuild could get 1388. I assume you don't have a Eyefi card. The wifi symbol is a constantly changing one and until it is finished uploading the photos the icon is constantly changing and on some occation it takes some or all of the menu with it. I have taken some pictures for you to see what I mean. It is especially bad when you are in the games option.

That's normal. CHDK is not integrated into the Canon OSD so there's only so much that can be done. If the Canon OSD erases part of the screen CHDK has no easy way to know about it.
There is code to detect a full screen erase and redraw the menus; but this is not active for games.
It might be possible to implement a screen redraw function for each game and have the system call this if it detects a full screen erase; but it won't help if only part of the screen is erased.

Phil.

arne182

I understand the point of P mode, and the point of Auto mode. It is just nice to be able to control the flash anyway in auto mode, because that is why I assume it has been coded into the CHDK, for that exact perpose. In P mode I don't need CHDK to control the flash, I can do that with Canon's options.

I wonder if there is a way to detect that the wifi logo is moving.

Would it be advisable to redraw the menu after a certain amount of time, say every second or minute? To make sure that it is on top.

arne182

I have now moved on to checking manual focus on the G12. I have not been able to get it to focus for me. Not in auto scene P or M mode.

Method,
1. Load up build 0.99 revision 1390
2. Set camera mode to P.
3. Set manual focus to some extremely close
4. Use CHDK to force focus at infinity http://chdk.wikia.com/wiki/CHDK_firmware_usage/AllBest#Quick-Set_Hyperfocal_.26_Infinite_Manual_Focus_Distances
5. Take picture using ultra intervalometer

If I am not mistaken the focus does get re-evaluated by the camera and then is used to take the picture ignoring the overide value. Can you confirm this.

philmoz

The camera has to be in manual focus mode for the focus to remain locked.
If you set the camera back to autofocus, or the script unlocks the AF mechanism, then the camera will refocus on each shot.

If the Canon manual focus bar is not displayed when the script is running then AF has been re-enabled.

Phil.

arne182

philmoz
The camera has to be in manual focus mode for the focus to remain locked.
If you set the camera back to autofocus, or the script unlocks the AF mechanism, then the camera will refocus on each shot.

If the Canon manual focus bar is not displayed when the script is running then AF has been re-enabled.

Phil.

Will try and do some Bracketing to see if I can control the focusing distance with P mode. Have you used the Subject Distance Bracketing before?

philmoz

I haven't used it a lot; but from memory it worked when I tested it.
The main limitation is that the G12 has discrete positions of the focus motor - it is not a continuous focus system.
See https://chdk.setepontos.com/d/6570/10 where I posted a graph of the requested versus actual focus distance graph (created using set_focus and get_focus in a script).
You have to be careful that your bracketing distance is large enough to actually select different focus points in the camera.

Phil.

arne182

philmoz
I haven't used it a lot; but from memory it worked when I tested it.
The main limitation is that the G12 has discrete positions of the focus motor - it is not a continuous focus system.
See https://chdk.setepontos.com/d/6570/10 where I posted a graph of the requested versus actual focus distance graph (created using set_focus and get_focus in a script).
You have to be careful that your bracketing distance is large enough to actually select different focus points in the camera.

Phil.

The graphic looks great. Do you still have the actual numbers that was used to plot the graph? Thanks for the information. So you could only do about 80 different distances, sounds like a good script to make sure these are fixed for the G12.

The Infinity focus worked very well on P mode, here is a timelapse that I did yesterday.
01/11/2011 Berlin Stars

philmoz

I don't have the numbers but the script I used is below. This is Lua code so save it with a .lua extension in the scripts directory.
The range of values to set_focus is from 0 - 65535 which will take a long time to run depending on the amount you increment each time (set to 10 below).
You can run it multiple times with different increments and start values to map out the focus distances.

--[[
Write actual versus requested focus distances
Results are written to LOGS/LOG_0001.TXT
--]]

print_screen(1)
f = 0
repeat
	set_focus(f)
	sleep(100)
	print(string.format("%d %d",f,get_focus()))
	f = f + 10
until f >= 65535

Phil.

arne182

philmoz
I don't have the numbers but the script I used is below. This is Lua code so save it with a .lua extension in the scripts directory.
The range of values to set_focus is from 0 - 65535 which will take a long time to run depending on the amount you increment each time (set to 10 below).
You can run it multiple times with different increments and start values to map out the focus distances.

[code]
--[[
Write actual versus requested focus distances
Results are written to LOGS/LOG_0001.TXT
--]]

print_screen(1)
f = 0
repeat
set_focus(f)
sleep(100)
print(string.format("%d %d",f,get_focus()))
f = f + 10
until f >= 65535
[/code]

Phil.

Maybe I am doing something wrong here but lets see if I can give you my approach.

1. Load CHDK
2. Change to P mode
3. Set Manual focus
4. Enter script
5. Execute

At the end the focus never changes. Could you check this and tell me if I did anything wrong?

philmoz

arne182
Maybe I am doing something wrong here but lets see if I can give you my approach.

1. Load CHDK
2. Change to P mode
3. Set Manual focus
4. Enter script
5. Execute

At the end the focus never changes. Could you check this and tell me if I did anything wrong?

I re-tried it on my G12 and it works fine.
Does it print lines of two numbers of the screen? Do both numbers change?

Phil.

arne182

philmoz

arne182
Maybe I am doing something wrong here but lets see if I can give you my approach.

1. Load CHDK
2. Change to P mode
3. Set Manual focus
4. Enter script
5. Execute

At the end the focus never changes. Could you check this and tell me if I did anything wrong?

I re-tried it on my G12 and it works fine.
Does it print lines of two numbers of the screen? Do both numbers change?

Phil.

Yes 2 numbers. Only first one changes. Second one is the value of where the maunal focus was set last.
Are there any other CHDK main menu features that need to be set like over ride on or off?
Is your firmware 1.00g?

philmoz

arne182

Yes 2 numbers. Only first one changes. Second one is the value of where the maunal focus was set last.
Are there any other CHDK main menu features that need to be set like over ride on or off?
Is your firmware 1.00g?

Did you leave the camera in manual focus mode when running the script? The Canon manual focus bar should still on screen.
AFAIK the other CHDK settings should not affect the script.
My camera has 1.00c firmware.

Phil.

arne182

philmoz

arne182

Yes 2 numbers. Only first one changes. Second one is the value of where the maunal focus was set last.
Are there any other CHDK main menu features that need to be set like over ride on or off?
Is your firmware 1.00g?

Did you leave the camera in manual focus mode when running the script? The Canon manual focus bar should still on screen.
AFAIK the other CHDK settings should not affect the script.
My camera has 1.00c firmware.

Phil.

Manual focus bar stays on the the screen. But doesn't move. I can move it by turning the jog dial while the script is running and the second values do then change. Might there be a problem in the 1.00g firmware where the setfocus command is not working? Could I debug this? I finally got the development environment set up and am able to compile CHDK, I just need to be guided in the right direction.

philmoz

arne182
Manual focus bar stays on the the screen. But doesn't move. I can move it by turning the jog dial while the script is running and the second values do then change. Might there be a problem in the 1.00g firmware where the setfocus command is not working? Could I debug this? I finally got the development environment set up and am able to compile CHDK, I just need to be guided in the right direction.

Well there's definitely something different - if I turn the jogdial while that script is running the camera crashes (not suprising since two things are trying to set the focus at the same time).

One thing, check the Canon settings.
I use:
AF Frame = FlexiZone
AF-Point Zoom = Off
Servo AF = Off
Continuous AF = Off
AF-Assist Beam = Off
MF-Point Zoom = Off
Safety MF = Off

Perhaps one of these settings is different.

If that still doesn't work then we'll have to dig into the code to see what's going on.

Phil.

Edit: Did a quick test and 'Continuous AF' may be the culprit. If I enable this I get the same behviour as you.

arne182

philmoz

arne182
Manual focus bar stays on the the screen. But doesn't move. I can move it by turning the jog dial while the script is running and the second values do then change. Might there be a problem in the 1.00g firmware where the setfocus command is not working? Could I debug this? I finally got the development environment set up and am able to compile CHDK, I just need to be guided in the right direction.

Well there's definitely something different - if I turn the jogdial while that script is running the camera crashes (not suprising since two things are trying to set the focus at the same time).

One thing, check the Canon settings.
I use:
AF Frame = FlexiZone
AF-Point Zoom = Off
Servo AF = Off
Continuous AF = Off
AF-Assist Beam = Off
MF-Point Zoom = Off
Safety MF = Off

Perhaps one of these settings is different.

If that still doesn't work then we'll have to dig into the code to see what's going on.

Phil.

Edit: Did a quick test and 'Continuous AF' may be the culprit. If I enable this I get the same behviour as you.

Definitively the Continous AF was causing it no to focus manually.
The focus values are here http://pastebin.com/Rum6cXsw
I have already tried my hand at scripting
http://chdk.wikia.com/wiki/UBASIC/Scripts:_Focus_Bracketing_with_set_focus_and_get_focus

I was working on one that particularly works for the G12, but the one that I posted will always work. I wonder if I can add some user interactivity into my script. 😎
I have attached my first DOF stack photo.

Here is part of the G12 specific code making a few checks on the properties before trying something that won't work

rem ------- camera specific section / omit if you are not using G12 -------
y=0
get_prop 133 x
if x=1 then y=y+1 else print "Not in MF mode"
get_prop 12 x
if x=0 then y=y+1 else print "Continuous AF is on!"
get_prop 277 x
if x=0 then y=y+1 else print "Safety MF is on!"
if y=3 then goto "continue"
 end
rem ------- camera specific section / omit if you are not using G12 -------

:continue

mr.burns

Hi Dataghost,

on the first page of this page I read following:

- IS Lens adjustments. On my S5IS, the lens is offset a bit and after quite some research I came up with a way to properly center it. The camera has a built-in 'center IS lens' function, but that centers the IS lens at the IS lens center point, which is not the camera lens center point (or so it seems). It's possible to manually adjust the IS lens (implemented) and to automatically center it (not implemented in this branch yet).

Do you think this will work also on my Powershot S110? I don't know if the S110 has a built in 'center IS lens' function - is it normally avaliable in the tools menu?

Thanks for any information.

waterwingz

mr.burns
Hi Dataghost, ...

fyi : a quick look at dataghost's profile suggests that he/she has not connected to this forum in over 3.5 years.

Microfunguy

mr.burnsI don't know if the S110 has a built in 'center IS lens' function

Well, the S100 has ISAutoCenter.

reyalp

mr.burns
Do you think this will work also on my Powershot S110? I don't know if the S110 has a built in 'center IS lens' function - is it normally avaliable in the tools menu?

FWIW, many of the IS related functions are available as eventprocs: http://chdk.wikia.com/wiki/Event_Procedure so much of the stuff discussed in earlier in this thread can now be done from Lua.

Since these may directly control hardware, caution is advised.

srsa_4c

@mr.burns
In case it wasn't mentioned before, you can find most event procedure names (and addresses) in the funcs_by_address.csv and funcs_by_name.csv files for a camera, look for names ending with '_FW'. Remove the _FW ending if you'd lke to use them from Lua.

« Previous Page Next Page »