This is to organize the issues that need to be fixed before the 17.12 release.
Description
Status | Assigned | Task | ||
---|---|---|---|---|
Resolved | jlskuz | T5082 Timeline Refactoring | ||
Resolved | jlskuz | T7077 Refactoring bugs | ||
Resolved | jlskuz | T7078 Bin | ||
Resolved | thediveo | T7095 loading existing 17.08 project triggers bin folder warning | ||
Invalid | None | T7079 Effects | ||
Invalid | None | T7080 Compositing | ||
Resolved | thediveo | T7097 loading existing 17.08 project crashes with missing volume transition | ||
Invalid | None | T7081 Rendering | ||
Resolved | mardelle | T10158 Refactor rendering to mimic Shotcut's embeded consumer parameters | ||
Resolved | jlskuz | T7082 Timeline | ||
Wontfix | jlskuz | T7096 Transitions | ||
Resolved | jlskuz | T7128 Refactoring Blockers |
UI regressions:
- timeline "fit zoom to project" button doesnt work
- dragging a small clip on the track hides what the clip looks like when the clip is short. Maybe add some transparency to the clip? or just move them around so they dont hide each other
- search bar in effects tab disspear when you switch tab. It should be showing and selected by default when entering the tab
- search bar in effects overlap with the effects when there enough room to the right
- effects dont have description on the tooltip
- if the window is small, description fixed screen room cant be resized and takes precedence to the list of effects since it has a scroolbar
UI suggestions:
- unclutter the ui: dont show leading zeroes and separete the frame notation. change the color of the marks that have a number. 00:00:01.2 -> 1.2 or :01.2
- make the sound tracks show bigger waves. Allow to toogle them in the video (if you are not going to separete them)
- clip/project monitor zoom could use a 100% button since the slider is not very precise
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.
But more important, Kdenlive uses the well-established SMPTE timecode textual representation, used throughout the countries day in, day out. Cf Wikipedia SMPTE timecode. The colon separating frames from seconds has a well-defined meaning: it's a non-drop time code. Displaying something else would be plain invalid and totally misleading. In particular, the comma and semicolon are indicating drop time codes, and must only be used in those situations.
And making this configurable only clutters the configuration dialog even more, something that diametrically to uncluttering the UI.
About the uncluttering the timeline notation, a final note
Blender timeline. This picture is just a quick glance, but I encourage you to play with it a little, just to show how even tho the notation length is not fixed, it is not an issue
Ive been playing with blender video sequence editor for 3 weeks now, and its timeline notation is just nice and intuitive. Shows only info that is relevant. It hides the frames when they dont make sense due to the scale, and shows the exact frame in the timeline. Ive always known where I was with a quick glance
Ive already worked in a few semi big ameteurish projects in kdenlive. I had to decode what I was looking at in my brain to find the relevant info in a sea of zeroes. Like showing the frame, when they dont make sense due to the scale
Maybe im just not used to fast decode that standard time format
And making this configurable only clutters the configuration dialog even more, something that diametrically to uncluttering the UI.
I dont see why adding the option would be a problem. Id even argue that this should be default
I understand the use of worldwide standards. It makes it less error-prone when sharing projects
But for local, single editor, not shared projects, this is a non issue. Id argue that 99% of kdenlive projects are like this. Having a setting to accommodate that other 1% its sensible though
I hope this wont be dismissed from all the pro editors here and suggestions to make life easier for the average joe have some room too
Anyway, thats just my 2 cents after giving a little more thought and usage to the idea :)