The Original Poster discovered (perhaps by searching the LabVIEW Forums) that I have used a Logitech C920 WebCam with IMAQdx, and asked me a series of questions in a Private Message. I posted an answer, but realized that I did not directly address the questions I was asked. So, for the benefit of the Original Poster and others who may have a similar problem, I'm going to post the Q&A here. Here are the questions, with my answers and comments below.
I am going to purchase a new Logitech C920 camera, and while I am searching in the forum, I find that you own one.
I am afraid of having the same issue with the Logitech camera. That's why I am texting you.
- Did you face such an issue in your camera ?
- Are the drivers supported in windows 10 ?
- Is there any problem working with grabbing 1280x720p @30fps ?
- Did you try to work with USB 3.0 interface ? If yes, is there any improvements in the performance ?
- What modes are you having in MAX ? YUY2 or MJPEG ?
Did I face "such an issue"? I explained that I was unclear what the "issue" was, as no code was posted, so I wasn't even clear if the problem was viewing images in MAX at the stated resolution (I pointed out that this is a transfer of >100MB/sec), viewing the images in LabVIEW, or saving the Images to a Video file.
I'm currently on my home Desktop, running Windows 10 with LabVIEW 2016. The drivers "auto-installed" without a hitch. I also have a Microsoft LifeCam Cinema (don't know the model, but the camera is pretty old, maybe 8 years) that shows up, as well.
Problem grabbing at 1280x720, 30 fps, MJPG? Works just fine in MAX -- I left it running for >15 minutes, looked pretty smooth.
USB 3.0 or 2.0? I'm pretty sure this is plugged into a USB 3.0 socket, but haven't yet crawled around to the back of my PC to verify -- just a second ...
Good thing I checked -- the camera is plugged into a USB 2.0 hub (along with my wireless keyboard/mouse, a Logitech controller, a Label Printer, something else I'm not sure about), which is plugged into a USB 2.0 port on my PC. I have another one of these Cameras at work, where it is easier to plug into USB 2 or 3 without a lot of crawling (somehow I managed to lock up my PC just now, requiring me to power down and restart -- fortunately the Forum saved my unfinished partial reply). So at the present time, I can't say what "improvement" plugging into USB 3.0 would be, as, in MAX, it looked fine in USB 2.0.
What mode? I was using MJPG.
OK, so "just for fun", I whipped up a few IMAQdx VIs to try to do the same thing in LabVIEW (the code's gone "bye-bye" in my reboot, but it's dirt simple to set up). I used about 4 or 5 IMAQdx functions (plus an IMAQ Create to create my Image, U32 RGB). The camera (in MAX) was configured as 1280x720, 30fps, MJPG, and when I looked at the image being displayed on the LabVIEW Front Panel, it was very "jerky", I'd say about 3-5 fps. Of course, the reason was obvious when looking at the information shown on the Image Display -- the camera was running at max resolution, 2304x1536 RGB24, 2fps. Simple fix to change the Video Mode to 1280x720, 30fps MJPG, and once again, images smooth as silk (I only wanted for a few minutes).
Some comments on earlier posts.
- If you installed LabVIEW, LabVIEW Vision Acquisition, and the Vision Drivers from a recent (say, LabVIEW 2015 or 2016 distribution), and you installed the 32-bit version of LabVIEW on the 64-bit version of Windows 10, you shouldn't need to worry about Drivers or the IID/ICD files that MAX creates for the Cameras that it "sees". Don't mess with them (it largely does not help, as MAX will probably try to rebuild them, anyway).
- I still don't know what it is you are trying to do, nor where you are having problems. A number of suggestions have been posted, several by people who really do know how LabVIEW Vision works. If you post your code (attaching the actual VIs that you use, as a file with the extension .VI, or, even better, if you compress the folder that contains your Project (or, alternatively, the VIs that you have written to do whatever you are trying to do) and attach the resulting .ZIP file, we will be in a much better position to (a) know and understand what you are trying to do, and (b) "fill in the missing steps" that are probably present (since your code doesn't work, but the VI I whipped together in 10 minutes did).
Don't give up -- it is definitely "do-able", though if you want to write Video files, you may have to think about compression techniques (which IMAQ will probably handle for you).
Bob Schor
