Doug, Thanks for the response. It gave me some ideas...
Okay everyone, So I can force vic to show my video streams, but I still can't get the NodeSetupWizard to acknowledge them... Here's what I did... I started AGServiceManager (attached AGS2.OUT output) Then I started the NodeSetupWizard (attached NODES.OUT) which again only showed x11 as a video source. So I started up the Venue Client and then started an AGNodeService instance (AGN.OUT). Adding the localhost as a service manager and adding a VideoConsumer service along with a VideoProducer service (again only x11 visible), I then see ~.AccessGrid/local_services/VideoConsumerService and VideoProducerService. I initiate vic using ./vic localhost/1283 (VIC2.OUT) I then manipulate the port and device and lo and behold I see my video feed. So, did I find a bug? What do I win? Can I win a fix if I can't create one? --Vic ----- Original Message ----- From: "Douglas Kosovic" <dougl...@itee.uq.edu.au> To: <ag-t...@mcs.anl.gov> Sent: Sunday, August 15, 2004 9:06 PM Subject: Re: [AG-TECH] 2.2 video problems. > Hi Vic, > > > So I had this linux box with 2.1.2 working just fine. > > > > Now that I have removed 2.1.2 and installed 2.2 I can't seem to get > > any video feed working. I installed xawtv (wasn't installed for > > 2.1.2 -- but v4l2 was). > > > > When running a prog like xcam, I can see my video feed just fine. > > When I try using xawtv, however, I get a blank screen. I've tried > > xawtv 3.54 to 3.93. > > It would be better to test it with vic, which can be found in a subdir of > ~/.AccessGrid/local_services/ , assuming you've enabled at least one of the > Video Services in AGTk. > > Only v4lctl is used from xawtv, you could try the following to see if it > detects the input ports: > /usr/bin/v4lctl -c /dev/video0 list > > > I've seen some posts that say I should edit the videopath in > > /usr/lib/python2.2/site-packages/AccessGrid/Platform/unix/Config.py > > to point to /dev instead of /proc/video/dev. I've done this, but it > > just makes the x11 feed disappear. > > You might want to have a look at the following log: > ~/.AccessGrid/Logs/ServiceManager.log > > or use the --debug switch with ServiceManager.py to see if there is any > useful diagnostic info. > > The V4L devices might be busy (i.e. you have other applications accessing > the V4L devices) when the ServiceManager tries to interogate them for their > input ports. > > > Cheers, > Doug
VIC2.OUT
Description: VIC2.OUT
AGS2.OUT
Description: AGS2.OUT
NODES.OUT
Description: NODES.OUT
AGN.OUT
Description: AGN.OUT
