So the encryption you mentioned refers to the keys used to encode the firmware, like the old dvd css key nonsense.
For anyone else who wants to compile CHDK for this camera here's a quick rundown:
Now that I can run the latest chdk versions I hope to test out more features and feed that info back so we can get this build mainstream.
For anyone else who wants to compile CHDK for this camera here's a quick rundown:...That's it. I hope that will save the next guy some time.
That's it. I hope that will save the next guy some time.Now that I can run the latest chdk versions I hope to test out more features and feed that info back so we can get this build mainstream.
Other than that, you could help us to enable autobuild for this camera.For that to happen, we need to know whether the camera is stable when using various CHDK features (photo overrides, video overrides, histogram, zebra, edge overlay, RAW, DNG), and test scripts found here: http://chdk.wikia.com/wiki/Testing
I have tried 2717 a bit, and it does DNG OK. Histogram and zebra also work.Regarding test scrips, I have tried llibtst.lua and ubtest.bas both seem to work OK (as far as I know).
For setmode.lua however, there were some FAILs, I attach here the log in case it helps.
Good. If possible, can you test photo related overrides, whether they work (and are stable)? Try setting a low ISO override too (with and without flash), and see whether it crashes the camera.Also test the stability of video recording, and the video related CHDK overrides.
You can find the missing mode numbers via the propcase browser (miscellaneous stuff -> debug parameters -> debug data display [props]), propcase 49 on page nr 4 (the 4 unmapped mode numbers are: https://trac.assembla.com/chdk/browser/trunk/platform/sx210is/sub/100c/stubs_entry.S#L23 ). Browse through the camera's shooting modes using the mode dial and Canon menus, and note the propcase number in each mode.
Quote from: DigiFan on 15 / March / 2013, 18:34:51yes, it runs stable if i set 80 oder greater, thats right.The reason I was asking this is that there's an option in CHDK to restrict ISO override values to a safe range. It won't enable lower ISO, but it will prevent that crash. Note that you can't expect super-low ISOs anyway due to hardware restrictions. QuoteOf course i tried most of the other features ( example RAW, but this was not so the result what i would have.something was wrong with that pictures. i tried too, to convert the *.dng for using on ps5.5 or ps6Are you saying that DNG (or RAW) is unusable? If so, what is the problem with it? Like:- there's no picture, just noise (-> this can happen when the camera is in AUTO mode)- the picture has wrong colors (-> if this is true, upload a JPEG + RAW (not DNG) file pair somewhere)- if you only mean that you are unable to make better pictures from the RAW/DNG than the camera's JPEG, that's normal
yes, it runs stable if i set 80 oder greater, thats right.
Of course i tried most of the other features ( example RAW, but this was not so the result what i would have.something was wrong with that pictures. i tried too, to convert the *.dng for using on ps5.5 or ps6
The camera hangs if ISO override lower than 80 and flash is on. You can use safely lower ISOs provided flash is off, actually getting ISOs lower than 80.
I've tested Av and Tv overrides. I've no prior experience using these so I can't compare, but they seem to work OK and the camera is stable.As I said previously RAW/DNG, zebra and histogram both work correctly.
However I have tested edge overlay, and it only shows garbage in screen.
Our current "solution" to this is to restrict minimum ISO override to a value that is always safe. However, if you can actually get lower ISOs to work, then this may need a second thought.
OK. Can you set a longer exposure (Tv override to 80 seconds for example), and see whether it actually takes 80 seconds (and not 64)? (Note that if dark frame subtraction kicks in, the total time will double.)
Is it always garbage or only when "frozen"? If the latter, try to take a longer (few seconds) exposure and see whether you get a correct "frozen" image.
Thanks for all your testing. If the camera remains stable (not counting the ISO override issue), this may be good enough for us to enable autobuild. If you have more time and patience, there might be additional things to test.
Quote from: srsa_4c on 21 / April / 2013, 21:41:13You can find the missing mode numbers via the propcase browser (miscellaneous stuff -> debug parameters -> debug data display [props]), propcase 49 on page nr 4 (the 4 unmapped mode numbers are: https://trac.assembla.com/chdk/browser/trunk/platform/sx210is/sub/100c/stubs_entry.S#L23 ). Browse through the camera's shooting modes using the mode dial and Canon menus, and note the propcase number in each mode.I have no idea how to use the debug menu to look for this, I'll try to find. But when I use the lua script, when set to manual, it displays these values. Are not these what we are looking for?P 2 32772 STLVIDEO_COLOR_SWAP 14 2611 VIDNIGHT_SNAPSHOT 36 32781 STLSCN_FOLIAGE 38 16405 STL
Started by HarpoMa « 1 2 ... 67 68 » General Discussion and Assistance
Started by Ameglin « 1 2 ... 13 14 » DryOS Development
Started by RoaR30 Hello, I'm a NEWBIE - HELP!! (Newbies assistance, User Guides and thank you notes)
Started by Frrost « 1 2 ... 56 57 » General Discussion and Assistance
Started by mlvitor Script Writing
