-
Similar Content
-
By Elancheran
Hi Everyone,
I am trying to play the video in reverse decrementing the frame number in IMAQ Read Frame function. Its working but the result is very choppy as every frame takes significant time to load, but when I just increment the frame number and play the video forward, its executing without any problem. I have attached the VI and info regarding the video, could you guys please let me know why I am having problem when I am trying to display the video in the reverse order.
Playing AVI file.vi
-
By Shaun07
Hello,
I need one help regarding changing the image image type
How can I convert grey scale image to false color image?
Here, I have attached two images. 1. greyscale image 2. is just an example that I want to convert. (False Color).
Any help would be appreciate.
Thanks,
Parth Panchal
-
By Karin Hellqvist
In the attached image I have four Code 128 and two Code 39. I have problem detecting them without down sampling the image first. Since I want to grade the bar codes I don't want to down sample since the code quality is reduced then. I noticed this from that sometimes some of the bar codes are found without down sampling an then the grade is higher for those. Down sampling a factor 2 sometimes work, down sampling a factor 4 always works.
I have tried croping the image around the bar code but this doesn't help.
I'm using IMAQ Read Barcode 2, and have tried to change the parameter Min Bar Width with no result. Is there any other parameter I can change for the algorithm to find the barcodes, without having to down sample my image.
Best regards
Karin Hellqvist
Certified LabVIEW Architect
DVel
-
By szalusky
I have a relatively large application which does heavy IMAQ image processing. Many IMAQ buffers are created and destroyed dynamically at runtime based on need (i.e. different system components will create their own temporary images for processing steps and destroy them when their work is finished). While this dynamic creation/destruction reduces the overall memory footprint at a given time, it appears the constant re-sizing or re-creating is causing memory fragmentation over time. When this dynamic creation/destruction is used heavily, we get IMAQ out of memory errors (at different places in the application) after the system has been running for some time. Total memory usage has not increased (and is well below 2GB) so the errors are presumably due to the fact that there are not large enough contiguous blocks available.
Are there any best practices or “standard” ways for managing lots of image references? Should they all be created initially? One idea is to allocate a pool of resources on startup (of images that will not get resized) that are shared throughout the application using a mechanism to “reserve” and “release” the resources in the pool. Is this a good approach? Thanks!
-
By ASalcedo
Hello to all.
First of all thanks a lot for reading this post and being able to help.
I have noticed the next problem:
My application has a camera, this camera takes images (snap mode) and application process them (detect some edges in the image). It works fine.
But when I make the Display bigger my application takes longer to process images (and for me that is crucial). I think that this happens because my application in this case has to process a bigger image (bigger display = bigger image??)
So maybe if My camera takes images with lower resolution I solve the problem.
So how can I change image resolution captured by my gigE camera? In NI MAX or in Labview?
Thanks a lot!
-