Whatever distance you want the camera to focus at. -sdmode is a modifier for -sd, not a way of setting the focus mode generally.The background for this is that SD overrides only work in some modes on some cameras. Some only work in AF, some only work in MF, some have quirks that make one or the other preferable in some situations. By default, -sd will try to pick one defined as working in the port. -sdmode lets you pick instead.
If you are using the last released version of chdkptp (r964), -1 in chdkptp shoot commands is broken. It's fixed in SVN, you can update the Lua files from https://app.assembla.com/spaces/chdkptp/subversion/source/HEAD/trunk if you want.
I don' think it's important, but FYI I don't understand what you mean here.What would it mean to say "-sdmode=AF -sd=100mm"? What would it mean to "autofocus" to a particular focus distance? (It's confusing, but since I'm hoping not to use AF it doesn't really matter to me.)
The entire ...\chdkptp-r964-raspbian-gui\chdkptp-r964\lua folder?From what source? From ...\trunk\lua ?
Yes, copy the entire lua directory from the trunk into your install directory. I would recommend using the entire directory rather than trying to mix and much.
1 - set_mf(1) is not necessary to get manual focus if using remoteshoot -sdmode=MF -sd<n>mm(if you use that remoteshoot command, camera does manual focus regardless of set_mf)
2 - However, set_mf() does affect the result of "=press'shoot_half' repeat sleep(10) until get_shooting() return get_focus()".If in set_mf(0), that appears to return the correct focus setting value (not actual distance) for the subject.If in set_mf(1), that appears to return the current focus position (where the lens is now). It doesn't appear to be influenced by the actual subject distance.
3 - Results of experiments with remoteshoot -sdmode=MF -sd=<value>:With set_mf(0) and set_zoom(0), and subject at infinity (~1000 meters):=press'shoot_half' repeat sleep(10) until get_shooting() return get_focus()returns 647 to 746 (may depend on aperture; not sure) Infinity Post-shot-sd= value Sharpness (0..10) get_focus() Interpretation -1mm 0 10 Focused at 10mm (closest focus?) -1 8 1023 Focused at 1.023m? 65535mm 4 65535 Focus is well past infinity. ~700mm 10 ~700 Correct infinity focus. With set_mf(0) and set_zoom(1), and subject at infinity (~1000 meters):
con 1> =set_mf(1)con 2> =set_focus(500) return get_focus()3:return:502con 3> =set_focus(700) return get_focus()4:return:693...con 18> =set_focus(9000) return get_focus()19:return:7483con 19> =set_focus(10000) return get_focus()20:return:14518...con 23> =set_focus(20000) return get_focus()24:return:14518con 24> =set_focus(30000) return get_focus()25:return:65535...con 27> =set_focus(20000) return get_focus()28:return:65535con 28> =set_focus(18000) return get_focus()29:return:12347
Two other things:Using chkdkptp_gui, live view display of the viewfinder doesn't seem to work in record mode on the Raspberry Pi at all, or on Windows on about 1 in 3 camera boots (randomly).It works OK in playback. When it fails (always on the Pi), the viewfinder display shows random-looking pixels. The random-looking pixels do updateto a different set of random-looking pixels after each shot. I can supply screenshots if it's helpful.
Finally, do you think a G-series camera (G9...G12) will produce better .DNG images than the A640?
One note of caution, which I probably should have documented or mentioned earlier : The chdkptp shoot commands do not restore the previous focus mode. So if you do rs -sdmode=MF ... the camera will stay in MF mode until you call set_mf(0) or a different -sdmode
Quote3 - Results of experiments with remoteshoot -sdmode=MF -sd=<value>Was this done with the r964 Lua files? If so, -1 is just broken and you shouldn't use it. In the current files, -1 and -1mm do *exactly* the same thing.
3 - Results of experiments with remoteshoot -sdmode=MF -sd=<value>
You can see how the value is interpreted using shoot -pretend -sd=...
QuoteUsing chkdkptp_gui, live view display of the viewfinder doesn't seem to work in record mode on the Raspberry Pi at all, or on Windows on about 1 in 3 camera boots (randomly).It works OK in playback. When it fails (always on the Pi), the viewfinder display shows random-looking pixels. The random-looking pixels do updateto a different set of random-looking pixels after each shot. I can supply screenshots if it's helpful. A screenshot would definitely be helpful.
Using chkdkptp_gui, live view display of the viewfinder doesn't seem to work in record mode on the Raspberry Pi at all, or on Windows on about 1 in 3 camera boots (randomly).It works OK in playback. When it fails (always on the Pi), the viewfinder display shows random-looking pixels. The random-looking pixels do updateto a different set of random-looking pixels after each shot. I can supply screenshots if it's helpful.
QuoteFinally, do you think a G-series camera (G9...G12) will produce better .DNG images than the A640?Really depends what the issue with the A640 DNG is. I'd expect the G series to have somewhat better image quality overall, but often issues people see with DNG are related to how the images are processed.
No, I did the experiments using the newer Lua files from the trunk.So I'm a little confused now.
QuoteYou can see how the value is interpreted using shoot -pretend -sd=...Is -pretend documented somewhere? It's new to me.
The first one shows what I saw after connecting to the camera (camera was already in rec mode).
Second one is after taking a picture (pressed 'shoot' button). Note slightly different patterned looking noise.
Actually the quality from the A640 is quite good - I'm happy with it. Just wondering if bidding on a G-series on eBay would be worthwhile.
Thanks. That definitely looks like the random garbage you see when viewport addresses are incorrect. Looking at the port code, it wouldn't be surprising at all if some of this were wrong.One question: Is the camera screen on when you see this? If the screen is off, the camera probably doesn't update the display buffers. If you have the screen folded closed face to the camera, please check if behavior is the same with it open.
(base) C:\Users\Dave\data\Projects\Photography - CHDK, CHDK PTP and Magic Lantern\CHDK PTP\chdkptp-r964-win-x86_64>chdkptp -i -eremoteshoot "c:\\users\\dave\\desktop\\test6"ERROR: unrecognized argument c:\\users\\dave\\desktop\\test6CHDK PTP control utilityUsage: chdkptp [options]Options: -g start GUI - default if GUI available and no options given -i start interactive cli -c connect at startup, with optional device spec e.g. -c"-d001 -bbus-0" -e execute cli command, multiple allowed, e.g -e"u DISKBOOT.BIN" -ereboot -r specify startup command file, if no file given skip default startup files -h helpERROR: not connected
I finally got to experiment with another A640. Yes, the live viewfinder in rec mode works OK with the screen folded out, but not with the screen folded in.
On Linux (Pi), this works OK: chdkptp -c -eremoteshoot "/home/pi/Desktop/"
When using -e, -c or -r, the values must immediately follow the option, withoutany space, e.g. -rmyfile or -r=myfile, not -r myfile. If any arguments includespaces, they must be quoted.
On Windows, "remoteshoot" requires the escaped backslashes if the path is in double quotes.
The characters " or ' can be used to quote arguments or switch values thatcontain spaces. Inside double quotes "", backslash \ is treated as an escapecharacter.
Started by toby LUA Scripting
Started by JvdP « 1 2 » General Discussion and Assistance
Started by axman General Help and Assistance on using CHDK stable releases
Started by andrew.stephens.754365 General Help and Assistance on using CHDK stable releases
Started by reyalp RAW Shooting and Processing