I have been struggling getting the ueye node from the image pack working on a machine for an installation.
I am using the ueye UI-1460LE and need to use pixel binning to achieve acceptable frame rates.
It works fine in the ueye cockpit and on my laptop (i7 win10 x64) it works fine, both using latest alpha and latest beta, when using the same settings on the installation machine (i3 win10 or 7 x64) it works fine in the ueye cockpit, but not with the image pack node. it works with the DShow nodes, but I can’t enable pixel binning so it has a horrible frame rate. (6fps)
Any ideas on what could make it work?
the same here.
all my uEye cameras (UI146xSE-C, UI-1240LE-NIR-GL,UI-1240ML-NIR-GL) are working with ueye cockpit, old uEyeCam node, CV.image DirectShow, showing camera info (S/N and model) in ListDevice (uEye help) but no picture in help patch.
I am running beta34.2 x64 and also a quite recent alpha (within a week or two from now). It the vvvv folder is copied from the laptop to the installation machine. everything is green in setup.exe, both the alpha setup and the beta setup.
TTY shows no errors, there are no red nodes
The camera works fine in the ueye cockpit application
I am now a bit wiser, it seems like the shortcut the installer makes in: “C:\ProgramData\Microsoft\Windows\Start Menu\Programs\IDS” does not survive a restart on windows 10, so it does not appear in the all programs list any more.
But it is still on it’s spot at “C:\Windows\System32\IdsCameraManager.exe”
EDIT: changed the link to where the file actually is, which is also what @sebl wrote after this post was first made
ok, i could reproduce the problem today on another computer…
the problem seems to be related to nvcuda.dll (which is also a hot topic on the contribution page).
so, @sunep, is a difference between those 2 comps you have, that the one that’s working has a nvidia card and the other doesn’t? if yes, copy the nvcuda.dll from the dependencies/x86 folder to system32/
i guess it’ll also work if you install the nvidia driver.
I’m not sure what’s going on there… the points i learned are:
emgucv2.4.2 (which is used atm) relies on nvCuda.dll since it is compiled with gpu-support
normally the nvcuda.dll is in Dependencies/x86 folder of the imagepack. but this seems not mandatory, because it worked without on my notebook.
i guess, the dll mus be somewhere in path or vvvv finds it on its own (wink over to the dependency-hell topic)
so, for now i think it’s best to mess around with the dll(s) until it works. but long-term solutions for the imagepack could be:
switch to a higher emgucv version that has gpu-support optionally (@mino talks 2.4.10 on the contribution page)
use nugets (instead of static linked dlls) if there are any available
Yes, the difference is built intel GPU vs. nvidia GPU
I don’t have a “dependencies/x86” folder in, I assume: “ImagePack\nodes\plugins\Dependencies” in any case there is no file with cuda in its name anywhere in the ImagePack besides one named: “cudart32_42_9.dll”
I do have a nvcuda.dll in my system32 folder on my laptop, it does not work copying it over to system32 on the machine with no nvidia GPU