We've problems with Vic on Windows XP when there are many cameras on h264/mpeg4 
as Visualization (VideoConsumerServiceH264). We've 3 cameras on h264/mpeg4 
(800kbps / 24fps, Size:Large) and we are doing tests with others Universities, 
so it can be about 10 cameras connected. When vic as VideoConsumer service 
runs, vic application crash and close all video windows.

In the official page of vic talks about this crash and recommend to use 320x240 
resolution (I supose that it's the size medium on vic preferences): 
http://mediatools.cs.ucl.ac.uk/nets/mmedia/wiki/VicFaq#a2.WhydoesVICcrashassoonasItrytotransmit

About Windows 7, in the first run we've problems and crash (python.exe don't 
work) on connect to a Venue and load the chat, and yes, it's due to the beacon 
option. But, the second and nexts runs the VenueClient close when load the 
splash screen. I run the VenueClient with debug and I realize that debug show a 
error in the VenueClient.py file:

" File "C:\Python24\lib\site-packages\AccessGrid3\AccessGrid\VenueClient.py", 
line 266, in __init__

    if int(self.preferences.GetPreference(Preferences.MULTICAST)):ValueError: 
invalid literal for int(): False"




These lines are:

"if int(self.preferences.GetPreference(Preferences.MULTICAST)):

            self.transport = "multicast"         else:            
self.transport = "unicast" "
So, I've changed "int" by "bool" and it works.
We've encountered other debug messages like this in others lines on other Files 
(PreferencesUI.py, for example that show a similar error in the line 1173:

self.multicastButton.SetValue(not 
int(preferences.GetPreference(Preferences.MULTICAST)))

), and I've this problems on my Windows XP system (installed in my home). We 
want to notify this messages to the mailing lists for developers, but we want, 
first, to assure this errors on all systems or if it's a particular problem.


Regards!

El dia 08 mar 2010 18:48, Terry McGuire <tmcgu...@ualberta.ca> escribió:

   AG 3.1 is probably the problem.  We're running AG 3.2 beta, without XP 
compatibility mode.  Just a standard install, with the beacon turned off.

   On 8 Mar 2010, at 1039h, Tran, Quang V. wrote:



      We are also having problems with VIC crashing even when beacon is 
disabled.  That brings up a question about installation.  When you install it 
on Vista/Windows 7, do you install it as Windows XP compatibility?  We are 
using AG Toolkits 3.1.

      Quang

      From: 
ag-tech-boun...@lists.mcs.anl.gov<mailto:ag-tech-boun...@lists.mcs.anl.gov> 
[mailto:ag-tech-boun...@lists.mcs.anl.gov] On Behalf Of Terry McGuire
      Sent: Monday, March 08, 2010 11:36 AM
      To: ag-t...@mcs.anl.gov<mailto:ag-t...@mcs.anl.gov>
      Subject: Re: [AG-TECH] Access Grid: Windows 7 and Vista support

      Even if you do have multicast, you can disable the beacon.  We're running 
Win 7 and have multicast running fine with the beacon disabled.

      Terry

      On 2 Mar 2010, at 2224h, John I. Quebedeaux, Jr wrote:

      Works fine for us here at LSU with both ? our new production machines are 
Win 7 for display and capture. If you don?t have multicast, disable the beacon 
I think is what everyone is saying. - John Q.


        _____

      From: Choon Ng <c...@ngame.edu.au<x-msg://273/c...@ngame.edu.au>>
      Date: Wed, 3 Mar 2010 15:23:50 +1100
      To: <ag-t...@mcs.anl.gov<x-msg://273/ag-t...@mcs.anl.gov>>
      Subject: [AG-TECH] Access Grid: Windows 7 and Vista support

      Does anyone know what's the support status for Windows 7 and Vista? AG 
seems to be crashing whenever VIC runs.

      ________________________________________________

      Terry McGuire
      Junior Analyst, Research Support Group
      Academic Information & Communication Technologies (AICT)
      University of Alberta
      Edmonton, Alberta, Canada  T6G 2H1
      Phone:  780-492-9422

      This communication is intended for the use of the recipient to which it 
is addressed, and may contain confidential, personal, and/or privileged 
information.  Please contact us immediately if you are not the intended 
recipient of this communication.  If you are not the intended recipient of this 
communication, do not copy, distribute, or take action on it.  Any 
communication received in error, or subsequent reply, should be deleted or 
destroyed.




Reply via email to