Please refer to bug 4153 for further info This version of blender should have a tainted version in a similar way to avidemux and others which have a statically linked ffmpeg.
Do we know if blender supports faad, opencore-amr, libvo-aacenc, or libvo-amrwbenc? Those are enabled in the tainted ffmpeg, but I don't see anything in the configure options blender is using for its bundled ffmpeg explicitly enabling those ones. If it doesn't support those, this might be as simple as disabling the patch that disables lame, xvid, and x264. --- blender-no-patent.spec 2012-03-20 09:42:30.846632706 -0400 +++ blender.spec 2012-03-20 09:42:35.486623954 -0400 @@ -63,6 +63,10 @@ %{?_with_avoidpatent: %global avoid_dunno_patent 1} %{?_without_avoidpatent: %global avoid_dunno_patent 0} +%if "%{?distro_section}" == "tainted" +%define avoid_dunno_patent 0 +%endif + %if %{use_smp} %define scons_smp --debug=time -j %(expr $(getconf _NPROCESSORS_ONLN) + 2) %else @@ -213,6 +217,9 @@ BuildRequires: libtheora-devel %endif BuildRequires: ImageMagick +%if ! %avoid_dunno_patent +BuildRequires: libxvid-devel liblame-devel x264-devel +%endif Requires: python-imaging >= 1.1.4 Requires: libtiff Suggests: yafaray
CC: (none) => luigiwalser
Created attachment 1810 [details] bundled ffmpeg configure output from build log Shlomi has built a tainted version with the above patch, so it can be tested. I'm attaching an excerpt of the build log from the build system: http://pkgsubmit.mageia.org/uploads/done/1/tainted/updates_testing/20120321121529.shlomif.valstar.20918/blender-2.49b-11.2.mga1.tainted/build.0.20120321121604.log The excerpt shows the configure output from ffmpeg, so we can see what is enabled and disabled in the internal build. If there are any supported codecs that don't work, we should be able to see pretty easily from this why.
The tainted build for blender is now available. I think you'll find as I did back in March (when testing this crashed and corrupted my VM :o) after this was added that it doesn't help much.
Depends on: (none) => 6485
Source RPM: blender 2.49b => qt4
Source RPM: qt4 => blender
https://bugs.mageia.org/show_bug.cgi?id=6485#c6 "After discussing with David, it appears that we don't need to push the tainted build, it belongs to another bug report." So what about this bug ? (the build is still in testing)
As I said in Comment 3, the tainted build didn't fix the issues like we hoped it would. This feature apparently just doesn't work very well in the version of Blender we have in Mageia 1.
Source RPM: blender => blender-2.49b-11.3.mga1
Source RPM: blender-2.49b-11.3.mga1 => blender-2.49b-11.3.mga1.tainted
This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 1's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 1 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad
Seems like an old bug, which is mostly fixed in Mageia 2. Until further notice, I am resolving it as OLD.
Status: NEW => RESOLVEDResolution: (none) => OLD