D10 porting thread - page 5 - DryOS Development - CHDK Forum
supplierdeeply

D10 porting thread

  • 131 Replies
  • 59824 Views
Re: D10 porting thread
« Reply #40 on: 23 / July / 2010, 13:32:04 »
Advertisements
I tried setting tv in script with no luck. 
Perhaps I'm using it wrong?
I tried set_tv96 1056, set_tv96 528 ,and set_tv 31 (all separately) camera totally ignored them and just shot normal speeds.
I am planning on having f/2.8 ND filter out 1/1500s shutter speed and manually adjusting ISO for exposure.  Sounds simple enough but I can't get the camera to do the 1/1500 second shutter speed

*

Offline reyalp

  • ******
  • 13400
Re: D10 porting thread
« Reply #41 on: 23 / July / 2010, 17:07:54 »
I tried setting tv in script with no luck. 
Perhaps I'm using it wrong?
I tried set_tv96 1056, set_tv96 528 ,and set_tv 31 (all separately) camera totally ignored them and just shot normal speeds.
I am planning on having f/2.8 ND filter out 1/1500s shutter speed and manually adjusting ISO for exposure.  Sounds simple enough but I can't get the camera to do the 1/1500 second shutter speed

What are command are you using to shoot ? How are you using autofocus ?

I would suggest
- set focus at infinity.
- shoot with a press half press, sleep until shooting ready, shoot loop.

Finally note from the first post.
Quote
Please understand this is not a fully functional port.
I do welcome bug reports, but do not expect it to be a fully (or even mostly) functional CHDK at this point.

Bv is the scene brightness in the APEX system. It is available from propcases in halfshoot. Note that the set_tv* commands must be called before halfshoot, so if you are calculating your own exposure, the easy way to do it is to do one half press as a metering pass, release and calculate your values, and then do the shot.

Note also that scripted overrides are reset after each shot.

Quote from: BlinkTooFast
If I delete a picture in-camera, CHDK can have problems starting next time the camera is turned on, either from auto-boot or from update firmware.
I just tried this, and was not able to reproduce the problem. If you can narrow down the circumstances it happens in, that would be helpful. It may depend on whether there are raw images present. It could also be a problem with the card or the filesystem.

What size/filesystem is the card ?

Have you tried reformatting ?
Quote from: BlinkTooFast
# Enable Optical Zoom in video appears to have no effect regardless whether digital zoom is on or off. I have no optical zoom in video, which is a shame.
Again from the first post:
Quote
Not implemented/Not Working
- movie_rec: meaning all movie related functions

Don't forget what the H stands for.

Re: D10 porting thread
« Reply #42 on: 24 / July / 2010, 02:49:47 »
Many thanks for your reply, Reyalp.

Quote from: BlinkTooFast
If I delete a picture in-camera, CHDK can have problems starting next time the camera is turned on, either from auto-boot or from update firmware.
I just tried this, and was not able to reproduce the problem. If you can narrow down the circumstances it happens in, that would be helpful. It may depend on whether there are raw images present. It could also be a problem with the card or the filesystem.

What size/filesystem is the card ?
4GB SD (not SDHC) FAT16 64k clusters. Non standard, but currently the only way I know to get >2GB to autoboot and be able to read the card on a PC.
Yes, RAW files are present.
At both occurrences of the problem, the camera had generated multiple image folders eg 100CANON and 103CANON, a mix of JPG and DNG files were across these, and a few of the JPG files had been deleted without deleting the accompanying DNGs. In particular, one folder contained DNGs and no JPGs.
Have you tried reformatting ?
No. The first time I fixed it by disabling CHDK, taking a new JPG, and re-enabling CHDK. This fix lasted only a few on-off cycles with a few shots.
The second time by disabling CHDK, starting the camera, play, menu, delete all, re-enable CHDK.
Since then, I have not deleted individual images and the problem has not returned. That was 4 days, 250ish photos and 30 videos ago, with a mix of shooting occasions (beach, pool, sea, above water, underwater, video, single/manual/servo focus, scripts, flash on/off)

Quote from: BlinkTooFast
# Enable Optical Zoom in video appears to have no effect regardless whether digital zoom is on or off.
Again from the first post:
Quote
Not implemented/Not Working
- movie_rec: meaning all movie related functions
Oops. My apologies. The sun has got to my head!

Thank you very much again

BlinkTooFast

*

Offline reyalp

  • ******
  • 13400
Re: D10 porting thread
« Reply #43 on: 25 / July / 2010, 01:20:34 »
Multi-partition added, new builds in first post.

Quote from: BlinktooFast
I am using Adobe DNG conv then RawShooter for the Raws. I have a gentle shadow around the edge of many of the images. I crop anyway, so not much of an issue.

This is also mentioned in the first post:
Quote
- DNG has dark borders. This is intentional, the active area covers all pixels that have any data, but there are large areas which have data but are distinct from the normal jpeg area.
DNG spec isn't really clear what to do here. However, the shadow area does have image data in it. My feeling is that most people will just crop it, but in a pinch, having those extra pixels to salvage in photoshop might come in handy.
Don't forget what the H stands for.


*

Offline reyalp

  • ******
  • 13400
Re: D10 porting thread
« Reply #44 on: 25 / July / 2010, 23:51:23 »
ibangpots:

Setting Tv from script works for me. For example, the following Lua script run in P mode produces images with 1/30th, 1/60th and 1/125th exposure as expected. The difference in exposure are plainly visible, and the expected Tv values are recorded in the exif.

Code: [Select]
for i=1,3 do
set_tv96_direct(384+96*i) -- APEX 4 + i stops
shoot()
end
I suggest using _direct, as regular set_tv96 will only accept values that correspond to the stops the canon firmware official stops.
Don't forget what the H stands for.

Re: D10 porting thread
« Reply #45 on: 26 / July / 2010, 06:02:01 »
Quote
- DNG has dark borders. This is intentional, the active area covers all pixels that have any data, but there are large areas which have data but are distinct from the normal jpeg area.
DNG spec isn't really clear what to do here. However, the shadow area does have image data in it. My feeling is that most people will just crop it, but in a pinch, having those extra pixels to salvage in photoshop might come in handy.
But not all my DNGs have this shadow, so please do not make any effort to autocrop them. I have noticed that the images with a shadow report f2.8. The images without a shadow report f3.8 or higher, suggesting the ND filter was in. I really ought to try something more systematic to ground this once and for all.
However, I do not favour the ND for two reasons - it either increases ISO or shutter time, and images taken with it appear less contrasty with rather washed out blacks. This is even more noticeable if sunlight catches the lens.
I am tempted to use CHDK to permanently leave it open.

Dark border
« Reply #46 on: 27 / July / 2010, 01:10:45 »
Ah-ha!
The ND filter has nothing to do with the dark borders. I forgive it. In/out makes no difference.
The dark border is zoom dependent. I took five images focused on the same item with focal lengths 6, 7, 10, 14, 19mm. The dark border only shows up with the 6mm focal length. (Yes, optical. No, not digital - it's RAW!)
So what does this mean for us?
Well, by applying the smallest amount of zoom (6mm to 7mm is the smallest change I can make), we can avoid the dark border. This gives us a less wide wide-end, a small amount of which we would crop anyway. Worth noting that we would lose much more than we would crop, so not necessarily recommended.
Otherwise, I don't know.
Maybe someone will point out how to make tiny changes in focal length that fixes the problem.
Maybe someone will write an override that changes the new minimum focal length.

More fiddling today, I suspect. Fair chance that I will find CHDK can already achieve some of the above!

*

Offline fe50

  • ******
  • 3132
  • IXUS50 & 860, SX10 Star WARs-Star RAWs
    • fe50
Re: D10 porting thread
« Reply #47 on: 27 / July / 2010, 01:17:22 »
I have noticed that the images with a shadow report f2.8. The images without a shadow report f3.8 or higher, suggesting the ND filter was in.
The ND filter only swaps between the lowest ( F/2.8 ) and the highest ( e.g. F/8 ) F-stop; steps between, like F/3.8, are the result of the optical zoom...


Battery limit values
« Reply #48 on: 31 / July / 2010, 18:42:42 »
Hope this is of use to someone.

Max 4.118V
Min 3.235V

If I fully charge my battery, remove from the charger, wait 5 minutes, then put it in the camera, max voltage is 4.118V.

If I then switch to movie mode, full time IS, full screen brightness, and take a video until the battery runs out, the battery runs down to 3.235V (and I pulled the battery everytime it reached 45C to let it cool down, then reinserted and continued filming)

*

Offline reyalp

  • ******
  • 13400
Re: D10 porting thread
« Reply #49 on: 31 / July / 2010, 19:36:42 »
The camera shuts down at 3.235 ?
Don't forget what the H stands for.

 

Related Topics