Hi Fred, > i removed a different version i had of wxPython and xawtv and > installed your rpms using yum. that went smoothly. > > i rebuilt my node configuration and saved it. > i still get this parsing error from the ServiceManager: > INFO:ServiceManager:Using services dir: /home/aguser/.AccessGrid/local_services > INFO:ServiceManager:__DiscoverResources > config: invalid value for input: (null) > valid choices for "input": "Television", "Composite1", "S-Video", "Composite3" > config: invalid value for input: (null) > valid choices for "input": "Television", "Composite1", "S-Video", "Composite3"
That looks like the stderr of /usr/bin/v4lctl that gets echoed to the console. This is the output of a Digital HDTV TV capture card I'm using (which only has one analog input) : bash$ v4lctl list -c /dev/video0 1> /dev/null ioctl: VIDIOC_G_TUNER(index=0;name="";type=unknown;capability=0x0 [];rangelow=0;rangehigh=0;rxsubchans=0x0 [];audmode=MONO;signal=0;afc=0): Invalid argument config: invalid value for input: Television valid choices for "input": "Composite0" > and when vic fires up, i still need to change each video capture from > Composite1 to S-Video each time i change venues. > > also, i cannot see my own video in the VIC, although it is being broadcast. > aguser 4616 4416 7 12:58 pts/11 00:00:46 ./vic -u /tmp/VideoProducerServi > ce_4416.vic -C "Video" -t 127 224.2.177.155/55524 > aguser 4623 4442 9 12:58 pts/11 00:01:01 ./vic -C Access Grid Lobby -t 12 > 7 -XrecvOnly 1 224.2.177.155/55524 > aguser 4630 4433 5 12:58 pts/11 00:00:36 ./vic -u /tmp/VideoProducerServi > ce_4433.vic -C "Video" -t 127 224.2.177.155/55524 > > with my previous version of AG2.2, i could launch VIC by itself > (e.g vic 224.2.177.155/55524) and see my video streams along with the others > once i'd set the port from Composite1 to S-Video. that is no longer the > case. I'm not sure why there is a difference, I just checked out a newer version of vic from CVS before building the new RPM snapshot. > if i disable my firewall i don't get my video feeds in VIC. > > these are almost identical to the problems i was having before. > it must be an Osprey-specific issue. Notice the "invalid value for input: (null)" stderr output from /usr/bin/v4lctl. I think the corresponding V4L2 driver (the bttv driver?) needs some minor mods in the source code to indicate the inputs that particular model of Osprey capture card has, currently all the inputs on that card don't have a name. Cheers, Doug
