Makes sense to me. So to rephrase my original question into a word of caution:
If you are using a recent build of ffmpeg, be sure to fix the spelling errors in the Matterhorn encoding profiles. Thanks, Josh On Aug 1, 2011, at 12:46 PM, [email protected] wrote: > Hi Josh, > > I'm really on the side of "if it ain't broke....". Unless someone is willing > to > take the task of testing the new ffmpeg against a number of different types of > media (capture agent, non capture agent, streamed via red5, progressive, etc.) > I wouldn't be for changing our ffmpeg. > > Especially since people can upgrade manually if they really really want to. > > Of course, if there is someone willing to take on this testing task, then I > say > lets upgrade. > > Chris > > > Quoting Josh Holtzman <[email protected]>: > >> I'm running Matterhorn trunk on a new laptop with the trunk version of >> ffmpeg. It looks like they fixed a spelling error, so "-strict inofficial" >> has now become "-strict unofficial". This means that our encoding profiles >> are broken when working with the trunk version of ffmpeg. >> >> Any opinions on what we should do about this? Should be upgrade to ffmpeg >> trunk for 1.3, and fix our encoding profiles? Or leave them as is? >> >> 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] _______________________________________________
