Reindl Harald thelounge.net> writes:
> when you specify something twice the right one wins
I fear it's not that easy: It is actually undefined
behaviour to specify an option twice (that is not
supposed to be specified more than once), so for
example ticket #4184.
Carl Eugen
Am 05.01.2016 um 17:00 schrieb Phil Rhodes:
thinking one can develop a GUI which is usable and supports all of the >
features of ffmpeg or even a large part of them is naive
Well, possibly, but the problem is that the CLI doesn't do a very good job of
it either. Inasmuch as CLI discoverabi
Am 05.01.2016 um 16:32 schrieb Paul B Mahol:
On 1/5/16, Reindl Harald wrote:
Am 05.01.2016 um 16:21 schrieb Michael Koch:
For example, Harald Reindl just wrote:
"and when you specify something twice the right one wins"
Is this already in the FFmpeg documentation?
that's common sense
f
> thinking one can develop a GUI which is usable and supports all of the >
>features of ffmpeg or even a large part of them is naive
Well, possibly, but the problem is that the CLI doesn't do a very good job of
it either. Inasmuch as CLI discoverability is effectively zero, it doesn't do
any job
well, then i ask the question different
"--width=600 --width=300" - what would you expect?
before I saw your answer, it was unclear to me if it's 300 or 600.
Michael
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/li
On 1/5/16, Reindl Harald wrote:
>
>
> Am 05.01.2016 um 16:21 schrieb Michael Koch:
For example, Harald Reindl just wrote:
"and when you specify something twice the right one wins"
Is this already in the FFmpeg documentation?
>>>
>>> that's common sense
>>
>> for you, but not fo
Am 05.01.2016 um 16:21 schrieb Michael Koch:
For example, Harald Reindl just wrote:
"and when you specify something twice the right one wins"
Is this already in the FFmpeg documentation?
that's common sense
for you, but not for a beginner
well, then i ask the question different
"--width
For example, Harald Reindl just wrote:
"and when you specify something twice the right one wins"
Is this already in the FFmpeg documentation?
that's common sense
for you, but not for a beginner.
Michael
___
ffmpeg-user mailing list
ffmpeg-user@
Am 05.01.2016 um 16:03 schrieb Michael Koch:
What part of this mailing list thread is not
documented in your opinion?
For example, Harald Reindl just wrote:
"and when you specify something twice the right one wins"
Is this already in the FFmpeg documentation?
that's common sense
signatu
Am 05.01.2016 um 15:43 schrieb Phil Rhodes:
I think in general a lot of problems with commandline software in general exist
when the software begins to exceed the ability of a commandline to act as a
workable UI.
Naturally there are reasons to provide serialised instructions to a piece of
so
What part of this mailing list thread is not
documented in your opinion?
For example, Harald Reindl just wrote:
"and when you specify something twice the right one wins"
Is this already in the FFmpeg documentation?
Michael
___
ffmpeg-user mailing
Michael Koch t-online.de> writes:
> For many questions, it might be better not to answer
> them here. Instead, please add the answers to the
> documentation and then just post a link.
What part of this mailing list thread is not
documented in your opinion?
Carl Eugen
___
I think in general a lot of problems with commandline software in general exist
when the software begins to exceed the ability of a commandline to act as a
workable UI.
Naturally there are reasons to provide serialised instructions to a piece of
software, but in many cases that isn't really inte
As mentioned, documentation improvements are *always* welcome.
I agree with Roger that for a beginner FFmpeg's documentation leaves
many questions unanswered. It would be great to have more details and
especially more examples in the documentation.
Many questions are answered in this user li
Am 05.01.2016 um 15:04 schrieb Roger Pack:
As a note, I just had to get this off my chest, and I'll only say this
once. Some of FFmpeg's command line syntax is *confusing* and *super
confusing* for beginners.
For instance this:
ffmpeg -r 30 -i input_file
specifies a framerate *override* for
On Tue, Jan 05, 2016 at 07:04:11 -0700, Roger Pack wrote:
> As a note, I just had to get this off my chest, and I'll only say this
> once. Some of FFmpeg's command line syntax is *confusing* and *super
> confusing* for beginners.
That may be the case. :-) Feel free to suggest improvements to
docu
Roger Pack gmail.com> writes:
> ffmpeg -i input -f rawvideo -f nut output.nut
>
> Using (or being able to use) "-f"
> typically using two "-f" s would be an override.
> But in this case it isn't. In fact, its using
> "-f" to specify two entirely different aspects of
> the output file.
I ha
As a note, I just had to get this off my chest, and I'll only say this
once. Some of FFmpeg's command line syntax is *confusing* and *super
confusing* for beginners.
For instance this:
ffmpeg -r 30 -i input_file
specifies a framerate *override* for the input, however if you specify
it for the o
18 matches
Mail list logo
