On 23/08/12 15:32, Oliver Burger wrote:
No comments on that? If I don't get any replies in the next days, I will
disable ffmpeg support in grass for the time being until upstream gets
it sorted out.
If this shouldn't happen before the Mga3 freeze, I will note it in the
Hi Master,
In my opinion, you should disable ffmpeg because the new ffmpeg 0.11 is
a completely new API. This kind of fixes should come from upstream.
I got into the same problem with "motion" and I had to disable
temporarily ffmpeg till it was fixed in git upstream.
Cheers,
Chris.
