If you count mp4 containers with H.264 as fancy, then... :)
What I still consider bad behavior is that ffmpeg crashes with a pointer
violation. I also have no clue why I was lacking the extra56 package, because I
usually install extra codecs right away.
Ursprüngliche Nachricht
I only saw this on 16.04 so far.
Ursprüngliche Nachricht
Von: Vincent Pinon
Datum: 30.08.2016 12:48 (GMT+01:00)
An: kdenlive@kde.org
Betreff: Re: FYI: (solved) Ubuntu 16.04LTS codec missing package needs to be
installed to use ffmpeg
Do you need extra codecs only for so
It is rework necessary tor the internals of Kdenlive, mostly invisible. It is
necessary to further develop Kdenlive. A first visible change may individually
resizable timeline tracks.
Ursprüngliche Nachricht
Von: DogFilm
Datum: 03.02.2017 12:51 (GMT+01:00)
An: Harald Albre
+100
Ursprüngliche Nachricht
Von: Vincent Pinon
Datum: 08.08.17 14:47 (GMT+01:00)
An: kdenlive@kde.org
Betreff: PPA to test future 17.12 (timeline rewrite)
Hello,
I've finally finished the setup of a new PPA to test the future Kdenlive 17.12
version,
containing a "kdenl
Alberto,
as is often the case, there are multiple ways to achieve the same outcome. But
there are multiple ways, depending on your workflow and project. And there
isn't a "one size fits it all" or the "one true way", as in politics.
First, Kdenlive is slightly unique in that it can achieve positi
For my workflow, I'm glad that the render pipeline is as is: because I need to
resize the timeline height while working on my project this would otherwise
invalidate the whole prerendering data. The downscaling is cheap, while the
prerendering is expensive. I fail to see how changing the pipelin
As for separate phab tasks I recommend to hear the devs on this. I see pros and
cons for both a summary task as well as individual tasks. Personally, from
previous work I got the impression that summary tasks auickly tend to get
"everything plus a kitchen sink", making it at least difficult to t
Yes, and no. As Evert pointed out, there's currently a bug in the timeline
handling that sometimes causes issues (but not always as far as I understand,
but I may be wrong here). The safest approach is as Evert suggested to render
at 50fps and then use ffmpeg for post-processing to drop every se
https://launchpad.net/ubuntu/+source/kdenlive lists the official package
data:artful has 17.08.2zesty has 16.12.3Kdenlive project:stable ppa is 17.04.3
for artfulmaster ppa is 17.11.70 from 2017-10-14
Ursprüngliche Nachricht Von: farid abdelnour
Datum: 12.11.17 16:54 (GMT+01
incredibly well made slides!
Ursprüngliche Nachricht Von: Jean-Baptiste Mardelle
Datum: 21.11.17 21:39 (GMT+01:00) An: kdenlive@kde.org
Betreff: Re: JBM's talk at Akademy 2017
On 21.11.2017 13:41, Sam Muirhead wrote:
> Great talk, cool to get an overview of what's happening u
Hi Andrew,
off my head it should work in Kdenlive as follows, see also
https://thediveo-e.blogspot.de/2016/05/kdenlive-ui-advanced-editing-timeline.html;
yeah, I need to migrate such stuff to kdenlive.org some day.
1. set in and out points in timeline using the I and O shortcuts; the so-called
r
Hi Farid,
should work out of the box (speed/freeze effect notwithstanding) as such. I'm
regularly mixing 30fps source footage into 25fps projects -- shame on me! :)
However, you may notice slight differences due to the different "shutter" speed
and the image pulldown. In my case, which is handdra
I notice that my reason for speaking up is unfortunately not getting through,
and that is, in my opinion, due to solely focusing on the developers
refactoring task and the primary goal of stability, where stability has
different semantica for devs and for different users. As a user I value
stab
13 matches
Mail list logo
