FS#31419 - [audacity] cannot load FFmpeg

Attached to Project: Arch Linux
Opened by Kazó Csaba (kazocsaba) - Wednesday, 05 September 2012, 10:37 GMT
Last edited by Eric Belanger (Snowman) - Wednesday, 05 September 2012, 17:16 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Audacity cannot load FFmpeg libraries.

From the log:
12:32:13: Audacity 2.0.2
12:32:14: Trying to load FFmpeg libraries...
12:32:14: Trying to load FFmpeg libraries from system paths. File name is 'libavformat.so.53'.
12:32:14: Checking for monolithic avformat from 'libavformat.so.53'.
12:32:14: Error: libavformat.so.53: cannot open shared object file: No such file or directory
12:32:14: Loading avutil from 'libavutil.so.51'.
12:32:14: Loading avcodec from 'libavcodec.so.53'.
12:32:14: Error: libavcodec.so.53: cannot open shared object file: No such file or directory
12:32:14: Loading avformat from 'libavformat.so.53'.
12:32:14: Error: libavformat.so.53: cannot open shared object file: No such file or directory
12:32:14: Error: Failed to load FFmpeg libraries.
12:32:14: Error: Failed to find compatible FFmpeg libraries.


Relevant packages:

Audacity: 2.0.2-1
FFmpeg: 1:0.11.1-1
FFmpeg-compat: 20120509-1
This task depends upon

Closed by  Eric Belanger (Snowman)
Wednesday, 05 September 2012, 17:16 GMT
Reason for closing:  Not a bug
Comment by Eric Belanger (Snowman) - Wednesday, 05 September 2012, 15:44 GMT
You need to tell it where the library is located:

Preferences -> Libraries then click on "Locate..." button for the ffmpeg libraries. You then need to select the libraries from the ffmpeg-compat package (/usr/lib/ffmpeg-compat/libavformat.so.53).
Comment by Kazó Csaba (kazocsaba) - Wednesday, 05 September 2012, 16:46 GMT
You're right. It is my mistake. Audacity said that it needed libavformat.so.52, because of some previous configuration or something, so it was the .52 file I was looking for. And then I copied the log from a whole different installation.

Sorry about that.

Loading...