On 2020-08-21 03:28, Nicolas George wrote:
Jim DeLaHunt (12020-08-20):
Nicolas, do you remember this?
On 2020-05-01 03:01, Nicolas George wrote [1]:
Carl Eugen Hoyos (12020-05-01):
-The desired output frame rate. The default is @code{25}.
+The output frame rate, in frames per second. May be
On 08/21/2020 11:08 AM, Gyan Doshi wrote:
On 21-08-2020 07:12 pm, Mark Filipak wrote:
On 08/21/2020 06:44 AM, Gyan Doshi wrote:
On 21-08-2020 04:03 pm, Michael Koch wrote:
Am 21.08.2020 um 12:09 schrieb Gyan Doshi:
FFmpeg's documentation is very incomplete. I had a rough roadmap at the start
Hi Barsnick
Thanks for your recommendation. I have cleaned up the *Options *which were
displayed in the logs, also i verified the *-preset fast* from the debug
log level. I ran the same ffmpeg command on 2 different servers, one
with *-preset
fast* and the other one with *-preset verfast*. There
On 2020-08-21 08:08, Gyan Doshi wrote:
On 21-08-2020 07:12 pm, Mark Filipak wrote:
On 08/21/2020 06:44 AM, Gyan Doshi wrote:
On 21-08-2020 04:03 pm, Michael Koch wrote:
Am 21.08.2020 um 12:09 schrieb Gyan Doshi:
…
FFmpeg's documentation is very incomplete. I had a rough roadmap
at the
On 8/21/2020 3:33 AM, Michael Koch wrote:
I never found that "General Documentation" file because I thought
"ffmpeg-all" contains what the filename implies: All. This is obviously not
the case. The filename is misleading, if the file doesn't contain all
documentation. Wouldn't it be better to
Am 21.08.2020 um 21:38 schrieb Gyan Doshi:
Git mystifies me, too. I also did a lot of reading but it was written
my Martians.
For the purposes of only generating doc patches, you only need to know
and apply a handful of git commands.
Most of the supposed difficulties of working with git
On 8/21/20, Simon Brown wrote:
> Hi,
> is it possible to stop FFmpeg from probing the input and just to tell it
> exactly what it is getting (and obviously suffering the consequences if
> it's different)? I can reduce probesize but I want essentially zero delay
> through ffmpeg (no encoding,
On 21-08-2020 11:27 pm, Mark Filipak wrote:
On 08/21/2020 12:34 PM, Michael Koch wrote:
Am 21.08.2020 um 17:06 schrieb Gyan Doshi:
On 21-08-2020 07:30 pm, Michael Koch wrote:
Am 21.08.2020 um 15:42 schrieb Mark Filipak:
On 08/21/2020 06:44 AM, Gyan Doshi wrote:
On 21-08-2020 04:03 pm,
On Friday, 21 August 2020, 15:01:00 BST, Michael Koch
wrote:
> I'm also ready to help, if it can be done without git.
I feel much the same way.
P
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
Am 20.08.2020 um 09:57 schrieb Masala Kentaro:
hello!
I have problems using FFmpeg, while trying to convert DNG-sequence
into mp4/mov/avi video file.
While converting, I also need to downgrade the resolution of the video
from original 6016x3200 to 2030x1080.
First problem: I got almost black
> Re pointers- consider them an assembly language address.
The concept is simple enough; I always thought that the C syntax for them was
unnecessarily opaque.
P
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
On 8/21/2020 10:59 AM, Paul B Mahol wrote:
I think git usage is far less complicated than ffmpeg.
Also git should be better documented too.
Both of those are true :), but still can be mystifying.
For those on windoze, there are git GUIs available that take some of the
pain out; I generally
On 8/21/20, Michael Koch wrote:
> Am 21.08.2020 um 18:41 schrieb Nicolas George:
>> Michael Koch (12020-08-21):
>>> The page https://www.ffmpeg.org/git-howto.html was obviously not written
>>> for beginners. Many terms are introduced without explaining them, and
>>> examples are missing.
>> I
On 08/21/2020 12:34 PM, Michael Koch wrote:
Am 21.08.2020 um 17:06 schrieb Gyan Doshi:
On 21-08-2020 07:30 pm, Michael Koch wrote:
Am 21.08.2020 um 15:42 schrieb Mark Filipak:
On 08/21/2020 06:44 AM, Gyan Doshi wrote:
On 21-08-2020 04:03 pm, Michael Koch wrote:
Am 21.08.2020 um 12:09
thanks
On Thu, 20 Aug 2020 at 23:16, Dennis Mungai wrote:
> On Thu, 20 Aug 2020, 20:35 Ashim Tom, wrote:
>
> > what is ffmpeg_g?
> >
>
> This is the ffmpeg binary with the debug symbols present.
> When stripped (without debug symbols) you get the ffmpeg binary.
>
> Debug symbols are useful for
Am 21.08.2020 um 18:41 schrieb Nicolas George:
Michael Koch (12020-08-21):
The page https://www.ffmpeg.org/git-howto.html was obviously not written
for beginners. Many terms are introduced without explaining them, and
examples are missing.
I think it was written for people who were familiar
Michael Koch (12020-08-21):
> The page https://www.ffmpeg.org/git-howto.html was obviously not written
> for beginners. Many terms are introduced without explaining them, and
> examples are missing.
I think it was written for people who were familiar with subversion.
Have you considered
Am 21.08.2020 um 17:06 schrieb Gyan Doshi:
On 21-08-2020 07:30 pm, Michael Koch wrote:
Am 21.08.2020 um 15:42 schrieb Mark Filipak:
On 08/21/2020 06:44 AM, Gyan Doshi wrote:
On 21-08-2020 04:03 pm, Michael Koch wrote:
Am 21.08.2020 um 12:09 schrieb Gyan Doshi:
On 21-08-2020 02:36 pm,
Hi,
is it possible to stop FFmpeg from probing the input and just to tell it
exactly what it is getting (and obviously suffering the consequences if
it's different)? I can reduce probesize but I want essentially zero delay
through ffmpeg (no encoding, just repackaging a transport stream as MP4).
On 21-08-2020 07:12 pm, Mark Filipak wrote:
On 08/21/2020 06:44 AM, Gyan Doshi wrote:
On 21-08-2020 04:03 pm, Michael Koch wrote:
Am 21.08.2020 um 12:09 schrieb Gyan Doshi:
On 21-08-2020 02:36 pm, Michael Koch wrote:
Am 21.08.2020 um 10:50 schrieb Paul B Mahol:
On 8/21/20, Michael
On 21-08-2020 07:30 pm, Michael Koch wrote:
Am 21.08.2020 um 15:42 schrieb Mark Filipak:
On 08/21/2020 06:44 AM, Gyan Doshi wrote:
On 21-08-2020 04:03 pm, Michael Koch wrote:
Am 21.08.2020 um 12:09 schrieb Gyan Doshi:
On 21-08-2020 02:36 pm, Michael Koch wrote:
Am 21.08.2020 um 10:50
Am 21.08.2020 um 15:42 schrieb Mark Filipak:
On 08/21/2020 06:44 AM, Gyan Doshi wrote:
On 21-08-2020 04:03 pm, Michael Koch wrote:
Am 21.08.2020 um 12:09 schrieb Gyan Doshi:
On 21-08-2020 02:36 pm, Michael Koch wrote:
Am 21.08.2020 um 10:50 schrieb Paul B Mahol:
On 8/21/20, Michael Koch
Am 21.08.2020 um 12:44 schrieb Gyan Doshi:
On 21-08-2020 04:03 pm, Michael Koch wrote:
Am 21.08.2020 um 12:09 schrieb Gyan Doshi:
On 21-08-2020 02:36 pm, Michael Koch wrote:
Am 21.08.2020 um 10:50 schrieb Paul B Mahol:
On 8/21/20, Michael Koch wrote:
Please add this to the documentation
On 08/21/2020 06:44 AM, Gyan Doshi wrote:
On 21-08-2020 04:03 pm, Michael Koch wrote:
Am 21.08.2020 um 12:09 schrieb Gyan Doshi:
On 21-08-2020 02:36 pm, Michael Koch wrote:
Am 21.08.2020 um 10:50 schrieb Paul B Mahol:
On 8/21/20, Michael Koch wrote:
Please add this to the documentation
On 2020-08-20 14:03 -0700, Jim DeLaHunt wrote:
> On 2020-08-20 09:03, Alexander Strasser wrote:
>
> > I will bring up a point that has become clear to me.
> >
> > Good documentation in general and especially for software is
> > incredibly hard to write and get right!
>
> I very much agree: it is
On 2020-08-21 12:28 +0200, Nicolas George wrote:
[...]
>
> They belong in an introduction chapter, with links from places where it
> is relevant. If you do it that way, and the contents makes sense, it
> will be accepted.
I agree on this in principle.
We use AVOptions implementation for
On 21-08-2020 04:03 pm, Michael Koch wrote:
Am 21.08.2020 um 12:09 schrieb Gyan Doshi:
On 21-08-2020 02:36 pm, Michael Koch wrote:
Am 21.08.2020 um 10:50 schrieb Paul B Mahol:
On 8/21/20, Michael Koch wrote:
Please add this to the documentation (for example in chapter 20.9
image2)
Am 21.08.2020 um 12:09 schrieb Gyan Doshi:
On 21-08-2020 02:36 pm, Michael Koch wrote:
Am 21.08.2020 um 10:50 schrieb Paul B Mahol:
On 8/21/20, Michael Koch wrote:
Please add this to the documentation (for example in chapter 20.9
image2)
FFmpeg supports the following image formats: BMP,
Jim DeLaHunt (12020-08-20):
> Nicolas, do you remember this?
>
> On 2020-05-01 03:01, Nicolas George wrote [1]:
> > Carl Eugen Hoyos (12020-05-01):
> > > > -The desired output frame rate. The default is @code{25}.
> > > > +The output frame rate, in frames per second. May be an integer, real,
> >
On 21-08-2020 02:36 pm, Michael Koch wrote:
Am 21.08.2020 um 10:50 schrieb Paul B Mahol:
On 8/21/20, Michael Koch wrote:
Please add this to the documentation (for example in chapter 20.9
image2)
FFmpeg supports the following image formats: BMP, DNG, GIF, JPG, PAM,
PGM (binary P5 files are
Am 21.08.2020 um 10:50 schrieb Paul B Mahol:
On 8/21/20, Michael Koch wrote:
Please add this to the documentation (for example in chapter 20.9 image2)
FFmpeg supports the following image formats: BMP, DNG, GIF, JPG, PAM,
PGM (binary P5 files are read/write, ascii P2 files are read-only),
On Friday, 21 August 2020, 08:49:13 BST, Jim DeLaHunt
wrote:
> I believe a lot of the FFmpeg developers do read this list.
Yes, and I think they hold this sort of discussion in nothing but complete
scorn.
> We are holding a mirror up to the project, and inviting them to take a look.
I don't
On 8/21/20, Michael Koch wrote:
> Please add this to the documentation (for example in chapter 20.9 image2)
>
> FFmpeg supports the following image formats: BMP, DNG, GIF, JPG, PAM,
> PGM (binary P5 files are read/write, ascii P2 files are read-only),
> PGMYUV, PNG, PPM, TGA, TIFF.
Sorry but
Please add this to the documentation (for example in chapter 20.9 image2)
FFmpeg supports the following image formats: BMP, DNG, GIF, JPG, PAM,
PGM (binary P5 files are read/write, ascii P2 files are read-only),
PGMYUV, PNG, PPM, TGA, TIFF.
Michael
On 2020-08-20 17:13, Phil Rhodes via ffmpeg-user wrote:
People;
This is not a new issue and I'm really rather tired of hearing it discussed.
The open source software movement is notorious for creating an absolutely
horrible user experience and one of the reasons that happens is because of
On Fri, Aug 21, 2020 at 08:27:28 +0530, KRISHNAKUMAR N K wrote:
> Thanks for your reply. I have uploaded the complete, uncut console output
> to the below google drive. I didn't observe latency with one output. I
> haven't tried a test without the yadif filter.
>
>
36 matches
Mail list logo
