CHDK Forum

Using CHDK => Obsolete (Other Builds) => CHDK Releases => AllBest's Builds => Topic started by: Allbest on 28 / March / 2008, 19:02:02

Title: Build 49 (hot fix for build 48)
Post by: Allbest on 28 / March / 2008, 19:02:02
hot fix for build 48:
+Fixed error in Custom AutoIso mode
+Now "Custom AutoIso" is accessible in any flash mode except auto flash mode
+Menu entry "IS Factor (Tv*factor)" was excluded for cameras without IS
Please reload version Build 48 (http://chdk.setepontos.com/index.php/topic,871.0.html)
Thanks
Title: Re: Build 49 (hot fix for build 48)
Post by: dzsemx on 28 / March / 2008, 20:45:59
thank you for bug fixes
autoiso stopped crashing :) tomorrow i'll try it more...
i'm sad that this feature can't be used in autoflash mode:(
Title: Re: Build 49 (hot fix for build 48)
Post by: akaloith on 29 / March / 2008, 10:16:21
hi i have a problem
at minumum asa at autoiso what is the minimum possible for canon s3 (50 or 80 or less)?
this is real iso or marketing?
what is the minimum,maximum real iso of canon s3 and what is the minimum,maximum marketing iso of canon s3
its very confusing to use for example 50 iso and see at the exif 77iso

Can it all use marketing iso instead of some have real iso and other have marketing?

Title: Re: Build 49 (hot fix for build 48)
Post by: g2mk on 29 / March / 2008, 17:30:58
May I ask for language file?

Thank you all for you work with CHDK.
Title: Re: Build 49 (hot fix for build 48)
Post by: PhyrePhoX on 29 / March / 2008, 18:07:36
May I ask for language file?

Thank you all for you work with CHDK.

https://tools.assembla.com/chdk/browser/trunk/lang/english.lng
Title: Re: Build 49 (hot fix for build 48)
Post by: Allbest on 29 / March / 2008, 20:19:58
at minumum asa at autoiso what is the minimum possible for canon s3 (50 or 80 or less)?
I think that minimum is around 50. May be slightly lower
Quote
this is real iso or marketing?
It is real ISO. Please see Build 48 (http://chdk.setepontos.com/index.php/topic,871.0.html)
Quote
what is the minimum,maximum real iso of canon s3 and what is the minimum,maximum marketing iso of canon s3
Anybody did deep testing of ISO for s3? May be Barney Fife SD1000 ISO Settings Error (http://chdk.setepontos.com/index.php/topic,613.msg6566.html#msg6566) ? You can do it personaly SD1000 ISO Settings Error (http://chdk.setepontos.com/index.php/topic,613.msg5816.html#msg5816)
SD1000 ISO Settings Error (http://chdk.setepontos.com/index.php/topic,613.msg6593.html#msg6593)
Quote
its very confusing to use for example 50 iso and see at the exif 77iso
I'm agree but Canon engineers (or marketologs) for some reason have include ISO of two types in their calculations
You can see corresponding "market" ISO in misc. values at haf press
Quote
Can it all use marketing iso instead of some have real iso and other have marketing?
There are some difficulties but we will try to do it


Title: Re: Build 49 (hot fix for build 48)
Post by: yunxiang on 30 / March / 2008, 01:55:25
when i taking the viedo, the zoom can work, but can not autofocus in video mode during taking video
hope the new verson can do it.
Title: Re: Build 49 (hot fix for build 48)
Post by: mkmenuts on 30 / March / 2008, 03:58:02
This is probably just me, but I can't get user menu to work on my SD700...

I change it to Edit mode, and try to use half-press to add menu items, but nothing happens (even after I turn user menu "On").

Could someone clue me in?

mkmenuts
Title: Re: Build 49 (hot fix for build 48)
Post by: Der Wichtel on 30 / March / 2008, 04:55:01
This is probably just me, but I can't get user menu to work on my SD700...

I change it to Edit mode, and try to use half-press to add menu items, but nothing happens (even after I turn user menu "On").

Could someone clue me in?

mkmenuts

Same here on my SD700
Title: Re: Build 49 (hot fix for build 48)
Post by: kamil on 30 / March / 2008, 04:58:16
Quote
when i taking the viedo, the zoom can work, but can not autofocus
I think it's impossible because of processor limits. When processor work with video compression he cant make af. BTW script are working so maybe it's possible to make independent slower af improvement into chdk and use it in video?

Good improvement in video mode will be possibility of changing ev correction during recording. Any control of ev will be great because main object is going black when you have some unimportant (sky for example) behind object. So lock/unlock auto ev correction during recording will be great.

any way thank guys. Customizable menu is great. Of curse it will be marvellous if we could make folders, script links, and standard menu links, but not all at now :)
Title: Re: Build 49 (hot fix for build 48)
Post by: pitquim on 30 / March / 2008, 05:36:02
I change it to Edit mode, and try to use half-press to add menu items...

try with "rubbish" button instead... it works on my A630
Title: Re: Build 49 (hot fix for build 48)
Post by: yunxiang on 30 / March / 2008, 10:07:47
every zoom, autofocus
is it possible
Title: Re: Build 49 (hot fix for build 48)
Post by: docvladi on 30 / March / 2008, 12:34:36
Title: Re: Build 49 (hot fix for build 48)
Post by: GrAnd on 30 / March / 2008, 13:16:08
I am using a Canon A650IS at the widest and tele settings but the values shown are 44mm and 266 (EFL).
That's due to incorrect CF_EFL coefficient coded in CHDK. It should be
#define CF_EFL 47297
for A650.

BTW. This coefficient need to be doublechecked for all cameras. Many of them has the same value.
Code: [Select]
a460/main.c:#define CF_EFL 70371
a530/main.c:#define CF_EFL 60345
a540/main.c:#define CF_EFL 60345
a550/main.c:#define CF_EFL 60345
a560/main.c:#define CF_EFL 60345
a570/main.c:#define CF_EFL 60345
a610/main.c:#define CF_EFL 47946
a620/main.c:#define CF_EFL 47946
a630/main.c:#define CF_EFL 47946
a640/main.c:#define CF_EFL 47946
a650/main.c:#define CF_EFL 47297
a700/main.c:#define CF_EFL 60345
a710/main.c:#define CF_EFL 60345
a720/main.c:#define CF_EFL 60345
g7/main.c:#define CF_EFL 47946
ixus55_sd450/main.c:#define CF_EFL 60345
ixus65_sd630/main.c:#define CF_EFL 47946
ixus700_sd500/main.c:#define CF_EFL 47946
ixus70_sd1000/main.c:#define CF_EFL 60345 // for 1/2,5" sensor (60345) for 1/1,8" sensor (47946)
ixus800_sd700/main.c:#define CF_EFL 60345
ixus850_sd800/main.c:#define CF_EFL 60345 // for 1/2,5" sensor (60345) for 1/1,8" sensor (47946)
ixus860_sd870/main.c:#define CF_EFL 60869
ixus950_sd850/main.c:#define CF_EFL 60345 // 60345 for 1/2.5" sensor, 47946 for 1/1.8" sensor
s2is/main.c:#define CF_EFL 6000
s3is/main.c:#define CF_EFL 6000

Title: Re: Build 49 (hot fix for build 48)
Post by: madp on 31 / March / 2008, 19:00:48
Hi All,

First of all big thanks for this marvellous piece of code!!!

Secondly I would like to report a bug:

Camera: Powershot S2 IS
Firmware 1.00E
Build: Allbest #49, Mar 29 2008 (and older too)

[-] Miscellaneous values are not updating (I can get an update in <Alt> mode with half-press)
with 'Show misc values' [Always]
[-] Miscellaneous values are not displayed at all
with 'Show misc values' [Shoot]

And thirdly I've got small feature request:

Maybe it would be possible to have 4 states for all OSD elements ? Like this:
- Always On
- Always Off
- Normal (disappears when half-press & shoot)
- Shoot  (displayed only when half-press)

There are a lot of OSD elements right now, all of them are useful and it is difficult to fit everything on one screen. Having those 4 states it would be possible to have a subset of OSD elements visible only in 'normal' view and other subset of OSD elements only visible during 'half-press'. Now it is not possible with all elements.

And maybe it would be more convenient to move 'Show live histogram' to 'OSD parameters' submenu. This way all OSD elements could be turned on/off from one submenu.



Thanks again,
madp
Title: Re: Build 49 (hot fix for build 48)
Post by: Allbest on 01 / April / 2008, 04:11:08
Quote
[-] Miscellaneous values are not updating (I can get an update in <Alt> mode with half-press)
with 'Show misc values' [Always]
When you set this parameter in such state you see values that corresponds you previous shoot (or as a consequence of half press). You can renew this values by half press (or if your camera in MF mode than by distance changing).
Quote
[-] Miscellaneous values are not displayed at all
with 'Show misc values' [Shoot]
You need half press shutter release button to see this values
Title: Re: Build 49 (hot fix for build 48)
Post by: docvladi on 01 / April / 2008, 08:06:55
Hi again:
A couple of days ago I wrote about wrong zoom values in a Canon A650 IS. I have just tried the latest release and now I get the following values: 29 - 177 mm (EFL).
I do not know if there is still a problem in the code or my camera has something wrong. If there is anybody out there with a Canon A650 IS that can verify if the current release has the code working properly or has the same problem like me.
Any news will be greatly appreciated
Regards
Title: Re: Build 49 (hot fix for build 48)
Post by: GrAnd on 01 / April / 2008, 08:34:57
Heh... Somebody, who did the port, slightly changed the formula which resulted in reducing the accuracy by 10000 times.
Code: [Select]
a460/main.c:    return (CF_EFL*get_focal_length(zp))/10000;
a530/main.c:    return (CF_EFL*get_focal_length(zp))/10000;
a540/main.c:    return (CF_EFL*get_focal_length(zp))/10000;
a550/main.c:    return (CF_EFL*get_focal_length(zp))/10000;
a560/main.c:    return (CF_EFL*get_focal_length(zp))/10000;
a570/main.c:    return (CF_EFL*get_focal_length(zp))/10000;
a610/main.c:    return (CF_EFL*get_focal_length(zp))/10000;
a620/main.c:    return (CF_EFL*get_focal_length(zp))/10000;
a630/main.c:    return (CF_EFL*get_focal_length(zp))/10000;
a640/main.c:    return (CF_EFL*get_focal_length(zp))/10000;
a650/main.c:    return ((int)(CF_EFL/10000))*get_focal_length(zp);    <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
a700/main.c:    return (CF_EFL*get_focal_length(zp))/10000;
a710/main.c:    return (CF_EFL*get_focal_length(zp))/10000;
a720/main.c:    return (CF_EFL*get_focal_length(zp))/10000;
g7/main.c:    return (CF_EFL*get_focal_length(zp))/10000;
ixus55_sd450/main.c:    return (CF_EFL*get_focal_length(zp))/10000;
ixus65_sd630/main.c:    return (CF_EFL*get_focal_length(zp))/10000;
ixus700_sd500/main.c:    return (CF_EFL*get_focal_length(zp))/10000;
ixus70_sd1000/main.c:    return (CF_EFL*get_focal_length(zp))/10000;
ixus800_sd700/main.c:    return (CF_EFL*get_focal_length(zp))/10000;
ixus850_sd800/main.c:    return (CF_EFL*get_focal_length(zp))/10000;
ixus860_sd870/main.c:    return (CF_EFL*get_focal_length(zp))/10000;
ixus950_sd850/main.c:    return (CF_EFL*get_focal_length(zp))/10000;
s2is/main.c:    return (CF_EFL*get_focal_length(zp))/1000;
s3is/main.c:    return (CF_EFL*get_focal_length(zp))/1000;

UPD: Ha! It was Allbest. He did this for "+Fixed: negative values of EFL for a650". But he did that in incorrect way.
Title: Re: Build 49 (hot fix for build 48)
Post by: dzsemx on 01 / April / 2008, 11:09:41
int before multiply?...
Title: Re: Build 49 (hot fix for build 48)
Post by: GrAnd on 01 / April / 2008, 11:22:34
int before multiply?...
And? This is a valid syntax. Do not forget that operations (div and mul) are integer, not floating. Without (int) the result will be the same.
Title: Re: Build 49 (hot fix for build 48)
Post by: Allbest on 01 / April / 2008, 11:58:08
GrAnd
Quote
UPD: Ha! It was Allbest. He did this for "+Fixed: negative values of EFL for a650". But he did that in incorrect way.
Sorry, It was only defence from overlow :) Not more. Thank you for correction!
Title: Re: Build 49 (hot fix for build 48)
Post by: madp on 01 / April / 2008, 12:13:20
Quote
[-] Miscellaneous values are not updating (I can get an update in <Alt> mode with half-press)
with 'Show misc values' [Always]
When you set this parameter in such state you see values that corresponds you previous shoot (or as a consequence of half press). You can renew this values by half press (or if your camera in MF mode than by distance changing).
Quote
[-] Miscellaneous values are not displayed at all
with 'Show misc values' [Shoot]
You need half press shutter release button to see this values

Thank you for an answer Allbest.

I know that it should work this way but on my S2 it doesn't :( I'm not able to get any value when half-press (or from previous shot) - that's why I'm reporting it as a bug :) I can get values only with half-press in <alt> mode.
Title: Re: Build 49 (hot fix for build 48)
Post by: dzsemx on 01 / April / 2008, 12:55:16
And? This is a valid syntax. Do not forget that operations (div and mul) are integer, not floating. Without (int) the result will be the same.
i mean (int)((CF_EFL/10000)*get_focal_length(zp)) should be the correct version
making int after multiply is processed

Title: Re: Build 49 (hot fix for build 48)
Post by: GrAnd on 01 / April / 2008, 13:22:01
And? This is a valid syntax. Do not forget that operations (div and mul) are integer, not floating. Without (int) the result will be the same.
i mean (int)((CF_EFL/10000)*get_focal_length(zp)) should be the correct version
making int after multiply is processed

That will not help. Because all operations are integer.
For example:
47297/10000*44400 = ((int)(47297/10000))*44400 = (int)(47297/10000*44400) = 177600 (that means 177.6mm)
because 47297/10000 = 4 (integer)
But
47297*44400/10000 = 209999 (that means 209.9mm)
That's the difference.
Title: Re: Build 49 (hot fix for build 48)
Post by: dzsemx on 01 / April / 2008, 13:44:08
you're right...
i didn't work in c for about a year :( so i forgot things like this :(
Title: Re: Build 49 (hot fix for build 48)
Post by: touristguy87 on 01 / April / 2008, 14:58:20
well, I made some "progress"...found out that WinXP simply refuses to format an 8GB SDHD card as fat16. Even if the format command says that is what it is doing. Won't do it. So I got out an old SD card and formatted that and put the diskboot.bin from allbest .57 on it and used the bootdisk tool and checked the mbr with a hexeditor and it looks ok...the camera a650 will not boot at all with this card in it in wp mode. It works ok in unlocked, but is dead when the card is locked.vvv thanks

Will someone please put up exactly the code and hardware that they are using and the *exact* procedures and directory-listing that they are using to get this to work with their a650?

thanks
Title: Re: Build 49 (hot fix for build 48)
Post by: Allbest on 02 / April / 2008, 16:13:55
I know that it should work this way but on my S2 it doesn't :( I'm not able to get any value when half-press (or from previous shot) - that's why I'm reporting it as a bug :) I can get values only with half-press in <alt> mode.
The behaviour of CHDK on your camera is very strange. Please try reload it on your card (before that you need to delete chdk.cfg)
Index of /hdk/autobuild/ (http://grandag.nm.ru/hdk/autobuild/)
Title: Re: Build 49 (hot fix for build 48)
Post by: madp on 03 / April / 2008, 18:11:18
The behaviour of CHDK on your camera is very strange. Please try reload it on your card (before that you need to delete chdk.cfg)
Index of /hdk/autobuild/ (http://grandag.nm.ru/hdk/autobuild/)

It worked! Thanks!
Title: Re: Build 49 (hot fix for build 48)
Post by: pyst on 03 / April / 2008, 19:27:29
I'm just new here.
I didn't download build48 (can't find it).
But I've already download "allbest-a650-100d-49.zip" , extract it.
The file I got is just diskboot.bin.
As I understood(??), there should be another file to put in the root folder of SDcard.
Where can i find "PS.FIR" like that one for a630-640.
Or may it should be "PS.FI2" to use with a650is (I read here -> A650IS - CHDK Wiki (http://chdk.wikia.com/wiki/A650IS))

thanks
Title: Re: Build 49 (hot fix for build 48)
Post by: A650ISfan on 03 / April / 2008, 19:50:42
If you are trying to get it to work in an A650, you will have to make the SD card bootable.. it is in the CHDK wiki about how to do this. You will need a card reader of course to do this. Once it the card formatted and made bootable, copy the diskboot.bin to the card, then LOCK the card with the little switch. place the card in the camera, turn it on, and CHDK will load:D  NO PS.fir file is needed.
Title: Re: Build 49 (hot fix for build 48)
Post by: pyst on 03 / April / 2008, 20:34:56
So it was my misunderstood.
> old models need 2 files
> new models (DryOS) need only 1 file
I'll try it when my friend return me my camera.

Thank you very much.


Oh..waiting for my "new" a650is. ^^
Title: Re: Build 49 (hot fix for build 48)
Post by: neilhand on 04 / April / 2008, 00:45:49
This release hangs for me when booting on a SD850 (solid blue light and no LCD activity). Has anyone else managed to test on this camera with success?

I am able to run the fingalo-allbest-ixus950_sd850-100c-42 build without problem, but really want to look into the video zoom supported by the allbest build 49.

Any help or suggestions would be greatly appreciated (i have tried multiple downloads from the two mirrors).

Title: Re: Build 49 (hot fix for build 48)
Post by: Vertigo on 04 / April / 2008, 06:06:58
hello ,

Just to report the #49 build works on the ixus850-SD800.

Great !

Some bugs anyway :

- ND filter override does not work well in continuous mode
(in strong light, if ND set to "Out", ND can go "In" after the first frame)

- Custom AutoIso does not seem to work at all (needs further testing though).

Manu