Will close this here continue in gitlab: https://invent.kde.org/multimedia/kdenlive/-/issues/407

moving to gitlab
https://invent.kde.org/multimedia/kdenlive/-/issues/682

https://invent.kde.org/multimedia/kdenlive/-/issues/460

Moving the ideas to gitlab since thgis is closing down.

Hi, sorry if it is late, but I have a suggestion about the look of the posts. Basically the idea is to post only have triptychs that way we could have a very good looking general view.

Hi, sorry if it is late, but I have a suggestion about the look of the posts. Basically the idea is to post only have triptychs that way we could have a very good looking general view.

Closing here, opened in gitlab: https://invent.kde.org/kde/kdenlive/issues/560

The Kdenlive team will also attend and have our yearly sprint either before or after LGM as well.

Doubt: Some projects accept donations, how would becoming part of KDE affect this?

In T12298#212614, @jbbgameich wrote:

For flathub (and probably snap store as well), you only need to update the appstream metadata. As soon as a new version is released to flathub which includes this changes, the screenshots will be automatically updated.

Btw, how can we put these in Flathub and Snapcraft?

Closing and moving here:

+1

Thanks for taking the time to post this, but as stated elsewhere, this should be filed as a sysadmin task. See here:

Will add @alcinos and @mardelle to review this. For future reference, please note that we have moved to gitlab: invent.kde.org for Kdenlive's development.

In T10875#184489, @paulb wrote:

In T10875#184485, @afarid wrote:

Some suggestions,

1. Get Blender artists involved by:
   • Write a post about the competition on BlenderNation
   • Write a post about the competition on BlenderArtists
   • Write a tweet tagging @blender and using #b3d and #blender hashtags

Do you belong to these forums, @afarid ? If so, if we wrote something, could you post it? Like that it would come from one of their own and seem less spammy.

Some suggestions,

In T10875#184332, @ngraham wrote:

I'm noticing that a lot of entries have the KDE logo or the Plasma name or version number embedded in it. I feel like this is kind of tacky and not really appropriate given that our prior wallpapers didn't do this, but we didn't make a rule prohibiting it. I'm tempted to recommend that we retroactively do so and ask the people who have submitted such wallpapers to remove those elements. Thoughts?

In T10747#181105, @emohr wrote:

Note for inkscape: QtSvg only supports TinySvg specification, so inkscape svg must be exported to this format to display properly in Kdenlive (note to add somewhere...)

How about adding some presets for text animations (Click on image to see GIF)?

Would be nice to say in the rules that it must be done with free software.

In T10712#180329, @paulb wrote:

In T10712#180321, @afarid wrote:

For Kdenllive we could just mention the refactoring release since i'll be doing an in depth video about it.

if our audience is the general public (and apps should be advertised to the general public), talking about refactoring is pointless. It is just noise. Reserve it for the more in-depth video.

For Kdenllive we could just mention the refactoring release since i'll be doing an in depth video about it.

As a Script task we must define which applications to highlight.

Folks, thanks for the effort. FYI, we have merged the refactoring branch to master so 19.04 will be completely new. So focus should be on the refactoring (which is now master.)

Rewrite the render dialog.

In T10511#176943, @emohr wrote:

proxy clips show up as MKV -> has to be checked why

In T10511#176928, @emohr wrote:

> Equaliz0r and G -> no settings -> We might however hide the arrow on such effects because it is confusing.

Here is the archive that valgrind produced after testing some actions in the bin like selecting and moving the arrows up and down, as well as jkl and playback.

Related to this: https://bugs.kde.org/show_bug.cgi?id=403924

Nice one, please have a look at this related task as well. :)

In T10034#174271, @GB_2 wrote:

The Calamares installer also seems like something we could adopt: https://calamares.io

In T10034#167218, @afarid wrote:

Here is my wishlist as well:

• Hydrogen
• Any the software by Rui Nuno Capela but specially Qtractor or Qjackctl.
• Musescore
• Mixxx
  
  Although I don't know how realistic these proposals are. Probably the most feasible is Hydrogen but it doesn't hurt to try the rest.

In T10085#173706, @emohr wrote:

+1

Individual colors for each clip should be possible (for a 2nd timeline with "pre-selected" clips).
Other basis color for video and audio should possible as well (for a 2nd or 3th timeline).

But we can switch off colors as well.

As I mentioned above

In T10085#173287, @mardelle wrote:

So I started implementing colors in the timeline. I agree that we should ideally use variations of the theme's original colors, in our case mostly breeze dark: https://community.kde.org/KDE_Visual_Design_Group/HIG/BreezeDark

So, as I said, in the refactoring branch yo will not have a mixed audio and video clip. Audio and video will be always split.

In T10314#172963, @mardelle wrote:

We could add a "record button" to audio tracks.

This happens when the clip has both video and audio right? In the refactoring branch this will change and a clip will be either audio or video.

A contribution from @tcanabrava <3

Another quick proposal about colors.

In T10085#170423, @msundman wrote:

This is probably already on the TODO-list, but in case it's not:
It would be great if one could just drag a clip to overlap another clip, creating a transition automatically, like crossfade in REAPER

In T10295#172701, @mhirczy wrote:

Just as an addon-info to this.
At the moment, resetting the color wheel does only that - the line values are not effected.
The other way around it's not like this: resetting the line will also reset the color wheel.
For what I saw on all color correction hardware, there are 2 seperate buttons to reset the wheel and the overall values.

I already implemented this in my local copy of the sourcecode.
If there's interest, I could commit it to the repo...

Scribus handles this nicely in situations like this. Maybe also add an option to automatically embed fonts?

In general, monochrome style icons should not be colored (compare action icons to emblem icons). What do you mean by 2 icons for each state and highlighted if active?

In T10085#169404, @ndavis wrote:

Here's what I've got right now. I thought the A# and V# labels were redundant, so I removed them. I decided to keep the lock white since I thought it looked better for a monochrome style icon. I also added an orange outline to the locked track area.

In T10085#169360, @ndavis wrote:

In T10085#169213, @afarid wrote:

More ideas for locked tracks. I cannot see orange working though in this case. What do you think @ndavis?

Would you mind sending me the mockup so I could play with it? Writing text isn't the most efficient way to make visual suggestions.

Proposal for track names. Should we have a max character limit?

More ideas for locked tracks. I cannot see orange working though in this case. What do you think @ndavis?

In T10085#169122, @ndavis wrote:

In T10085#169115, @afarid wrote:

When you lock it it will disable that track, you wont be able to move clips in the track anymore.

By disable, do you mean actually make it so that video/audio on that track won't be visible/audible? It's not really off/disabled if it still plays video or audio.

In T10085#169082, @ndavis wrote:

I noticed you used green as the color for "Target". What is a "Target"? Is that the current selection? If so, the color should be Plasma Blue (#3daee9). Green should generally be used for positive things or successful operations while Plasma Blue is used for selections.

In T10085#169080, @ndavis wrote:

I think the locked track stuff should be orange. Red should generally be reserved for things that can be destructive, errors or things meaning off/disabled.

Proposal for locked tracks. Two versions:

In T10034#168057, @matheusm wrote:

Lutris? I don't think this will ever gonna happen. It is a gtk+ application and their next major release (0.5.0) is going to use GtkHeaderBar 🙄

Another project which is interesting is FreeCad. It is still Qt4 but if the community can help porting it to Qt5 that can be a bonus to make it join KDE.

In T10034#168055, @apol wrote:

This process is called incubation, you can see how it works here: https://community.kde.org/Incubator

Here is the initial proposal.

@ognarb I am not a dev but part of the team. We will look into it and give you feedback. Thanks for updating the screenshots.

In T10034#167261, @paulb wrote:

Although I don't know how realistic these proposals are. Probably the most feasible is Hydrogen but it doesn't hurt to try the rest.

It is okay to forget realism for the moment. We'll look at each project individually later.

Here are some Kdenlive one's if you like to use.

Here is my wishlist as well:

This is an example of the current state in the refactoring branch.

In T9345#154359, @emohr wrote:

Here are some points from TIM out of the video: https://drive.google.com/open?id=1T5ULFHnHe4jM1vWUVkA3enygxHJvc2z8

• Bezier Curve crashes project. At 0.00
• Project crashes when moving multiple clips onto video tracks without corresponding audio tracks. At 1:21 and Bug 397198
• Double clicking on a clip causes the clip to remain in the state until the cursor is clicked somewhere else. At 2:47
• Some effects work, but adjusting their value slider causes glitching. At 3:18