Cases 1 and 2 alternate very consistently over runs. One time it will work, the next time it will fail, etc.
Configuration: MacOS 10.7.5 with iSight/Facetime camera using Processing
Do you think it would help if we would light up the sphere not in white but in some other color? To avoid having the white balance destroy the colors?
We should try to run unlockForConfiguration at startup to avoid the current values to be carried on to the next run.
We can try the color thing too. Blue seems to be the most powerful.
I'll be happy to try both if you give me some directions.
All this does not account for the slower blinking though, does it?
So it ends up it was really a problem with not unlocking the auto-exposure at startup. I tried it again, doing an unlockForConfiguration between each run* and everything went fine.
It also means that this and issue #34 are two different problems.
*I used the small test program I made in cocoa which does the unlockForConfiguration when you launch it (here's the app if you want to do some tests: https://docs.google.com/open?id=0B4qt2CFBOa6VZV9yS28tQkxBbG8)
We should then unlock at shutdown (if possible) and unlock at startup to be safe.
On my system (MacBookPro5,5) it seems like once I lock the exposure, it isn't possible to unlock it until I reboot the machine. Also, locking the exposure for me means that whenever the camera device is opened, the exposure is determined, and then it's fixed until the camera device is closed again - is this the case for you too?
On my MacBookPro8,2, I can unlock the exposure anytime. Maybe it's a hardware difference between the older iSight cameras and the Facetime camera on more recent macs. We would need to test it on more computers to be sure.
I just did some tests with locked exposure in Photo Booth and Skype. Interestingly enough, Skype does the unlock when you launch a capture session (for example, by going in the audio/video section of the preferences) while Photo Booth doesn't. It's good to know for testing purposes.
When I launch Photo Booth with the lock active, I get a low exposure that does not depend on the lighting conditions at the opening of the device. No matter how I cover the lens or direct a flashlight to the camera while I launch the app, the setting stays the same. This seems to be another difference and can explain the particular issue we are dealing with here.
In a nutshel: easy fix for recent macs (unlockForConfiguration at launch). Not a problem on older macs.
What about this issue? Is it related to #53? Can you provide a patch for recent Macs (unlockForConfiguration) that I can apply? I don't think I have a recent enough Mac to test/fix this :)
It's not related to #53. I'm testing and will submit a patch if I manage to fix it.
Pull request #65 fixes this issue.
Fixed by merging pull request #65. Thanks :)