MP4 video does not have sound after installation of codecs

[Eugenia Loli-Queru]

Binary package hint: gstreamer0.10-ffmpeg

After a clean installation of the latest Feisty ISO, I tried to play this file:
http://www.osnews.com/img/16983/f3.mp4
Ubuntu downloaded some gstreamer "ugly" codecs automatically, but it did not download everything needed. It didn't download the AAC and m4a support it seems. You see, after the automatic installation of the codecs, the video plays now, but not the sound. There is an error message with Totem saying that the following decoders were not found MPEG-4 Video decoder and MPEG-4 AAC decoder.

[Sebastian Dröge (slomo)]

Hi,
do you have gstreamer0.10-plugins-bad-multiverse installed?

[Eugenia Loli-Queru (eloli)]

No, Ubuntu only installed automatically gstreamer-extra-plugins and ffmpeg video plugin. This is the actual bug report: that Ubuntu did not *automatically* pulled that plugins-bad-multiverse package when Totem loaded the request.

BTW, I have now installed the "restricted extras" from multiverse, but the MP4 video still doesn't play on Totem. IMO support for these kinds of files must be added one way or another, because these videos is the same kind of MP4 videos cellphones produce so people would want to have access to them on their computer.

[Sebastian Dröge (slomo)]

Ok, most probably this is caused by the following:

mad and faad are currently registred to decode audio/mpeg. The former can do "audio/mpeg, mpegversion=1", the latter "audio/mpeg, mpegversion=[2,4]" though the latter part of each string is not saved in the package datebase.

Now if totem plays this file it notices that it can't play "audio/mpeg, mpegversion=4" and will ask gnome-codec-install. This will look in the database for "audio/mpeg", see that mad is installed which can handle this and is happy to tell totem that it can continue playing the file. Totem now still can't play the file and gives the error.

We definitely need proper caps intersecting in gnome-codec-install and the complete caps saved in the package/codec database to have this really working.

[Michael Vogt (mvo)]

Thanks for your bugreport and the detailed description.

This problem was a missing codec in the autoinstall whitelist. I added it and this problem should be fixed now.

@Sebastian: your analysis is correc, having caps intersection would be really good. but it did not trigger this problem.

Cheers,
 Michael

[Michael Vogt (mvo)]

This should work now in the current feisty.