Well, without code, it is impossible to say. Note that with IMAQ, good design is especially important, as the IMAQ functions are a little strange, do some "unconventional" things (relative to other LabVIEW I/O modules), and are not the best-documented features of LabVIEW (to put it mildly).
We have a project, completed about 4 years ago (developed in LabVIEW 2010, I believe) that records videos of behaving animals at 30 fps. A recording session lasts about 2-3 hours -- that's a whole lot of video! However, we only want 5-10 seconds of "important" behavior (which we have an independent way of tracking), so we use a signal that says "Behavior is Now!" and save 5 seconds of video before the behavior and 5 seconds during/after. Since the behavior takes place every few minutes, we only have, say, 20 10-second videos instead of a 2-3 hour single video.
Oh, and we do this on 24 animals, simultaneously.
We are using Axis cameras with an Ethernet interface. We've also tried this with USB cameras, but can't do as many cameras, I think because of the traffic at the USB Hub.
So, yes, you can record from multiple cameras at the same time. It is vital that you use something like a Producer/Consumer Design Pattern to keep the Acquire Frame function as isolated from other processing (other than enqueuing its image) as possible -- use LabVIEW's inherent parallelism to allow (24) cameras to work together.
Bob Schor
But do take his advice and encapsulate some functionality in SubVIs. Try to keep your wires with as few kinks as possible. Not just for us, or the guy who inherits your project, but for yourself too. A little bit of time organizing and commenting now, will save a lot down the road!
