Greg,

 I believe I first set it up to be V4L2SRC, but an error occurred, and I
read in the custom capture devices page that I should use custom producer -
or that's what I understood. I cannot make the modifications now, but I
will do it later and let you know what happened.

 Thanks a lot! I appreciate the quick responses.

 Luis Galeana.

2012/7/27 Greg Logan <[email protected]>

> On 12-07-27 10:15 AM, Luis Galeana wrote:
> >  Hi, Greg,
> >
> >  I followed some examples from
> > here<
> http://opencast.jira.com/wiki/display/MHDOC/Custom+Capture+Devices+v1.3>
> > and
> > the instructions in the configuration manager file, but I could have
> easily
> > messed up. I am new to the media environment and I don't know about
> > encoding and that stuff.
>
> Yep, and it is somewhat confusing :)
>
> >  What I'm trying to do is to be able to record with my Webcam, which I
> > believe is a H264 device. The microphone was detected during the capture
> > agent installation, using the script. The webcam was not, and I added it
> to
> > the file. I'm not sure what kind of encoding (if any) or container to
> use.
>
> Baring some kind of super webcam, it's highly unlikely that the device
> itself is outputting h264.  More likely it's outputting raw uncompressed
> frames which your computer can then encode to h264.
>
> >  Could you elaborate a little on what you recommend I should do?
>
> Try removing the custom producer, and changing your type to V4L2SRC.
> This will encode to mpeg2, but requires fewer resources from your
> computer.  Once that's working we can step back up to h264 if you feel
> the need.
>
> G
>
> >  Thanks a lot.
> >
> >  Luis Galeana.
> >
> > 2012/7/27 Greg Logan <[email protected]>
> >
> >> On 12-07-27 09:12 AM, Luis Galeana wrote:
> >>>  P.S. I keep getting a warning that says that some capabilities and
> state
> >>> pushes failed with code 405. It repeats indefinitely. Some of the
> >> messages
> >>> can be seen at the end of the post.
> >>
> >> Ok, easy fix here.  The configuration you're using is incorrect, and
> >> it's a common newbie mistake.  The org.opencastproject.server.url entry
> >> is what Matterhorn actually listens on.  So, for your core is would be
> >> something like http://my_core.example.com:8080, and your CA would be
> >> http://my_ca.example.com:8080.  I would reset any of the other fields
> >> that you changed back to their default values, just to be safe (service
> >> registry on the core, for example).  Then, on the CA, you need to change
> >> the org.opencastproject.capture.core.url value to point at your *core*.
> >>  In the above example, the value would be
> >> http://my_core.example.com:8080.  Restart both Matterhorn instances and
> >> things should clear up.
> >>
> >>> 22:31:14  INFO (GStreamerPipeline:430) - Successfully initialised 2
> >> devices.
> >>> 22:31:14  INFO (CustomVideoProducer:73) - Custom Video Producer is
> using
> >>> Pipeline: "filesrc location=/dev/video0 ! mpegtsmux ! x264enc !
> >> videoscale
> >>> ! video/x-raw-yuv,width=1280,height=1024 ! queue"
> >>> org.gstreamer.GstException: could not link mpegtsmux0 to x264enc0
> >>
> >> Your custom producer appears to be... backwards?  Can I ask what kind of
> >> input this is?  You're taking the raw stream from the device, trying to
> >> mux it (without encoding it), then trying to encode the muxed stream
> >> (without scaling it), then trying to scale it.  I would suggest first
> >> off using the default pipelines, but if you really need that h264
> >> encoding then try reversing the order of the elements that come after
> >> the filesrc.  You may also want to change mpegtsmux to something else,
> >> I'm not entirely sure that you can link x264enc and mpegtsmux.  Take a
> >> look at the plugin caps to see.
> >>
> >> G
> >>
> >>
> >> _______________________________________________
> >> 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
> >
>
>
>
> _______________________________________________
> 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

Reply via email to