This issue was fixed five years ago in FFmpeg, please close this bug.
On Mon, Jun 11, 2012 at 4:27 PM, Reinhard Tartler wrote:
> tag 677035 upstream
> stop
>
> On Mon, Jun 11, 2012 at 3:04 PM, wrote:
>> On Mon, Jun 11, 2012 at 12:05:05PM +0200, Reinhard Tartler wrote:
>>>
>>> In order to check if that bug has already been fixed upstream, could
>>> you please insta
tag 677035 upstream
stop
On Mon, Jun 11, 2012 at 3:04 PM, wrote:
> On Mon, Jun 11, 2012 at 12:05:05PM +0200, Reinhard Tartler wrote:
>>
>> In order to check if that bug has already been fixed upstream, could
>> you please install the libavcodec-extra-53 package from backports.org
>> and check if
On Mon, Jun 11, 2012 at 12:05:05PM +0200, Reinhard Tartler wrote:
>
> In order to check if that bug has already been fixed upstream, could
> you please install the libavcodec-extra-53 package from backports.org
> and check if the segmentation fault still occurs?
>
I've just tried libav-tools 4:0
On Mon, Jun 11, 2012 at 11:40 AM, giuseppe bonacci wrote:
> Package: libavcodec52
> Version: 4:0.5.8-1
> Severity: normal
>
>
> When transcoding an MP4 stream (h264 + aac), to avi (mpeg4 + mp3lame),
> I get a SEGV in sad16_sse2(). Please note that I have rebuilt
> ffmpeg-0.5.8-1 (via dpkg-buildpa
Package: libavcodec52
Version: 4:0.5.8-1
Severity: normal
When transcoding an MP4 stream (h264 + aac), to avi (mpeg4 + mp3lame),
I get a SEGV in sad16_sse2(). Please note that I have rebuilt
ffmpeg-0.5.8-1 (via dpkg-buildpackage) in order to include libmp3lame.
Here is the command line:
/usr/
6 matches
Mail list logo
