Hi Labview users, Currently, I am looking for some high speed image processing. I watched that ImagetoEDVR is more suitable than Imagetoarray, especially for memory management and CPU ressource. (i.e. https://zone.ni.com/reference/en-XX/help/370281AG-01/imaqvision/edvr_with_vision/) Before starting to write a program, I just compare the processing speed to get data using either ImagetoEDVR or Imagetorray. Surprinsingly, for a same image the while loop with ImagetoEDVR took 4ms to display a table and Imagetoarray 0.04ms. ImagetoEDVR seems to be very slow (about 100 times) by comparison with Imagetoarray. Firstly, I thought that displaying data at every while loop run was time consuming. However, even without displaying any data ImagetoEDVR is slower than imagetoarray. So the question: Did I make a mistake somewhere to explain the low processing speed? Thank you in advances for your help Best regards

LabVIEW

ImagetoEDVR slower than Imagetoarray? (Labview vision)

@Mathias85 wrote:

Hi wiebe@CARYA,

Thank you again for your message and your explanations.

I just slightly modify the vi to add a processing step (increment+1 every pixel value) and the results observed seems to explain why it slower.

Indeed in the case ImagetoEDVR, the pixels in the image continuously increase as a function of time (it's look like the structure 'in place element structure' act as a while loop). Consequently the time to process an image using imagetoEDVR is longer than imagetoarray because every pixel is process many many times.

So my new question is: how to force the 'in place element structure' to run only once.

Thank you in advance for your help

In the loop, you're reusing the same image. So apparently the data isn't copied into the DVR, but the DVR accesses the data of the image. So, increasing the data will increate the data in the image, so it will accumulate over iterations.