Gour, I normally use the yuv stream piped to ffmpeg for video. The biggest problem I have is that the default ffmpeg options included on the render sub-window no longer exist (I can send you the options that work for me).
Audio, on the other hand is a real mess because I need to use 5.1 AC3 (Dolby Digital Surround Sound). My first priority is to get fileac3.C updated to properly use the current versions of libavcodec including options for different sample formats (U8, S16, S32, float, and double) and channel layouts(libavutil supports 16 different layouts). Once I get fileac3.C functioning as I want it, I will send the updates to this mailing list and then see if I can build a direct rendering methodology using ffmpeg, the current versions function calls provide much better functionality and flexibility than what's bundled with Cinelerra. Until I submit the upgrades, there are patches available for 2.1.5 to work with current versions of ffmpeg without any new functionality. I will verify that they work with 2.2 and submit an updated patch. Regards, Paul On Mon, 2011-09-19 at 21:23 +0200, Gour-Gadadhara Dasa wrote: > On Mon, 19 Sep 2011 14:43:59 -0400 > Paul Taggart <ptagg...@cinci.rr.com> wrote: > > > I'm a bit confused, why release an new release of Cinelerra with a > > version of ffmpeg that's 3 or 4 releases out of date? Version 0.4.9 is > > so far away from the current 0.8.2 that most of the ffmpeg functions > > no longer exist. I will build a new patch to work with 0.8.x but a > > decision needs to be made to either abandon or upgrade the internal > > ffmpeg because the amount of changes make supporting both obsolete > > and current versions impractical. > > Whenever I try Cinelerra using external ffmpeg on my x86_64 machine, rendered > mpeg (via yuv stream) is totally garbled. However, it works OK with internal > ffmpeg. > > I already posted about (see archives) considering one specific patch has > created the problem. > > > Sincerely, > Gour > >
