From noreply at kde.org  Mon Nov  5 22:24:09 2018
From: noreply at kde.org (CI System)
Date: Mon, 5 Nov 2018 22:24:09 +0000 (UTC)
Subject: =?UTF-8?Q?KDE_CI:_Applications_=C2=BB_kdenlive_=C2=BB_stable-kf?=
 =?UTF-8?Q?5-qt5_FreeBSDQt5.11_-_Build_#_31_-_Failure!?=
Message-ID: <1300648913.761.1541456650190.JavaMail.production@nellie>

An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdenlive/attachments/20181105/bf3b1a46/attachment.html>

From noreply at kde.org  Mon Nov  5 22:26:39 2018
From: noreply at kde.org (CI System)
Date: Mon, 5 Nov 2018 22:26:39 +0000 (UTC)
Subject: =?UTF-8?Q?KDE_CI:_Applications_=C2=BB_kdenlive_=C2=BB_stable-k?=
 =?UTF-8?Q?f5-qt5_FreeBSDQt5.11_-_Build_#_32_-_Fixed!?=
In-Reply-To: <1300648913.761.1541456650190.JavaMail.production@nellie>
References: <1300648913.761.1541456650190.JavaMail.production@nellie>
Message-ID: <1010537091.765.1541456799467.JavaMail.production@nellie>

An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdenlive/attachments/20181105/59679d36/attachment.html>

From noreply at kde.org  Mon Nov  5 22:38:29 2018
From: noreply at kde.org (CI System)
Date: Mon, 5 Nov 2018 22:38:29 +0000 (UTC)
Subject: =?UTF-8?Q?KDE_CI:_Applications_=C2=BB_kdenlive_=C2=BB_stable-?=
 =?UTF-8?Q?kf5-qt5_SUSEQt5.9_-_Build_#_103_-_Failure!?=
Message-ID: <61502939.769.1541457509516.JavaMail.production@nellie>

An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdenlive/attachments/20181105/490b9d36/attachment-0001.html>

From noreply at kde.org  Mon Nov  5 22:50:34 2018
From: noreply at kde.org (CI System)
Date: Mon, 5 Nov 2018 22:50:34 +0000 (UTC)
Subject: =?UTF-8?Q?KDE_CI:_Applications_=C2=BB_kdenlive_=C2=BB_stable?=
 =?UTF-8?Q?-kf5-qt5_SUSEQt5.9_-_Build_#_104_-_Fixed!?=
In-Reply-To: <61502939.769.1541457509516.JavaMail.production@nellie>
References: <61502939.769.1541457509516.JavaMail.production@nellie>
Message-ID: <1258941573.771.1541458234541.JavaMail.production@nellie>

An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdenlive/attachments/20181105/eab23462/attachment-0001.html>

From snd.noise at gmail.com  Tue Nov  6 12:08:35 2018
From: snd.noise at gmail.com (farid abdelnour)
Date: Tue, 6 Nov 2018 10:08:35 -0200
Subject: =?UTF-8?Q?Caf=C3=A9_tonight?=
Message-ID: <CAHMxv37UqFXU3uXSkBdaaePxqch-=b5ttpe5s-An5Ek3V3BngQ@mail.gmail.com>

Greetings all

Just a reminder that tonight at 9PM (Paris time) we'll be having our Café.

If you have any topics list them here or at the beginning of the meeting.

See you!

-- 
1111.1010.r.i.1101|n.o.i.s.1110|i.m.1010.g.1110|مقاومة
fsf member #5439
usuario GNU/Linux #471966
|_|0|_|
|_|_|0|
|0|0|0|
<a href="http://www.gunga.com.br">gunga</a>
<a href="http://www.tempoecoarte.com.br">tempoecoarte</a>
<a href="http://www.atelier-labs.org">atelier-labs</a>
<a href="http://www.mocambos.net">rede mocambos</a>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdenlive/attachments/20181106/fe6c2440/attachment.html>

From mi.hi at gmx.net  Mon Nov 12 11:57:54 2018
From: mi.hi at gmx.net (Michael Hirczy)
Date: Mon, 12 Nov 2018 12:57:54 +0100
Subject: Interest in supporting Tangent Colorgrading Panels? LiftGammaGain
 Widget reset bug
Message-ID: <002701d47a7e$f261f140$d725d3c0$@gmx.net>

Greetings!

I have been using kdenlive for quite some time now, and it's a fantastic
NLE, thx a lot for that!

While trying to learn the craft of filmmaking (as a hobbyist), I also
stumbled upon the topic of color correction.
Since I'm a full-stack-nerd/geek *gg*, I like nice hardware with knobs and
displays :D

So I managed to find a used Tangent CP200 color control surface and
contacted Tangent about support for Linux.
I got the full development package and I'm actually in the process of
learning c++ and qt to make support for the Tangent hardware inside of
KDEenlive.
(I've been coding for about 30 years, worked fulltime as Java-Dev and
although technology has quite evolved through the years, it's still easy for
me to read someone's code and refactor it to my needs)

Is there interest to put Tangent-support into the official repository?
since they released their Ripple, color grading software is not so expensive
anymore...

I will program it anyways, so maybe it can be some help to others...

When researching the code for color grading, I found a interesting behaviour
of the LiftGammaGain-Widget:
On every color correction panel you have 2 buttons to reset color and
brightness independently.
During my first steps I found, that resetting the color wheel in the LGGW
works as intended (just reset the color wheel), but resetting the brightness
bar will reset the color wheel, too!

I don't know if this is intended or a bug - but I decided to change it to my
needs (only reset the brightness/value bar):
In colorwheel.cpp I just changed line 178:
            // old code: c =
NegQColor::fromRgbF(m_defaultValue/m_sizeFactor,
m_defaultValue/m_sizeFactor, m_defaultValue/m_sizeFactor);
            c = NegQColor::fromHsvF(m_color.hueF(), m_color.saturationF(),
m_defaultValue/m_sizeFactor);

ATM I'm not very good at git, so I don't like to submit such a small change
to the official repository.
(aaand I'm actually using the 18.08 branch for my dev-testing)

If there's need to implement this into the repo, could someone of the devs
do this? 
Otherwise, if the actual reset-algorithm is planned to work like this, just
keep it this way :)

thx and greetings
michi



From snd.noise at gmail.com  Mon Nov 12 20:02:34 2018
From: snd.noise at gmail.com (farid abdelnour)
Date: Mon, 12 Nov 2018 18:02:34 -0200
Subject: Interest in supporting Tangent Colorgrading Panels? LiftGammaGain
 Widget reset bug
In-Reply-To: <002701d47a7e$f261f140$d725d3c0$@gmx.net>
References: <002701d47a7e$f261f140$d725d3c0$@gmx.net>
Message-ID: <CAHMxv37FoTctM7JxifWHsBeE=JBsa5da7TWYHPVUF8OrPRjQ3w@mail.gmail.com>

Hi Michael and welcome!

That is some sweet hardware and I think it would be great to have support
for it in the next releases. I don't know technically what would be
involved to make it happen though. A first step can be to create a KDE
account and maybe start a thread on phabricator about this. Here s the link
to the Kdenlive board: https://phabricator.kde.org/project/view/40/

Here is some info on git, hope it helps somehow:
https://community.kde.org/Infrastructure/Git

Also besides the mailing list we have a telegram and irc channels.

Cheers :)


Em seg, 12 de nov de 2018 às 09:58, Michael Hirczy <mi.hi at gmx.net> escreveu:

> Greetings!
>
> I have been using kdenlive for quite some time now, and it's a fantastic
> NLE, thx a lot for that!
>
> While trying to learn the craft of filmmaking (as a hobbyist), I also
> stumbled upon the topic of color correction.
> Since I'm a full-stack-nerd/geek *gg*, I like nice hardware with knobs and
> displays :D
>
> So I managed to find a used Tangent CP200 color control surface and
> contacted Tangent about support for Linux.
> I got the full development package and I'm actually in the process of
> learning c++ and qt to make support for the Tangent hardware inside of
> KDEenlive.
> (I've been coding for about 30 years, worked fulltime as Java-Dev and
> although technology has quite evolved through the years, it's still easy
> for
> me to read someone's code and refactor it to my needs)
>
> Is there interest to put Tangent-support into the official repository?
> since they released their Ripple, color grading software is not so
> expensive
> anymore...
>
> I will program it anyways, so maybe it can be some help to others...
>
> When researching the code for color grading, I found a interesting
> behaviour
> of the LiftGammaGain-Widget:
> On every color correction panel you have 2 buttons to reset color and
> brightness independently.
> During my first steps I found, that resetting the color wheel in the LGGW
> works as intended (just reset the color wheel), but resetting the
> brightness
> bar will reset the color wheel, too!
>
> I don't know if this is intended or a bug - but I decided to change it to
> my
> needs (only reset the brightness/value bar):
> In colorwheel.cpp I just changed line 178:
>             // old code: c =
> NegQColor::fromRgbF(m_defaultValue/m_sizeFactor,
> m_defaultValue/m_sizeFactor, m_defaultValue/m_sizeFactor);
>             c = NegQColor::fromHsvF(m_color.hueF(), m_color.saturationF(),
> m_defaultValue/m_sizeFactor);
>
> ATM I'm not very good at git, so I don't like to submit such a small change
> to the official repository.
> (aaand I'm actually using the 18.08 branch for my dev-testing)
>
> If there's need to implement this into the repo, could someone of the devs
> do this?
> Otherwise, if the actual reset-algorithm is planned to work like this, just
> keep it this way :)
>
> thx and greetings
> michi
>
>
>

-- 
1111.1010.r.i.1101|n.o.i.s.1110|i.m.1010.g.1110|مقاومة
fsf member #5439
usuario GNU/Linux #471966
|_|0|_|
|_|_|0|
|0|0|0|
<a href="http://www.gunga.com.br">gunga</a>
<a href="http://www.tempoecoarte.com.br">tempoecoarte</a>
<a href="http://www.atelier-labs.org">atelier-labs</a>
<a href="http://www.mocambos.net">rede mocambos</a>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdenlive/attachments/20181112/beae14fa/attachment.html>

From Mi.Hi at gmx.net  Mon Nov 12 22:20:15 2018
From: Mi.Hi at gmx.net (Michael Hirczy)
Date: Mon, 12 Nov 2018 23:20:15 +0100
Subject: Interest in supporting Tangent Colorgrading Panels?
 LiftGammaGain Widget reset bug
In-Reply-To: <CAHMxv37FoTctM7JxifWHsBeE=JBsa5da7TWYHPVUF8OrPRjQ3w@mail.gmail.com>
References: <002701d47a7e$f261f140$d725d3c0$@gmx.net>
 <CAHMxv37FoTctM7JxifWHsBeE=JBsa5da7TWYHPVUF8OrPRjQ3w@mail.gmail.com>
Message-ID: <trinity-8d019a88-6660-4256-9878-6871bcc21ab6-1542061215248@msvc-mesg-gmx124>


thx farid!

account has already been created and I‘m already on the phabricator page ;)

technically talking to the tangent panels is not too complicated, since all communication is done though their hub-software, which has socket based communication with the application.
I first wanted to start with the loftgammagain widget, it would need some slight modifications, at the moment it‘s 100% mouse controlled, so I‘d do some wrapper methods to make adjustments possible through code.
nothing fancy for starters... :)

thx for the added links, I‘ll have a look...

greetings
michi

On 12.11.18 at 21:02, farid abdelnour wrote:

> Hi Michael and welcome!
> 
> That is some sweet hardware and I think it would be great to have support
> for it in the next releases. I don't know technically what would be
> involved to make it happen though. A first step can be to create a KDE
> account and maybe start a thread on phabricator about this. Here s the link
> to the Kdenlive board: https://phabricator.kde.org/project/view/40/
> 
> Here is some info on git, hope it helps somehow:
> https://community.kde.org/Infrastructure/Git
> 
> Also besides the mailing list we have a telegram and irc channels.
> 
> Cheers :)
> 
> 
> Em seg, 12 de nov de 2018 às 09:58, Michael Hirczy <mi.hi at gmx.net> escreveu:
> 
> > Greetings!
> >
> > I have been using kdenlive for quite some time now, and it's a fantastic
> > NLE, thx a lot for that!
> >
> > While trying to learn the craft of filmmaking (as a hobbyist), I also
> > stumbled upon the topic of color correction.
> > Since I'm a full-stack-nerd/geek *gg*, I like nice hardware with knobs and
> > displays :D
> >
> > So I managed to find a used Tangent CP200 color control surface and
> > contacted Tangent about support for Linux.
> > I got the full development package and I'm actually in the process of
> > learning c++ and qt to make support for the Tangent hardware inside of
> > KDEenlive.
> > (I've been coding for about 30 years, worked fulltime as Java-Dev and
> > although technology has quite evolved through the years, it's still easy
> > for
> > me to read someone's code and refactor it to my needs)
> >
> > Is there interest to put Tangent-support into the official repository?
> > since they released their Ripple, color grading software is not so
> > expensive
> > anymore...
> >
> > I will program it anyways, so maybe it can be some help to others...
> >
> > When researching the code for color grading, I found a interesting
> > behaviour
> > of the LiftGammaGain-Widget:
> > On every color correction panel you have 2 buttons to reset color and
> > brightness independently.
> > During my first steps I found, that resetting the color wheel in the LGGW
> > works as intended (just reset the color wheel), but resetting the
> > brightness
> > bar will reset the color wheel, too!
> >
> > I don't know if this is intended or a bug - but I decided to change it to
> > my
> > needs (only reset the brightness/value bar):
> > In colorwheel.cpp I just changed line 178:
> >             // old code: c =
> > NegQColor::fromRgbF(m_defaultValue/m_sizeFactor,
> > m_defaultValue/m_sizeFactor, m_defaultValue/m_sizeFactor);
> >             c = NegQColor::fromHsvF(m_color.hueF(), m_color.saturationF(),
> > m_defaultValue/m_sizeFactor);
> >
> > ATM I'm not very good at git, so I don't like to submit such a small change
> > to the official repository.
> > (aaand I'm actually using the 18.08 branch for my dev-testing)
> >
> > If there's need to implement this into the repo, could someone of the devs
> > do this?
> > Otherwise, if the actual reset-algorithm is planned to work like this, just
> > keep it this way :)
> >
> > thx and greetings
> > michi
> >
> >
> >
> 
> -- 
> 1111.1010.r.i.1101|n.o.i.s.1110|i.m.1010.g.1110|مقاومة
> fsf member #5439
> usuario GNU/Linux #471966
> |_|0|_|
> |_|_|0|
> |0|0|0|
> <a href="http://www.gunga.com.br">gunga</a>
> <a href="http://www.tempoecoarte.com.br">tempoecoarte</a>
> <a href="http://www.atelier-labs.org">atelier-labs</a>
> <a href="http://www.mocambos.net">rede mocambos</a>

From jb at kdenlive.org  Tue Nov 13 07:23:14 2018
From: jb at kdenlive.org (Jean-Baptiste Mardelle)
Date: Tue, 13 Nov 2018 08:23:14 +0100
Subject: Interest in supporting Tangent Colorgrading
 =?iso-8859-1?Q?Panels=3F_LiftGammaGain_Widget_reset_bug?=
In-Reply-To: <trinity-8d019a88-6660-4256-9878-6871bcc21ab6-1542061215248@msvc-mesg-gmx124>
References: <002701d47a7e$f261f140$d725d3c0$@gmx.net>
 <CAHMxv37FoTctM7JxifWHsBeE=JBsa5da7TWYHPVUF8OrPRjQ3w@mail.gmail.com>
 <trinity-8d019a88-6660-4256-9878-6871bcc21ab6-1542061215248@msvc-mesg-gmx124>
Message-ID: <1e8023b0-5bef-412e-b4d1-16efc9986cfb@kdenlive.org>

On lundi, 12 novembre 2018 23.20:15 h CET, Michael Hirczy wrote:
> thx farid!

Hello Michael and welcome!

> account has already been created and I‘m already on the phabricator page ;)


Nice. Any improvment is welcome. We just need to make sure that all code is 
open source and that we don't have to include headers from their SDK that 
has an incompatible license.

Also, we should try to think of a reusable architecture, allowing future 
hardware to be added to the implementation in the future.

> technically talking to the tangent panels is not too 
> complicated, since all communication is done though their 
> hub-software, which has socket based communication with the 
> application.
> I first wanted to start with the loftgammagain widget, it would 
> need some slight modifications, at the moment it‘s 100% mouse 
> controlled, so I‘d do some wrapper methods to make adjustments 
> possible through code.
> nothing fancy for starters... :)

Seems like a good start. Please use the refactoring_timeline git branch if 
possible since it's where all the code changes have been pushed since 2 
years, and is targeted for an april 2019 release.


> thx for the added links, I‘ll have a look...

Feel free to ask your questions.

> greetings
> michi
>
> On 12.11.18 at 21:02, farid abdelnour wrote:
>
>> Hi Michael and welcome!
>> 
>> That is some sweet hardware and I think it would be great to have support
>> for it in the next releases. I don't know technically what would be
>> involved to make it happen though. A first step can be to create a KDE
>> account and maybe start a thread on phabricator about this. 
>> Here s the link ...
>
>
>


From mi.hi at gmx.net  Tue Nov 13 08:54:49 2018
From: mi.hi at gmx.net (Michael Hirczy)
Date: Tue, 13 Nov 2018 09:54:49 +0100
Subject: Interest in supporting Tangent Colorgrading Panels? LiftGammaGain
 Widget reset bug
Message-ID: <000e01d47b2e$892851a0$9b78f4e0$@gmx.net>

>Hello Michael and welcome!

Thx a lot, Jean-Baptiste!

>Nice. Any improvment is welcome. We just need to make sure that all code is open source and that we don't have to include headers from their SDK >that has an incompatible license.

No problem in this scenario. Tangent designed their own hub-software, which talks to the hardware itself.
The application (kdenlive) talks to the hub through a socket connection with given protocol, so all communication to the hub has to be implemented by myself.
So no SDK, no include headers (except the self-written).

The only thing I'm going to ask Tangent, is to make the Linux version of their Hub-software available on the website.
Or maybe we can get the admit to include it in kdenlive's download package.
At the moment, only the development package has the Linux hub included.

>Also, we should try to think of a reusable architecture, allowing future hardware to be added to the implementation in the future.

I thought quite some time about this :)
Because I'm not very good at C++/Qt coding yet, I decided to use the already implemented widgets and make small changes there.

My goal at the end, once I managed Qt better, would have been some kind of "full functional color grading widget", like the Lumetri Color Panel in Premiere:
https://www.youtube.com/watch?v=SX3kMRM6EmU

Should I create a "feature idea" on phabricator?

>> technically talking to the tangent panels is not too complicated, 
>> since all communication is done though their hub-software, which has 
>> socket based communication with the application.
>> I first wanted to start with the loftgammagain widget, it would need 
>> some slight modifications, at the moment it‘s 100% mouse controlled, 
>> so I‘d do some wrapper methods to make adjustments possible through 
>> code.
>> nothing fancy for starters... :)

>Seems like a good start. Please use the refactoring_timeline git branch if possible since it's where all the code changes have been pushed since 2 years, >and is targeted for an april 2019 release.

ok, I'll change to refactoring.

greetings
michi


From noreply at kde.org  Thu Nov 15 07:51:24 2018
From: noreply at kde.org (CI System)
Date: Thu, 15 Nov 2018 07:51:24 +0000 (UTC)
Subject: =?UTF-8?Q?KDE_CI:_Applications_=C2=BB_kdenlive_=C2=BB_kf5-q?=
 =?UTF-8?Q?t5_FreeBSDQt5.11_-_Build_#_64_-_Failure!?=
Message-ID: <1651990732.111.1542268284194.JavaMail.production@nellie>

An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdenlive/attachments/20181115/da45e87a/attachment.html>

From noreply at kde.org  Thu Nov 15 07:52:01 2018
From: noreply at kde.org (CI System)
Date: Thu, 15 Nov 2018 07:52:01 +0000 (UTC)
Subject: =?UTF-8?Q?KDE_CI:_Applications_=C2=BB_kdenlive_=C2=BB_kf5-?=
 =?UTF-8?Q?qt5_SUSEQt5.9_-_Build_#_108_-_Failure!?=
Message-ID: <1753788724.113.1542268321331.JavaMail.production@nellie>

An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdenlive/attachments/20181115/de94d29a/attachment-0001.html>

From camille.moulin at free.fr  Thu Nov 22 22:30:03 2018
From: camille.moulin at free.fr (Camille)
Date: Thu, 22 Nov 2018 23:30:03 +0100
Subject: Rendering dialog
Message-ID: <22784ef4-1d93-d4e0-917c-b9b95774f331@free.fr>

Hi all,

When I started using kdenlive, I found the Rendering dialog a little bit
confusing. Once you know how it works, it's completely fine, but may be
we could make it a little bit more obvious for newcomers.

What do you think on the following points :

- Removing the "Close" button, as IMHO it is redundant with the cross in
the window bar and it would unclutter the dialog.

- Changing "Render to file" to "Render now"

- Aligning the two buttons "Render now" and "Generate script" to the right

- Changing the check box "More options" to a large button

It would look like the image attached.

Thanks,

Camille



-------------- next part --------------
A non-text attachment was scrubbed...
Name: Capture d??cran de 2018-11-22 23-27-12.png
Type: image/png
Size: 64436 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kdenlive/attachments/20181122/4b8cd10c/attachment-0001.png>

From jdd at dodin.org  Fri Nov 23 07:03:24 2018
From: jdd at dodin.org (jdd at dodin.org)
Date: Fri, 23 Nov 2018 08:03:24 +0100
Subject: Rendering dialog
In-Reply-To: <22784ef4-1d93-d4e0-917c-b9b95774f331@free.fr>
References: <22784ef4-1d93-d4e0-917c-b9b95774f331@free.fr>
Message-ID: <7732ff00-8295-8831-818b-517b8db7da7a@dodin.org>

Le 22/11/2018 à 23:30, Camille a écrit :

> - Removing the "Close" button, as IMHO it is redundant with the cross in
> the window bar and it would unclutter the dialog.

please, don't. the "x" button is often for "exit" when "close" only send 
the windows in the background. Render in background would be more clear, 
but too long :-(

this background thing is one of the better Kdenlive feature :-!

jdd


-- 
http://dodin.org

From camille.moulin at free.fr  Fri Nov 23 08:18:21 2018
From: camille.moulin at free.fr (Camille)
Date: Fri, 23 Nov 2018 09:18:21 +0100
Subject: Rendering dialog
In-Reply-To: <7732ff00-8295-8831-818b-517b8db7da7a@dodin.org>
References: <22784ef4-1d93-d4e0-917c-b9b95774f331@free.fr>
 <7732ff00-8295-8831-818b-517b8db7da7a@dodin.org>
Message-ID: <2268e45b-c191-d38b-07ee-8ce2566a45a6@free.fr>


Le 23/11/2018 à 08:03, jdd at dodin.org a écrit :
> Le 22/11/2018 à 23:30, Camille a écrit :
>
>> - Removing the "Close" button, as IMHO it is redundant with the cross in
>> the window bar and it would unclutter the dialog.
>
> please, don't. the "x" button is often for "exit" when "close" only
> send the windows in the background. 

Currently, both have exactly the same action : if you close the window
with "x" or with the close button, you rendering will still continue in
the background

> Render in background would be more clear, but too long :-(
>
> this background thing is one of the better Kdenlive feature :-!

Don't worry, I never intended to have it removed ;-)



From jdd at dodin.org  Fri Nov 23 08:23:55 2018
From: jdd at dodin.org (jdd at dodin.org)
Date: Fri, 23 Nov 2018 09:23:55 +0100
Subject: Rendering dialog
In-Reply-To: <2268e45b-c191-d38b-07ee-8ce2566a45a6@free.fr>
References: <22784ef4-1d93-d4e0-917c-b9b95774f331@free.fr>
 <7732ff00-8295-8831-818b-517b8db7da7a@dodin.org>
 <2268e45b-c191-d38b-07ee-8ce2566a45a6@free.fr>
Message-ID: <8597f487-6d37-c05b-6413-5109e1f58d7d@dodin.org>

Le 23/11/2018 à 09:18, Camille a écrit :
> 
> Le 23/11/2018 à 08:03, jdd at dodin.org a écrit :
>> Le 22/11/2018 à 23:30, Camille a écrit :
>>
>>> - Removing the "Close" button, as IMHO it is redundant with the cross in
>>> the window bar and it would unclutter the dialog.
>>
>> please, don't. the "x" button is often for "exit" when "close" only
>> send the windows in the background.
> 
> Currently, both have exactly the same action : if you close the window
> with "x" or with the close button, you rendering will still continue in
> the background

yes, but who knows? It's not obvious at first sight :-(

> 
>> Render in background would be more clear, but too long :-(
>>
>> this background thing is one of the better Kdenlive feature :-!
> 
> Don't worry, I never intended to have it removed ;-)
> 
> 
:-)

jdd

-- 
http://dodin.org

From informatica at actiu.net  Fri Nov 23 09:50:48 2018
From: informatica at actiu.net (Narcis Garcia)
Date: Fri, 23 Nov 2018 10:50:48 +0100
Subject: Rendering dialog
In-Reply-To: <22784ef4-1d93-d4e0-917c-b9b95774f331@free.fr>
Message-ID: <7c99c831-394f-c585-cd65-a1e801d7682f@actiu.net>

On 22/11/18 23:30, Camille wrote:
> Hi all,
> 
> When I started using kdenlive, I found the Rendering dialog a little bit
> confusing. Once you know how it works, it's completely fine, but may be
> we could make it a little bit more obvious for newcomers.
> 
> What do you think on the following points :
> 
> - Removing the "Close" button, as IMHO it is redundant with the cross in
> the window bar and it would unclutter the dialog.

Better a [Hide] or [To background] button.
And [X] button should not appear.

> - Changing "Render to file" to "Render now"
> 
> - Aligning the two buttons "Render now" and "Generate script" to the right
> 
> - Changing the check box "More options" to a large button
> 
> It would look like the image attached.
> 
> Thanks,
> 
> Camille
> 
> 
> 

From elhoir at gmail.com  Fri Nov 23 20:07:16 2018
From: elhoir at gmail.com (=?UTF-8?Q?Javier_Agust=C3=ACn_Fern=C3=A0ndez_Arroyo?=)
Date: Fri, 23 Nov 2018 21:07:16 +0100
Subject: translating the website
In-Reply-To: <CAAHf8rePBHVXBUdGqi6iaD9YNvu=f_dFKSwb82jjP1Cg1xwcLA@mail.gmail.com>
References: <CAHMxv37obHS8s-D4_d_8LtMx1zny35-8jWaBzOAQD19a1RYvGg@mail.gmail.com>
 <CAAHf8rfS0qSMSutpL3Bp=N-VA_cYnykPm_bL9MQHZSYGRpuXCA@mail.gmail.com>
 <CAHMxv34zHEgcRukUg34Pw+dAM=6hgcs4CeRR5o3vfQno8LwGBQ@mail.gmail.com>
 <CAAHf8rdx4HxjT_B8nU6GxZRE4mvpwReOe7D9xdZ_2Oz3SKnsLg@mail.gmail.com>
 <CAAHf8rddqaZ-Vr9Js2qLZ=x6-QFSu9iTbY6_Mr15WT8VehhAbA@mail.gmail.com>
 <CAHMxv35=EhdxW25Gxg8tWMyMhddtOC5kRovCBxNN0f0FALSWmQ@mail.gmail.com>
 <CAAHf8reMyeL93tkdm3KVaudJrNR8kx_J6XLzXYoVaQ6ikhDCvQ@mail.gmail.com>
 <CAAHf8rdMuSrz=NtAbUtS+c2EPWOZCARFz=A=1_n5-ZcCwnuNEg@mail.gmail.com>
 <CAAHf8rePBHVXBUdGqi6iaD9YNvu=f_dFKSwb82jjP1Cg1xwcLA@mail.gmail.com>
Message-ID: <CAAHf8rcDx1_5qa1QrP-ECYjdWPAh+DV9LqK6ZAYjWrXAnkaAbw@mail.gmail.com>

hello again,

i cant login into kde... whats my username and password?

thanks

On Sun, Jun 3, 2018 at 6:35 PM Javier Agustìn Fernàndez Arroyo <
elhoir at gmail.com> wrote:

> i alreado have an account at wordpress with the "elhoir" username for the
> ancient ReactOS blog.... maybe thats the problem?
>
> On Sun, Jun 3, 2018 at 6:29 PM, Javier Agustìn Fernàndez Arroyo <
> elhoir at gmail.com> wrote:
>
>> hello again,
>>
>> i just received the password reset email. But, every time i do it (reset
>> my password) i get an "Could not authenticate your credentials." error..
>>
>>
>>
>> On Sun, Jun 3, 2018 at 6:23 PM, Javier Agustìn Fernàndez Arroyo <
>> elhoir at gmail.com> wrote:
>>
>>> hello,
>>>
>>> thank you , i will check asap. But... what about password? :)
>>>
>>> No i dont know about Polyang, sorry :(
>>>
>>> On Sun, Jun 3, 2018 at 1:33 AM, farid abdelnour <snd.noise at gmail.com>
>>> wrote:
>>>
>>>> Sorry for the delay,
>>>>
>>>> I have just added you. Please check.
>>>>
>>>> We are using the Polylang plugin, are you aware how to use it? If not,
>>>> let us maybe mark a day to introduce the translation system.
>>>>
>>>> Cheers
>>>>
>>>> 2018-05-30 5:12 GMT-03:00 Javier Agustìn Fernàndez Arroyo <
>>>> elhoir at gmail.com>:
>>>>
>>>>> btw, i use the nickname "elhoir" at IRC and reactos.org. Would you
>>>>> mind to choose same username for kdenlive? thank you!
>>>>>
>>>>> On Wed, May 30, 2018 at 9:48 AM, Javier Agustìn Fernàndez Arroyo <
>>>>> elhoir at gmail.com> wrote:
>>>>>
>>>>>> thank you! now it`ś up to ¿you? to give me username & password :)
>>>>>>
>>>>>> On Tue, May 29, 2018 at 4:29 AM, farid abdelnour <snd.noise at gmail.com
>>>>>> > wrote:
>>>>>>
>>>>>>> Hi Javier
>>>>>>>
>>>>>>> Please go here:
>>>>>>> http://identity.kde.org/
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> 2018-05-28 18:37 GMT-03:00 Javier Agustìn Fernàndez Arroyo <
>>>>>>> elhoir at gmail.com>:
>>>>>>>
>>>>>>>> hello,
>>>>>>>> sorry for the delay
>>>>>>>>
>>>>>>>> No i dont have any KDE account....
>>>>>>>>
>>>>>>>> what is the URL to log in?
>>>>>>>>
>>>>>>>> thank you!
>>>>>>>>
>>>>>>>> On Mon, May 28, 2018 at 7:43 PM, farid abdelnour <
>>>>>>>> snd.noise at gmail.com> wrote:
>>>>>>>>
>>>>>>>>> Hi Javier,
>>>>>>>>>
>>>>>>>>> Do you have a KDE account so I can give you ccess to the website?
>>>>>>>>>
>>>>>>>>> Please let me know and I'll create an account for you.
>>>>>>>>>
>>>>>>>>> Cheers :D
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> 1111.1010.r.i.1101|n.o.i.s.1110|i.m.1010.g.1110|مقاومة
>>>>>>>>> fsf member #5439
>>>>>>>>> usuario GNU/Linux #471966
>>>>>>>>> |_|0|_|
>>>>>>>>> |_|_|0|
>>>>>>>>> |0|0|0|
>>>>>>>>> <a href="http://www.gunga.com.br">gunga</a>
>>>>>>>>> <a href="http://www.tempoecoarte.com.br">tempoecoarte</a>
>>>>>>>>> <a href="http://www.atelier-labs.org">atelier-labs</a>
>>>>>>>>> <a href="http://www.mocambos.net">rede mocambos</a>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> 1111.1010.r.i.1101|n.o.i.s.1110|i.m.1010.g.1110|مقاومة
>>>>>>> fsf member #5439
>>>>>>> usuario GNU/Linux #471966
>>>>>>> |_|0|_|
>>>>>>> |_|_|0|
>>>>>>> |0|0|0|
>>>>>>> <a href="http://www.gunga.com.br">gunga</a>
>>>>>>> <a href="http://www.tempoecoarte.com.br">tempoecoarte</a>
>>>>>>> <a href="http://www.atelier-labs.org">atelier-labs</a>
>>>>>>> <a href="http://www.mocambos.net">rede mocambos</a>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> 1111.1010.r.i.1101|n.o.i.s.1110|i.m.1010.g.1110|مقاومة
>>>> fsf member #5439
>>>> usuario GNU/Linux #471966
>>>> |_|0|_|
>>>> |_|_|0|
>>>> |0|0|0|
>>>> <a href="http://www.gunga.com.br">gunga</a>
>>>> <a href="http://www.tempoecoarte.com.br">tempoecoarte</a>
>>>> <a href="http://www.atelier-labs.org">atelier-labs</a>
>>>> <a href="http://www.mocambos.net">rede mocambos</a>
>>>>
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdenlive/attachments/20181123/ad51f256/attachment.html>

From coreyoconnor at gmail.com  Mon Nov 26 17:18:47 2018
From: coreyoconnor at gmail.com (Corey O'Connor)
Date: Mon, 26 Nov 2018 09:18:47 -0800
Subject: Nvidia crash using kdenlive: where to start?
Message-ID: <CANTmfBQo41y=HwUsuTSFREapirmhROy1UyAKjGxg6F6_9zkNJg@mail.gmail.com>

Hi all,

I have the time and inclination to look into this bug:
https://devtalk.nvidia.com/default/topic/1019615/movit-library-crash-when-used-in-kdenlive/

I have master and refactoring_timeline branches compiling from git.
Plus movit and mtl compiling from git. All ready to fork and fix
but.... where to start? Any pointers?

Cheers,
Corey

-Corey O'Connor
coreyoconnor at gmail.com

From snd.noise at gmail.com  Mon Nov 26 23:32:31 2018
From: snd.noise at gmail.com (farid abdelnour)
Date: Mon, 26 Nov 2018 21:32:31 -0200
Subject: Bug squashing day
Message-ID: <CAHMxv3572KPHHJtkDXUGCo5bNhUbGPSuAS7xifvCu-gPRig-uw@mail.gmail.com>

Hi all

Just a reminder or for those who still don't know...

We'll be having a bug squashing day this Sunday (December 2) please help
spread the word and hope to see you there.

More info:
https://kdenlive.org/en/2018/11/bugsquashing-day/

Cheers :D

-- 
1111.1010.r.i.1101|n.o.i.s.1110|i.m.1010.g.1110|مقاومة
fsf member #5439
usuario GNU/Linux #471966
|_|0|_|
|_|_|0|
|0|0|0|
<a href="http://www.gunga.com.br">gunga</a>
<a href="http://www.tempoecoarte.com.br">tempoecoarte</a>
<a href="http://www.atelier-labs.org">atelier-labs</a>
<a href="http://www.mocambos.net">rede mocambos</a>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdenlive/attachments/20181126/b054cdbe/attachment.html>

From eugen.mohr at gmx.net  Thu Nov 29 17:43:19 2018
From: eugen.mohr at gmx.net (Eugen Mohr)
Date: Thu, 29 Nov 2018 18:43:19 +0100
Subject: Nvidia crash using kdenlive: where to start?
In-Reply-To: <CANTmfBQo41y=HwUsuTSFREapirmhROy1UyAKjGxg6F6_9zkNJg@mail.gmail.com>
References: <CANTmfBQo41y=HwUsuTSFREapirmhROy1UyAKjGxg6F6_9zkNJg@mail.gmail.com>
Message-ID: <663ecd5a-4544-cdf1-f909-04aed24cfe9c@gmx.net>

Hi Corey

I would say use the refactoring_timeline branch. The master branch 
contains the 18.08 / 18.12 branch only. The refactoring branch contains 
the Vaapi and Nvidia (Nvenc) acceleration. MLT has v6.12.0 released with 
some fixes. <https://www.mltframework.org/blog/v6.12.0_released/>I can’t 
say anything about Movit. But fixing/implementing the GPU acceleration 
would be great.

Am 26.11.2018 um 18:18 schrieb Corey O'Connor:
> Hi all,
>
> I have the time and inclination to look into this bug:
> https://devtalk.nvidia.com/default/topic/1019615/movit-library-crash-when-used-in-kdenlive/
>
> I have master and refactoring_timeline branches compiling from git.
> Plus movit and mtl compiling from git. All ready to fork and fix
> but.... where to start? Any pointers?
>
> Cheers,
> Corey
>
> -Corey O'Connor
> coreyoconnor at gmail.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdenlive/attachments/20181129/2a3266e4/attachment.html>

From coreyoconnor at gmail.com  Thu Nov 29 18:03:25 2018
From: coreyoconnor at gmail.com (Corey O'Connor)
Date: Thu, 29 Nov 2018 10:03:25 -0800
Subject: Nvidia crash using kdenlive: where to start?
In-Reply-To: <663ecd5a-4544-cdf1-f909-04aed24cfe9c@gmx.net>
References: <CANTmfBQo41y=HwUsuTSFREapirmhROy1UyAKjGxg6F6_9zkNJg@mail.gmail.com>
 <663ecd5a-4544-cdf1-f909-04aed24cfe9c@gmx.net>
Message-ID: <CANTmfBRYHaLaq-O9MZ=Kywi1QsRz9ZWy8inc4GsfhacXrjXhmA@mail.gmail.com>

Thanks for the info! I'll start with making sure I can compile MLT
6.12. Then see about joining the bug bash :)

Is this the closest ticket for the issue? https://phabricator.kde.org/T2908

Cheers,
Corey O'Connor

On Thu, Nov 29, 2018 at 9:44 AM Eugen Mohr <eugen.mohr at gmx.net> wrote:
>
> Hi Corey
>
> I would say use the refactoring_timeline branch. The master branch contains the 18.08 / 18.12 branch only. The refactoring branch contains the Vaapi and Nvidia (Nvenc) acceleration. MLT has v6.12.0 released with some fixes. I can’t say anything about Movit. But fixing/implementing the GPU acceleration would be great.
>
> Am 26.11.2018 um 18:18 schrieb Corey O'Connor:
>
> Hi all,
>
> I have the time and inclination to look into this bug:
> https://devtalk.nvidia.com/default/topic/1019615/movit-library-crash-when-used-in-kdenlive/
>
> I have master and refactoring_timeline branches compiling from git.
> Plus movit and mtl compiling from git. All ready to fork and fix
> but.... where to start? Any pointers?
>
> Cheers,
> Corey
>
> -Corey O'Connor
> coreyoconnor at gmail.com
>

From snd.noise at gmail.com  Thu Nov 29 18:08:37 2018
From: snd.noise at gmail.com (farid abdelnour)
Date: Thu, 29 Nov 2018 16:08:37 -0200
Subject: Nvidia crash using kdenlive: where to start?
In-Reply-To: <CANTmfBRYHaLaq-O9MZ=Kywi1QsRz9ZWy8inc4GsfhacXrjXhmA@mail.gmail.com>
References: <CANTmfBQo41y=HwUsuTSFREapirmhROy1UyAKjGxg6F6_9zkNJg@mail.gmail.com>
 <663ecd5a-4544-cdf1-f909-04aed24cfe9c@gmx.net>
 <CANTmfBRYHaLaq-O9MZ=Kywi1QsRz9ZWy8inc4GsfhacXrjXhmA@mail.gmail.com>
Message-ID: <CAHMxv37FA7WXqxu6e3fRTFiLQp-3QR52jd7VnjotFHeBkqYUwg@mail.gmail.com>

Hi Corey

Welcome to the team, happy to have you here.

Em qui, 29 de nov de 2018 às 16:03, Corey O'Connor <coreyoconnor at gmail.com>
escreveu:

> Thanks for the info! I'll start with making sure I can compile MLT
> 6.12. Then see about joining the bug bash :)
>
> Is this the closest ticket for the issue?
> https://phabricator.kde.org/T2908


There is also this list:
https://bugs.kde.org/buglist.cgi?quicksearch=product%3Akdenlive%20flag%3Amovit&list_id=1568316

I can help out producing some debugging info if you like.

See you in the bug squashing day. :)

>
>
> Cheers,
> Corey O'Connor
>
> On Thu, Nov 29, 2018 at 9:44 AM Eugen Mohr <eugen.mohr at gmx.net> wrote:
> >
> > Hi Corey
> >
> > I would say use the refactoring_timeline branch. The master branch
> contains the 18.08 / 18.12 branch only. The refactoring branch contains the
> Vaapi and Nvidia (Nvenc) acceleration. MLT has v6.12.0 released with some
> fixes. I can’t say anything about Movit. But fixing/implementing the GPU
> acceleration would be great.
> >
> > Am 26.11.2018 um 18:18 schrieb Corey O'Connor:
> >
> > Hi all,
> >
> > I have the time and inclination to look into this bug:
> >
> https://devtalk.nvidia.com/default/topic/1019615/movit-library-crash-when-used-in-kdenlive/
> >
> > I have master and refactoring_timeline branches compiling from git.
> > Plus movit and mtl compiling from git. All ready to fork and fix
> > but.... where to start? Any pointers?
> >
> > Cheers,
> > Corey
> >
> > -Corey O'Connor
> > coreyoconnor at gmail.com
> >
>


-- 
1111.1010.r.i.1101|n.o.i.s.1110|i.m.1010.g.1110|مقاومة
fsf member #5439
usuario GNU/Linux #471966
|_|0|_|
|_|_|0|
|0|0|0|
<a href="http://www.gunga.com.br">gunga</a>
<a href="http://www.tempoecoarte.com.br">tempoecoarte</a>
<a href="http://www.atelier-labs.org">atelier-labs</a>
<a href="http://www.mocambos.net">rede mocambos</a>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdenlive/attachments/20181129/2c567734/attachment-0001.html>