February 2006 - Ag-tech - mailman3.cels.anl.gov

[Fwd: Invitation to Broadening Participation in Computing Access Grid Meeting, March 15, 3:30pm EST]
by Jennifer Teig von Hoffman 28 Feb '06

28 Feb '06

Please see attached; my apologies for cross-posting. - Jennifer

1 0

Re: [AG-TECH] multiple firewire cams
by Douglas Kosovic 27 Feb '06

27 Feb '06

Hi Gavin, > Is it possible to use multiple firewire cameras on a Mac simultaneously? > Does the Mac version of VIC recognize two firewire devices separately? If you are using iSights with AGTk 2.4 (or later), they come up as iSight, iSight #2, iSight #3, ... As for other firewire devices, I'm not sure. Doug

1 0

[Fwd: Re: [AG-TECH] One-page summary of AG port usage -- please help us complete it]
by Thomas D. Uram 27 Feb '06

27 Feb '06

I'm reposting this to encourage responses. There was a lot of noise on this thread initially; please be noisy now. If you have concerns about firewalls and the AG, talk to your network admins so we can address them. Specifically (reposting from original): > What are the concerns of your admins? > Do they care at all about opening up the multicast address range? Why? > Would it be enough to be able to select a bridge with a known port range that would work for any venue? > > I think the real problem is in bridging, where you're concerned with traffic from > real hosts. But let's get input from some of those (Draconian) net admins and build > a practical solution.

1 0

Re: [AG-TECH] Osprey 300 capture card vic woes
by Niall Moran 27 Feb '06

27 Feb '06

Thanks for the reply. The Microsoft WDM Image Capture (Win32) is the only option present in this configuration menu. Think I will just format one of the client machines and reinstall everything the way it was done on the working nodes. This should verify ( or not ) that using the driver installer was what caused the problem. It just seems weird that it would affect the vic and not any other capture software. Thanks again, Niall. -- -- | Niall Moran | Systems Administrator | Irish Centre for High-End Computing \niall.moran(a)ichec.ie -------------------------- On Mon, Feb 27, 2006 at 12:38:12PM -0600, monika.k.rabarison(a)ccaix.jsums.edu wrote: > Hey, > > I had a similar issue on Windows. Not sure if this is > exactly the case for you though. When I select the capture > card driver as the resource in the VideoService > Configuration, vic crashes. Selecting "Microsoft WDM Image > Capture (Win32)" instead, made vic works smoothly. > > -Monika > > > Hi, > > > > I am trying to setup an access grid system. We are using a > > linux machine to host the venue server and windows XP > > machines for the access grid clients. Each machine is > > identical and has the same specs. > > > > * Pentium 4 3.0Ghz > > * 1GB ram > > * 160gb disk > > * nvidia quatro 1400 dual dvi card > > * osprey 300 video capture card > > > > Software running on each machine is windows xp SP2 > > Access grid toolkit 2.4 > > > > I setup the first 2 clients and everything worked fine. > > When setting up the second 2 clients however I ran into > > some difficulties. The vic capture process crashes with a > > runtime error. > > > > The only difference between the setup procedures was that > > on the 2 clients that do work the capture card drivers > > were simply installed using the windows add/remove devices > > utility. However on the 2 clients that are having the > > problems the capture card drivers were installed using the > > setup utility that came on the cd. There was a dialog > > during the install to set the format of the video ( i.e. > > NTSC, PAL ... ). PAL was choosen here. > > > > So far I uninstalled the driver and reinstalled the way > > that worked previously. Downloaded the latest osprey > > drivers from the net and installed them using both > > methods. None of this has made any difference. > > > > On the 2 machines that do not work. All other software > > that accesses the capture card works perfectly, VLC, > > windows movie maker and the utilities that came with the > > capture card. > > > > Has anyone come accross anything similar or know of any > > where to go from here? I would greatly appreciate any > > help. > > > > Cheers, > > > > Niall. > > > > -- > > -- > > | Niall Moran > > | Systems Administrator > > | Irish Centre for High-End Computing > > \niall.moran(a)ichec.ie > > -------------------------- > > > > > > > > [Attachment: niall.moran(a)ichec.ie.sig] > > -------------------------------------------------------------- > Monika Rabarison > Systems Administrator > Jackson State University > Office: (601)979-5933 > SciVis Lab: (601)979-1061 > http://vislab.jsums.edu > > "Computers are incredibly fast, accurate and stupid; humans > are incredibly slow, inaccurate and brilliant; together they > are powerful" Albert Einstein

1 0

Re: [AG-TECH] Osprey 300 capture card vic woes
by monika.k.rabarison＠ccaix.jsums.edu 27 Feb '06

27 Feb '06

Hey, I had a similar issue on Windows. Not sure if this is exactly the case for you though. When I select the capture card driver as the resource in the VideoService Configuration, vic crashes. Selecting "Microsoft WDM Image Capture (Win32)" instead, made vic works smoothly. -Monika > Hi, > > I am trying to setup an access grid system. We are using a > linux machine to host the venue server and windows XP > machines for the access grid clients. Each machine is > identical and has the same specs. > > * Pentium 4 3.0Ghz > * 1GB ram > * 160gb disk > * nvidia quatro 1400 dual dvi card > * osprey 300 video capture card > > Software running on each machine is windows xp SP2 > Access grid toolkit 2.4 > > I setup the first 2 clients and everything worked fine. > When setting up the second 2 clients however I ran into > some difficulties. The vic capture process crashes with a > runtime error. > > The only difference between the setup procedures was that > on the 2 clients that do work the capture card drivers > were simply installed using the windows add/remove devices > utility. However on the 2 clients that are having the > problems the capture card drivers were installed using the > setup utility that came on the cd. There was a dialog > during the install to set the format of the video ( i.e. > NTSC, PAL ... ). PAL was choosen here. > > So far I uninstalled the driver and reinstalled the way > that worked previously. Downloaded the latest osprey > drivers from the net and installed them using both > methods. None of this has made any difference. > > On the 2 machines that do not work. All other software > that accesses the capture card works perfectly, VLC, > windows movie maker and the utilities that came with the > capture card. > > Has anyone come accross anything similar or know of any > where to go from here? I would greatly appreciate any > help. > > Cheers, > > Niall. > > -- > -- > | Niall Moran > | Systems Administrator > | Irish Centre for High-End Computing > \niall.moran(a)ichec.ie > -------------------------- > > > > [Attachment: niall.moran(a)ichec.ie.sig] -------------------------------------------------------------- Monika Rabarison Systems Administrator Jackson State University Office: (601)979-5933 SciVis Lab: (601)979-1061 http://vislab.jsums.edu "Computers are incredibly fast, accurate and stupid; humans are incredibly slow, inaccurate and brilliant; together they are powerful" Albert Einstein

1 0

Osprey 300 capture card vic woes
by Niall Moran 27 Feb '06

27 Feb '06

Hi, I am trying to setup an access grid system. We are using a linux machine to host the venue server and windows XP machines for the access grid clients. Each machine is identical and has the same specs. * Pentium 4 3.0Ghz * 1GB ram * 160gb disk * nvidia quatro 1400 dual dvi card * osprey 300 video capture card Software running on each machine is windows xp SP2 Access grid toolkit 2.4 I setup the first 2 clients and everything worked fine. When setting up the second 2 clients however I ran into some difficulties. The vic capture process crashes with a runtime error. The only difference between the setup procedures was that on the 2 clients that do work the capture card drivers were simply installed using the windows add/remove devices utility. However on the 2 clients that are having the problems the capture card drivers were installed using the setup utility that came on the cd. There was a dialog during the install to set the format of the video ( i.e. NTSC, PAL ... ). PAL was choosen here. So far I uninstalled the driver and reinstalled the way that worked previously. Downloaded the latest osprey drivers from the net and installed them using both methods. None of this has made any difference. On the 2 machines that do not work. All other software that accesses the capture card works perfectly, VLC, windows movie maker and the utilities that came with the capture card. Has anyone come accross anything similar or know of any where to go from here? I would greatly appreciate any help. Cheers, Niall. -- -- | Niall Moran | Systems Administrator | Irish Centre for High-End Computing \niall.moran(a)ichec.ie --------------------------

1 0

multiple firewire cams
by Gavin W. Burris aka 86 27 Feb '06

27 Feb '06

Is it possible to use multiple firewire cameras on a Mac simultaneously? Does the Mac version of VIC recognize two firewire devices separately? Cheers, -- Gavin W. Burris aka 86 Senior Systems Programmer Penn State Visualization Group http://viz.aset.psu.edu/ga5in

1 0

Re: [AG-TECH] Problem with BridgeServer
by Thomas D. Uram 27 Feb '06

27 Feb '06

I suspect that the bridge server is advertising itself using the internal IP. When external clients try to use the bridge, what address/hostname appears in RAT? If this is the problem, you can control the IP address used by the BridgeServer (and other AG components) by setting the GLOBUS_HOSTNAME environment variable to the desired address/hostname. Tom On 2/27/06 9:29 AM, Sebastian Tabarce wrote: > Hello! > > I have the folowing setup for an AG Venue Server and an AG Bridge Server: > - the Venue Server: one machine running Fedora Core 4 and AGTK 2.4. This > machine has the internal IP 192.168.103.55 and the domain name > silicon.fe.up.pt. This machine has linked to it the real IP address > 193.136.28.183. I don't know exactly what this means in terms of > networking, I just asked my network admin to make my machine visible to > the Internet and he told me that my machine can be seen from the > Internet with this address and also by its name silicon.fe.up.pt. Ports > 8000, 8002, 8004, 8006 TCP are opened for this machine. > - the Bridge Server is running Slackware 10 and AGTK 2.4. Same as above, > internal IP is 192.168.103.62, external IP is 192.136.28.184. and name > poly.fe.up.pt. Ports 50000-50010 UDP are opened. > > I've conducted some tests. On the internal network everything works > fine. From outside, people can connect to my Venue Server using > https://silicon.fe.up.pt:8000/Venues/default , they see the BridgeServer > and can choose Unicast, however they do not appear in my RAT window and, > of course, I cannot talk to them. Multicast is not an option. Also no > output in the terminal of the BridgeServer for machines trying to > connect from outside. For those on the local network I have the normal > output. > > Any thoughts about why the Bridge Server is not doing its job? > > Thanks, > Sebastian >

1 0

Problem with BridgeServer
by Sebastian Tabarce 27 Feb '06

27 Feb '06

Hello! I have the folowing setup for an AG Venue Server and an AG Bridge Server: - the Venue Server: one machine running Fedora Core 4 and AGTK 2.4. This machine has the internal IP 192.168.103.55 and the domain name silicon.fe.up.pt. This machine has linked to it the real IP address 193.136.28.183. I don't know exactly what this means in terms of networking, I just asked my network admin to make my machine visible to the Internet and he told me that my machine can be seen from the Internet with this address and also by its name silicon.fe.up.pt. Ports 8000, 8002, 8004, 8006 TCP are opened for this machine. - the Bridge Server is running Slackware 10 and AGTK 2.4. Same as above, internal IP is 192.168.103.62, external IP is 192.136.28.184. and name poly.fe.up.pt. Ports 50000-50010 UDP are opened. I've conducted some tests. On the internal network everything works fine. From outside, people can connect to my Venue Server using https://silicon.fe.up.pt:8000/Venues/default , they see the BridgeServer and can choose Unicast, however they do not appear in my RAT window and, of course, I cannot talk to them. Multicast is not an option. Also no output in the terminal of the BridgeServer for machines trying to connect from outside. For those on the local network I have the normal output. Any thoughts about why the Bridge Server is not doing its job? Thanks, Sebastian -- Sebastian Tabarce Junior Researcher INESC Porto Campus da FEUP - Rua Dr. Roberto Frias, nï¿½ 378 4200-465 Porto Portugal E-mail : stabarce(a)inescporto.pt Web : http://www.inescporto.pt

1 0

Re: [AG-TECH] Problem with winnov videum card when changing venues
by Thomas D. Uram 26 Feb '06

26 Feb '06

I've not seen that behavior. There is some mapping done in the VideoProducerService code specifically for this type of card. Maybe the VideoProducerService.log file has an indication of the problem? If you don't see anything, you could send it along for us to take a look at. Tom On 2/26/06 9:26 AM, Natalia Costas Lago wrote: > > > Hi everybody, > > I have been dealing with our winnov card recently (after some time being > iddle) and i got a problem I havent been able to solve so far. The > problem appears after the third time I change to a different venue, then > the card stops working properly (maybe 2 out of 4 video devices work, or > maybe 0 out of 4). Any idea about what is going on? > > Kind regards, > Natalia. > > > > > > > >

1 0