search

janpaulus / BRICS_OODL

BRICS Object Oriented Device Layer
4 stars 2 forks source link

Device identities #5

Closed shakhimardanov closed 13 years ago

shakhimardanov commented 14 years ago

So far, API allows to work with any camera from IIDC, UVC, V4L1/2. These are supported standards by unicap API. But, currently API allows you to work only with "one camera" at a time because it can not differentiate them. This will be later changed and most probably will be done through passing a camera ID (any literal, like int or device node name) to camera constructor. Also, note that each camera instance should have its own thread of execution, otherwise system can not allocate resources appropriately.

nicoh commented 13 years ago

Is this a problem of "our" API or of the unicap driver. Maybe we could "generate" a randomized ID based on the cameras parameters within the constructor?

shakhimardanov commented 13 years ago

no it is not, it is just a matter of implementation. Since any HW device in OS abstracted as a file, they have a unique ID and access goes through that device file in linux /dev/video0 for instance. So it is not really an ID problem, it is just the matter of how to make it user friendly and neat in implementation. I have some ideas, but this will come later...

shakhimardanov commented 13 years ago

It works, depending on the driver we can capture from multiple cameras. Todays test showed that we can capture from 2 USB cams, 1 firewire at the same time. Next milestone to test this 3-5 usb cams and 2-5 firewire cams.