StefanDesu
1. I know there's always some risk involved with these things. Do you think the risk of damaging the camera using this test build is higher than the average CHDK build?
Unfortunately, it's really hard to quantify. Because this port is new, on a camera that is quite different from other cameras, the room "unknown unknowns" is definitely bigger. I put a fairly strong warning on the test builds because of this, and the fact that it's a relatively expensive camera.
I don't worry about it too much myself, in the ~9 year history oF CHDK, there have only been a handful of reported brickings that plausibly attributed to it. At the same time, I can't guarantee this camera won't be different.
I have not tried that script, but in general, most script features should work. If there are port bugs that prevent it from working, I will probably fix them.
Skimming what's posted on that page, I see some versions use set_prop 23 to set the jpeg quality. This is not correct on any camera newer than propset 1 (digic II) and actually sets the AV propcase on many (which probably has no effect, being set outside of half shoot), but can easily be commented out or replaced with set_quality.
If you want something more sophisticated, I have briefly tested my
Raw Meter Intervalometer script, and it seems to work fine.
Another alternative is waterwingz
Ultimate Intervalometer. I have not tested this, but it should probably work, and again, I'd expect to fix port specific bugs that prevent it from working.
