Bug 1384180

Summary: Cannot add movies to Blender
Product: [Fedora] Fedora Reporter: Yajo <yajo.sk8>
Component: blenderAssignee: Luya Tshimbalanga <luya_tfz>
Status: NEW --- QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 27CC: design-devel, hobbes1069, jochen, kwizart, luya, luya_tfz, promac
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-10-14 21:55:34 EDT Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Yajo 2016-10-12 14:22:23 EDT
Description of problem:
Using its built-in Video Sequence Editor, I cannot input any video file.

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

How reproducible:

Steps to Reproduce:
1. Open Blender.
2. Open its Video Sequence Editor.
3. Press Shift+A.
4. Choose "Video".
5. Choose a video file.

Actual results:
UI says:
  File /home/yajo/Vídeos/GOPR4948-20161012-194939.webm could not be loaded
Console logs say:
  not an anim: /home/yajo/Vídeos/GOPR4948-20161012-194939.webm

Expected results:
File loaded.

Additional info:
I only tried with MP4 and webm files.
This thread seems related: http://blender.stackexchange.com/questions/28839/cannot-load-movie-files-on-ubuntu
It suggests to add ffmpeg support at compile time. I hope that's possible.
I have ffmpeg installed from RPMFusion, with no luck.
Comment 1 Yajo 2016-10-13 03:02:03 EDT
Workaround: Install from blender.org
Comment 2 Luya Tshimbalanga 2016-10-14 21:50:52 EDT
Hi Yajo, 
Unfortunately ffmpeg support for Blender 3D in Fedora version is disabled due to the encumbered patents it contains. Please read this information about software patents (https://fedoraproject.org/wiki/Software_Patents). A side effect of ffpmpeg being the sole video plugin impacts the support of unencumbered patented codecs like webm and ogg.

An alternative will be supporting gstreamer but that request needs to be addressed upstream. I hope these information helps clarifying the current condition of Video Sequence Editor in Blender.
Comment 3 Yajo 2016-10-17 05:09:45 EDT
Thanks, reported upstream: https://developer.blender.org/T49752
Comment 4 Yajo 2016-10-17 06:53:42 EDT
They answered a intelligent option. Any thoughts on https://developer.blender.org/T49752#399201, please?

(Sorry for reopening, close it again if you still consider this a CANTFIX please)
Comment 5 Nicolas Chauvet (kwizart) 2016-10-17 10:29:46 EDT
So, no it's not possible for us to do the same as debian.
IIRC, debian only disable encoders that might be patented and leaves all decoders.

Also, it's not only a matter to make a single ffmpeg disabled version and shooting such nuked version to the users face. It has to be maintainable across versions instead.

I would voice for having a look at what is done with firefox instead.
That might be interesting for blender upstream because that's an equivalent situation with them. Right now, firefox is built with the ffmpeg headers, but does not link to ffmpeg libraries, instead they dlopen them at runtime which allows them to enabled the possibly patented codecs.

The last solution that might be available is for blender upstream to provide flatpak, so that will be compatible with every distro out there.
Comment 6 Yajo 2016-10-18 03:31:05 EDT
Do you think you could join that upstream thread I linked above and speak directly to them about these things?

After all you are the one with this knowledge and me just a user...

Thanks! :)
Comment 7 Yajo 2016-10-31 04:27:05 EDT
After reading upstream's answer, although I certainly consider your solution is better, I have been reading about ffmpeg compilation, and there are acouple of interesting links:


It seems you can certainly enable only the free-of-patent-problems parts of FFmpeg, what would be the legal problem with packaging that?
Comment 8 Fedora End Of Life 2017-07-25 19:27:11 EDT
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

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 Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 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 Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

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 Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Comment 9 Luya Tshimbalanga 2017-07-26 19:38:43 EDT
Assigned to rawhide for legal issue related to ffmpeg.
Comment 10 Nicolas Chauvet (kwizart) 2017-07-27 03:19:45 EDT
One way would be to pick the ffmpeg-clean script from chromium and to apply to blender builtin ffmpeg.
This should have both tests and legal review...
Comment 11 Luya Tshimbalanga 2017-07-28 01:26:17 EDT
(In reply to Nicolas Chauvet (kwizart) from comment #10)
> One way would be to pick the ffmpeg-clean script from chromium and to apply
> to blender builtin ffmpeg.
> This should have both tests and legal review...

Could you work on that approach and provide the resulted scratch build please?
Comment 12 Nicolas Chauvet (kwizart) 2017-07-28 02:37:16 EDT
No sorry, I can't handle the tasks in the foreseeable future
Comment 13 Jan Kurik 2017-08-15 02:39:37 EDT
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle.
Changing version to '27'.