Hi all, I'm sorry I didn't answer before -- I completely missed the mail!
I think Adam and Greg have answered all your questions, but still I would just want to clarify: The standard utility for interacting with "video4linux 2" devices is v4l2-ctl. Therefore, in my (rather short, I have to admit) experience with video cards in linux, you should use this to set up any parameters you like (as long as the card supports that). you can see the man page for detailed info on how that works. As Adam and Greg said, there is a script which is run everytime matterhorn starts, called device_config.sh, which contains several v4l2-ctl commands to set the values for the cards which you chose in the installation scripts. This is because cards don't store those values by default, and they have to be set up everytime the system reboots. What I meant in my previous mail was that you can use v4l2-ctl to modify the card settings and, by some trial-and-error method, figure out what the correct settings are for the card. It seems that Greg and Adam gave you the answer (or at least a good suggestion) for those settings. If, by some chance, the card still doesn't work with them, you can modify the conflicting parameters using v4l2-ctl directly (again, please read the manual to learn the proper syntax, which is pretty straightforward --arguments in capitals show the current values, while non-capitals set the value. For instance, -S prints the current system, while -s <system> sets the card TV system to <system>; -I shows the current input, while -i <input> sets the input to <input>-, and so on). I hope this all helps. Best regards 2011/2/7 Adam Mckenzie <[email protected]> > Hi Everyone, > > Sorry I missed in Simen's comment that he was running 1.0. I was assuming > he was running 1.1 because he mentioned the CUSTOM_VIDEO_PRODUCER. The > CUSTOM_VIDEO_PRODUCER is actually only available in the matterhorn branch > 1.1.x or in trunk. It has actually been re factored heavily since 1.0. I > have fixed the bug that requires a src property and added some debugging > information around using custom pipelines but this won't do you any good if > you are using 1.0. > > Greg is probably right that your > /opt/matterhorn/capture-agent/device_config.sh has NTSC instead of PAL. It > probably looks something like: > > #! /bin/bash > v4l2-ctl -s 0 -d /dev/video1 > v4l2-ctl -d /dev/video1 -i 5 > > Which you can change to PAL mode by changing it to: > > #! /bin/bash > v4l2-ctl -s PAL -d /dev/video1 > v4l2-ctl -d /dev/video1 -i 5 > > The first line changes the input standard (NTSC vs. PAL) and the second > line changes the input (the Hauppauge card I currently have in my machine I > need to capture from input 5 hence -i 5) so both of these lines could be run > from the command line. > > If you are making changes to the code in > /opt/matterhorn/capture-agent/matterhorn-source and running install.sh > without redownloading it should deploy the new code. A handy logging message > might be the best way to make sure that your changes are making it in. > > Hope this helps, > Adam > > > On Mon, Feb 7, 2011 at 11:24 AM, shinymonk > <[email protected]>wrote: > >> >> Hi Rubén, >> >> I confirm, that this an issue as Adam Mckenzie suggested: >> https://opencast.jira.com/browse/MH-5404 >> because I see the video ok with using the video/x-raw-rgb-Pipeline but not >> with the other one in the issue description. >> >> Open question is, what can I do to change the implemented faulty pipeline >> to >> the working pipeline. >> I tried to mess with the JavaCode in PipelineFactory by adding/changing >> the >> code of the method getBluecherryPipeline() as highligted: >> ... >> if (framerate != null) { >> fpsCaps = Caps.fromString("video/x-raw-rgb, framerate=" + framerate + >> "/1"); >> logger.debug("{} fps: {}", captureDevice.getName(), framerate); >> } >> else >> fpsCaps = Caps.anyCaps(); >> fpsfilter.setCaps(fpsCaps); >> >> Element ffmpegcolorspace = ElementFactory.make("ffmpegcolorspace", >> null); >> pipeline.addMany(v4l2src, queue, videorate, ffmpegcolorspace, >> fpsfilter, >> enc, muxer, filesink); >> ... >> >> and rerun the ./install.sh script without re-downloading matterhorn >> source, >> but to no avail, still green is all I get. >> >> Any recommendations, what kind of workaround I can use to get the camera >> capture working ? Or will I have to wait vor matterhorn version 1.1 or >> even >> 1.2 ? >> >> Greetings, Andreas >> BTW: what do you mean with "Please use v4l2ctl to set the output format >> instead of the system" ? Please provide a short example. And thx for the >> recommendations ! >> >> >> Rubén Pérez-2 wrote: >> > >> > I just wanted to do some recommendations, but I hope I'm not stating >> > something too obvious (in the spirit of "divide and conquer"): >> > >> > - Please use v4l2ctl to set the output format instead of the system >> (ntsc >> > or >> > pal), or both parameters at the same time, but focus on that tool rather >> > than trying to combine the effects of Gstreamer and some random preset. >> > Those settings may be easily applied everytime the device is plugged in, >> > using udev rules. Therefore, try to set the camera working without >> > gstreamer >> > first (check with vlc or whichever player you want) >> > - Once you've got that right, try to use the line Adam suggested. He's >> our >> > gstreamer expert, and even though he may have mistakes, they are not >> > common. >> > Of course, try other configurations if that doesn't work, but always >> make >> > sure that the camera is well configured previously (using the procedure >> > you >> > came up with in the previous step). >> > - A word of advice, somehow unrelated with this topic: I would rather >> use >> > a >> > symlink than directly access to /dev/video0, at least when the system >> goes >> > into production or pre-production somehow. Even though we believe those >> > device names to be permanent, they're not. And while it's unlikely for >> > the >> > device assignment order to change, it may happen sometimes, that what >> you >> > usually get on /dev/video0 appears in /dev/video1 and vice-versa. That >> is >> > the reason why symlinks are created to access the devices with >> matterhorn: >> > udev uses some matching rules to create the link for the appropriate >> > device, >> > so that "/dev/camera" will always point to the same card, no matter >> which >> > video[0-9]* it may be. >> > >> > Good luck! >> > >> > 2011/2/4 shinymonk <[email protected]> >> > >> >> Just to add some more info about the behaviour: >> >> >> >> The camera shows OK when starting VLC-Player after fresh boot of Ubuntu >> >> 10.4.1.LTS. >> >> >> >> Starting a simple capture results in a green capture with a very thin >> >> stripe >> >> on the top showing camera content (ie. contents change with the moving >> of >> >> the camera). >> >> >> >> And after that capture, VLC-Player won't display the camera anymore, >> >> instead >> >> we see the green picture described above. >> >> >> >> Switching to NTSC and then to PAL makes it display correctly again. >> >> >> >> Switching directly to PAL has no effect. >> >> >> >> gst-launch -e v4l2src device=/dev/video0 ! ffenc_mpeg2video ! mpegpsmux >> ! >> >> filesink location=test.mpg >> >> >> >> results in a green picture also, whereas >> >> >> >> streamer -t 0:10 -s 352x240 -r 24 -o movie3.avi -f mjpeg >> >> >> >> results shows the camera ok. >> >> >> >> We read something about the palette not set correctly, but how to set >> it >> >> ? >> >> >> >> To me it seems, that the capture client somehow modifies the v4l2 >> >> settings, >> >> since VLC shows OK before the capture, but bad after the capture. How >> can >> >> this be prevented or circumvented ? >> >> >> >> Greetings, Andreas >> >> -- >> >> View this message in context: >> >> >> http://opencast.3480289.n2.nabble.com/Matterhorn-users-Problem-with-customProducer-in-capture-impl-configurationmanager-properties-tp5970958p5992442.html >> >> Sent from the Matterhorn Users mailing list archive at Nabble.com. >> >> _______________________________________________ >> >> Matterhorn-users mailing list >> >> [email protected] >> >> http://lists.opencastproject.org/mailman/listinfo/matterhorn-users >> > >> >> -- >> View this message in context: >> http://opencast.3480289.n2.nabble.com/Matterhorn-users-Problem-with-customProducer-in-capture-impl-configurationmanager-properties-tp5970958p6001042.html >> Sent from the Matterhorn Users mailing list archive at Nabble.com. >> _______________________________________________ >> Matterhorn-users mailing list >> [email protected] >> http://lists.opencastproject.org/mailman/listinfo/matterhorn-users >> > > > > -- > Adam McKenzie > MSc Student > ARIES Laboratory, University of Saskatchewan > > Web: http://aries.usask.ca/aiwiki/Adam_McKenzie > Mail: Advanced Research in Intelligent Educational Systems Laboratory > Department of Computer Science > University of Saskatchewan > 176 Thorvaldson Building > 110 Science Place > Saskatoon, SK > S7N 5C9 > > _______________________________________________ > Matterhorn-users mailing list > [email protected] > http://lists.opencastproject.org/mailman/listinfo/matterhorn-users > >
_______________________________________________ Matterhorn-users mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
