Please file an issue.... Chris
On Mon, 28 Mar 2011 16:14:31 +0200 Rubén Pérez <[email protected]> wrote: > If you have the default configuration for your TV (Hauppauge) card > and the default workflow, you're going to get the error described, > because: > > a) the Hauppauge hardware-encoded MPG stream does have an audio > track, even though no microphone is plugged to the card. The audio > should be stripped out of the mpg containter before storing it to a > file, which is not done by default. > b) the capture scripts show you the default sound card in the > computer to configure as the audio device. There are no options to > use the card or no information that the Hauppauge, once configured, > is *already* recording audio -if it is plugged to the card. > > In other words, the default configuration always fails. One can > either use the card audio input and not the default audio device (and > then, no audio device must be configured in the scripts, which is > counter-intuitive), or, because of the design of the pipeline in the > capture agent, include the key org.opencastproject.<DEVICE_ > NAME>.container (there are others than this one that work, too), > NAME>which will > effectively remove the audio from the card and send a single track > mpg file. > > I believe this behaviour should be considered a bug and a blocker, > since the basic configuration is failing and requires a (no matter > how small it is) change to function, but I reported it and it wasn't > considered a serious problem. I think it is a strong disagreement > between the CA and the core, and that should fixed somehow because it > makes no sense at all, but of course, this is only my opinion. > > Best regards > > P.S.: If you use the TV card audio and you erase the lines referring > to the capturer's audio card in the file > $FELIX_HOME/conf/services/org.opencastproject.capture.impl.ConfigurationManager.properties, > the processing should not fail at this step. > > > 2011/3/28 Greg Logan <[email protected]> > > > On 2011-03-27 11:46 PM, Jack Barokas wrote: > > > Hi there, > > > > > > > > > > > > I apologize in advance for my very limited understanding the > > > workflow of Matterhorn capture agent but I would like to take > > > both audio and video input from the TV card and not as it is > > > now, taking the video input from the card and the audio input > > > from the onboard audio card of the encoding machine. > > > > I don't remember exactly what you have in that machine, but what > > happens if you just disable the normal microphone input? Hopefully > > the workflow will just figure things out from there, but I'm not > > exactly a workflow expert... > > > > G > > > > > Can someone help me (I think Greg once tried to help me on this > > > but I was not successful) > > > > > > > > > > > > Best > > > > > > Jack > > > > > > > > > > > > *From:*[email protected] > > > [mailto:[email protected]] *On Behalf Of > > > *Josh > > Holtzman > > > *Sent:* Monday, March 28, 2011 7:38 AM > > > *To:* Opencast Matterhorn > > > *Subject:* Re: [Opencast Matterhorn] problems finding working > > > version of matterhorn and CA > > > > > > > > > > > > On Mon, Mar 28, 2011 at 12:07 AM, Greg Logan <[email protected] > > > <mailto:[email protected]>> wrote: > > > > > > On 2011-03-27 2:57 PM, Josh Holtzman wrote: > > > > It looks like your mediapackage contains two tracks with the > > > > "preseter/source" flavor. This would be OK if one track > > > > contained > > a > > > > video stream and another an audio stream, but if they both > > > > contain > > an > > > > audio stream, we won't know how to disambiguate which audio > > > > stream > > to > > > > use in subsequent workflow operations. Rather than picking > > > > one at random we throw this error so you can quickly see > > > > that there is a configuration problem. > > > > > > Why not mux the audio together by default? I bet most of the > > > time > > this > > > would be fine (since one track wouldn't have input) and it > > > would eliminate configuration issues like this? > > > > > > G > > > > > > > > > I'm not sure what you mean by "one track wouldn't have input". > > > This error is thrown only after we've inspected the media, so we > > > know that there are audio and/or video streams in both tracks. > > > > > > Josh > > > > > > > > > > > > _______________________________________________ > > > Matterhorn mailing list > > > [email protected] > > > http://lists.opencastproject.org/mailman/listinfo/matterhorn > > > > > > > > > To unsubscribe please email > > > [email protected] > > > _______________________________________________ > > > > > > > > _______________________________________________ > > Matterhorn mailing list > > [email protected] > > http://lists.opencastproject.org/mailman/listinfo/matterhorn > > > > > > To unsubscribe please email > > [email protected] > > _______________________________________________ > > -- Christopher Brooks, BSc, MSc ARIES Laboratory, University of Saskatchewan Web: http://www.cs.usask.ca/~cab938 Phone: 1.306.966.1442 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 mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
