CHDK Forum
CHDK Development => General Discussion and Assistance => Topic started by: Mikecad on 06 / May / 2014, 08:02:29
-
Hi all,
I have been successfully using CHDK on my G12 for some time now but have decided that carrying it and my underwater enclosure around is at an end.
I just bought a Powershot D30 for my under water shots, probably similar image quality to the G12 when shooting underwater but I've not gotten to test it yet. That it is pretty much a D20 under the hood, with the same lens and Digic 4 image processor I was wondering if the current issues with more recent Canon cameras would be present in a new camera based on old tech? I'm referring to some of the problems I've been reading on the forums with the firmware of the newer Digic 6 processor and that they haven't been "cracked" yet.
Also given that this kind of question has been asked lots of times before, i.e. can I use a D20 firmware on a D30 th e answer looks to be no considering the potential changes that have occurred between these two generations. Is there a risk in giving it a go? Then again, one post I read said that this approach has never been successful so....
Given that I don't have the programming experience to create my own, I'm reliant on someone else with the technical know how to create a CHDK for the D30. Any takers? I'll pay ya :)
-
Hi,
Cameras released this year are using DRYOS 2.3, release #0054+p3, there is no port for any of them, so maybe we'll see new challenges.
The first step to start the port is to make a firmware dump. Could you do it? You can find instructions here: http://chdk.wikia.com/wiki/Canon_Basic/Scripts/Dumper (http://chdk.wikia.com/wiki/Canon_Basic/Scripts/Dumper)
-
Yep I should be able to do that for tomorrow.
-
Ok here is the firmware from the Canon Powershot D30.
http://www.mikecad.com/PRIMARY.BIN (http://www.mikecad.com/PRIMARY.BIN)
-
Dump file is fine:
// Camera info:
// DRYOS R50 (DRYOS version 2.3, release #0050)
// Firmware Ver GM1.00A // Found @ 0xff079358, "GM1.00A" @ 0xff079365
// Firmware build timestamp: Jan 20 2014 19:08:20
// Canon PowerShot D30
-
// DRYOS R50 (DRYOS version 2.3, release #0050)r50// Firmware build timestamp: Jan 20 2014 19:08:20in 2014. D20 in a new package?
-
// DRYOS R50 (DRYOS version 2.3, release #0050)r50// Firmware build timestamp: Jan 20 2014 19:08:20in 2014. D20 in a new package?
D20 with a BSI sensor.
Phil.
-
// DRYOS R50 (DRYOS version 2.3, release #0050)r50// Firmware build timestamp: Jan 20 2014 19:08:20in 2014. D20 in a new package?
D20 with a BSI sensor.
Phil.
The D20 also has a BSI sensor (http://www.dpreview.com/reviews/canon-powershot-d20)
So yeah, I wouldn't be surprised if they even used the exact same mainboard as the D20.
To give it credit though, it does go down further down than any of last-year's competition (http://www.dpreview.com/reviews/2013-waterproof-roundup), to 25 metres (but not that it'll be very usable at that depth though with an f/3.9 aperture). And it supposedly has a brighter screen (http://www.cnet.com/products/canon-powershot-d30/).
-
To be fair I wasn't exactly blown away by the enhancements over the D20 but I needed an UW camera and I've always had Canon so.....
I guess the D30 won't exactly be mainstream like the more popular Canon P&S cameras and that CHDK could be a long time coming, if ever?
-
I guess the D30 won't exactly be mainstream like the more popular Canon P&S cameras and that CHDK could be a long time coming, if ever?
I sent you a test version via PM. Please run test scripts (http://chdk.wikia.com/wiki/Testing) and report the results.
-
Added the
full 16MB dump by Mikecad from this forum post (http://chdk.setepontos.com/index.php?topic=11489.msg112664#msg112664) to the CHDK P&S FW dumps (https://drive.google.com/folderview?id=0B08pqRtyrObjTy11Y003Sk1lYTQ#list) repository.
-
Hello nafraf!
It seems Mikecad didn't read your message.
I will get my D30 within next days. If you provide the test version I will do the test scripts.
-
I will get my D30 within next days. If you provide the test version I will do the test scripts.
The first step is to check the firmware version of your camera. See ACID (http://www.zenoshrdlu.com/acid/acid.html) tool.
-
I will do that as soon as I get the D30!
-
Received my cam today. Button call of firmware version did not work. Shot a picture - EXIF data tells me "Canon firmware version 1.00"
-
You need to use the ACID utility to determine your firmware version. The information in the exif data is not correct.
-
You need to use the ACID utility to determine your firmware version. The information in the exif data is not correct.
I would say EXIF data is correct, but a better EXIF reader is needed :)
Wit exiftool (http://www.sno.phy.queensu.ca/~phil/exiftool/), firmware version is shown as field "Firmware revision".
-
Now checked a JPG with ACID. It showed the correct firmware version: 100a
-
@miti.ranieri
I sent you a test version via PM. Please run test scripts (http://chdk.wikia.com/wiki/Testing) and report the results.
-
I executed the testscripts and procedures according to the document in the link. Please consider that I'm a newbie to CHDK and I hope the feedback is useful.
The results:
https://docs.google.com/document/d/1GXS91PuPrjW54E64jdN2-Vek9mwLpytHM7nkVvWCuuM/edit?usp=sharing
-
I executed the testscripts and procedures according to the document in the link.
Thanks for the report.
I sent you a new file. Please test zebra again.
mftest.lua: Could you post the log file generated by the script?
ubtest.bas: Please check this:
Output is logged to CHDK/LOGS/LOG_0001.TXT. The log will indicate whether the shots above were + or -, with the corresponding exposure number. Compare the jpegs to ensure the images show the expected variation in exposure.
-
Also please check DNG
1) DNG is saved in the same folder as jpegs with the correct name if you select "Raw in folder with jpeg"
2) DNG contains a valid image. Take several shots. Try both AUTO mode and P mode. You can look at them using a free program like irfanview. The quality probably won't look very good, but you should be able to tell if the image is there.
3) DNG file does not have large black borders
4) DNG validates with adobe dng_validate (available with the adobe DNG SDK)
If you upload a sample DNG somewhere, we can take care of the last two.
-
Hi
Tested the new version - Zebra now is ok...
Hope I made all the tests you need - please find all attached files you requested and the new test report in this shared folder:
https://drive.google.com/folderview?id=0B3xKqP5oRrFqeDdROWhGcDltN00&usp=sharing
Thank you for your effort!
-
Hi
Is everything allright with my test report? Too bad the test version of CHDK is expired. I appreciate it very much - even though it's only beta.
Hope to hear from you soon - best regards!
-
Thanks for the report.
I'll send you a new version. Two more tests:
- Test if overrides are applied correctly when you press the shutter quickly without waiting for auto-focus.
- chdkptp connections and remote capture.
chdkptp binaries are available here (https://www.assembla.com/spaces/chdkptp/documents). Documentation is here: https://www.assembla.com/spaces/chdkptp/wiki (https://www.assembla.com/spaces/chdkptp/wiki)
Thanks
-
Hello Nafraf!
Now I tried to test different variations of overrides - with and without waiting for AF to focus.
I had some problems with chdkptp - but I'm unsure wether the problem was located between my chair and keyboard or in chdk/chdkptp ;)
Please find the test report here (hope it is useful):
https://docs.google.com/document/d/1_L0Oxe-RdhvdpqnlaPg3fEJkmUAyNS8Lp1ZJtqJdwiw/edit?usp=sharing
-
Hi!
I had some problems with chdkptp - but I'm unsure wether the problem was located between my chair and keyboard or in chdk/chdkptp ;)
Why did you use a virtual machine? there are chdkptp versions for windows and linux :)
-
Hi Nafraf!
my Win7 at work is locked by policies - no special USB drivers installable
at home I'm Linux user for 10+ years now. Therefore the complicated test with Win XP in a VM. But beside being a little workaround it should be ok this way.
Is my test log useful for you?
I did a couple of other tests with chdkptp but it seems I can only read from the camera but not send any commands with chdkptp.
-
Is my test log useful for you?
nafraf send me a link to the test log to look at. It seems that the exposure overrides are working correctly. However, you probably need to understand a bit about how those overrides work.
When you set an override from CHDK, the Canon firmware has no idea that you are doing that. So it sets the other exposure parameters not being overridden to whatever it would normally have set them to. Your override will thus result in an incorrect exposure (unless you happened to set the override value to whatever the Canon firmware was going to use). Think of overrides as "M" or manual mode settings. Once you pick one, you have to set the other two if you want the exposure to be correct.
As a side note, the D30 does not have an adjustable aperture (just like most Canon small PS cameras). The effective aperture you see on the display will change with zoom position but that is the only way it will change. There is a neutral density filter that can be inserted resulting in about a 3 stop change in exposure.
I did a couple of other tests with chdkptp but it seems I can only read from the camera but not send any commands with chdkptp.
Not sure what to tell you here. I run chdkptp on a Linux machine every day and have a Win7 partition where it also works fine. I'm not so sure I'd want to try something that hardware dependent from any sort of a virtual machine.
-
thank you, waterwingz! I don't have much experience with chdk up to now. I heard from chdk in June this year.
Now the technical background about chdk-overrides is clear to me, I will try to make use of the nd-filter to compensate.
Regarding the chdkptp test - is there a short summary how to get the tool running on Ubuntu 14.04 LTS. I installed lua5.2 but what to do then? The hint to find information about the Linux installation in README.TXT file didn't help me.
I'm not a developer but I'm not afraid of the commandline. Is there a short description of the necessary steps?
Thank you for any hints!
-
Regarding the chdkptp test - is there a short summary how to get the tool running on Ubuntu 14.04 LTS. I installed lua5.2 but what to do then? The hint to find information about the Linux installation in README.TXT file didn't help me.
You would have to build it from source, or get someone else to do it. The Linux binaries I post are built on 10.04 (yes, I know it's ancient), and require your to have the IUP and CD libraries installed.
Building is not terribly hard if you don't need the GUI: You need to install the development packages mentioned in the readme (the exact names may vary depending on the distro), copy config-sample-linux.mk to config.mk and edit it to match your configuration, and then run make. You will also gcc etc installed of course.
-
Hello Everyone,
I also own a powershot d30 and am interested in implementing chdk. How can I be of assistance? I can test builds or assist with coding. Thanks for the help and look forward to working with everyone.
Cody
-
Hi!
Today I found the time to test chdkptp again on Windows 7.
This time the special usb driver installed successful. Start of chdkptp worked as well and the camera was displayed in chdkptp gui. But when I push the button "Connect" I get the following error message on the PC and on the camera's display:
ERROR: error loading module 'capmode' from file 'A/CHDK/LUALIB/capmode.lua':
cannot fopen A/CHDK/LUALIB/capmode.lua
The file capmode.lua exists on the path - I checked that with the chdk filebrowser!
I even opened capmode.lua with Notepad++ without a problem (inserted the camera's SD-card in a card reader on the PC)
UPDATE:
I tried the same procedure now with my Canon D10 and chdkptp works perfectly! I was able to shoot pictures, replay etc. Everything worked fine.
What's wrong?
-
ERROR: error loading module 'capmode' from file 'A/CHDK/LUALIB/capmode.lua':
cannot fopen A/CHDK/LUALIB/capmode.lua
What's wrong?
This can happen if there isn't much free memory on the cam.
Try
=return get_meminfo()
and
=return get_meminfo('system')
Also check that capmode.lua is actually visible to chdk:
=return os.stat('A/CHDK/LUALIB/capmode.lua')
-
This is what the commands returned:
ERROR: error loading module 'capmode' from file 'A/CHDK/LUALIB/capmode.lua':
cannot fopen A/CHDK/LUALIB/capmode.lua
> =return get_meminfo()
2:return:table:{chdk_start=3461540,free_size=9440,chdk_size=171008,allocated_size=1899096,free_block_count=14,name="combined",allocated_count=1500,chdk_malloc=true,free_block_max_size=7256,allocated_peak=1903168,total_size=1908536,}
> =return get_meminfo('system')
3:return:table:{start_address=1684248,chdk_start=3461540,free_size=8984,chdk_size=171008,allocated_size=1899552,free_block_count=16,allocated_count=1501,name="system",end_address=3592784,chdk_malloc=true,free_block_max_size=6600,allocated_peak=1903168,total_size=1908536,}
> =return os.stat('A/CHDK/LUALIB/capmode.lua')
4:return:table:{is_file=true,mtime=1405333320,ctime=1406275608,attrib=32,is_dir=false,size=2517,}
Is there a possibility to free some memory?
-
free_size=8984
That confirms that free memory is the problem. Maybe nafraf can implement exmem.
Otherwise, this camera will have very limited functionality with CHDK.
-
The other possibility is to reduce the memory size reserved for the UI (http://chdk.setepontos.com/index.php?topic=11246). This cam has 600000 bytes allocated for that purpose. The code in question is:
task_Startup:
ff00a638: push {r4, lr}
ff00a63c: bl loc_ff0048c8
ff00a640: bl loc_ff025e10
ff00a644: bl loc_ff025ea4
ff00a648: bl loc_ff026158
ff00a64c: bl loc_ff026324
ff00a650: bl loc_ff02614c
ff00a654: bl loc_ff02602c
ff00a658: bl loc_ff0242a8
ff00a65c: bl loc_ff02632c // ->
ff00a660: bl loc_ff01e454
ff00a664: bl loc_ff021fd8
ff00a668: bl loc_ff026344
ff00a66c: bl loc_ff01ba14
ff00a670: bl loc_ff01c55c
ff00a674: bl loc_ff025b04
ff00a678: bl loc_ff01cb94
ff00a67c: bl loc_ff01c4f8
ff00a680: bl loc_ff026150
ff00a684: bl loc_ff026ffc
ff00a688: bl loc_ff01c4bc
ff00a68c: pop {r4, lr}
ff00a690: b loc_ff0049e8
loc_ff02632
ff02632c: push {r4, lr}
ff026330: bl loc_ff080de0 // ->
ff026334: bl loc_ff07e434
ff026338: bl loc_ff07ede8
ff02633c: pop {r4, lr}
ff026340: b loc_ff07fdec
loc_ff080de
ff080de0: push {r4, r5, r6, lr}
ff080de4: bl loc_ff0200c4 ; <IsFactoryMode_FW>
ff080de8: cmp r0, #0
ff080dec: ldr r4, =0x3390
ff080df0: ldrne r0, =0xff02437c
ff080df4: strne r0, [r4, #4]
ff080df8: ldrne r0, =0xff024380
ff080dfc: strne r0, [r4, #8]
ff080e00: popne {r4, r5, r6, pc}
ff080e04: ldr r0, [r4]
ff080e08: cmp r0, #0
ff080e0c: popne {r4, r5, r6, pc}
ff080e10: ldr r5, =0x927c0 // 600000 bytes, change this to something smaller
ff080e14: mov r0, r5
ff080e18: bl loc_ff024384
ff080e1c: mov r1, r5
ff080e20: bl loc_ff0243b8
ff080e24: tst r0, #1
ff080e28: str r0, [r4]
ff080e2c: popeq {r4, r5, r6, pc}
ff080e30: pop {r4, r5, r6, lr}
ff080e34: mov r1, #0x4d
ff080e38: ldr r0, =0xff080e5c
ff080e3c: b loc_476afc ; <DebugAssert>
-
The other possibility is to reduce the memory size reserved for the UI (http://chdk.setepontos.com/index.php?topic=11246). This cam has 600000 bytes allocated for that purpose. The code in question is:
task_Startup:
ff00a638: push {r4, lr}
ff00a63c: bl loc_ff0048c8
ff00a640: bl loc_ff025e10
ff00a644: bl loc_ff025ea4
ff00a648: bl loc_ff026158
ff00a64c: bl loc_ff026324
ff00a650: bl loc_ff02614c
ff00a654: bl loc_ff02602c
ff00a658: bl loc_ff0242a8
ff00a65c: bl loc_ff02632c // ->
ff00a660: bl loc_ff01e454
ff00a664: bl loc_ff021fd8
ff00a668: bl loc_ff026344
ff00a66c: bl loc_ff01ba14
ff00a670: bl loc_ff01c55c
ff00a674: bl loc_ff025b04
ff00a678: bl loc_ff01cb94
ff00a67c: bl loc_ff01c4f8
ff00a680: bl loc_ff026150
ff00a684: bl loc_ff026ffc
ff00a688: bl loc_ff01c4bc
ff00a68c: pop {r4, lr}
ff00a690: b loc_ff0049e8
loc_ff02632
ff02632c: push {r4, lr}
ff026330: bl loc_ff080de0 // ->
ff026334: bl loc_ff07e434
ff026338: bl loc_ff07ede8
ff02633c: pop {r4, lr}
ff026340: b loc_ff07fdec
loc_ff080de
ff080de0: push {r4, r5, r6, lr}
ff080de4: bl loc_ff0200c4 ; <IsFactoryMode_FW>
ff080de8: cmp r0, #0
ff080dec: ldr r4, =0x3390
ff080df0: ldrne r0, =0xff02437c
ff080df4: strne r0, [r4, #4]
ff080df8: ldrne r0, =0xff024380
ff080dfc: strne r0, [r4, #8]
ff080e00: popne {r4, r5, r6, pc}
ff080e04: ldr r0, [r4]
ff080e08: cmp r0, #0
ff080e0c: popne {r4, r5, r6, pc}
ff080e10: ldr r5, =0x927c0 // 600000 bytes, change this to something smaller
ff080e14: mov r0, r5
ff080e18: bl loc_ff024384
ff080e1c: mov r1, r5
ff080e20: bl loc_ff0243b8
ff080e24: tst r0, #1
ff080e28: str r0, [r4]
ff080e2c: popeq {r4, r5, r6, pc}
ff080e30: pop {r4, r5, r6, lr}
ff080e34: mov r1, #0x4d
ff080e38: ldr r0, =0xff080e5c
ff080e3c: b loc_476afc ; <DebugAssert>
well ，anyluck？
-
The other possibility is to reduce the memory size reserved for the UI (http://chdk.setepontos.com/index.php?topic=11246). This cam has 600000 bytes allocated for that purpose. The code in question is:
task_Startup:
ff00a638: push {r4, lr}
ff00a63c: bl loc_ff0048c8
ff00a640: bl loc_ff025e10
ff00a644: bl loc_ff025ea4
ff00a648: bl loc_ff026158
ff00a64c: bl loc_ff026324
ff00a650: bl loc_ff02614c
ff00a654: bl loc_ff02602c
ff00a658: bl loc_ff0242a8
ff00a65c: bl loc_ff02632c // ->
ff00a660: bl loc_ff01e454
ff00a664: bl loc_ff021fd8
ff00a668: bl loc_ff026344
ff00a66c: bl loc_ff01ba14
ff00a670: bl loc_ff01c55c
ff00a674: bl loc_ff025b04
ff00a678: bl loc_ff01cb94
ff00a67c: bl loc_ff01c4f8
ff00a680: bl loc_ff026150
ff00a684: bl loc_ff026ffc
ff00a688: bl loc_ff01c4bc
ff00a68c: pop {r4, lr}
ff00a690: b loc_ff0049e8
loc_ff02632
ff02632c: push {r4, lr}
ff026330: bl loc_ff080de0 // ->
ff026334: bl loc_ff07e434
ff026338: bl loc_ff07ede8
ff02633c: pop {r4, lr}
ff026340: b loc_ff07fdec
loc_ff080de
ff080de0: push {r4, r5, r6, lr}
ff080de4: bl loc_ff0200c4 ; <IsFactoryMode_FW>
ff080de8: cmp r0, #0
ff080dec: ldr r4, =0x3390
ff080df0: ldrne r0, =0xff02437c
ff080df4: strne r0, [r4, #4]
ff080df8: ldrne r0, =0xff024380
ff080dfc: strne r0, [r4, #8]
ff080e00: popne {r4, r5, r6, pc}
ff080e04: ldr r0, [r4]
ff080e08: cmp r0, #0
ff080e0c: popne {r4, r5, r6, pc}
ff080e10: ldr r5, =0x927c0 // 600000 bytes, change this to something smaller
ff080e14: mov r0, r5
ff080e18: bl loc_ff024384
ff080e1c: mov r1, r5
ff080e20: bl loc_ff0243b8
ff080e24: tst r0, #1
ff080e28: str r0, [r4]
ff080e2c: popeq {r4, r5, r6, pc}
ff080e30: pop {r4, r5, r6, lr}
ff080e34: mov r1, #0x4d
ff080e38: ldr r0, =0xff080e5c
ff080e3c: b loc_476afc ; <DebugAssert>
well,anyluck?
-
Hi, I'm new to CHDK but keen to test anything on Powershot D30 if it helps
I've got a D10 and I'll try to set that up to familiarize myself.
-
Hi nafraf
Hi All
Today I had the chance to test the latest beta release for the D30 regarding the problem with chdkptp.
Now chdkptp works fine!
I was able to activate Viewfinder in all variations, use all buttons (left,right,up,down, menu etc.) successful. Recording images works as well as shooting video. Play function to review images or videos works fine.
Only one small issue that I observed: when recording video the chdkptp-live-viewfinder stream frequently flickers between a normal image and a distorted (streched vertically) view aspect. Despite that visible flaw the recorded video is ok and when pressing the "play"-button in chdkptp and reviewing the video it is displayed without distortions or flickering in the chdkptp-window.
Do you need any further tests of chdkptp?
-
Thanks. The latest beta release uses srsa_4c suggestion.
Do you need any further tests of chdkptp?
Please test remote capture. Connect to chdkptp, go to User tab, and test JPEG and DNG capture.
If you prefer to use command line:
rs -jpg /destination_dir
rs -dng /destination_dir
-
Can you please advise where I can download beta to test - sorry if it's obvious - it's not to me!
I realise there are older links but don't want to test old load.
Thanks
-
Please test remote capture. Connect to chdkptp, go to User tab, and test JPEG and DNG capture.
If you prefer to use command line:
rs -jpg /destination_dir
rs -dng /destination_dir
Hi nafraf,
remote capture works perfectly:
1. I set destination by clicking first button
2. tried JPG and DNG shot - both were taken
3. checked the images - both were existing on the configured path on my pc (and are not on the sdcard - as expected)
Minor issue: I use DNG version 1.1 to successfully avoid bad pixels in my DNG images and configured CHDK on the D30 to make DNG shots in version 1.1. With remote capture the DNG seems to be version 1.3 as I can see the bad pixels in the DNG file. CHDKPTP GUI doesn't seem to have a possibility to configure that option and "help rs" didn' show a command line option for another DNG version.
But as mentioned above remote capture works!
Any other tests?
@melb: testing is almost thru, I guess nafraf will soon release CHDK for the D30 in a final version. Testbuilds are provided by personal messages not in the thread here.
-
With remote capture the DNG seems to be version 1.3 as I can see the bad pixels in the DNG file. CHDKPTP GUI doesn't seem to have a possibility to configure that option and "help rs" didn' show a command line option for another DNG version.
You should be able to fix badpixels with the -badpix option in the CLI. This doesn't change the DNG version, but it does approximately the same thing the CHDK DNG 1.1 code would do.
-
You should be able to fix badpixels with the -badpix option in the CLI. This doesn't change the DNG version, but it does approximately the same thing the CHDK DNG 1.1 code would do.
Thank you reyalp! Tested that - you are right!
Now I got a perfect DNG without bad pixels by using the following command:
rs -dng -badpix D:\
By the way ... can I get the same result when using CHDK on the D30? Being a newbie to CHDK the only way to get DNGs without badpixels was to select DNG version 1.1
I don't know wether it is an advantage to use DNG version 1.3 or not. But with version 1.3 I was not able to get DNGs without bad pixels up to now.
-
By the way ... can I get the same result when using CHDK on the D30?
Only by using 1.1. You can use chdkptp to do the same thing to DNG 1.3 files, without using remoteshoot
https://www.assembla.com/spaces/chdkptp/wiki/DNG_Processing (https://www.assembla.com/spaces/chdkptp/wiki/DNG_Processing)
I don't know wether it is an advantage to use DNG version 1.3 or not.
Only that it uses less memory on the camera, doesn't require you to create badpixel.bin, and is very slightly quicker.
Why is it like this?
In DNG 1.1, the spec requires that any bad pixels must be fixed in the raw data. To do this, CHDK makes a list (badpixel.bin) and interpolates over them. The list is needed because scanning over the whole raw would be extremely slow, but it can require a significant amount of RAM.
In DNG 1.3, the spec allows the you to just specify what values are bad, so we can in theory say that pixels with value 0 are bad, and the raw software will handle them. In reality though, most non-adobe programs don't support this feature.
chdkptp just interpolates over the bad values like CHDK would for DNG 1.1. Since PCs are much faster than the cameras, scanning the entire file is not a problem.
-
Thank you for the explanation, reyalp!
Things are becoming clearer to me now.
-
Hi nafraf and all other CHDK hackers!
Thank you for creating such a great software and for your effort to adapt it for the D30.
I told nafraf I had the chance to make use of it during my holidays at the red sea in egypt a few weeks ago.
To thank you here's a little gallery of some images I took:
http://www.dpreview.com/forums/post/54407735 (http://www.dpreview.com/forums/post/54407735)
We - users of the D30 - are looking forward to the official release of CHDK for this camera.
Thanks!
-
I'm considering buying the D30. Where can I find the latest test version of CHDK for it, if I do?
Edit: Actually, let me rephrase that. If someone sends me a test build of CHDK, I will go out and buy the D30. I will gladly help test it in any way I can, but I don't really know what I'm doing. BUT, if I'm sort of useless because I don't know what I'm doing, and therefore I can't get access to a copy of the beta CHDK, then I will buy something else, because the ability to shoot RAW on an upcoming trip is the real reason I want the D30.
-
I'm thinking of buying a D30 (my SX260 and S100 are not coping well with the desert sand + multicopter!).
Can anyone confirm whether remote triggering working in the current D30 beta?
Thanks, Andy
-
Can anyone confirm whether remote triggering working in the current D30 beta?
In case you don't hear from anyone who actually has the camera, if remote triggering does not work then this would be the first Canon model in (approximately) the last 100 over seven plus years that did not work. I think you are safe assuming it does.
-
Happy to see that CHDK for the D30 was released two days ago!!
Thanks to the developer team!
-
That's amazing! Now I can buy a D30. Thanks, team!
-
I have an issue with motion detection on my D30 as described here:
http://chdk.setepontos.com/index.php?topic=12274 (http://chdk.setepontos.com/index.php?topic=12274)
(mod edit: fixed link)
-
I'd consider using the d20 viewport routines since the two models are probably very similar inside...
-
I'd consider using the d20 viewport routines since the two models are probably very similar inside...
The *vid_get_viewport_live_fb() function in both camera's lib.c files are the same - the D30 looks like a c&p from the D20 in fact (and is marked "TO DO"). Did you have something different in mind with your comment?
-
The *vid_get_viewport_live_fb() function in both camera's lib.c files are the same - the D30 looks like a c&p from the D20 in fact (and is marked "TO DO"). Did you have something different in mind with your comment?
What I meant was the rest (the viewport dimension related stuff, including a #define in platform_camera.h). Those look suspicious to me. Problem is, the d20 code also has "to do" comments around...
-
I have an issue with motion detection on my D30 as described here:
chdk.setepontos.com/index.php?topic=12274
Some things that could cause viewport weirdness
- Using an aspect ratio that isn't the same as the screen
- Using digital zoom
However, these should cause visible problems with zebra too.
PTP live view might show viewport problems http://chdk.wikia.com/wiki/PTP_Extension (http://chdk.wikia.com/wiki/PTP_Extension)
-
I couldn't get the LiveView in chdkptp to work while browsing files worked. Is that the kind of problem you mean?
-
I couldn't get the LiveView in chdkptp to work while browsing files worked. Is that the kind of problem you mean?
Can you be more specific? What happens when you tick "Viewfinder" and/or "UI overlay" on the "Live" tab?
-
Uhm... :o
What I actually meant was that I did not get any picture in the Live tab even though file browsing worked ok. That was a few hours ago.
Now that I try it again to give you a more detailed description I get the default Canon startup image (even though the camera display show me the last picture taken) and both overlays(Canon and CHDK) as they appear on the display. I can't switch to rec mode though and the console plays dumb when I enter lua commands.
But I guess those are entirely different problems that don't have to do with anything you meant.
-
I can't switch to rec mode though and the console plays dumb when I enter lua commands.
So the "rec" button in the gui just doesn't do anything? Is there any error in the console
But I guess those are entirely different problems that don't have to do with anything you meant.
We would need to get rec mode to work first, then if there's some problem with the viewport set up it might give us clue about what is wrong with MD.
What OS are you using chdkptp on?
-
Oh boy... :-[
I was trying to change the mode by pressing physical buttons and press("shoot_half") and didn't even see the "rec" button.
The "rec" button works and I can see the live image in chdkptp on Windows 7.
Sorry.
-
The "rec" button works and I can see the live image in chdkptp on Windows 7.
No problem, it's not really obvious that the camera buttons stop working.
Next question is, does the live view look OK. Can you see the same area that show on the physical screen? Do you see "snow" or any other sort of artifacts?
If you press the "quick dump" button in the debug tab and upload the results, I can take a log.
-
I can't find anything wrong with the live view except for some distortions directly after calling "luar shoot()" which disappear almost instantly. (see attachment)
Are we talking about different programs? I don't see a debug tab(see attachment).
-
Are we talking about different programs? I don't see a debug tab(see attachment).
Small tab next to statistics.
Seeing garbage when you shoot is normal, and shouldn't affect MD. The memory range used for the viewport buffer gets re-used for other things.
-
Here's a quickdump from rec mode:
https://depot.tu-dortmund.de/bqn5m
(File will be gone in 7 days.)
-
Here's a quickdump from rec mode:
Thanks. I agree it seems to be working fine. There is a fair amount of moving noise which would presumably trigger MD at some level, but it doesn't seem too different from what I see on my cams in low light.
I'm not sure what could be causing your MD triggering. MD uses the essentially the same buffers and YUV decoding as live view and zebra. The MD code itself is generic, so if there were a problem with the comparison it should affect other cameras.
-
I should have paid closer attention the the first thread. I assumed you were seeing spurious triggering, but now I realize this isn't the case.
You script uses md_get_cell_val, not md_get_cell_diff so this doesn't represent spurious motion detection. It represents the average value of the cell.
-
First day with D30 :haha
Meanwhile I know enough Dutch=132097 to find the language German=131329 or 131073=English
in the CHDK -> Menu Instellingen-> Taal... setting.
md_detect covers full size in the 16:9 & 3:2 ratio; 1:1 & 4:3 are fine.
Edit: CHDK always boots to <rec>. (D20 too)
Edit2: ???? #undef CAM_HAS_IS // Camera does not have an image stabilizer
-
The md_/aspect ratio-, ptp-(video resolutions & buffer) issues are solved with excerpts from Ix255 & 265´s lib.c...
Compiled it without "#undef CAM_HAS_IS", no crash so far... 8)
-
Compiled it without "#undef CAM_HAS_IS", no crash so far... 8)
Thanks for pointing that out. No crashes are expected either way, I believe CAM_HAS_IS only affects one option related to custom auto-ISO, but in any case, I corrected it for D20 and D30, both of which have IS according to Canon documentation.