Can we begin the process of integration with natron?

[Narcis Garcia]

This page has a big ugly hole where it's intended to embed a 3rd party 
video:
kdenlive.org/about

I suggest to add that page a chapter called "Other recommended software"
And list a funcional-classified list of projects, with some selection 
requisites:
0. 100% FOSS
1. Useful in the video-editing job (including image design, audio, etc.)
2. File formats compatible with Kdenlive
3. Has a project's website and community resources fot it (lists/forum/?).
4. More than 1 year from its first stable release.


El 6/5/22 a les 17:37, Zeke Williams ha escrit:
> I think advertising natron on kdenlive.org <http://kdenlive.org> is the 
> simplest solution for the time being as well as bundling natron with 
> kdenlive when downloaded.
> 
> On Fri, May 6, 2022, 10:30 AM Narcis Garcia <debianlists at actiu.net 
> <mailto:debianlists at actiu.net>> wrote:
> 
>     "integration" word can mean many things.
>     Formats compatibility, interoperation / interaction, can be a bit more
>     concrete, but maybe not enough.
> 
>     You could open concrete feature requests at each project, to ask for
>     concrete actions that produce concrete results.
> 
>     Another (simpler) way can be to put Natron and Kdenlive logos together
>     in the title bar and website headers. And a single downloadable package
>     with both applications. Total integration and sympathy.
> 
> 
> 
>     Narcis Garcia
> 
>     __________
>     I'm using this dedicated address because personal addresses aren't
>     masked enough at this mail public archive. Public archive administrator
>     should fix this against automated addresses collectors.
>     El 6/5/22 a les 15:56, Zeke Williams ha escrit:
>      > Sorry, my previous message was meant for this one. As I said:
>      >
>      > I don't see why not. I don't think natron needs to be a
>     dependency for
>      > kdenlive to be used, but a degree of integration between the two is
>      > definitely possible without going crazy with things.
>      >
>      > On Fri, May 6, 2022 at 9:36 AM Mehdi Haghgoo
>     <powergame_coder2 at yahoo.com <mailto:powergame_coder2 at yahoo.com>> wrote:
>      >>
>      >> Then, they should make a nice creation suite.
>      >> Do you think the two will work together without making the
>     software too heavy and complex?
>      >>
>      >>
>      >> On Fri, May 6, 2022 at 17:47, Zeke Williams
>      >> <lakeleaf8 at gmail.com <mailto:lakeleaf8 at gmail.com>> wrote:
>      >> Natron is a compositing editor for video and special effects. A
>      >> completely different purpose from what kdenlive is striving to
>     be. If
>      >> kdenlive is premier pro, then natron is after effects. Natron can do
>      >> many things that cannot be done in kdenlive or can't be done as
>      >> complex. Natron would go with kdenlive like bread and butter if
>     there
>      >> was tighter integration with the two applications.
>      >>
>      >> On Fri, May 6, 2022 at 9:06 AM Mehdi Haghgoo
>     <powergame_coder2 at yahoo.com <mailto:powergame_coder2 at yahoo.com>> wrote:
>      >>>
>      >>> Hi Zeke,
>      >>>
>      >>> I have never used Natron. What can be done in it that are not
>     currently possible in kdenlive?
>      >>>
>      >>>
>      >>>
>      >>> On Fri, May 6, 2022 at 15:26, Zeke Williams
>      >>> <lakeleaf8 at gmail.com <mailto:lakeleaf8 at gmail.com>> wrote:
>      >>> Natron is highly usable despite stalling a bit in development.
>     There
>      >>> should be some awareness of kdenlive users for natron.
>     Something basic
>      >>> like the ability to open a clip or project into natron to make
>     edits
>      >>> and then have the edits be applied to the kdenlive video. It's been
>      >>> discussed last month about how there once was a possibility of
>     making
>      >>> natron an official kde project, but in order for that to
>     happen, more
>      >>> awareness of natron's existence is required.
> 

-- 


__________
I'm using this express-made address because personal addresses aren't
masked enough at this mail public archive. Public archive administrator
should fix this against automated addresses collectors.