New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2 cameras on the compute module?! #84

Closed
waveform80 opened this Issue Apr 15, 2014 · 3 comments

Comments

Projects
None yet
1 participant
@waveform80
Owner

waveform80 commented Apr 15, 2014

Apparently the compute module can support 2 cameras - when they're available, buy one and test it with picamera

@waveform80 waveform80 added the task label Apr 15, 2014

@waveform80

This comment has been minimized.

Owner

waveform80 commented May 3, 2014

At the very least we're going to need to remove the stuff that guards against creating two instances of PiCamera. I think the firmware guards against lockups related to this now so this is probably safe to do - test it?

@waveform80

This comment has been minimized.

Owner

waveform80 commented Jul 29, 2014

Commit raspberrypi/userland@b3b728f adds support for multiple cameras to raspistill et al - need to duplicate this functionality in picamera for 1.7

@waveform80 waveform80 added enhancement and removed task labels Jul 29, 2014

@waveform80 waveform80 added this to the 1.7 milestone Jul 29, 2014

@waveform80 waveform80 self-assigned this Jul 29, 2014

@waveform80

This comment has been minimized.

Owner

waveform80 commented Jul 31, 2014

And apparently there's a multiplexer project now (not yet funded at the time of writing, but apparently their proof of concept can at least switch between cameras): https://www.indiegogo.com/projects/ivport-raspberry-pi-camera-module-multiplexer - anyway, it's another reason to at least get rid of the check against multiple instances

@waveform80 waveform80 closed this in 7a9fda1 Aug 2, 2014

waveform80 added a commit that referenced this issue Aug 7, 2014

Fix camera init test
Broke with implementation of #84
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment