the focus terms or sequences
Hi Laurent,
I heard of that there was a chance between you and Sylwester telling about the menu entries focus, and so after that, probably this menu style of the patch I sent, need to be more upgraded. So, can you tell me the kind or sequence of the UVC device breifly?
I guess the word *AUTO* at the UVC device means doing focus continuously, not once or one time. But, at the sensors I used the *AUTO* focus means doing focus once, on the other hand *CONTINUOUS* means doing continuously. So, we need to be clear terms about focus.
At the sensor I used, the focus needs 3 kinds of commands:
1) setting mode
: it makes the lens initial position for each AF(Normal, Continuous, Night mode Focus, etc),
and set the AF status Idle.
2) execute AF
: doing the move of the lens
3) read AF status
: checking the lens status(Focus failed, Focus success, Idle, Busy)
and do the proper jobs.
I don't know uvc case well, so, If you share about this, it can be help.
Thanks,
Heungjun Kim
Hi HeungJun,
Quoted 9 lines · HeungJun
Hi Laurent,
I heard of that there was a chance between you and Sylwester telling about the menu entries focus, and so after that, probably this menu style of the patch I sent, need to be more upgraded. So, can you tell me the kind or sequence of the UVC device breifly?
I guess the word *AUTO* at the UVC device means doing focus continuously, not once or one time.
That's correct. In the UVC context, auto focus means CAF and manual focus means... well, manual focus :-)
Quoted 15 lines
But, at the sensors I used the *AUTO* focus means doing focus once, on the other hand *CONTINUOUS* means doing continuously. So, we need to be clear terms about focus.
At the sensor I used, the focus needs 3 kinds of commands:
1) setting mode: it makes the lens initial position for each
AF(Normal, Continuous, : Night mode Focus, etc),and set the AF status Idle.
2) execute AF: doing the move of the lens
Quoted 7 lines
3) read AF status
: checking the lens
status(Focus failed, Focus success, Idle, Busy)and do the proper jobs.
I don't know uvc case well, so, If you share about this, it can be help.
What bothers me with your auto-focus implementation is that the user might want to perform auto-focus several times. Let's imagine this use case:
1. The user points the camera (webcam, cellphone camera, digital camera, it doesn't matter) at an object.
2. The user presses a button to perform singleshot auto-focus (it can be a physical button or a button on the camera screen, once again it doesn't matter).
3. The application sets the focus control to AUTO.
4. The driver and device perform auto-focus once. The lens is moved so that the object is in focus.
5. The user points the camera at another object.
6. The user presses a button to perform singleshot auto-focus.
7. The applications sets the focus control to AUTO. As the focus control value was already AUTO, nothing is done.
This is clearly broken. That's why we need a V4L2 button control in addition to the menu control.
Signature · 3 lines
Regards, Laurent Pinchart
Hi Laurent,
First, I hope to be good at the warsaw meeting. :)
2011-03-16 오전 9:14, Laurent Pinchart 쓴 글:
Quoted 56 lines
Hi HeungJun,
Quoted 9 lines · HeungJun
Hi Laurent,
I heard of that there was a chance between you and Sylwester telling about the menu entries focus, and so after that, probably this menu style of the patch I sent, need to be more upgraded. So, can you tell me the kind or sequence of the UVC device breifly?
I guess the word *AUTO* at the UVC device means doing focus continuously, not once or one time.
That's correct. In the UVC context, auto focus means CAF and manual focus means... well, manual focus :-)
Quoted 15 lines
But, at the sensors I used the *AUTO* focus means doing focus once, on the other hand *CONTINUOUS* means doing continuously. So, we need to be clear terms about focus.
At the sensor I used, the focus needs 3 kinds of commands:
1) setting mode: it makes the lens initial position for each
AF(Normal, Continuous, : Night mode Focus, etc),and set the AF status Idle.
2) execute AF: doing the move of the lens
Quoted 7 lines
3) read AF status
: checking the lens
status(Focus failed, Focus success, Idle, Busy)and do the proper jobs.
I don't know uvc case well, so, If you share about this, it can be help.
What bothers me with your auto-focus implementation is that the user might want to perform auto-focus several times. Let's imagine this use case:
1. The user points the camera (webcam, cellphone camera, digital camera, it doesn't matter) at an object.
2. The user presses a button to perform singleshot auto-focus (it can be a physical button or a button on the camera screen, once again it doesn't matter).
3. The application sets the focus control to AUTO.
4. The driver and device perform auto-focus once. The lens is moved so that the object is in focus.
5. The user points the camera at another object.
Quoted 8 lines
6. The user presses a button to perform singleshot auto-focus.
7. The applications sets the focus control to AUTO. As the focus control value was already AUTO, nothing is done.
This is clearly broken. That's why we need a V4L2 button control in addition to the menu control.
Yes. Youre'rignt. The menu control dosen't called one more with the same value. It's now worked I know. But, the reason why I choose menu type for focus, is because the menu type can let the user-application know how many kinds of focus this sensor have & support, using querymenu. The only way letting know, is currently the menu type.
On the other hand, not-working twice or more executions is handled by user-application. The user-application want twice auto focus, it calls AUTO-Manual-(or any other control value)-and AUTO once again. It's wierd, but It can satisfy application and drivers.
And, but it might be irrelevant, the user-application(or upper layer platform) can determine how to draw & arrange the UI objects after it knows the kinds of focus method at last.
It may be a time to need another type of control. And such control should satisfy these:
1. letting the user-application know how many kinds in the controls(like a querymenu)
2. being available to be called one more.
How about your opinion?
Regards,
Heungjun Kim
Hi,
Quoted 1 line · HeungJun
2011-03-16 오전 9:14, Laurent Pinchart 쓴 글:
[snip]
Quoted 41 lines
Quoted 18 lines
What bothers me with your auto-focus implementation is that the user might want to perform auto-focus several times. Let's imagine this use case:
1. The user points the camera (webcam, cellphone camera, digital camera, it doesn't matter) at an object.
2. The user presses a button to perform singleshot auto-focus (it can be a physical button or a button on the camera screen, once again it doesn't matter).
3. The application sets the focus control to AUTO.
4. The driver and device perform auto-focus once. The lens is moved so that the object is in focus.
5. The user points the camera at another object.
Quoted 7 lines
6. The user presses a button to perform singleshot auto-focus.
7. The applications sets the focus control to AUTO. As the focus control value was already AUTO, nothing is done.
This is clearly broken. That's why we need a V4L2 button control in addition to the menu control.
Yes. Youre'rignt. The menu control dosen't called one more with the same value. It's now worked I know. But, the reason why I choose menu type for focus, is because the menu type can let the user-application know how many kinds of focus this sensor have & support, using querymenu. The only way letting know, is currently the menu type.
On the other hand, not-working twice or more executions is handled by user-application. The user-application want twice auto focus, it calls AUTO-Manual-(or any other control value)-and AUTO once again. It's wierd, but It can satisfy application and drivers.
And, but it might be irrelevant, the user-application(or upper layer platform) can determine how to draw & arrange the UI objects after it knows the kinds of focus method at last.
Quoted 5 lines
It may be a time to need another type of control. And such control should satisfy these: 1. letting the user-application know how many kinds in the controls(like a querymenu) 2. being available to be called one more.
How about your opinion?
I think we need a menu control (to select the focus type) and a button control (to run singleshot auto-focus). When the menu control is in auto-focus mode, setting the button control will run the auto-focus algorithm once.
Is the macro focus mode a singleshot focus or a continuous auto-focus ?
Signature · 3 lines
Regards, Laurent Pinchart
2011. 3. 16., 오후 11:15, Laurent Pinchart 작성:
Quoted 52 lines
Hi,
Quoted 1 line · HeungJun
2011-03-16 오전 9:14, Laurent Pinchart 쓴 글:
[snip]
Quoted 45 lines
Quoted 18 lines
What bothers me with your auto-focus implementation is that the user might want to perform auto-focus several times. Let's imagine this use case:
1. The user points the camera (webcam, cellphone camera, digital camera, it doesn't matter) at an object.
2. The user presses a button to perform singleshot auto-focus (it can be a physical button or a button on the camera screen, once again it doesn't matter).
3. The application sets the focus control to AUTO.
4. The driver and device perform auto-focus once. The lens is moved so that the object is in focus.
5. The user points the camera at another object.
Quoted 7 lines
6. The user presses a button to perform singleshot auto-focus.
7. The applications sets the focus control to AUTO. As the focus control value was already AUTO, nothing is done.
This is clearly broken. That's why we need a V4L2 button control in addition to the menu control.
Yes. Youre'rignt. The menu control dosen't called one more with the same value. It's now worked I know. But, the reason why I choose menu type for focus, is because the menu type can let the user-application know how many kinds of focus this sensor have & support, using querymenu. The only way letting know, is currently the menu type.
On the other hand, not-working twice or more executions is handled by user-application. The user-application want twice auto focus, it calls AUTO-Manual-(or any other control value)-and AUTO once again. It's wierd, but It can satisfy application and drivers.
And, but it might be irrelevant, the user-application(or upper layer platform) can determine how to draw & arrange the UI objects after it knows the kinds of focus method at last.
It may be a time to need another type of control. And such control should satisfy these: 1. letting the user-application know how many kinds in the controls(like a querymenu) 2. being available to be called one more.
Quoted 5 lines
Quoted 1 line
How about your opinion?
I think we need a menu control (to select the focus type) and a button control (to run singleshot auto-focus). When the menu control is in auto-focus mode, setting the button control will run the auto-focus algorithm once.
Ah. it's very reasonable. When the focus mode keeps the menu type, and doing focus is button type, even if another new mode is needed to insert, we can add easily. I agree with this.
But, the drivers using focus like uvc, should be changed. And we should probably consider the cluster between focus mode and execution. is it right?
Quoted 2 lines
Is the macro focus mode a singleshot focus or a continuous auto-focus ?
Of course. yes.
I'll make another patch about this, and could you look around this?
Thanks,
Heungjun Kim
Quoted 58 lines · On Wednesday 16 March 2011 16:17:30 Kim HeungJun wrote:
2011. 3. 16., 오후 11:15, Laurent Pinchart 작성:
Quoted 50 lines · HeungJun
Quoted 1 line
2011-03-16 오전 9:14, Laurent Pinchart 쓴 글:
[snip]
Quoted 46 lines
Quoted 18 lines
What bothers me with your auto-focus implementation is that the user might want to perform auto-focus several times. Let's imagine this use case:
1. The user points the camera (webcam, cellphone camera, digital camera, it doesn't matter) at an object.
2. The user presses a button to perform singleshot auto-focus (it can be a physical button or a button on the camera screen, once again it doesn't matter).
3. The application sets the focus control to AUTO.
4. The driver and device perform auto-focus once. The lens is moved so that the object is in focus.
5. The user points the camera at another object.
Quoted 7 lines
6. The user presses a button to perform singleshot auto-focus.
7. The applications sets the focus control to AUTO. As the focus control value was already AUTO, nothing is done.
This is clearly broken. That's why we need a V4L2 button control in addition to the menu control.
Yes. Youre'rignt. The menu control dosen't called one more with the same value. It's now worked I know. But, the reason why I choose menu type for focus, is because the menu type can let the user-application know how many kinds of focus this sensor have & support, using querymenu. The only way letting know, is currently the menu type.
On the other hand, not-working twice or more executions is handled by user-application. The user-application want twice auto focus, it calls AUTO-Manual-(or any other control value)-and AUTO once again. It's wierd, but It can satisfy application and drivers.
And, but it might be irrelevant, the user-application(or upper layer platform) can determine how to draw & arrange the UI objects after it knows the kinds of focus method at last.
It may be a time to need another type of control. And such control should satisfy these: 1. letting the user-application know how many kinds in the controls(like a querymenu) 2. being available to be called one more.
Quoted 6 lines
Quoted 1 line
How about your opinion?
I think we need a menu control (to select the focus type) and a button control (to run singleshot auto-focus). When the menu control is in auto-focus mode, setting the button control will run the auto-focus algorithm once.
Quoted 7 lines
Ah. it's very reasonable. When the focus mode keeps the menu type, and doing focus is button type, even if another new mode is needed to insert, we can add easily. I agree with this.
But, the drivers using focus like uvc, should be changed. And we should probably consider the cluster between focus mode and execution. is it right?
UVC only has manual focus and CAF. A menu control will be enough, we don't need an additional button control as singleshot AF isn't standardized by UVC.
Quoted 3 lines
Quoted 1 line
Is the macro focus mode a singleshot focus or a continuous auto-focus ?
Of course. yes.
Which one ? Singleshot ? Or CAF ?
Quoted 1 line
I'll make another patch about this, and could you look around this?
Sure.
Signature · 3 lines
Regards, Laurent Pinchart
Hi,
2011. 3. 17., 오전 12:27, Laurent Pinchart 작성:
Quoted 5 lines · On Wednesday 16 March 2011 16:17:30 Kim HeungJun wrote:
Quoted 4 lines
2011. 3. 16., 오후 11:15, Laurent Pinchart 작성:
Quoted 3 lines · HeungJun
Quoted 1 line
2011-03-16 오전 9:14, Laurent Pinchart 쓴 글:
[snip]
[snip]
Quoted 5 lines
Quoted 3 lines
Quoted 1 line
Is the macro focus mode a singleshot focus or a continuous auto-focus ?
Of course. yes.
Which one ? Singleshot ? Or CAF ?
I mean Singleshot :)
Regards,
Heungjun Kim