03-24-2016 05:25 PM
the problem here is not CPU it is RAM
altran
could you tell us about your RAM usage ?
also could you tell about the images size that you capture from your cam?
also I have 2014 LV
could you send your vis in 2014 version ?
03-24-2016 07:45 PM
Hi Ryan,
I just remove the AVI Write function and leave the queues and it gets up to ~30fps (not instantly, but it goes up to 30, as with the no recording vi).
I tried the Overwrite Mode and I get not acquisition errors.
@hatef
I have 16GB of RAM and it doesn't look like its a RAM issue either as it reports 16% RAM usage when I record.
03-24-2016 08:28 PM
03-25-2016 11:16 AM
thanks for the suggestion Hatef, my computer is 64-bit and from the link it looks like it enables up to 4gb of virtual memory.
03-25-2016 01:31 PM
03-25-2016 01:38 PM
I record at 1920x1080.
I attached both files for LV14, thanks.
03-25-2016 04:03 PM
03-28-2016 11:44 AM
1. I've tried that, It has made no difference. Can you explain why it is not needed for 30fps? I've read on this forum that the producer/consumer approach is the method to use when recording to AVI as it will capture and record the frames at the fastest rate.
2. I am using a codec to record, it is shown in my VI as "Motion JPEG (NI Vision)" I've also tried several other codecs and this one seems to be the best one for me.
3. I did not realize this, I tried it and it still makes no difference.
4. I also have tried this, it does not help.
03-29-2016 04:54 PM
Hi altran,
Sorry it's been a while since I've been able to reply.
It's interesting that we get no errors with an Overwrite Mode of fail - that means that even while the code is running slower, we're not writing over any of the IMAQdx buffers in memory. It's not the behavior I would have expected, so it's an interesting data point to have, but I don't have any new suggestions based on that at the moment.
Based on your post from the 24th, it seems like AVI write is the bottleneck, which is odd; it amost makes me think there's an issue with the speed that your computer is able to write to disk. Are you still just writing to a local drive? Can you think of any reason your computer's hardware would be causing a bottleneck at the write to disk?
@Hatef - just fyi, I can run altran's recording code on my machine at the full 30 fps in LabVIEW 2015 32-bit without any obvious memory leaks or other issues, so I don't think memory is the problem here.
03-29-2016 05:12 PM
I write locally to my C drive. I am not aware of any hardware issues. I have also tried on two other laptops.
At least I know my code is working since it works for you, I just have to find where the issue is on my computer! grrrr