Hi there, just to clear up some confusion on some points...
Some applications have a default scheme, and also a setting for following
the system scheme. This makes just about everyone happy.
Kdenlive is by default to follow the system, scheme, and that is not a bad
default at all.
Not a single complaint from me there.
That Kdenlive is buggy is a statement of fact. That this buggyness detracts
from the user experience is a fact. I can point you to a rather long list
of open bugs on kdenlive.
I can also point you to a much longer list of closed out bugs, which
attests to the Herculean efforts that JB is putting in. Still no complaints
from my side.
If I could code, I would contribute, but I can't, and I am doing the next
best thing and reporting bugs that I find, as I find them. Hopefully no one
is confusing this with complaining.
In my opinion, Kdenlive is doing about as well as a single main developer
can do with maintenance in his spare time.
We either need more developers donating spare time, or hire a developer
either part time or full time... for which we need money.
Any ideas on how much money is needed or how it can be made are quite
welcome, of course.
One way would be to pay for preferential treatment for bug fixes or feature
additions. I would gladly pay $50 to be able to switch projects between fps
without corruption, for instance.
Kind regards,
Evert
On 18 June 2016 at 15:35, Massimo Stella wrote:
> I never commented before emails about topics not directly linked to the
> improvement of Kdenlive. But now I'm really bored in reading texts which
> contains, though in a respectful form, insults, outlets for frustration and
> useless polemics.
> My opinion is that we have to help developers in creating an application
> which can interest professionals and I believe that we'll be able to do it
> by inserting in Kdenlive the majority of the tools professionals need
> before we create the windows version. When the Windows version will be
> ready (as Windows on desktop is still adopted by 75% of the users) people
> will be able to decide if to continue to use proprietary software or FLOSS
> for professional video editing purpose.
> When I read sentence like "Thereby, making Kdenkive a amateur second class
> editor. It is more than a bug" related to chromakey feature, or "I
> respectfully disagree on same look everywhere." and then "Kdenlive today is
> that it is so buggy that you can't do any serious work on it" I think that
> people before to write has to know better what are real video editor
> applications on the market, how they are used by real professionals and
> take respect for the hard job people, like Jean-Baptiste, are doing.
> About chromakey and effects filters I already wrote that in real world
> producers use video editor applications for editing and compositing
> software for comppositing. So generally in a professional studio or in
> television nobody use AVID for chromkeying purpose. Of course it's better
> to have a fully functionally chromakey feature working inside Kdenlive (for
> fast and rough keying jobs) but the lack of it doesn't make "make Kdenkive
> a amateur second class editor. It is more than a bug". Feature lacks for
> real editors are others. For a good chromakey you can use Blender
> compositor and Natron, just for eg., which were created also for this
> purpose. You create effects in a compositing application and then you edit
> them inside your video with a video editor applications, this is what
> happens in real productions.
> Then someone complains about bugs but it also complains about the GUI. He
> wants less bugs but also a configurable theme fo making his computer looks
> all the same.
> Actually in proprietary software world each application has it's own theme
> and you can just maybe change the color if you are lucky. Also some
> application on the FLOSS world work this way too. If to create a fixed
> theme and set of icons help to fix bugs in the Kdenlive GUI we have to
> choose the way which easier solve the problem instead of ask for something
> which consume time in developping other more important features.
> I believe we have to test and know what others very costly applications,
> developped by groups of dozens of people, do and try to sugguest how to
> improve Kdenlive for becoming the best video editor application ever,
> instead of complain and use these tones.
>
> My suggestion is to follows these steps:
> 1. Complete the application with all the tools for editing (not for
> compositing) professionals need.
> 2. Fix all the bugs (even during the first step)
> 3. Propose the software to the Windows community and simplify the way to
> install it on MacOS (and with this move we'll enter in direct competition
> with Adobe, Avid and other software houses)
> 4. Improve the software by adding filters and compositing feature we still
> miss.
>
> So, please, stop to complain and collaborate!
>
> Messaggio originale
>