Idea for Microfocus adjustment
OrhCh
Straight to the point :) I read here http://magiclantern.wikia.com/wiki/Unified/Vote_for_Features
that on this stage Microfocus adjust will not be developed as a
feature of Magic Lantern.
If it can't be realized as Canon did it in 50D, 7D why not trying it
so:
A menu entry in which you can set 1, 2, 3, ... focus steps (far or
close). This steps, if enabled, will be triggered automatically after
the standard focus confirmation or by a button if it is not possible
to make it automatically.
In theory it must work this way. You focus the standard way and after
the confirmation Magic Lantern moves the focus X steps (as set) and
then you take the shot. Again, if Magic Lantern can't move the focus
automatically this action can be assigned to a button.
Standard focus --->ML adjusts the focus as set (automatically or via
button) --->You take the shot.
Hope I explained the idea clear enough and the developers see
potential in it. I read a lot of Canon shooters are plagued by Back/
Front focus issues and if implemented this feature will help many.
Thanks for your time!
Alex
adjust is not needed.
If you need it in LiveView, you can try follow focus after a quick
focus attempt.
> --
> http://magiclantern.wikia.com/
>
> To post to this group, send email to ml-d...@googlegroups.com
> To unsubscribe from this group, send email to ml-devel+u...@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/ml-devel?hl=en
OrhCh
Sad that LiveView is not practical for me, too slow :(
I guess I will have to learn to adjust the focus manually after the
auto focus does its thing (Canon 50mm f 1.4) or some sunny day Canon
will release a firmware update with this function for the 60D.
On Oct 23, 2:38 pm, Alex <broscutama...@gmail.com> wrote:
> Magic Lantern can only control focus in LiveView, where microfocus
> adjust is not needed.
>
> If you need it in LiveView, you can try follow focus after a quick
> focus attempt.
>
>
>
>
>
>
>
> On Sun, Oct 23, 2011 at 10:07 AM, OrhCh <orhan...@gmail.com> wrote:
> > Hi there,
>
Colin Peart
OrhCh
On Oct 26, 3:48 pm, Colin Peart <cgape...@gmail.com> wrote:
> Don't hold your breath for a firmware update from canon. They don't
> typically provide firmware updates that add features when they can try to
> sell you a new camera instead ;)
>
> Colin Peart
Peter Scharff
Just thinking aloud here, but could ml somehow send ptp commands to the camera so you could get microfocus adjustment without liveview alex ?
Andrew Coutts
50d, in an attempt to use it on the 500d. There is some functionality
in the firmware for microadjustments, but i think the property is
inert / not used. Here are some strings from a search in the console:
(500d v1.1.1 firmware):
In [7]: s afshift
ff3c0ca0: 'UpdateAfShiftForMnCustomFn'
ff092534: 'MasterResultCBR_DefaultAfShift(0x%x)'
ff092e70: '***** GUI_SetDefaultAfShift handle NULL'
ff359edc: 'Illegal Data SetCFnDetailDataForAfShift (%d)'
ff34a008: 'PlayUtility AfShift Value Max Over!!!(%d)'
ff3bef38: '***** SetAfShiftDataToWinSystem: unknown No(%d)'
Basically everything is there except the winsystem functions aren't
implemented (for menu stuff). But - I dont' yet understand how it
works on the 50d enough to try to change it on the 500d.
Andrew Coutts
of framework missing (looks like 500d was compiled without afshift.c
from canon :/ ):
In [16]: s afshift
ffba02a8: 'StartMnCustomFnAfShiftApp'
ffba02c4: '***** StartMnCustomFnAfShiftApp '
ffba02ec: '***** StartMnCustomFnAfShiftApp CreateDialogBox(%#x)'
ffba0328: 'DlgMnCustomFnAfShift.c PROP_ICU_UILOCK(0x%x)'
ffba0390: '***** DlgMnCustomFnAfShift.c GUI_LOCKED(0x%x)'
ffba035c: 'DlgMnCustomFnAfShift.c GUI_RequestGetAllLensName'
ffbc4254: 'UpdateAfShiftForMnCustomFn'
ff88a9f4: 'MasterResultCBR_DefaultAfShift(0x%x)'
ff88b344: '***** GUI_SetDefaultAfShift handle NULL'
ffb39264: 'Illegal Data SetCFnDetailDataForAfShift CfnNo(%d)'
ffb39234: 'Illegal Data SetCFnDetailDataForAfShift (%d)'
ffb9f168: '***** DlgMnCustomFnAfShift.c AllocateMemory(%x)'
ffb9f560: 'DlgMnCustomFnAfShift.c PROP_CURRENT_LENS_NAME
add[%#x]size[%d]'
ffb9f0f0: 'StopMnCustomFnAfShiftApp'
ffb9f114: 'GUI\\Menu\\DlgMnCustomFnAfShift.c'
ffb9f138: '***** DlgMnCustomFnAfShift.c pAllLensName(%x)'
ffb9f198: 'DlgMnCustomFnAfShift.c PROP_CFN_TAB3 add[%#x]size[%d]'
ffb9fdf0: 'DlgMnCustomFnAfShift.c PRESS_SET_BUTTON'
ffb9fe18: 'DlgMnCustomFnAfShift.c ROTATE_ELECTRONIC_SUB_DIAL'
ffb9facc: 'DlgMnCustomFnAfShift.c IDC_DBN_DISABLE/LENS/ALL'
ffb9fb00: 'DlgMnCustomFnAfShift.c DELETE_DIALOG_REQUEST'
ffb9fd70: 'DlgMnCustomFnAfShift.c TERMINATE_WINSYS'
ffb9fd98: 'DlgMnCustomFnAfShift.c PRESS_INFO_BUTTON'
ffb9fdc4: 'DlgMnCustomFnAfShift.c PRESS_MENU_BUTTON'
ffb9fe4c: 'DlgMnCustomFnAfShift.c PRESS_ERASE_BUTTON'
OrhCh
Yesterday I tested my camera with three more lenses and this confirmed
my back focus issues :(
A lot of people like me out there :( Hope some fix for this comes out
some day.
Sam
first step is a property but then I think it goes out over SIO3
(AJ_dw_Size_TXBD_data_size in 5d2)? Presumably there's another CPU
doing AF stuff.
Cheers,
Sam.
Alex
- electronic level (I can see the values of
PROP_ROLLING_PITCHING_LEVEL by watching the data received by SIO3_ISR
and MREQ_ISR)
- raw button codes (the same, but I have no idea how to decode or block them)
Sam
running on this other CPU. If it's doing AF it seems likely.
Sam
diff them - http://canoncanada.custhelp.com/app/answers/detail/a_id/17664/~/service-notice%3A-eos-1d-mark-iv%3A-firmware-1.0.6
Sam
AF CPU - http://cpn.canon-europe.com/content/news/eos_mark_iv_550d_firmware.do
On Oct 28, 1:28 pm, Sam <sam87549...@live.com> wrote:
> If anybody has the 1d4 1.0.4 and 1.0.6 FWs it might be interesting to
Andrew Coutts
lenses. There's gotta be some database of some sort somewhere
containing the different configurations for different lenses.
On Oct 28, 9:56 am, Sam <sam87549...@live.com> wrote:
> There's a chance that the 550d 1.0.8 update changed something on the
arm.indy
On Oct 28, 1:28 pm, Sam <sam87549...@live.com> wrote:
> If anybody has the 1d4 1.0.4 and 1.0.6 FWs it might be interesting to
> diff them -http://canoncanada.custhelp.com/app/answers/detail/a_id/17664/~/servi...
>
> On Oct 28, 1:20 pm, Sam <sam87549...@live.com> wrote:
>
>
>
>
>
>
>
> > I wonder if there have been any FW updates that change the code
> > running on this other CPU. If it's doing AF it seems likely.
>
> > On Oct 28, 1:15 pm, Alex <broscutama...@gmail.com> wrote:
>
> > > I believe there's a second CPU overSIO3, which also handles (among others):
arm.indy
http://groups.google.com/group/ml-devel/browse_frm/thread/60ba655554088550/3ca242ce075ef557
and
http://groups.google.com/group/ml-devel/browse_frm/thread/f813fe19f9c9813d/7b966debae9dc2e4
On Oct 28, 9:30 pm, Andrew Coutts <andrewjohncou...@gmail.com> wrote:
> I noticed that it seems to make or add properties or something for new
> lenses. There's gotta be some database of some sort somewhere
> containing the different configurations for different lenses.
>
> On Oct 28, 9:56 am, Sam <sam87549...@live.com> wrote:
>
>
>
>
>
>
>
> > There's a chance that the 550d 1.0.8 update changed something on the
> > AF CPU -http://cpn.canon-europe.com/content/news/eos_mark_iv_550d_firmware.do
>
> > On Oct 28, 1:28 pm, Sam <sam87549...@live.com> wrote:
>
> > > If anybody has the 1d4 1.0.4 and 1.0.6 FWs it might be interesting to
> > > diff them -http://canoncanada.custhelp.com/app/answers/detail/a_id/17664/~/servi...
>
> > > On Oct 28, 1:20 pm, Sam <sam87549...@live.com> wrote:
>
> > > > I wonder if there have been any FW updates that change the code
> > > > running on this other CPU. If it's doing AF it seems likely.
>
> > > > On Oct 28, 1:15 pm, Alex <broscutama...@gmail.com> wrote:
>
> > > > > I believe there's a second CPU overSIO3, which also handles (among others):