audio codec unrecognised

Asked by Al Williams

Only a few export settings work for me. And unfortunately all of them that work are ok on my machine but after processing by YouTube have all the audio up front at light speed (about 1 or 2 seconds of chipmunk chatter -- the video is normal).

Running with a console reveals messages like:

on_btnExportVideo_clicked
consumer_avformat.c: audio codec libmp3lame unrecognised - ignoring
Segmentation fault

I have libmp3lame installed (x64) both "regular" and "dev" flavors.

Any suggestions? If this were fixed and the issue when you cut video the audio goes out of sync (which I know is an MLT problem) I would actually be able to use this program -- which would be cool.

Thanks!

Question information

Language:
English Edit question
Status:
Answered
For:
OpenShot Video Editor Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Helen McCall (wildnfree) said :
#1

Hello Al,

Please will you tell us which version of OpenShot you are using?

Also whether .deb or wizard used to install. And which operating system and version and whether 32 or 64 bit please?

Thanks, Helen

Revision history for this message
Helen McCall (wildnfree) said :
#2

I can confirm this as a bug:

Not the primary instance of OpenShot. Not starting queue watcher thread.
on_tlbMakeMovie_clicked called with self.tlbMakeMovie
on_cboProjectType_changed
on_cboExportTo_changed
on_cboProjectType_changed
on_btnExportVideo_clicked
consumer_avformat.c: audio codec libmp3lame unrecognised - ignoring
on_frmExportVideo_destroy

I am going to convert this to a bug report.

Helen

Revision history for this message
Hans Petter Birkeland (hanspb) said :
#3

I have a related problem. I am not exporting to Youtube, so I don't know anything about that. I do my filming with a stills camera with 640x480 resolution, and I want my finished videos to be 720x576 Pal. So I made a test project containing one short clip to keep the rendering time down. With "Project Type" set to "All formats" I went through every item on the "Target" list and exported with "Video Profile" set as DV PAL and "Quality" set to High. 7 of them ended with messages about unrecognized audio and/or video codecs and then either a segmentation fault or a floating point exception and a crash. These made an empty or a very small file of a few bytes. 3 of them complained about a missing codec but still made a valid video file. 2 of them (AVI mpeg2 and MPEG mpeg2) were completely successful without complaints and one (FLV h.264) complained about both audio and video codec and gave out a file with black video and white noise as audio.

As far as I can see I have all the codecs installed, so that should not be a problem.

All the details can be fount here:
ftp://81.191.206.144/ftp_pub/OpenShot/OpenShot_test_report.ods

This is with OpenShot 0.9.52 installed from .deb on Linux Mint 6 (Ubuntu 8.10 based). 32 bit architecture.

Also, I would like to know, are the lists of codecs hard coded, or do they relate to the codecs actually available on the system? Either way I think codec problems should be handled without crash. Just check if all the codecs are present at startup, and if not grey them out in the list.

I'll post a separate question about my other question.

All the best,
Hans Petter Birkeland

Revision history for this message
Jonathan Thomas (jonoomph) said :
#4

The codecs are hard-coded (at least for now). I haven't figured out how to dynamically get a list of installed codecs. The ffmpeg command line seems to always return all of the codecs... whether they are installed or not.

Yes, I agree that OpenShot should not crash if you choose an invalid codec. However, when MLT crashes, it kills the Python interpreter before I can handle the error. So... this is a work in progress. =)

Revision history for this message
Hans Petter Birkeland (hanspb) said :
#5

I see. So it is MLT that doesn't recognize codecs that in fact are installed?

Can you help with this problem?

Provide an answer of your own, or ask Al Williams for more information if necessary.

To post a message you must log in.