uEye camera not working with ueye node from image pack

vvvv beta question
1

Hi all

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?

Sune

2

not patch is needed for demonstrating the behavior, just start the help patch for the ueye node

3

hey sebl,
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.

4

which vvvv version, any errors?

5

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

6

I began looking at the other files in the image pack, not sure if it is relevant, but the basics girlpower patch has CaptureProperty and VideoIn as red and throw the error:

Could not load file or assembly ‘VideoInputSharp, Version=1.0.4542.15384, Culture=neutral, PublicKeyToken=null’ or one of its dependencies. The system cannot find the file specified.

And gives the log: Dropbox

This happens on both my laptop and the installation machine

7

so, when this log message also appears on your notebook, it is unrelated to the ueye problem?+

iirc videoinputSharp is for imagepacks videoplayer (i guess this is x86 only
 i don’t remember exactly)

8

Yes, it is unrelated to the ueye problem

So that didn’t make us much wiser.

9

maybe worth a try:

open ueye camera manager → give cam another → enter that id manually in the videoin plugin (before enabling it)

10

I don’t have ueye camera manager installed
 I did install everything from the full download from here: The comprehensive download center for all IDS products

not on any of the machines

11

that should install with the full driver


it’s this tool IDS Software Suite

12

Yes, it should, but it don’t

EDIT: I can’t find it anywhere in C:\Program Files\IDS\uEye

13

@sebl which version of the IDS software suite d you have installed?

14

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

15

ids camera manager is here C:\Windows\System32\IdsCameraManager.exe

(don’t ask me why it’s here and why windows search doesn’t find it properly)

16

changing the ID of the camera does not seem to make any difference

17

i have no more ideas


i just downloaded the freshest alpha x64 incl. addonpack (d95355abd7) and the pack from the contribution. it works out of the box on my machine.

maybe one of those 2 things:

  • the folderin the zip is named ÎmagePack (which is a stupid typo) and i fixed that to ImagePack.
  • i used VideoIn (uEye) help 2.v4p instead of VideoIn (uEye) help .v4p

my specs are:

  • W10 1607
  • gpu is 580 GTX
  • cpu is i7 980
  • latest ueye driver installed
  • nvidia driver is 373.06
1 Like
18

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
  • make emgucv a submodule of the imagepack
19

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

I am a bit confused

20

Hey,
I am running Win10 64 with beta34.2_x86.
trying VVVV.Packs.Image-sebl_beta43.2 with nvcuda.dll inside node>plugins> Dependencies
no success
ueye driver 480