But, as I understood, I'll still be in trouble using the AGTK2.3? Maybe I should buy 4 cards instead a quad one?
----- Original Message ----- From: "Thomas D. Uram" <[email protected]> To: "Natalia Costas Lago" <[email protected]> Cc: <[email protected]> Sent: Tuesday, April 26, 2005 8:41 PM Subject: Re: [AG-TECH] Problem finding new video capture card (Winnov Videum Quattro) > Natalia: > > As far as I remember, the iTuner Spectra card already uses wdm drivers, so > it is less well supported than the winnov card for multiple capture in > windows, thereby further making the case for wdm support in vic. > > Tom > > > On 04/26/05 13:23, Natalia Costas Lago wrote: >> >> Thomas, >> >> I am about to purchase the Winnov Videum? Maybe should I change my mind >> and buy the Ituner Spectra 8 in order to avoid having trouble with it? >> >> >> >> ----- Original Message ----- From: "Thomas D. Uram" <[email protected]> >> To: <[email protected]> >> Cc: <[email protected]> >> Sent: Tuesday, April 26, 2005 7:54 PM >> Subject: Re: [AG-TECH] Problem finding new video capture card (Winnov >> Videum Quattro) >> >> >>> There are updates to the VideoProducerService and VideoService on the >>> Windows page for the 2.3 release that have improved support for the >>> Videum card. These attempt to achieve the same effect as Darran's >>> modifications. >>> >>> I suspect the problem you are running into is that the more recent >>> Videum drivers are WDM only. The earlier drivers were VFW-based, which >>> is the type of driver that vic relies on. If you use the vfw drivers, >>> you'll see each input as a selection in vic and in node management. >>> >>> It's unfortunate that Winnov is moving to WDM drivers, but it's entirely >>> expected, since that's the path forward. What the AG community needs is >>> WDM support in vic. I'd encourage anyone in the community with >>> knowledge in this area to look into adding this support; I'm sure that >>> if someone begins the effort, others will jump in and help out to bring >>> robust WDM support to vic. >>> >>> Tom >>> >>> >>> On 04/26/05 11:10, Chris Rosenthal wrote: >>> >>>> I am working on putting together a new hardware configuration for our >>>> main node and we are testing the new 4 (s-video) input card from >>>> Winnov (Videum Quattro). After receiving some new drivers from >>>> Winnov, I seem to have the card installed properly (I can see video in >>>> their included software). >>>> >>>> However, the card does not show up as an option in the Manage My Node >>>> dialogue when I try to add a VideoProducer service. I've seen this >>>> problem in the past with multiple Osprey cards, and currently I am >>>> using the edit that Darran Edmundson sent to the list last July (see >>>> below). I could do the same thing, but the card doesn't even show up >>>> as a device option in vic (so I don't know the name of the resource to >>>> append to the resource list). >>>> >>>> I would really appreciate the help getting this card working as soon >>>> as possible. >>>> >>>> Thanks, >>>> Chris >>>> >>>> >>>> From: Darran Edmundson [mailto:[email protected]] >>>> Sent: Tuesday, July 06, 2004 1:31 AM >>>> To: [email protected] >>>> Subject: [AG-TECH] hack to solve Osprey problem under AGtk2.2 and WinXP >>>> ... >>>> >>>> Problem: >>>> >>>> For nodes with multiple Osprey cards running AGTk-2.2 under >>>> Windows XP, multiple instances of vic contend for the same >>>> capture card. The workaround is to manually resolve >>>> the vic contentions after changing venues. This is a >>>> pain. Pending a proper fix, you might wish to try the >>>> following. It works for us - your mileage may vary. >>>> >>>> Hack: >>>> >>>> 1) On your video machine, open the file >>>> c:\Python23\Lib\site-packages\AccessGrid\Platform\win32\Config.py >>>> Save a copy of this file so you can undo the following if >>>> necessary. >>>> >>>> 2) Line 985 should be the definition of the SystemConfig class >>>> method GetResources: >>>> >>>> def GetResources(self): >>>> """ >>>> Return a list of the resources available on the system >>>> """ >>>> ... >>>> >>>> 3) This method builds a list of AGVideoResource entries (one >>>> for each capture device) by scanning your Windows registry. >>>> Our registry did not contain entries for both Osprey cards. >>>> Rather than change the registry, the following hack sets >>>> the list of "found" resources explicitly. >>>> >>>> Around line 1020, a return statement sends back the list >>>> of discovered resources. Insert the following code indented >>>> the same amount as the final return statement. >>>> >>>> # hack to hardcode known resources >>>> resourceList = list() >>>> resourceList.append( AGVideoResource( >>>> 'video', 'o100vc.dll - Osprey Capture Card 1','producer', >>>> ['external-in'])) >>>> resourceList.append( AGVideoResource( >>>> 'video', 'o100vc.dll - Osprey Capture Card 2','producer', >>>> ['external-in'])) >>>> resourceList.append( AGVideoResource( >>>> 'video', 'o100vc.dll - Osprey Capture Card 3','producer', >>>> ['external-in'])) >>>> print "hack to hardcode known video resources ..." >>>> return resourceList >>>> >>>> 4) Save and restart your video machine AGServiceManager. You >>>> should see the "hack to hardcode .." print statement output. >>>> >>>> 5) "Manage my node" and remove and re-add the VideoProducer services. >>>> You should be prompted for the desired resource. >>>> >>>> 6) Let me know if it works ... >>>> >>>> Cheers, >>>> Darran. >>>> >>>> -- >>>> Darran Edmundson ([email protected]) >>>> ANU Supercomputer Facility Vizlab >>>> Australian National University, Canberra, ACT 2600 >>>> tel: +61 2 6125-0517 fax: +61 2 6125-5088 >>> >>> >>> >> >> >
