Congradulations, Doug! i believe we have a winner. even with these funky-ass Osprey cards and bttv-0.9.15, everything works as it should! both the VideoService and the VideoProducerService configs load properly and are reflected properly in the VIC.
RAT has been pretty stable on Fedora Core2 all along. the only issue i've got left (pretty minor) is that from this Gnome SM, if i run VenueClient from the GUI, it seems to not usually clean up and shut down cleanly and i usually have to go in and kill 4 or 5 python processes. if i run it from the command line, it seems much more accomidating when i tell it to die. no biggie, 'cause i can't stand Gnome anyway. so. i'm off to configuring fvwm with fvwm themes! Ta ta. --fred On Tue, Jul 20, 2004 at 09:26PM, Douglas Kosovic said: > Hi Fred, > > My apologies, I was inadvertently using and modifying VideoService.py & > VideoProducerService.py from the AGTk22_ServiceUpdate.zip file rather > than CVS. > > New modified versions of VideoService.py & VideoProducerService.py can > be found at: > > http://www.itee.uq.edu.au/~agn/ag_fedora/FC2/unstable/patches/ > > > this is a very interesting and promising upgrade of VideoServer.py > > VideoProducerService.py, on the other hand, is still languishing on my > > system. > > on one hand, your new VideoService.py breaks your previous patch's correct > > loading of the 'port' field in the [serviceconfig] for VideoService. > > 'same with VideoProducerService. The Venue Client comes up with a Service > > Manger where those fields are, again, defaulting to 'Television'. > > more importantly in my opionion, however, once those configurations are > > changed in the Configuration GUI for those services, the changes are > > transmitted correctly to VIC for VideoService. VideoProducerService still > > comes up defaulting to 'Composite1'. > > Hopefully it's fixed now, but I didn't get much chance today to to test > if there are still problems with the Configuration GUI for those > services. > > > Cheers, > Doug >