Help us get CHDK 1.4 ready for release

  • 8 Replies
  • 2840 Views
*

Offline reyalp

  • ******
  • 11266
Help us get CHDK 1.4 ready for release
« on: 15 / November / 2015, 16:08:22 »
Advertisements
CHDK 1.4 is almost ready for release. Before we officially retire 1.3, we're asking all interested users to help test. The 1.4 builds should generally be good enough for everyday use.

What's new
See http://chdk.wikia.com/wiki/Releases#1.4 for an overview of signification changes. See also the 1.4 development planning thread

Where to get it
Use stick and choose 1.4 development version, or download from Unstable section of the download page

If downloading / updating manually, be sure to download the "complete" package.

If there's anything you wouldn't want to lose on the card you are installing it on (scripts, existing CHDK install or CFG files, precious cat photos), backing up is a good idea.

Compatibility
  • Scripts are generally compatible. You will see a warning if there isn't a @chdk_version, but 1.3 compatible behavior will be used. If you use @chdk_version 1.4, the return values of some functions are changed. (see https://subversion.assembla.com/svn/chdk/trunk/CHDK/LUALIB/wrap13.lua for a list)
  • Some CHDK script mode numbers have changed, and some names have been removed. This does not affect common modes like, M, P and Auto, but might affect scripts that use more obscure modes, especially if the are referred to by number rather than capmode.lua names
  • CFG files: CHDK 1.4 uses the same CFG files as 1.3. It should generally be compatible and retain your settings, but if you don't want to risk re-doing your CFG, backing up the CHDK/*.CFG files before updating is recommended. Custom colors will be reset, and if you switch back to 1.3, colors may be incorrect. CHDK 1.2 CFGs should be migrated as was done for 1.3.
  • Modules and language files are NOT compatible. You must update these when you update your build.

Things you can do to help

Reporting bugs
Post in this thread, or in the development thread for the particular feature if it's obvious.

If the camera crashes (shuts down unexpectedly) please get a romlog as described on http://chdk.wikia.com/wiki/Debugging#Camera_crash_logs_.28romlog.29 and post it as an attachment.

edit:
If a post looks like it will lead to a lot of back and forth, I will probably split it to a new thread. This doesn't mean you did anything wrong :)
« Last Edit: 29 / November / 2015, 01:35:28 by reyalp »
Don't forget what the H stands for.

*

Offline reyalp

  • ******
  • 11266
Re: Help us get CHDK 1.4 ready for release
« Reply #1 on: 17 / November / 2015, 15:38:19 »
OK, just an update, zebra mode is working with 4293. I think I had to reboot camera after enabling it. I'll keep an eye open for this....

EDIT: No, spoke too soon, sometimes it does work and other it powers off when pressing shutter...
::)
Thanks for reporting, I split the posts to the sx510 thread, since this looks like a port specific issue that will require some discussion:  http://chdk.setepontos.com/index.php?topic=10984.msg125497#msg125497
Don't forget what the H stands for.

Re: Help us get CHDK 1.4 ready for release
« Reply #2 on: 17 / November / 2015, 15:40:15 »
Ok, Now I had a power off without lens retraction (I don't know if this means it's a crash) when I tried purging orphaned DNG's

Thanks!
---------------------------------
Never tie a ship to a single anchor
nor life to a single hope

Re: Help us get CHDK 1.4 ready for release
« Reply #3 on: 18 / November / 2015, 04:29:08 »
I updated my G1x 101a with R4291and did most test which you descript above. Everything works fine except the well-known problems.

All my other cams (S110, SX230 and SX50) have versions greater R 4203. I think, there not many differences between R4291, but I will update them as soon as possible.
 
About the CFG file: Are they compatible between my cams? So can I generate one CFG file with my default settings on G1x and copy these file to my other cams?

I want to say ‘thank you’ for all, which helped, to get CHDK 1.4 for release….



*

Offline msl

  • *****
  • 1235
  • A720 IS, SX220 HS 1.01a
    • CHDK inside
Re: Help us get CHDK 1.4 ready for release
« Reply #4 on: 18 / November / 2015, 09:26:48 »
@c_joerg:

The configuration is splitted in 4 parts: core (cchdk4.cfg), osd (osd__4.cfg), user (user__4.cfg) and gps (gps__4.cfg). In principle, the CHDK configuration is independent of the camera. The core configuration includes all basic adjustments, e.g. overrides or RAW/DNG. OSD stores colors and positions of CHDK OSD elements. User stands for the user menu and gps is for GPS cameras. Both are only available when you use this functions.

There is also a script for saving/loading of the configaration: http://chdk.setepontos.com/index.php?topic=10894.0

For the topic:

For the A720 and SX220 is all fine. The A720 is one of the first cameras with a new adjusted color palette (blue/yellow menu). Originally the camera had palette 1.

msl
German CHDK pages:  CHDK forum | CHDK inside | CHDK Twitter News by msl | Download CHDK-DE (Autobuild)
Note: SDM violates the GPL rules!

Re: Help us get CHDK 1.4 ready for release
« Reply #5 on: 23 / November / 2015, 14:03:13 »
Not sure, if this the right place to post here.
I start to play with my SX50 => sx50hs-100c-1.4.0-4293

First problem:
I run rawopint with the SX50. Normally I stop the script by pressing the Menu bottom. On all my other cams this works without any problems. On the SX50 I notice the following:
1) After pressing the Menu bottom, the cam shows no reaction for about 10-15s.
2) The cam makes on more picture.
3) Than another 10-15s without reaction after the script finished.
This only happens in continues mode. On Quick mode it works fine.

Second problem:
I got a negative value from dof_value.hyp_dist on full Focal Length.

Script:

Code: [Select]
print_screen(get_day_seconds()/10)
print("akt. Zeit:",os.date("%X"))
sleep(2000)                               
print("Shoot with AutoFocus")             
shoot()               
print("Auto Focus   = ",get_focus())
dof_value    = get_dofinfo()
print("DOF Focus    = ",dof_value.focus)
print("Near         = ",dof_value.near)
print("Far          = ",dof_value.far)
print("Hyp Dist     = ",dof_value.hyp_dist)
print("Aperture     = ",dof_value.aperture)
print("Focal Length = ",dof_value.eff_focal_length)

 
Result:

akt. Zeit: 20:27:08
Shoot with AutoFocus
Auto Focus   =  9090770
DOF Focus    =  9090770
Near         =  -1
Far          =  11854583
Hyp Dist     =  -2147483
Aperture     =  3564
Focal Length =  1200000

Smaller Focal Length are OK

akt. Zeit: 17:59:04
Shoot with AutoFocus
Auto Focus   =  216313
DOF Focus    =  216313
Near         =  187402
Far          =  255770
Hyp Dist     =  1401304
Aperture     =  3564
Focal Length =  881938
« Last Edit: 23 / November / 2015, 14:20:00 by c_joerg »

*

Offline msl

  • *****
  • 1235
  • A720 IS, SX220 HS 1.01a
    • CHDK inside
Re: Help us get CHDK 1.4 ready for release
« Reply #6 on: 23 / November / 2015, 14:36:27 »
Aperture     =  3564
Focal Length =  1200000

One of this values is wrong. You can calculate the hyperfocal distance by yourself: (fl*fl)/(F*coc)+fl

With a focal length of 1,200,000 your minimal aperture is 6.5! What says the CHDK OSD DOF calculator? (Use an option with +.) The calculation for the hyperfocal distance in the CHDK source code is not as accurate, but usable.

msl
German CHDK pages:  CHDK forum | CHDK inside | CHDK Twitter News by msl | Download CHDK-DE (Autobuild)
Note: SDM violates the GPL rules!

Re: Help us get CHDK 1.4 ready for release
« Reply #7 on: 23 / November / 2015, 15:18:35 »
Hello msl,

Quote
One of this values is wrong.

Yes, the aperture is wrong!

Quote
What says the CHDK OSD DOF calculator?

1384m, but after I switched the CHDK OSD DOF calculator on,
 the script works fine with the correct aperture

Joerg
« Last Edit: 23 / November / 2015, 15:20:23 by c_joerg »


*

Offline reyalp

  • ******
  • 11266
Re: Help us get CHDK 1.4 ready for release
« Reply #8 on: 25 / November / 2015, 15:34:09 »
rawopint discussion moved to the development thread: http://chdk.setepontos.com/index.php?topic=11081.msg125678#msg125678
Don't forget what the H stands for.

 

Related Topics