On 12-07-19 03:27 AM, adeseye a. (aa5g11) wrote: > Thanks Greg for your detailed response. It appears am trying to install the > core and CA on the same machine. I will do a seperate installation for it > now. concerning the capture, what configuration settings should I use to > capture both the video and audio when setting up the capture agent. I will > also prefer that the video format should be in mp4 and the audio in mp3. Can > I achieve this during set-up or do I need to create a new workflow and > encoding. from my understanding mp2 captures both the video and audio.
If you're using the installation script it should prompt you for each device that it detects. If it's not prompting you for an input that you're expecting to work then I would suspect that the device itself is not set up right. Are you using the reference hardware? Non-spec hardware should still work, but it could easily require drivers or some other setup steps that aren't included in the install script. Non-spec hardware also sometimes requires manual editing of the config file, see http://opencast.jira.com/wiki/display/MHDOC/Capture+Agent+Configuration+v1.3 and http://opencast.jira.com/wiki/display/MHDOC/Custom+Capture+Devices+v1.3. It's possible to get the reference CA to generate mp4 and mp3, but you will need beefier hardware than the reference I believe. Adam McKenzie, and/or the guys at UCB might have more insight into this. Keep in mind that the primary Matterhorn processing pipeline creates flvs containing Sorensen Spark (last I checked, this may have changed), so the input format matters little. G > Thanks > > Date: Wed, 18 Jul 2012 15:51:39 -0600 > From: Greg Logan <[email protected]> > To: [email protected] > Subject: Re: [Matterhorn-users] getting the capture agent running > Message-ID: <[email protected]> > Content-Type: text/plain; charset="iso-8859-1" > > On 12-07-18 03:33 PM, adeseye a. (aa5g11) wrote: >> Can someone help resolve this issue. >> Anticipating your prompt response. > > Unfortunately the European are likely asleep, and there aren't a huge > number of North American devs. Responses can take a day or two on list. > There is also an IRC channel at #opencast on freenode for live support > and chat, assuming people are around. > >> ________________________________ >> From: adeseye a. (aa5g11) >> Sent: 18 July 2012 14:03 >> To: [email protected] >> Subject: getting the capture agent running >> >> Hi, >> >> After installing the core. am trying the install the capture agent. after >> the installation, I think it failed to work. The URL >> http://localhost:8080/engage/ui and http://localhost:8080/admin/ which >> signifies the go to admin tools and go to media modules respectively display >> an http error 404. also clicking on the Go to Capture and clicking start >> capturing displays the error "There was a problem starting your capture, >> please check the logs". the log file is attached and the cofiguration of >> both the Core. Am not sure which directory to check to get the configuration >> file of the CA. the core files where copied from the directory >> /opt/matterhorn/felix/conf. can anyone please help resolve this issue. > > A few questions: > > 1. Are you installing a CA on your core? Or is this a separate machine? > 2. Your log appears to be from the CA, but the config files you > attached are labelled CORE. They appear to be from a CA, so are they > just a tad mislabelled? > > It's not recommended to install a full CA on a core. This will more > than likely mangle the config files quite badly if you use the install > script. I'm going to operate on the assumption that this is all on the > CA, and the core is somewhere else. In this case your configuration > files are incorrect, which explains the log messages you are seeing. > > config.properties: > > org.opencastproject.server.url is the URL to the current host. For > instance http://my_ca:8080 and http://my_core:8080, which I will use in > the rest of this email. Your CA's config file should contain the former > example, your core's config file should contain the latter. > > org.opencastproject.capture.impl.ConfigurationManager.properties: > > org.opencastproject.capture.core.url is the URL of the core which this > CA should talk to. This should be the same as the value of > org.opencastproject.server.url in your core's config.properties file. > > Also, your device configuration at the bottom of this config file is > badly mangled. It appears you removed the name of the device itself, > which means that your CA will not be able to capture properly. The > bottom five lines should look like this (replace my_device with whatever > friendly name you want to use): > > capture.device.my_device.src=hw: > capture.device.my_device.outputfile=.mp2 > capture.device.my_device.flavor=presenter/source > capture.device.my_device.buffer.bytes=536870912 > capture.device.names=my_device > > Just a warning, the above configuration will only capture the audio > input. It has no video inputs defined, which may or may not be what you > want! > > G > ________________________________ > From: adeseye a. (aa5g11) > Sent: 18 July 2012 22:33 > To: [email protected] > Subject: RE: getting the capture agent running > > Can someone help resolve this issue. > Anticipating your prompt response. > ________________________________ > From: adeseye a. (aa5g11) > Sent: 18 July 2012 14:03 > To: [email protected] > Subject: getting the capture agent running > > Hi, > > After installing the core. am trying the install the capture agent. after the > installation, I think it failed to work. The URL > http://localhost:8080/engage/ui and http://localhost:8080/admin/ which > signifies the go to admin tools and go to media modules respectively display > an http error 404. also clicking on the Go to Capture and clicking start > capturing displays the error "There was a problem starting your capture, > please check the logs". the log file is attached and the cofiguration of both > the Core. Am not sure which directory to check to get the configuration file > of the CA. the core files where copied from the directory > /opt/matterhorn/felix/conf. can anyone please help resolve this issue. > > thanks > > > > _______________________________________________ > Matterhorn-users mailing list > [email protected] > http://lists.opencastproject.org/mailman/listinfo/matterhorn-users >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Matterhorn-users mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
