[AG-TECH] FW: Videum problem

Fred Dech fdech at uchicago.edu
Fri Sep 24 14:15:30 CDT 2004


oh Marcus.

i completely forgot about this.  it's important.  i haven't tried these
 patches yet because my system was working like i wanted already.

----- Forwarded message from "Thomas D. Uram" <turam at mcs.anl.gov> -----

Okay, thanks to the logs I got from the two of you, I understand the
problem you've run into.  The videum card has four drivers that can be
used by vic; unfortunately, each driver can be mapped to any one of the
capture devices on the card, as indicated by the Source value in the
registry.

The video producer service (and video service) attempt to map the
drivers to capture devices directly (1 to 1, 2 to 2, etc.), which gives
you a convenient reference (i.e., WnvVdm32.dll 1-blahblah always shows
you the same camera).  The code was failing to map, but not fatally
(that's by design ;-).

The flaw is fixed in a newer VideoProducerService.zip and
VideoService.zip that you can get here, if you're interested:

http://www.mcs.anl.gov/fl/research/accessgrid/software/releases/2.3/patches/VideoProducerService.zip
http://www.mcs.anl.gov/fl/research/accessgrid/software/releases/2.3/patches/VideoService.zip

To use these, you can copy these files to

C:\Program Files\AGTk-2.3\NodeServices

If you've set the Source values properly, you really don't need to
update your services.  If you do try them, let me know your results.

Thanks,

Tom
----- End forwarded message -----





More information about the ag-tech mailing list