LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

CIN or Call Library?

reading up on CINs over the weekend, but . . . having not done CINs in the
past i am not certain that this is the way to go. breifly, a co-worker is
writing some code in Visual C++ to control the output of a video card (true
NTSC video on the secondary output of a MATROX card). basically, i need
to pass the name of a folder (path defined) to the code, and it will proceed
to play the *.jpg files that are found in that folder sequentially. single
images, not movies or anything. alternatively, the name of the specific
*.jpg file will be passed and displayed for a specified period of time.
this should be a parralel or background process, as the machine must monitor
and control all the other hardware whether video output is happening
or not
(in otherwords, can't hog the system to itself until the process is completed).
this should be possible since the process itself should be idle most of
the time (4 to 6 jpegs @ 15 to 40Kb each, 30 to 60 seconds per image), with
the video output handled by the card and its memory. i seem to remember,
though, that a CIN will hog the system until the process is completed 😞
0 Kudos
Message 1 of 2
(2,162 Views)
DLL's is the way to go.
CINs are less easy to maintain and less visible in the system.
NI is also moving code to dll's.
A dll may also hog the system ! But you also can run it in another thread.
greetings from the Netherlands
0 Kudos
Message 2 of 2
(2,162 Views)