@Gregory wrote:
You may not care, but the "Image" data type is one of the few reference data types in LabVIEW. This means there is a buffer holding the image and if you write to the buffer in one loop, and read from it in another loop, the actual data that is read will depend on when those write and reads happen in relation to each other.
You absolutely should care because (depending on your Frame rate and other considerations) the Images you save may have rather little resemblance to the "Image" that you view in the Display Window inside the Acquisition Loop. Ordinarily, you would use a Queue or Stream Channel (yay!) to create a Producer/Consumer design that lets the Consumer "lag" the Producer, at least initially, and "catch up" without missing any data, but since what you are passing is the address of the Image Buffer in LabVIEW, if you've only allocated a single buffer, you are always passing the same thing in the Stream, so it will show whatever is in the current buffer.
Needless to say, learning how to handle images and buffers was one of the more confusing and challenging aspects of learning how to use IMAQdx to save streaming videos. I'm grateful I'm not doing that these days ...
Bob Schor
