Bug 10900

Summary:	Since update of libavformat, MPEGS no longer playable in Audacity or Totem
Product:	Mageia	Reporter:	Doug Laidlaw <laidlaws>
Component:	RPM Packages	Assignee:	José Jorge <lists.jjorge>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	Normal	CC:	fundawang, mageia
Version:	3
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:	libavformat54-1.1.5-1.mga3	CVE:
Status comment:

Description Doug Laidlaw 2013-08-02 15:37:46 CEST

Description of problem:

MPEGS no longer playable in Audacity or Totem

Version-Release number of selected component (if applicable):


How reproducible:
   Obvious.

A few days ago, I found that Totem could not find the codec to play MPEGS.

A post on alt.os.linux.mageia says that Audacity can't open the MPEG codec in libavformat, using 64-bit:

<quote>
Clean install of Mageia3. I am trying to import video clips intoÂ 
Audacity as I did in Mageia2 to select just one audio channel, butÂ 
Audacity claims to not understand the video format.

If I check on preferences of Audacity, it says can't find FFMPEG library.
</quote>

I went to my Audacity on i586 and was greeted with the following:

<quote>
"FFmpeg was configured in Preferences and successfully loaded before,Â 
but this time Audacity failed to load it at startup."Â 
</quote>

Audacity is looking for libavformat52, while the current version is libavformat54.  Looks as though some consequencial changes have been overlooked?


Reproducible: 

Steps to Reproduce:

Comment 1 David Walser 2013-08-10 22:49:20 CEST

If I remember correctly, audacity wasn't compatible with the version of ffmpeg that we shipped in Mageia 3.  We were waiting for this to be corrected upstream in audacity, but it wasn't fixed in time for the Mageia 3 release, so we had to disable the ffmpeg support in audacity.  Whenever audacity fixes this incompatibility and releases a new version, we can backport and ship it for Mageia 3.  As far as I know, they haven't fixed it yet.

CC: (none) => fundawang, mageia
Assignee: bugsquad => lists.jjorge

Comment 2 Doug Laidlaw 2013-08-11 04:06:04 CEST

Thanks David.  I don't need the particular combination.  I will pass your comments on.

Comment 3 David Walser 2013-08-21 00:11:31 CEST

Sure thing.  This is basically the same issue (and will have the same fix) as Bug 9043, so marking this one as a duplicate.

*** This bug has been marked as a duplicate of bug 9043 ***

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE