[AG-TECH] Osprey Cards....... Desperation

[John I Quebedeaux Jr]

Stuart,

Our PIG node uses 2 ospreys in our XP machine. We only get the 
simulstream message when the VICs try to use the same card at once. If 
you're getting the simulstream message, probably two+ vics trying to 
access the same card. With AG 2.1.2 we do not have any problems. Easy 
enough to setup: Enabled the appropriate card in the manager, made sure 
each vic pointed to a separate device (card), saved it in the node 
management. That was it. When we tested 2.2 we hit with the problem 
everyone is having with the ospreys. Just haven't had time to try the 
hack yet, but probably will give it a try soon.

In anycase, yes - we have it working just fine with multiple ospreys 
using version AG 2.1.2. I'm about to crank up a new node with 4 
osprey's (actually two computers, each with 4 - a multiple room 
node(s)) this weekend, I'll let you know the result after I do it. I 
should have time to give the latest 2.x a try even if I have to use the 
hack...

-John Q.
-- 
John I. Quebedeaux, Jr.
Louisiana State University
Computer Manager / LBRN & CCT / 131 Life Sciences Bldg. & 339 Johnston 
Hall
e-mail: johnq at lsu.edu or johnq at cct.lsu.edu / web: http://lbrn.lsu.edu & 
http://cct.lsu.edu
phone: 225-578-0062 / fax: 225-578-2597

On Jul 23, 2004, at 3:16 AM, Stuart Poulton wrote:

> No joy again,
>
> I still get complaints from the osprey driver that I need simulstream.
>
> Does anyone have 4 osprey cards working under windows XP with any
> version of the accessgrid software ?
>
> Regards
>
> Stuart
>
>
> On Thu, 2004-07-22 at 13:42, A Quay wrote:
>> Stuart,
>> This hack from Darran worked for me and saved my life!
>> -andy
>>
>>
>> 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.
>