IMAQ Write Image And Vision Info File 2 not saving overlay information

[bentaztick]

Hello Smart People,

I have modified the Optical Flow Feature Tracking Example VI to track the white lines in the attached images. I uploaded three, but the series will actually have 100+ images. We would like to track 6-10 points in the image depending on the experiment. Note: You have to pick points, not rectangles or anything else to construct the ROI. Also, the program only runs if you download the original example VI.

My main problem is that the IMAQ Write Image And Vision Info File 2 is not saving the overlay information that shows the point tracking for the images. Right now the program is set to record just the last image. I will modify it to save all the images when I figure out how to include the overlay information.

It would also be super awesome if the program could:

1. Let you select all the points at the same time. I.e. pick Point 1, click o.k., pick Point 2 click o.k., etc... and when complete all the chosen points would be visible at the same time. Then one final o.k. to run the program. 

2. Let you have the option to be able to confirm the location of, or re-position, the points in each frame.

3. We only need Point, Zoom, and Pan from the Tools drop down, but it doesn't want to save them as defaults.

These are indicated with red text on the Front Panel/Block Diagram. 

Thank you for being you!

bentaztick

[Bob_Schor]

I've never been a fan of overlays.  However, a colleague of mine loved them and cluttered up his video data with copious text that was (in my opinion) better saved in a second "Frame-data" file.  As I recall, when the AVI2 functions came out (LabVIEW 2011? 2012?), this "feature" went away, largely (as I understand it) because there was no standard for putting supplemental text on images.

Bob Schor

[bentaztick]

Hi Bob,

I would like for the user, or someone else, to be able to refer back to each image and be able to double check that it tracked the white lines properly. There are work arounds I could use. The program saves the x and y data for the points, so I could have another program that reads in the image and the data points. I could also try to use a VI that screen captures the Front Panel for every image.

Cheers,

bentaztick