Closed beny closed 3 years ago
I've seen that simple message Error.
when imagesnap can't write to its output directory. What happens if you simply redirect it to your home dir, as in imagesnap ~/test.jpg
?
I don't experience this same behavior. In addition, with the code included in https://github.com/rharder/imagesnap/pull/13, I have it running successfully in OS X El Capitan. Are you still experiencing this issue?
No issues here. Think this issue should be closed.
I noticed something similar under OS X 10 when connecting my laptop to a monitor. Running
imagesnap -l
did not show any devices. Once I started and stopped FaceTime, it showed
"FaceTime HD Camera (Built-in)"
.
I had this same issue on El Capitan MBA 2012.
Running this command solved the problem without any restart:
sudo killall VDCAssistant
I ran into
2018-04-10 12:47:34.987609+0200 imagesnap[31620:6736480] [General] *** -[AVCaptureStillImageOutput captureStillImageAsynchronouslyFromConnection:completionHandler:] Inactive/invalid connection passed
and @carleryd's command solved the problem
Simply calling
imagesnap
returns error