I want to know thoughts from users of Kdenlive at Fedora distro.
As maintainer I thinking about splitting MLT into two packages. One of all free staff which will be go to Fedora's official repo and second with only forbidden staff on Fedora, and it will be go to RPMFusion.
In that case Kdelive itself will be switched to Fedora's repo (from RPM Fusion)
Advantages:
- Kdenlive and MLT will be on Fedora official repository which mean that it will be sooner in repo that on RPM Fusion.
- All people who do not want to use RPM Fusion can work with Kdenlive (with all open codecs)!
- If you want to use patented and copyrighted codecs, simply install MLT-nonfree package from RPM Fusion.
Disadvantages:
- This is less comfortably than install all of that from one repository (like now from RPM Fusion)
- If you want to additionally install this 'non-free' part of MLT, than you must start Kdenlive's Config Wizard again because of rescaning newly codecs.
- Users which isn't know about this MLT-nonfree package can be in problem and periodically asking for ffmpeg, for example.
Before talking with Fedora developers I wnat to know yours stands about that, so please tell me yours opinions.
thanks.
Fedora's maintainer,
Grof

Well...yes. Can be premature, yet.
I did some experimental splitting, and it was mostly successful.
Two things make me some troubles for now.
1st) Module: Kino
------------------
I can not correctly divide this modul to quicktime - nonguicktime. Becasue it is the same .so file.
So, if I build 'free' package (without quicktime) than libmltkino.so do not provide quicktime capabilities.
On other hand, if I build 'non-free' package, then I should get libmltkino.so with full capabilities, but I can not correctly handle 'non-free' .so file which overwrites the same name 'free' .so file.
Ok, I can do some renaming of 'old' libmltkino.so file when user install 'mlt-nonfree' package over the 'mlt-free' package. And renaming to old state when and if user uninstall 'mlt-nonfree' package only. But the mainly problem laying in debuginfo packages. This is very hard to resolve in this case.
Honestly, I do not currently know how it would be well resolved. :)
2nd) Kdenlive: webcapturing
---------------------------
This is minority problem, but I notice that here.
Webcapuring is the only thing why Kdenlive depend of ffmpeg.
Can the webcamera capture solved in some other way, except via ffmpeg?