OpenShot crashes when trying to encode with libfaac

Bug #505368 reported by Nicola Ferralis
24
This bug affects 5 people
Affects Status Importance Assigned to Milestone
OpenShot Video Editor
Confirmed
Wishlist
Unassigned

Bug Description

Using OpenShot 1.0 on Ubuntu karmic. When trying to encode a movie for YouTube HD which uses libfaac, OpenShot crashes. This only happens while using libfaac.

Revision history for this message
Nicola Ferralis (feranick) wrote :

The encoding works if I install medibuntu version of libfaac (which has aac support enabled). Regardless, OpenShot should not simply crash with no intuitive message about the problem. The correct behavior should be a warning message saying that the ffmpeg version supplied lack the aac support, and it should point to a source (medibuntu?) where such support is provided. Simple crash doesn't help...

summary: - OpenShot cannot crashes when trying to encode with libfaac
+ OpenShot cannot crash when trying to encode with libfaac
summary: - OpenShot cannot crash when trying to encode with libfaac
+ OpenShot crashes when trying to encode with libfaac
Revision history for this message
Vladimir Yakovlev (nagos) wrote :

Same problem, you must install libavcodec* and libavformat* from medibuntu to work.

Revision history for this message
Daz23 (daz2three) wrote :

Here's the command line info during the crash.

consumer_avformat.c: audio codec libfaac unrecognised - ignoring
consumer_avformat.c: video codec libx264 unrecognised - ignoring
consumer_avformat.c: Unable to encode audio - disabling audio output.
[mp4 @ 0x2683160]track 1: codec frame size is not set
Floating point exception

Revision history for this message
Daz23 (daz2three) wrote :

Thanks Vladimir,
Installing libavformat-extra-52 and libavcodec-extra-52 from Medibuntu repository has fixed the HD encoding for me.

Revision history for this message
Jonathan Thomas (jonoomph) wrote :

Sounds like the solution is to install libavformat-extra-52 and libavcodec-extra-52. I am marking this incomplete, since this does not require a fix to OpenShot. Thanks!

Changed in openshot:
status: New → Incomplete
Revision history for this message
OiPenguin (lars-andreas-kvisle) wrote :

Confirmed that the problem described in <a href="https://bugs.launchpad.net/openshot/+bug/505203/comments/1">duplicate bug</a> is solved by installing libavformat-extra-52.

Revision history for this message
Nicola Ferralis (feranick) wrote :

I don't think it's fair to say that OpenShot doesn't need a fix. For the casual user, with the stock version of ffmpeg, OpenShot just crashes, woth no indication of what the problem is. This is a HUGE usability issue, that should be dealt within OpenShot somehow. Here's a couple of suggestions:

1. disable HD endoding if the correct libraries are not present. Clearly indicate that for HD to work, medibuntu needs to be used.
2. Instead of just closing the program, at least a warning of the problem of the solution.

Just the way it is now show poor QA, in my modest opinion.

Revision history for this message
Jonathan Thomas (jonoomph) wrote :

Good point. OpenShot could do a better job of prompting the user. But for right now, it sounds like we have solved the issue. I'll mark this as a "wishlist" item... specifically to improve the prompting about which formats are supported and not supported. I really wish ffmpeg had a way to help me determine which formats were installed. That would be nice.

Changed in openshot:
importance: Undecided → Wishlist
status: Incomplete → Confirmed
Revision history for this message
Jamin W. Collins (jcollins) wrote :

Wishlist? You're kidding right?

From your own release notice:

Improved Stability - Just try and crash OpenShot now. We dare you. Seriously though, many common issues that would crash OpenShot have been resolved, and the overall stability is great now.

Yet, what do we find almost immediately upon release? It's extremely easy to crash because basic checks aren't being made. Worst case the command should attempt to execute, error, and the application should remain running and report that the encoding failed. And now you're classifying these basic checks as "wishlist"? Anything that results in the application utterly bailing out and exiting is *far* from "wishlist". In fact, I'd say it's *critical*.

Revision history for this message
Hasnain Lakhani (m-hasnain-lakhani) wrote :

It's just poor QA to allow the software to crash with a known issue, instead of patching the software to (at the bare minimum) stop the offending action from taking place. A simple message showing a warning and a suggestion to install the required packages would be more than enough. As a LOT of users do encode high definition videos these days, this is not just a *wish* but an important fix.

Revision history for this message
Jonathan Thomas (jonoomph) wrote :

We are working hard to resolve these issues. We can not fix them all at once. Please be patient and we'll update this ticket when it's fixed. I agree that this is a big deal, and we'll try to get it fixed quickly.

Revision history for this message
Jamin W. Collins (jcollins) wrote :

I think you misunderstand. The issue here (at least for me) isn't how fast a bug is (or isn't) fixed. Instead it's the apparent lack of concern, based on the previous ticket actions. First the ticket was marked as "Incomplete", then as an apparent compromise it was upgraded to "Wishlist". Both of these are complete understatements of this bugs impact and importance. Neither of these would leave anyone viewing this ticket with any indication that this is seen by the developer (you) as "a big deal", but rather quite the opposite.

Revision history for this message
Noel Arzola (noel.arzola) wrote :

ppp@904:~$ openshot
Added /usr/share/openshot to system path
--------------------------------
   OpenShot (version 1.0.0)
--------------------------------
/usr/share/openshot/windows/SimpleGladeApp.py:340: GtkWarning: gtk_toolbar_set_icon_size: assertion `icon_size != GTK_ICON_SIZE_INVALID' failed
  return gtk.glade.XML(self.glade_path, root, domain)
A new frmMain has been created
on_mnuMakeMovie1_activate called with self.mnuMakeMovie
on_tlbMakeMovie_clicked called with self.mnuMakeMovie
on_cboProjectType_changed
on_cboExportTo_changed
on_cboProjectType_changed
on_btnExportVideo_clicked
consumer_avformat.c: audio codec libfaac unrecognised - ignoring
consumer_avformat.c: Unable to encode audio - disabling audio output.
[mp4 @ 0xb609430]track 1: codec frame size is not set
Floating point exception
ppp@904:~$

9.10 ops 1 youtube hd

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

Other bug subscribers

Related questions

Remote bug watches

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