- User Since
- Mar 4 2016, 4:11 PM (167 w, 2 d)
Dec 16 2018
Are you aware that icons need to be in a square design? So your suggestion needs to be scaled down in order to cope with its almost 1.5x width for the open state. In turn, it won't fit into the overall UI breeze icon design anymore.
Which resolutions are the lock/unlock icons too small for? Is this also with scaling enabled? Can you send a full screen screenshot of an instance where it isn't easy to tell the difference between lock/unlock icons?
Dec 4 2018
(I'm an old git, obviously ;)
The track locking frame indication gives both clear visual guidance but can also distract enormously, more so when multiple tracks are locked, which I sometimes need to do. Any of my projects has at least a topmost locked company logo track ... which currently won't distract, but with the new suggestion it would stick out prominently. Of course, people are different, so some prefer prominent indications depending on their workflow, while others might get diatracted by too much bling.
I see a problem reappearing with the unlock/lock icons which I fought I had squashed before. The open lock is barely distinguishable on higher resolution screens from the locked one, as there's not enough visual difference. On purpose back then I reworked Kdenlive icons to use the slash when unlocked, as this gives much more visual difference than just a small break in the lock's shackle. So, please keep in mind higher res displays, and make things clearly visually different!
Jun 14 2018
Cannot reproduce anymore with 18.08-beta3.
Tried with 18.08-beta3 refactoring branch AppImage and this issue is resolved when loading some existing 18.04 project. Sweet, it even loads the project without burning!
Oct 4 2017
I beg to disagree with uncluttering by removing leading zeros. Personally, I'm glad the notation length is fixed, as otherwise it would constantly change length while working on a project.
Oct 2 2017
It seems that reparenting a task (not only) in phabricator is a difficult procedure...
the irony here may be that the volume transition may then belong to the compositing task branch...
Sep 29 2017
I was under the impression that we wanted to differentiate between compositing and transitions in the future ... albeit the volume transition then would belong into the (audio) compositing category...? Argh! :)
Jan 5 2017
Oct 8 2016
A poll in our G+ community (https://plus.google.com/103555172011502893674/posts/ijcVd2FsbKa) shows that 16% out of 31 users use Affine on a regular basis in their projects. I don't think that blacklisting or removing would be a good idea.
Sep 30 2016
So, would it make sense to make it a full editing mode, excluding others in the way we have normal, insert, and overwrite?
Sep 23 2016
No, to me it's unclear as to what right here means, more so as we have a tradeoff slider, so which side is speed and which is qualify? Why not clearly label things? And no, I'm not asking for Gary Larson-like labelling! ;)
Could we label the quality / speed slider for which end is which?
I rely heavily on affine, especially in many existing projects. Dropping or hiding it would be catastrophic for my work. I'm now using composite & transform wherever possible, yet I still have compositing needs where I have to zoom in or out. So please don't mess with affine, it's been used 95Z in my projects.
Hmm. Preview sounds ambiguous to me, as we also have the timeline/project preview. Personally, I find the current wording to be intuitive and concise: I have clips and I preview them. I have a project and preview that. Source monitor might be an idea though.
Sep 17 2016
I usually can edit only one clip, afterwards, ctrl+click doesn't work anymore for some reason. What's the purpose of the Done button? Do I need to explicitly accept my changes? What if I just click anywhere else in the timeline; can I ever go back to this edit?
Timeline preview rendering has proved to be rock solid. The only UI-wise issue I have is that the red used for invalid chunks is barely visible on my desktop where I use a dark color theme.
This has been landed in git master. Done.
Aug 22 2016
Well, we still have some blockers, such as all keyframable effects not working on tracks. And I had another timeline corruption using the spacer: two additional transitions. Fortunately, the new code dealt with these overlapping duplicate transitions and killed them. But most users may think about panicking when greeted with an error dialog box saying that some transitions were deleted...
Whatever language, we first need to have an object model, such as:
Aug 16 2016
Yes and no. Each frame has an alpha channel. But depending on the encoding format there may be no alpha encoded in the source footage. As Kdenlive adds a lowest black track, and with the internally added track transitions, the result would be fafe to blaclk. However, I would not change the existing fade to/from black effects as these do a dissolve with black. With fade to transparency disdolves to other colors or clips would be straightforward to most newcomers.
Aug 15 2016
Which EDL, by the way? I did some (limited) research and the results were rather dicouraging to me. Everyone seems to interpret EDL differently. Next, does a particular import really needs a reel, which is limited to 5, 6, or so characters ... so we would need to export reels together with the cut list? Some programs seem to be more liberal, but I found many contradicting EDL examples even for the same tool. In principle, we could do a simple EDL export from a Kdenlive project even outside Kdenlive (probably even using XSLT), but only if the original EDL restrictions could be eased a lot...
Farid, not to the best of my understanding. Dissolve is a transition, working on two tracks. You can also dissolve to the black track, but that's what the fade from/to black effects do, too. Albeit the dissolve may be a way to work around the current issues of the fade from/to black effects when using as a user effect, for instance. However, you cant store a dissolve transition as a user transition.
Jul 27 2016
Jul 20 2016
Fixed. Internally added (mix/composite) transitions getting out of sync with project and producing large overhead (I even saw 234 internally added transitions in a single project for just 9 tracks): https://bugs.kde.org/show_bug.cgi?id=365887
Jul 15 2016
Fixed. Another ugly one: trying to move existing transition keyframes has no visible effect, does not get saved with project, https://bugs.kde.org/show_bug.cgi?id=365695
Jul 13 2016
FYI, the parameter problem also appears when expanding library clips. That basically makes working with library clips and expanding them in the timeline for further project adaption a real pain in some body parts. ;)
There is also a really annoying bug that causes effect parameters on clips when copied as part of a clip to not correctly update their in and out points. In consequence, many parameters turn into keyframed parameters that sometimes even have their in points beyond the clip's end. This is a grave problem as it severely breaks any smooth workflow and given new users a really bad impression of Kdenlive. People won't understand why their projects after some copying or moving of clips suddenly starts behaving odd, with effects not working at all and non-keyframed parameters suddenly turning into keyframed parameters with odd time settings. :(
Jul 12 2016
Farid, this is one I would also like to see resolved! I often could work with reduced track hight just perfectly, but not without the track header controls. Track titles could be abbreviated, but I would really like to see a resizeable track header area (by dragging the divider between the header and the tracks).
Jul 7 2016
Some more stuff:
Some once working but around/after 16.04 becoming defunct things:
- Fixed. Incorrect undo after automatic resize of a transition; https://bugs.kde.org/show_bug.cgi?id=363558
- Fate to black doesn't fade correctly on title/image clip which got resized in length; https://bugs.kde.org/show_bug.cgi?id=363538
- Volume effect looses its setting when applied to track; https://bugs.kde.org/show_bug.cgi?id=363032
- Fixed. Changing bin effect parameters does not mark project as changed -- causes loss of changes; https://bugs.kde.org/show_bug.cgi?id=361819
- Resetting effect does not work for bin effects; https://bugs.kde.org/show_bug.cgi?id=361822
- Regression project with "ineffective" effect; https://bugs.kde.org/show_bug.cgi?id=364318
Jun 26 2016
Jun 17 2016
Jun 15 2016
I have to admit that I'm stuck with 25 fps for all the time so far :)
Jesse, Phonon is related to audio, but not video. I doubt that it is related to preview; but then, I may be wrong here.
In a project I just finished today I noticed something odd that seems to be related to preview rendering; however I'm not exactly sure, another reason could be the recent timeline code refactoring.
First one: first add zone(s), then start preview rendering. This way, you can even render multiple, non-continuous zones.
Jesse, it should be working, at least it did so for me on a project I just finished this day using recent git master (well, call me gambler doing projects on git master). However, from time to time I'm also seeing this error message. I'm unclear as to how to trigger it.
It's a start, but most people won't read that amount of text and start writing bug reports anyway. So, in my humble opinion, we need a short and concise intro that explains how to write a good Kdenlive(!) bug report.
For the contact/help topic: we should explain to new users not to flood the bug tracker with distro-specific installation and packaging problems. Lately, we see many useless bug reports with highly specific system and distro combinations. Probably no dev is able to figure out what's wrong with all the broken Kdenlive distro packages out there.
Just a minor note, don't know if this is really an issue for potential Kdenlive.org visitors: many web sites have menu navigation that still doesn't work with touch. So, visiting these sites is a pain when using a tablet (Android, iOS, Windows). Even KDE forums don't work correctly when visited using a touch display device.
Jun 12 2016
Got Ctrl+Click+Drag working. However, I still mostly don't see the two clips side-by-side but only one. Could be the reason that I also have another track on top that uses a transition to combine with the track where I work on a clip cut?
Massimo, thank you for your help! Unfortunately, I still can't make it work this way. I'm always only seeing one clip with the buttons below. Do the clips need to be on different tracks?
- I can't get it ripple mode working at all. I've found the new button and added it to my timeline toolbar. Then I added some clips to the top track of my timeline. Then I selected either none, one, two clips or three clips and pressed ripple mode. In either case I get the cancel and accept buttons, but only a single clip displayed. This clip is also overlaid by the buttons, so I only see roughly the top half of my clip. But I don't see two clips. What am I doing wrong?
Jun 6 2016
With the preview rendering and timeline toolbar now in place, ripple editing using the mouse would be the final blow to send me to Kdenlive Heaven (at least for the moment).
The only thing now missing may be for some users to change folder locations from the XDG standards to their own settings?
My impression is that the new timeline toolbar is fine for now. For me, it has proven to be an incredible UI improvement as I rarely used the main toolbars at the top, mainly so because they are out of reach. The timeline toolbar is right on spot.
Jun 5 2016
Good idea! Thank you for implementing it!
May 24 2016
May 23 2016
Jean-Baptiste, I've sent you a bunch of new and updated icons for preview rendering and advanced editing functions. Hope you can make use of it.
Same over here as massimostella noticed; cannot configure and cannot use the timeline toolbar. I'm on Qt 5.5.1, KF 5.22.
Re: icons ... give me some time. I have an idea now about the preview zone add and remove buttons.
May 22 2016
I like the new design too. Would it be possible to add configuration to it so that users can adapt it to their editing habbits? This way, Kdenlive could offer the old edit mode buttons too. And this may also allow for dragging the timeline bar to another position or even to the left in vertical mode?
In case you are installing Kdenlive in a non-standard location, please see https://community.kde.org/Thread:Talk:Kdenlive/Development/KF5/Make_sure_to_set_env_variables_correctly_for_home_dir-based_setups on how to set up the required environment variables, so that Kdenlive correctly finds its icons and configuration data. I'm using such a setup myself so I know that it works.
May 21 2016
What about storing the project file timestamp or some hash of it in a simple cache ident file in the .cache/kdenlive folder? That is, a simple small file that accompanies the mlt file and the other rendered preview chunk files.
Automatic preview rendering is way too cool ... I now need sunglasses at work, even with Breeze dark theme :D
The preview rendering button looks very strange on Qt 5.5.1 when Kdenlive is rendering the preview. When the button is not selected, the e.t.a. and the progress bar is shown. But when clicking on the button, then it looks like this:
I found a few premade preview render profiles. The only thing that I think needs improvement is to guess suitable profiles based on frame size and fps. When I opened the configuration dialog, I had a 24fps profile set or so, albeit default project is 25fps.
May 19 2016
Another issue I notice: my source footage are .mp4/H.264 clips. When preview rendering in 1s chunks, these chunks do not always correctly start with the desired frame. The result is a sometimes slightly rough playback with jumps in between -- not due to frame dropping but because rendering an individual 1s chunk does not correctly start where it is supposed to start. This may probably be caused by MLTs picky behavior when seeking in certain footage formats?
I've tried preview rendering for the first time using recent git master: while I see the preview rendering progress bar running up to 100% I don't get any preview. After progress is finished, no green preview indication to be seen in the timeline ruler. Also, I don't see any temporary .mp4 files in ~/.cache/kdenlive in which I suppose they should show up. Also, no temporary .mlt file present.
Is there a reason why I can't disable certain clips? For instance, I can't disable clips with speed effect or image clips? Or am I doing something wrong here? I'm on latest git master.
May 18 2016
Ctrl+Enter is already used (if I remember correctly) for opening the Render dialog, i.e. what you are calling "export".
May 17 2016
Just a minor idea: what about later adding a "full preview render" button to the future toolbar? For easily rendering the complete project without having to set a full-length timeline zone first?
May 16 2016
Looks great with good readability! Jean-Baptiste, once again many thanks for your work!
Just added this day, so it won't be in the nightly until tomorrow. (There's a reason I compile directly from source, as Jean-Baptiste killed a lot of bugs I tripped on all the time during the 15.08-16.04 timeframe and I needed these fixes quickly in order to continue working on my projects; many kudos to JBM!!!)
It's in the Clip menu (but not in the context menu). See here for screenshots and description: http://thediveo-e.blogspot.com/2016/05/kdenlive-ui-disable-timeline.html
Tried the new disable feature and noticed that especially the disabled status icon next to a clip's title can be near to impossible to read. Please see also this screenshot, where the red forbidden icon blends in with the red title background next to it, thus becoming almost invisible:
May 9 2016
I would also expect to be able to position the playhead beyond the latest clip in the timeline. It's not necessary to position further. Compare this to your text editor where you are allowed to position the insertion cursor after the last character to add new text.
May 8 2016
One reason can be that the video clip also contains audio, but you don't want and need to split this audio from the video because you are going to use a separate audio clip. In my projects, the audio part of the video is the raw audio I never use in the Kdenlive project. Instead of splitting audio, then ungrouping, then deleting to splitted audio clip I simply switch splitting off and mute the video track. Simple and fast workflow.
Re 1. ... same idea over here, keyboard shortcut is alreay enough; we could add a toolbar button as default if really necessary.
Let's see if I'm now correctly set... there are two ways of inserting some clip content into the timeline, either:
- insert the bin clip zone (from in to out) into the timeline starting from the playhead position; this is when use timeline zone is off.
- insert bin clip content starting from the clip in point into the timeline zone from in to out; use timeline zone is on.