On Sun, 2010-03-14 at 18:16 +0300, Stanislav Maslovski wrote: > On Sun, Mar 14, 2010 at 04:09:45PM +0200, Uoti Urpala wrote: > > You've specified the --ffmpeg-source-dir option to enable code that > > depends on internal FFmpeg implementation details. > > Yes, you are right, I forgot to mention that. > > > It's expected that you may encounter exactly this kind of problems if > > you specify that option (and so generally you should mention you've > > enabled it when reporting problems, and test whether things work > > without it - in this case they should). > > Well, it worked before. The issue is exactly that even if it works at some point it can break at any FFmpeg change, and I won't check (and especially not immediately fix) that before updating the default FFmpeg version specified in the build repo. And users can use FFmpeg versions other than the default one anyway. > > I'll look at fixing the build with the unsafe option enabled later, it > > should probably be easy. > > Thanks. Why did you enable it btw? I think lavcac3enc is one of the main reasons people enable it, and that could be easy to fix to work reliably (so that option isn't needed). Maybe I'll do that instead of fixing the build with FFmpeg internals now.
