Re: "File rendering"

2016-12-18 Thread farid abdelnour
Hi

I'm a linux user for 20 years now, and I don't see free codecs win the race
> now. I could make ogv files (webm), but my goal is to be read now, not in
> the future. I regret that but mp4 is the only really universal codec. That
> don't prevent you from using an other.
>
> we are promoting with Ethic Cinema anyway. Web browsers are not the
>> only place where you watch movies
>>
>
> my users do use browsers or smartphones (including iphones to my
> displeasure :-)
>

maybe one day we could use something like this:

https://www.indiegogo.com/projects/mox-file-format#/


-- 
.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|
http://www.gunga.com.br";>gunga
http://www.tempoecoarte.com.br";>tempoecoarte
http://www.atelier-labs.org";>atelier-labs
http://www.mocambos.net";>rede mocambos


Re: "File rendering"

2016-12-18 Thread jdd

Le 18/12/2016 à 18:36, François Téchené a écrit :


with more and more coming free licensed film productions.


I'm a linux user for 20 years now, and I don't see free codecs win the 
race now. I could make ogv files (webm), but my goal is to be read now, 
not in the future. I regret that but mp4 is the only really universal 
codec. That don't prevent you from using an other.



we are promoting with Ethic Cinema anyway. Web browsers are not the
only place where you watch movies


my users do use browsers or smartphones (including iphones to my 
displeasure :-)



Please, do consider free formats as much as you consider H264 ones.


well, I wont answer anymore to this part of the discussion, I don't want 
to drive an unuseful codec flame war...


jdd


Re: "File rendering"

2016-12-18 Thread François Téchené
Even if H264 is currently the main format, WebM should be made available to the 
user. WebM is a professional grade format as much as H264 is. Also it is not 
proprietary. Its usage should be progressing with more and more coming free 
licensed film productions. It is what we are promoting with Ethic Cinema 
anyway. Web browsers are not the only place where you watch movies and software 
like VLC have no problem reading WebM.

As of today, free format seem to be useless because their proprietary 
alternatives seem to be giving their users many freedom, which may not be the 
case forever and there is nothing one can do about it.

At Ethic Cinema, we are building our internal workflow around free formats only 
so we make sure to avoid any restrictions with using them in the future.

Please, do consider free formats as much as you consider H264 ones.

Thanks! :)

François

On 18 déc. 2016, at 12:10, jdd  wrote:

> Le 18/12/2016 à 11:44, Lionel Allorge a écrit :
>> Hi,
>> 
>>> IMHO the only universal format is mp4... but I don't want to start a
>>> license flame war :-(
>> 
>> The problem with mp4 are the software patents. That's why projects that
>> want to keep information free like Wikipedia avoid this file format and
>> use only webm and ogg theora :
>> https://commons.wikimedia.org/wiki/Commons:File_types
>> 
>> Best regards.
>> 
> I konw, but not any browser use free codecs... including in html5
> 
> jdd


Re: "File rendering"

2016-12-18 Thread jdd

Le 18/12/2016 à 11:44, Lionel Allorge a écrit :

Hi,


IMHO the only universal format is mp4... but I don't want to start a
license flame war :-(


The problem with mp4 are the software patents. That's why projects that
want to keep information free like Wikipedia avoid this file format and
use only webm and ogg theora :
https://commons.wikimedia.org/wiki/Commons:File_types

Best regards.


I konw, but not any browser use free codecs... including in html5

jdd


Re: "File rendering"

2016-12-18 Thread Lionel Allorge
Hi,

> IMHO the only universal format is mp4... but I don't want to start a 
> license flame war :-(

The problem with mp4 are the software patents. That's why projects that
want to keep information free like Wikipedia avoid this file format and
use only webm and ogg theora :
https://commons.wikimedia.org/wiki/Commons:File_types

Best regards.

-- 
Lionel Allorge
April : http://www.april.org
Lune Rouge : http://www.lunerouge.org
Wikimedia France : http://wikimedia.fr



Re: "File rendering"

2016-12-18 Thread Lionel Allorge
Hi,

> Agreed with your point: I reorganized the formats, making webm #1... in 
> January 2016, just after the 15.12 release!
> So if you upgrade to a newer version (16.12 recommended of course!) you could 
> enjoy this simpler format selection.

Great ! Many thanks.

Best regards.
-- 
Lionel Allorge
April : http://www.april.org
Lune Rouge : http://www.lunerouge.org
Wikimedia France : http://wikimedia.fr


Re: "File rendering"

2016-12-17 Thread jdd

Le 17/12/2016 à 21:53, Vincent Pinon a écrit :

Le samedi 17 décembre 2016, 12:09:37 CET jdd a écrit :



Agreed with your point: I reorganized the formats, making webm #1... in January 
2016, just after the 15.12 release!
So if you upgrade to a newer version (16.12 recommended of course!) you could 
enjoy this simpler format selection.


IMHO the only universal format is mp4... but I don't want to start a 
license flame war :-(





for what I see, all the media render system have to be revamped (may be
it's already on the way): much too "command line oriented" for a GUI
application. MLT options are not that easy to understand. IMHO the
situation is worst than for the 0.9xx era.


Strange, all options are basically the same as 0.9,


I remember changes: bit rate become quality numbers and now there is 
only a confusing slider and no slider for presets


confusing because it's grayed out for most of my own profiles.

verifying this, I see that you have the slider active for internal setup 
in main render windows, but no slider if you hit "edit" (pencil icon).


this "edit" window is specially confusing, because what mean the double 
lines "quality/default quality"? which one is used to render? in the 
first line there are often several values?


Why is speed options an editable windows?

MLT options are not that easy to master :-( - specially the relation 
between quality and presets (speed)


if necessary, I Ok to participate to any work on the subject (as tester, 
not programmer)


thanks
jdd


Re: "File rendering"

2016-12-17 Thread Vincent Pinon
Le samedi 17 décembre 2016, 12:09:37 CET jdd a écrit :
> Le 17/12/2016 à 11:06, Lionel Allorge a écrit :
> 
> > I agree ! It took me some time too to find the right option. Webm should
> > be available right away as it is one of the main formats nowadays.

Hey,

Agreed with your point: I reorganized the formats, making webm #1... in January 
2016, just after the 15.12 release!
So if you upgrade to a newer version (16.12 recommended of course!) you could 
enjoy this simpler format selection.

> for what I see, all the media render system have to be revamped (may be 
> it's already on the way): much too "command line oriented" for a GUI 
> application. MLT options are not that easy to understand. IMHO the 
> situation is worst than for the 0.9xx era.

Strange, all options are basically the same as 0.9,
just hiding the least common ones in a side pane, and using cursors instead of 
text boxes:
I tried to improve the things towards a more GUI approach!
Even comparing to commercial programs, I find it simpler & more complete... at 
least for me :)

It's open to suggestions (other examples, mockups, patches...)
but sorry if I'm sometimes extremely long to put it into application!

BR,

Vincent



Re: AW: Re: "File rendering"

2016-12-17 Thread jdd

Le 17/12/2016 à 12:15, Harald Albrecht a écrit :

Did you know that the MLT render engine uses the ffmpeg encoding engine?
And handbrakr is using ffmpeg too.



not that sure, anyway the handbrake devs answered: "codec not 
supported". VLC didn't play fine neither. kdenlive renbdered it ok


from CLI I could solve making two passes, one with handbrake and the 
other with ffmpeg


but it's done, now and was archive coding so not to be found now (AFAIK, 
low audio and video encoding in MOV or AVI by cheap cameras from 10 
years ago)


jdd





AW: Re: "File rendering"

2016-12-17 Thread Harald Albrecht
Did you know that the MLT render engine uses the ffmpeg encoding engine? And 
handbrakr is using ffmpeg too.

 Ursprüngliche Nachricht 
Von: jdd  
Datum: 17.12.16  12:09  (GMT+01:00) 
An: kdenlive@kde.org 
Betreff: Re: "File rendering" 

Le 17/12/2016 à 11:06, Lionel Allorge a écrit :

> I agree ! It took me some time too to find the right option. Webm should
> be available right away as it is one of the main formats nowadays.
>

for what I see, all the media render system have to be revamped (may be 
it's already on the way): much too "command line oriented" for a GUI 
application. MLT options are not that easy to understand. IMHO the 
situation is worst than for the 0.9xx era.

thanks, the render engine itself is engine is extremely good. I only 
could render in kdenlive some source videos that ffmpeg or handbrake 
where only capable to run with sound or with image, but not the two of 
them :-))

jdd



Re: "File rendering"

2016-12-17 Thread jdd

Le 17/12/2016 à 11:06, Lionel Allorge a écrit :


I agree ! It took me some time too to find the right option. Webm should
be available right away as it is one of the main formats nowadays.



for what I see, all the media render system have to be revamped (may be 
it's already on the way): much too "command line oriented" for a GUI 
application. MLT options are not that easy to understand. IMHO the 
situation is worst than for the 0.9xx era.


thanks, the render engine itself is engine is extremely good. I only 
could render in kdenlive some source videos that ffmpeg or handbrake 
where only capable to run with sound or with image, but not the two of 
them :-))


jdd



Re: "File rendering"

2016-12-17 Thread Lionel Allorge
Hi,

> First of all, kdenlive, the best video editing software for GNU/Linux.

I agree :-)

> When rendering a work, the default destination is "File rendering". The
> pop-up shows an overview of profiles. Today, I've been searching for a
> way to make the overview include WebM. For literally hours. I've been
> reading web pages, installed all kinds of additional packages,
> reinstalled kdenlive, Googled, talked with people on IRC, and so on.
> 
> Eventually, I learned that the destination drop-down includes "Web
> sites", which delivered me WebM. The drop-down also includes
> "Lossless/HQ".
> 
> This is a problem. The problem is that WebM also renders to a file. The
> destination is file rendering. In fact, even the button on the pop-up
> window still says "Render to File" when "Web sites" is selected.

I agree ! It took me some time too to find the right option. Webm should
be available right away as it is one of the main formats nowadays.

Best regards.

-- 
Lionel Allorge
April : http://www.april.org
Lune Rouge : http://www.lunerouge.org
Wikimedia France : http://wikimedia.fr



"File rendering"

2016-12-16 Thread Norbert de Jonge
Hi everyone,

First of all, kdenlive, the best video editing software for GNU/Linux.

Hey, I have a request. Although perhaps calling it a bug report is more
accurate. (I'm using v15.12.3.)

When rendering a work, the default destination is "File rendering". The
pop-up shows an overview of profiles. Today, I've been searching for a
way to make the overview include WebM. For literally hours. I've been
reading web pages, installed all kinds of additional packages,
reinstalled kdenlive, Googled, talked with people on IRC, and so on.

Eventually, I learned that the destination drop-down includes "Web
sites", which delivered me WebM. The drop-down also includes
"Lossless/HQ".

This is a problem. The problem is that WebM also renders to a file. The
destination is file rendering. In fact, even the button on the pop-up
window still says "Render to File" when "Web sites" is selected.

That "Destination: File rendering" does not include the option that
renders to WebM files is very misleading. Too misleading.

I could suggest changing "File rendering" to something else, but I
won't. The reason I'm not is that this would not completely solve the
problem. As a user, it's too easy to miss (not see) the drop-down
altogether.

The window needs something like a checkbox with the text "Show all
profiles". Which, if checked will display, literally, _all_ the
profiles, including those listed under destination "Web sites".

Yes, there already is a checkbox with the text "Show all profiles". You
guessed it, that is (thus) another thing that is misleading on this
window. Show all profiles does not "show all profiles", what it does is
"show all profiles for this destination".

There's a tooltip. I don't know what exactly you're doing with it, but
all tooltips are unreadable on both of my systems. They have white text
on a very white kind of yellow.

Still, kdenlive remains my favorite editor. :) Blender's VSE, pretty
nice too.

Best regards,
Norbert