Transcode segfaults using vid.stab stabilization

Bug #789649 reported by Michiel van Wessem
52
This bug affects 9 people
Affects Status Importance Assigned to Milestone
transcode (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: transcode

 vid.stab filters filter_stabilize and filter_transform cause a Segmentation Fault.

This is too bad, because this appears to be the only/only convenient way to stabilize video on Linux.

Revision history for this message
Michiel van Wessem (windsunrain) wrote :

I'm using 11.04 x86_64.

transcode -J on all my 1-5 minute 720p MP4/AVC/H.264 files stabilize causes a segfault in the standard package (after numerous [filter_stabilize.so] warning: unsupported Codec: 2 ( 9| 0|11) messages.

I tried to rebuild the package from the Ubuntu source. This exposed a bug in gcc when building filter_smartyuv. By eliminating filter_smartyuv, I was able to rebuild.

But to no avail. Same issue.

I also tried rebuilding from the transcode 1.1.5 tarball. This produces a filter_stabilize that does succeed and does not show all the unsupported Codec messages, however the transcode -J transform step produces a segfault.

Revision history for this message
Michiel van Wessem (windsunrain) wrote :

Upgrading to GCC 4.6 allowed successful compilation of the entire package, but the segfault on filter_stabilize persists.

Revision history for this message
Michiel van Wessem (windsunrain) wrote :

transcode segfault is in quicktime_decode_audio, called from import_mov_decode in import_mov.c, line 426

Audio on my MP4 files is MPEG-4 AAC audio, Stereo, 16kHz, 61 kbps

This segfault is not related to filter_stabilize.so

Revision history for this message
Gabriel (misc-evotex) wrote :

works for me on 32bit 11.04, transcode 1.1.5, vid.stab 0.75 (downloaded from http://public.hronopik.de/vid.stab/download.php?lang=en)

Revision history for this message
Alexey Osipov (lion-simba) wrote :

The "unsupported Codec" problem caused by patch 05_codec_yuv.diff in Ubuntu source deb. When I disable this patch in debian/patches/series, and rebuild the package, stabilizing works fine for me even with vid.stab 0.61.

05_codec_yuv.diff description says that the patch fix a typo CODEC_YUV -> TC_CODEC_YUV420P. My question is: what side effects will appear if we just drop this patch? Is this patch fixing some bug? Anyone have a link, clarifying why this patch is necessary?

Changed in transcode (Ubuntu):
status: New → Confirmed
Revision history for this message
Alexey Osipov (lion-simba) wrote :

You can find fixed version of transcode in my PPA: https://launchpad.net/~lion-simba/+archive/fixes/

There are versions for Lucid and Natty.

Revision history for this message
BlackDragon (walbertr) wrote :

When reading the bug-reports, this error seems to occur only on the 64 bit version. When operating on 32 bits, the programme seems to work as normal. I have ubuntu 11.4 64 bits installed, and it occurs for me (unsupported codec).

Revision history for this message
BlackDragon (walbertr) wrote :

From: http://public.hronopik.de/vid.stab/files/Changelog

0.76 BUGFIX in calcFieldTransYUV caused SEGFAULT

Bug seems to be fixed in the upstream.

Revision history for this message
tankdriver (stoneraider-deactivatedaccount) wrote :

I have this bug too with oneiric 64-bit.
The files from the link in the comment above does not work (crash) and I can't install package from the PPA neither.
;-(

Revision history for this message
Alessio Treglia (quadrispro) wrote :

Hi,

thanks for the report.

Could you try to reproduce this with the latest upstream release available in Quantal?

Changed in transcode (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for transcode (Ubuntu) because there has been no activity for 60 days.]

Changed in transcode (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Edward (edward-coffey) wrote :

This is still an issue in trusty.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.