Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - cbob

#1
Tragic Lantern / Re: 7D Raw Thread
October 22, 2013, 10:01:52 AM
Quote from: 1% on October 21, 2013, 05:40:57 PM
Heheh, I had 2 cars where the hand/parking brake disintegrated. I didn't need it. Disc brakes are pneumatic, they still work and their chances of failure are lower than the cheap drum brake...

Hydraulic! ...and though the chances of failure may be lower or higher, it's the diversity (of actuation and operation) that'll save your hide some day.  ;)
#2
Interesting idea!

My understanding of phase detection is that it works on edges/differences in the incident light. If so, it's unlikely that the dual-pixel AF will return a 100% populated Z map (per-pixel distance to target) that you could use for creating a synthetic shallow DOF. There are methods to fill in a sparse Z map but not without their own downsides.

Bear in mind that the effect of a shallow DOF is more than a simple Z-dependant Gaussian blur, particularly illustrated by the tendency for highlights to blow out.
#3
General Development / Re: Flexible info screen
May 27, 2013, 02:00:38 AM
I see what you mean about the GB postfix. I've updated the code and pull request. GB is anchored to the right of the self-centered free space. The INFO_STRING with GB included is no longer present.

I still can't see how to properly center Kelvin (or free photos) when it's padded with %Xd though. The raw Kelvin value can be 4 or 5 chars long, but the %5d means the centering routine always centers for 5 chars and the text is only properly centered for > 10,000 K?
#4
General Development / Re: Flexible info screen
May 27, 2013, 01:17:09 AM
I enabled flexinfo for the 550D: clock, free space, MLU, kelvin and bracketing.

Pull request: https://bitbucket.org/hudson/magic-lantern/pull-request/97/added-550d-flexinfo/diff



The clock is restored at the same font/position as before, but the other items have moved. I particularly like the new free space display.

A few comments/questions about flexinfo:

1) It's very flexible(!) and works great, but perhaps allows too much scope for making ML look entirely different on each model.

Just from the code, it's difficult to visualise how other camera models look without having familiarity/access to such bodies. e.g. the 7D seems to have a very complete flexinfo, including colours, but I have no idea how those features sit within the Canon 7D info screen. Making the 550D look consistent with that was impossible for me.

2) I presume the platform-specific X, Y coordinates defines can now be magic numbers in flexinfo.c rather than platform/consts.h? Lines from the platform-specific code islands at the top of flexinfo.c can never be shared between models anyway due to the need to hard code anchor references.

3) I added replications of some 7D info string types, with different padding and postfix (GB). Doing this could result in a lot of replicated code to suit different models. There's probably a better way to do this?