the sx20 porting thread

fe50

Microfunguy
(you always get those warnings, EWAVR once asked how do you get rid of them).

You won't get those clock skew warnings with a correct working dev environment & the default settings / options 😉

f_m_b

@SkyWalker9
Thank you for elaborating the idea with two 4GB partitions in your tutorial. 😀

@fe50
Thank you for your explanation. I begin to understand...

There are two repositories:
- chdk "https://tools.assembla.com/svn/chdk/trunk" with head revision 905
- chdkde "https://tools.assembla.com/svn/chdkde/trunk" with head revision 345 (de for german version)

The version from acid2000 is in the chdk repository, which i use.

What differences are beetween the two repositories? Only the language?
Are there code-merges beetween the two versions?

I tried with a new folder using CHDK-Shell 2.70 and although with another new folder using CHDK-Shell 2.71.
The problem (only warning) insists.

@Microfunguy:
You are right. There are only warnings and the bin files are "zipped" in the bin folder.

The creation date of the bin file is 2 days in the future (24.06.2010), but works fine in the sx20.
Time settings of my windows xp system are GMT +1hour +daylight saving.

I think i can "play" with this. 😁

To warm up with the sources i'am looking to find a solution for swaping more then 2 partitions...
... and I am sure, sooner or later i will need some aid. 😀

fe50

f_m_b
There are two repositories:
- chdk "https://tools.assembla.com/svn/chdk/trunk" with head revision 905
- chdkde "https://tools.assembla.com/svn/chdkde/trunk" with head revision 345 (de for german version)

Correct.

What differences are beetween the two repositories? Only the language?
Are there code-merges beetween the two versions?

The german DE version has some additions, modifications and enhancements, e.g. additional scripting commands, multicolor battery OSD, updated DOF calculator & a lot more; the DE autobuild server delivers packages with additional sample scripts and some other stuff discussed in the german forum.

Almost all changes from the international version are adapted & added to the DE version.
Most code changes or new features from the german forum will additionally be published here in the forum or in the CHDK Bug Tracker, some of them also get into the "official" (international) CHDK after some time (e.g. the customizable script console, http://chdk.wikia.com/wiki/CHDK_firmware_usage/MoreBest#set_console_layout )

For german users there's also the german wikia portal, a doxygen site, an advanced version of the german CHDK user manual in PDF format (also as JPG for in-camera use) for downloading, a german web site with more informations, samples & details in german language...

radusx

hello,

is there a way to add the seconds, in the time stamp that the camera puts directly on the photo ? and maybe some text, so that you don't have to edit on the computer later ?

tks

Coaster

f_m_b posted a description of the failure of CHDK to follow the Canon "continuous" number setting in saving images. I have the same issue.

I find CHDK quite intriguing and I'm exploring many of the options. I've been watching the progress made on the SX20 version since before posting #1 of this thread. I salute the great efforts made by neszt and acid2000 to port CHDK to the SX20. Thank you both and all the others who have lent help.

I do hope that the numbering issue can be fixed. I am finding the repeated restarting of numbering to be a problem when dealing with the images. Files easily get overwritten and file names must be revised if images with the same number are to be used on web pages and in various database programs. After looking at a thread on this problem with another camera model, it might help to say that my camera is indeed set for continuous numbering. When I put in a memory card without CHDK installed, it reverts back to the normal numbering. It is CHDK, not my camera.

Has anyone found a suitable workaround?

Don

SkyWalker9

@radusx

is there a way to add the seconds, in the time stamp that the camera puts directly on the photo ? and maybe some text, so that you don't have to edit on the computer later ?

I haven't seen the capability within CHDK to do the renaming you mentioned. Not to long ago I tested a Windows app that appears to be able to do what you want - Batch Rename Pro & free versions (http://foryoursoft.com/). Here is a link to the apps online help that explains the renaming capabilities: http://www.foryoursoft.com/batchrename/brhelp.htm

@Coaster

I do hope that the numbering issue can be fixed. I am finding the repeated restarting of numbering to be a problem when dealing with the images. Files easily get overwritten and file names must be revised if images with the same number are to be used on web pages and in various database programs. After looking at a thread on this problem with another camera model, it might help to say that my camera is indeed set for continuous numbering. When I put in a memory card without CHDK installed, it reverts back to the normal numbering. It is CHDK, not my camera.

I haven't experienced this problem yet, but I suspect that it's because I may not have tried the same sequence of events you used when you experienced the problem. If you could remember briefly what you were doing just before the numbering problem happened or happens I'll be glad to test and see if I can replicate the same problem to verify how and when it happens. If we can discover exactly how and when it happens it will help the folks who do the coding to find & fix the problem.

radusx

SkyWalker9 tks for answer, maybe i didn't explain very well (for renaming i use acdsee works ok) ,

I have seen on some other version of chdk the option that the camera adds directly on the image some text, in our case the sx20 can add a date stamp, but not the second, it would be nice to be able to put the text on the image (event name, location, your name, exif info, time with seconds, etc) even if it can be done on the computer later, a watermark , like this soft does http://www.batchphoto.com/howto/add-date/add-date.html , or http://picmarkr.com/

R

mx3

friend of mine has sx20 1.02b
I checked following builds:
sx20-102b-0.9.9-902-full_BETA_without_games.zip
sx20-102b-1.1.0-DE-full_BETA_rev_345.zip

it starts in play mode.
alt menu accessible.

problem encountered in both builds: when switching to record mode camera seems to power off (power led is off).

Coaster

@SkyWalker9

I haven't experienced this problem yet, but I suspect that it's because I may not have tried the same sequence of events you used when you experienced the problem. If you could remember briefly what you were doing just before the numbering problem happened or happens I'll be glad to test and see if I can replicate the same problem to verify how and when it happens. If we can discover exactly how and when it happens it will help the folks who do the coding to find & fix the problem.

Thanks for the reply. Wow. Just knowing that others are not experiencing this effect is a major step forward that will get me experimenting to figure out how to get things straightened out.

As best as I can recreate events they are:

1. Formatted 4GB SDHC card as FAT16.
2. Made it bootable using Linux & hexedit as described in the installation methods page.
(I just checked and confirmed "BOOTDISK" text starting at hex 40 in the only partition of that SDHC card.)
3. Installed CHDK downloaded from acid2000's bitbucket repo:
sx20-102b-0.9.9-885-full.zip
4. Played with it until I decided it was time to RTFM 😀 (With that amount of "free play" it is possible that I did something "unusual" that triggered something strange.
5. Noticed that the SX20-102b had been added to the autobuilder, downloaded and installed it.
that version, sx20-102b-0.9.9-902-full_BETA_without_games. is the current install in my SX20.

6. Since that time, I have noticed that the SX20-102b has been removed from the autobuilder. I found some comment on it that I have since lost but it didn't seem as if it invalidated the 902 build.

So, is the 902 build from the autobuilder suspect? Is the transition from the 885 build to the 902 build some kind of problem? I can think of lots of simple things to try for getting things straightened out. For instance, I can nuke the DCIM folder and let the SX20 set it up again. I can remove CHDK and reload the 885 version. I can wait (so as not to destroy any of the "forensic evidence") for suggestions of more logical steps to try to figure out the actual source of the issue.

Thanks for any suggestions.

Don

kellyrx8

havent been on in a while...but im assuming 1.02c is still on hold right now?

if I can be of any assistance in getting it going im all game!

tsdillon

Coaster
f_m_b posted a description of the failure of CHDK to follow the Canon "continuous" number setting in saving images. I have the same issue.

I find CHDK quite intriguing and I'm exploring many of the options. I've been watching the progress made on the SX20 version since before posting #1 of this thread. I salute the great efforts made by neszt and acid2000 to port CHDK to the SX20. Thank you both and all the others who have lent help.

I do hope that the numbering issue can be fixed. I am finding the repeated restarting of numbering to be a problem when dealing with the images. Files easily get overwritten and file names must be revised if images with the same number are to be used on web pages and in various database programs. After looking at a thread on this problem with another camera model, it might help to say that my camera is indeed set for continuous numbering. When I put in a memory card without CHDK installed, it reverts back to the normal numbering. It is CHDK, not my camera.

Has anyone found a suitable workaround?

Don

I have the same problem - camera set to "Folder monthly" and numbering "Continous".
I think the problem in my case is the fact that the camera creates a new folder everytime it is turned on and subsequently restarts the file numbering. Out the other day with the camera on and off all day.....at the end of the day I had 15 new folders of JPG's + 15 Raw file folders. Camera set to save JPG's in raw folder which it did not. I have not found a way round this apart from not loading CHDK (mem card unlocked).
Would love a solution to this.

Terry

Coaster

@SkyWalker9
@tsdillon

Between us we have two SX20's that open a new folder whenever the camera is turned on and one SX20 that does continuous numbering normally. It would help us to rule in or out some hypotheses if you two would let us know which version of CHDK you're using.

Don

SkyWalker9

Coaster
Between us we have two SX20's that open a new folder whenever the camera is turned on and one SX20 that does continuous numbering normally. It would help us to rule in or out some hypotheses if you two would let us know which version of CHDK you're using.

Rather then just list the CHDK version, I thought the following compilation of things that describe how I setup and use my camera in one post might help - most are excerpts from previous posts.

I've only been using @ACID2000's downloads, the last on May 16, 2010 (sx20-102b-0.9.9-885-full.zip) located here: http://chdk.wikia.com/index.php?title=Special:Outbound&f=SX20&u=http%3A%2F%2Fbitbucket.org%2Facid2000%2Fchdk_sx20%2Fdownloads

I setup and installed CHDK according to the directions in a tutorial I created: http://rapidshare.com/files/400436852/Installing_CHDK_on_SD_Cards__Windows_OS_.pdf

Since the post by f_m_b on 17 / June / 2010, 23:42:11 (https://chdk.setepontos.com/d/4348/694) I've been using only the dual 4G partitions for all of my photos. I have used (and carry) all of the SD card configurations mentioned in the tutorial but I haven't experienced any numbering problems yet.

I carry the following in my SD card carrier (yea, I know "overkill" but there was a sale on 8G SDHC cards...):
non-CHDK
(1) 8G SDHC card formatted FAT32
CHDK setups
(2) dual 4G bootable FAT16 partitioned SDHC cards (8G SDHC cards)
(1) dual partitoned 2/6G SDHC card
(1) 4G SDHC card

I have my camera set to "Folder monthly" and numbering "Continous". I normally only have the three folders under the DCIM: the 100CANON (DNGs), 109_06 (JPGs for that month), and the CANONMSC. The only time I got more than one monthly folder was when the month changed, but even then I had only one folder for each of the months.

I've been shooting a lot of DNGs lately (rather than CRWs, etc.) and for them I created my badpixel.bin file using the CHDK menu and ran the badpixel.lua script. I created a small tutorial describing how to create the file that might be of help: http://rapidshare.com/files/390852020/DNG_or_RAW.pdf

Not to long ago I was asked if I could post the DNG/RAW setting I use: http://rapidshare.com/files/397866398/Raw_settings_I_used_from_2010_Prelude_to_the_Dream_race.JPG

While I may change several settings for a photo (I use M and Av a lot), I typically change only one setting when switching between RAW/DNG and Canon Fine settings and that is to disable/enable RAW and leave the rest of the RAW Menu settings alone.

Coaster

@SkyWalker9

OK, I haven't exhausted the possibilities but have found several things. First, I'll lend a little more detail about how I installed.

1. Formatted 4GB SDHC card as one partion, FAT16 format, under Linux using gparted.
2. Used hexedit to put the string "BOOTDISK" at hex 40 in the partition.
3. Unzipped the chdk zip.
4. Manually copied the contents of the zip to SDHC card, with DISKBOOT.BIN in root folder.
5. Made badpixel.bin using badpixel.lua script.
6. Made badpixel using .CRW file and show_bad compiled from source in Linux.

As I said before, I upgraded from 885 to 902 after I think I saw a suggestion to get versions from the autobuild system (at that point the beta for 1.02B was in the autobuilder--later it disappeared from that listing). I upgraded by deleting CHDK files and Canon files and copying over the contents of the zip with BOOTDISK.BIN again in the root folder. I saved and reused the badpixel files since the bad pixels were unlikely to have changed.

I took very few images with the 885 version before removing and installing 902. It was using the 902 version that I noticed that the setting "raw file in dir with JPG" actually put the two types of files in different directories. It was also at this point that I realized that not only was numbering reset to 0001 but it repeatedly got reset to 0001 and new folders were created.

It wasn't clear whether this also happened with my earlier install of 885 for two reasons. One, because so few photos were taken with 885--possibly all at one time. Two, because the latest version of my image downloading software in Linux has gotten "cute" by showing all image names regardless of the folder they're in and showing no folder names. [Grrr for cute software that wants you to think of it as a simple black box. I like detail myself and hate it when detail is hidden.]

I tested over and over with 902 and continously had new folders started each time the camera was turned on and new pictures then taken. It happened, even though I had the start a new folder "monthly" and "continuous" numbering set in the Canon menus.

******************

Now for new tests. I installed (exactly as described above) version 885 and then copied over badpixel files. New photos started from the current numbering I had before playing with CHDK. New folders were not created every time I turned on the camera. All was as I expected, not as I had experienced at first.

I then went back to the SDHC card with the renumbering issue. I deleted the Canon folders, the CCHDK.CFG file (from the CHDK folder) and put it back into the camera. I took photos, turned the camera off and on again, took more photos, raw and jpg....No problem. Numbering is now continuous and not from 0001 but the previous continuous last number.

I don't know whether it was something in a Canon folder or CCHDK.CFG, but clearly something whacky got into the card and caused the problem. How? When exactly? Who knows. At least I can tell folks how to fix it and I can fix it myself if it happens again.

Don

Veria

Hi.
anybody have good news about 1.02D?
finally may we have CHDK?!

hellgate

kellyrx8
havent been on in a while...but im assuming 1.02c is still on hold right now?

if I can be of any assistance in getting it going im all game!

The same here 😀

I know, it´s a damn time, with warm, beautiful weather, summertime 😀 but it is a great time to work with the chdk 😁

f_m_b

Hello

i think the problem comes with the date/time of the first DNG. Always the first foto has a date/time stamp of 1.1.2000 and so the sx20 has to create a new folder to avoid a override of pictures.

I don't think the problem comes with 902, because i have used revision 885 with the same problem.

DandyOne
I guess this trick can't be used for 16GB cards? It's limited to 2 partitions?

I changed the swap partition code in the following way:
With swap partition you get the next partition on the card. This should work with 2,3 and 4 Partitions.

How can i check in this feature? i have no write rights for the repository.
Are there coding conventions for chdk?
The autobuild has a selfstart or need a trigger?

and then i need some brave tester with 16 GB cards 😉 and if it works someone who documents the new feature.

Bye Frank

fe50

Coaster
As I said before, I upgraded from 885 to 902 after I think I saw a suggestion to get versions from the autobuild system (at that point the beta for 1.02B was in the autobuilder--later it disappeared from that listing).

The SX20 port was added to the official CHDK trunk with changeset #900; it is commented out in the main makefile, this way the Autobuild Server do not generate & deliver "official" CHDK binary packages.
ATM there are some open issues with this port, therefore automatic building is disabled - the porter devs should have a look to the open issues first 😉

The AB server has never provided SX20 binaries !

Don't mix up the official CHDK source tree & Autobuild server (http://mighty-hoernsche.de/) with the german DE branch; the german Autobuild Server (http://www.wirklemms.de/chdk/forum/autobuild.php) provides SX20 binaries ATM, the source code is the same as in the official trunk...

f_m_b

Hello fe50

can you look over my changes? And when you think they are ok please commit it to the two repositories?

The file is wrappers.c, the changed function is swap_partitions.

The new feature: swapping more then two partitions, up to four.

You know a feature to show the partition name?

Bye Frank

Coaster

@Fe50

The SX20 port was added to the official CHDK trunk with changeset #900; it is commented out in the main makefile, this way the Autobuild Server do not generate & deliver "official" CHDK binary packages.
ATM there are some open issues with this port, therefore automatic building is disabled - the porter devs should have a look to the open issues first Wink

The AB server has never provided SX20 binaries !

Thanks for providing the explanation for why the SX20 1.02B build is not currently on the autobuild listing.

Just to be clear, and with no intent to be argumentative, I am pretty sure that the 902 version I got was temporarily available from the list of cameras and versions that is linked at the top of the autobuild page. I do not think it is possible to mistake that list from the very different style of selecting files for download on the German autobuilder. I also notice that the naming convention for the zips is different. The file I downloaded from the autobuild listing was named "sx20-102b-0.9.9-902-full_BETA_without_games.zip"

How the file and the file link in the listing of the autobuilder got there when the makefile had the SX20 commented out, I don't know. My guess is that the most likely explanation is that for a short time the SX20 was in the makefile without being commented out.

edited: Looking at the German autobuild for the SX20 I see that there is no way to confuse the contents with the version I got.

Don

« Previous Page Next Page »