12-15-2006 04:20 PM
12-18-2006 10:32 AM
12-18-2006 10:52 AM
It is a fresh install of all Labview software (including machine vision and IMAQ drivers). I did run the "Read Write AVI with Data" example and it seems to work fine (I see the video and can subsequently review the frames with the slider bar).
Maybe it is just a formatting issue of my avi files. The software that creates them is SPOT Windows version 4.5.3. It is the software that came with my firewire camera. I take image sequences which are stored as stacked tiffs. I then have the option of converting these into avi (which itself takes a significant amount of time) or extracting all images and saving them individually.
I just tried using the "Read AVI" example to read my avi files and at least no errors appear, but the colors are completely wrong. I think I have seen this before when the file isn't being read properly, but I don't know what causes it. I will try to narrow down the cause of the problem and post again with more details soon if I can get them.
Thanks for the help guys,
Tim
12-18-2006 11:21 AM
OK, I seem to have narrowed the problem down a bit. The "AVI Read" example can at least open my avi files (although I still have the formatting problem with incorrect color noise on all but the first frame). The only difference between the beginning of my program and the example is the way the file is selected. So I guess this is not really a problem any more since I can use the method the example does. But I can't reason out why there should be a difference between them. I attached a vi that highlights the difference. The first part is a copy/paste from the example. The second part is the code I was trying to use. If you run it, you can see that, although both file paths are identical, the second part throws an error.
But this still leaves me with the problem with how my images are presented. I realized that for these files, Windows Media player shows them the same way (incorrectly). I checked with the SPOT software and it says it is using Cinepak Codec by Radius version 1.10.0.11 for compression. Are their any known issues with this?
Thanks again,
-Tim
12-18-2006 01:29 PM
12-18-2006 02:05 PM
My IMAQ version is 3.7.0.
Thanks for the quick and helpful response. At least we have found a way to avoid the error. I will see if I can figure out the issue with the compression. I'll try your idea of converting the avi or possibly see if I can change which compressor my software uses.
Thanks again,
Tim
12-19-2006 08:31 AM
12-19-2006 09:28 AM
I finally got the compression figured out. I noticed in my SPOT software that when I export to avi, there is a compression setting button. Upon opening that up (which is how I found the name and version of the compressor yesterday) there are a number of different compressors available. It turns out the one I was using was set by default for color images while I was using grayscale. So that problem is solved.
I do have the IMAQdx driver (version 3.0.0) since I am using the software at my school which pretty much has the full academic site license. I hope to get to full implementation with LabView eventually, but since I only have a little experience with LabView and none with video and image editing, I thought I would start with just image analysis (probably the harder of the two). Once I've got that done, I may try to tackle the acquisition. I was just looking at some of the examples and it looks like I could just about replicate our SPOT softaware if I can figure out the details.
Just as extra info, I'm basically trying to do a particle tracking program and analyzy the motion of the particles I view in a microscope. Luckily, I found the tracking vi in the code-sharing section of the forums, written by the Milne research group (tracker1.0). So now I just have to work on the analysis and the acquisition. I'm trying to see how high a framerate I can get out of my firewire camera while maintaining high resolution. Currently, I'm getting about 6-7 fps obtaining 1024x1024 8-bit grayscale images using the firewire connection. The camera has a 2048x2048 native res, but auto bins grayscale 2x2.
Thanks for all you help.
Tim
12-20-2006 12:53 PM