rharder/imagesnap

Images extremely dark on new Mac Air Mid 2013s A1466

Closed this issue ยท 9 comments

Camera works fine in photobooth, but command line shots that are dark. If theres tons of light they sort of come out, but are still very dark. I'm guessing some sort of iso setting is now available and needs to be set during capture?

Macosx 10.8 Build 12E3067

imagesnap

Photobooth

Checked on a friends machine, A1369 Mac with 10.8.4 12E55 takes fine images...So it doesnt appear to be a 10.8 api change... but hardware maybe?

OK. Looks like you NEED to use -w 2 at least for a white balance check

blah-1
blah-2
blah-3
blah-point5

Thanks @zgiles!

I am experiencing the same problem. -w 2 does fix it.
Mac Book Pro Mid 2014 with the FaceTime HD Camera.
Mac OS X 10.10.1 (Yosemite)

Thankyou so much for this!! I was having the same problem

Happening here too... Mavericks, brew installed, total blackness... odd thing is, when I clamped the luminosity in Photoshop, I noticed white specks appearing on what should've been NOTHING.

What was actually going on in the picture:

This wouldn't be so confusing if there were actually reflective surfaces behind me...

I won't be sleeping tonight.

Wait, sorry... I realised what the white specks were... they were just the (extremely dull) sheen of metallic bolts under my shelf. Makes sense now.

Also, my hair looks fucking FABULOUS. New display pic.

In a perfect world this would have been some slenderman shit that went on
for weeks. Shame on you for solving it so quick :)

On Tue, Jun 21, 2016 at 1:00 AM, John Gardner notifications@github.com
wrote:

Wait, sorry... I realised what the white specks were... they were just the
(extremely dull) sheen of metallic bolts under my shelf. Makes sense now.

Also, my hair looks fucking FABULOUS. New display pic.

โ€”
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#4 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AAb0dF8yaZb4s3gXHbpIu4J6JCS_fKmrks5qN5ougaJpZM4A6G2k
.

Qix- commented

Sorry to gravedig but -w 2 did indeed solve this for me as well.

Perhaps it should be the default?

v0.2.14 (finally) makes a wait of 3 seconds the default.