@LouL
__________________
You are right. using async > 2 does not give segmentation faults, neither in Jaunty, nor in Karmic, this workaround should work for me, thanks
@Reinhard Tartler
__________________
I use the "default" installation
in Karmic:
ffmpeg 4:0.5+svn20090706-2ubuntu2
libavcodec-extra-52 4:0.5+svn20090706-2ubuntu3
ubuntu-restricted-extras 36
and Jaunty:
ffmpeg 3:0.svn20090303-1ubuntu6
libavcodec-unstripped-52 3:0.svn20090303-1ubuntu2+unstripped1
ubuntu-restricted-extras 31
I would have to compile ffmpeg trunk on both to test, but as these are production servers I don't really dare.
The problems seems to be libavcodec, no?
If I find some time this afternoon I 'll compile trunk on clean Karmic, if it encoding produces segfault I'll report upstream bug.
In any case I'll let you know.
@LouL
__________________
You are right. using async > 2 does not give segmentation faults, neither in Jaunty, nor in Karmic, this workaround should work for me, thanks
@Reinhard Tartler 06-2ubuntu2 06-2ubuntu3 restricted- extras 36
__________________
I use the "default" installation
in Karmic:
ffmpeg 4:0.5+svn200907
libavcodec-extra-52 4:0.5+svn200907
ubuntu-
and Jaunty: -1ubuntu6 unstripped- 52 3:0.svn20090303 -1ubuntu2+ unstripped1 restricted- extras 31
ffmpeg 3:0.svn20090303
libavcodec-
ubuntu-
I would have to compile ffmpeg trunk on both to test, but as these are production servers I don't really dare.
The problems seems to be libavcodec, no?
If I find some time this afternoon I 'll compile trunk on clean Karmic, if it encoding produces segfault I'll report upstream bug.
In any case I'll let you know.