Similar colors get mixed up with Facetime calibration (3 controllers) #34

Open
SableRaf opened this Issue Nov 5, 2012 · 5 comments

Comments

2 participants
@SableRaf
Contributor

SableRaf commented Nov 5, 2012

Colors that are too close get mistaken for one another by the tracker. This is probably due to the exposure lock altering the colors.

See video: https://docs.google.com/open?id=0B4qt2CFBOa6VSlJ1ZHNxNGZPWjg

@thp

This comment has been minimized.

Show comment Hide comment
@thp

thp Nov 6, 2012

Owner

Maybe one option could be to use a specific color instead of white during exposure lock calibration. The problem here is that the exposure lock mechanism is still a hack, and OS X should ideally allow us to set the exposure manually without tweaking the hue(?), just like the Linux and Windows drivers do.

Owner

thp commented Nov 6, 2012

Maybe one option could be to use a specific color instead of white during exposure lock calibration. The problem here is that the exposure lock mechanism is still a hack, and OS X should ideally allow us to set the exposure manually without tweaking the hue(?), just like the Linux and Windows drivers do.

@SableRaf

This comment has been minimized.

Show comment Hide comment
@SableRaf

SableRaf Nov 9, 2012

Contributor

«OS X should ideally allow us to set the exposure manually without tweaking the hue(?), just like the Linux and Windows drivers do»

I don't believe that's ever happening unfortunately, or at least, we should not count on it. FaceTime/iSight camera will probably stay more limited than PSeye (lower controller count, awkward calibration) but it's better to have that than nothing. Maybe we will get PSeye support on macOS and then internal camera could be used for development purposes and less demanding applications whereas the PSeye will be required for full featured PS Move support. What do you think?

Contributor

SableRaf commented Nov 9, 2012

«OS X should ideally allow us to set the exposure manually without tweaking the hue(?), just like the Linux and Windows drivers do»

I don't believe that's ever happening unfortunately, or at least, we should not count on it. FaceTime/iSight camera will probably stay more limited than PSeye (lower controller count, awkward calibration) but it's better to have that than nothing. Maybe we will get PSeye support on macOS and then internal camera could be used for development purposes and less demanding applications whereas the PSeye will be required for full featured PS Move support. What do you think?

@SableRaf

This comment has been minimized.

Show comment Hide comment
@SableRaf

SableRaf Nov 9, 2012

Contributor

«Maybe one option could be to use a specific color instead of white during exposure lock calibration.»

Possibly. Also, a good way to ensure color consistency over runs would be to sample the image and wait for the right color/brightness to come up before we lock the exposure (and white balance?). That would make debugging easier as we would have the same exact configuration each time.

Contributor

SableRaf commented Nov 9, 2012

«Maybe one option could be to use a specific color instead of white during exposure lock calibration.»

Possibly. Also, a good way to ensure color consistency over runs would be to sample the image and wait for the right color/brightness to come up before we lock the exposure (and white balance?). That would make debugging easier as we would have the same exact configuration each time.

@thp

This comment has been minimized.

Show comment Hide comment
@thp

thp Nov 10, 2012

Owner

By the way, is this a duplicate of issue #33? Seems like they are caused by the same root cause?

Owner

thp commented Nov 10, 2012

By the way, is this a duplicate of issue #33? Seems like they are caused by the same root cause?

@SableRaf

This comment has been minimized.

Show comment Hide comment
@SableRaf

SableRaf Nov 10, 2012

Contributor

It was not supposed to be a duplicate. I cannot say much about the root cause. It is still a bit fuzzy to me.

Contributor

SableRaf commented Nov 10, 2012

It was not supposed to be a duplicate. I cannot say much about the root cause. It is still a bit fuzzy to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment