Submitting a Feature Request

classic Classic list List threaded Threaded
26 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Submitting a Feature Request

FFmpeg-users mailing list
What is the best way to submit a feature request for ffmpeg that will not get blown off or tossed aside?
I have looked at the developer mailing list and it appears to be full of patches — no feature requests.
There is also the bug tracker but this is not really a bug, just a feature request.
I want to have unity video levels as described in a previous post, without the levels being forced to 0 - 255 or 16 - 235.
I would code it myself but it would be a very inefficient use of time while I unravel the inner workings of the libraries, the source code, the coding conventions, the compilation environment, etc. from the bottom of the learning curve.
Thank you.
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: Submitting a Feature Request

Carl Eugen Hoyos-2
Am So., 19. Jan. 2020 um 18:55 Uhr schrieb Chris via ffmpeg-user
<[hidden email]>:
>
> What is the best way to submit a feature request for ffmpeg that will not get blown off or tossed aside?
> I have looked at the developer mailing list and it appears to be full of patches — no feature requests.

Please do not post feature requests on the development mailing list.

You may open a ticket but it is better if you explain the issue here first,
this typically includes providing a command line you tested together with
the complete, uncut console output testing current FFmpeg git head.

Carl Eugen
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: Submitting a Feature Request

FFmpeg-users mailing list
I described the desired feature in a post several weeks ago. That thread has now stalled with no progress being made. Here is the desired feature again:
We already have:



out_range=full  and out_range=tv



Why not have out_range=unity which does not alter the video levels at all?



I am trying to make video levels compliant with EBU R 103 which is RGB in the range 5 - 246. I have written a C program to do this which uses ffmpeg to import and export video frames, but ffmpeg makes it impossible because it overrides the video levels my program sets, forcing levels to 0 - 255 or 16 - 235. I want ffmpeg to leave my levels alone.

-----Original Message-----
From: Carl Eugen Hoyos <[hidden email]>
To: FFmpeg user questions <[hidden email]>
Sent: Sun, Jan 19, 2020 10:02 am
Subject: Re: [FFmpeg-user] Submitting a Feature Request

Am So., 19. Jan. 2020 um 18:55 Uhr schrieb Chris via ffmpeg-user
<[hidden email]>:
>
> What is the best way to submit a feature request for ffmpeg that will not get blown off or tossed aside?
> I have looked at the developer mailing list and it appears to be full of patches — no feature requests.

Please do not post feature requests on the development mailing list.

You may open a ticket but it is better if you explain the issue here first,
this typically includes providing a command line you tested together with
the complete, uncut console output testing current FFmpeg git head.

Carl Eugen
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: Submitting a Feature Request

Carl Eugen Hoyos-2
In reply to this post by Carl Eugen Hoyos-2
Am So., 19. Jan. 2020 um 19:02 Uhr schrieb Carl Eugen Hoyos
<[hidden email]>:

>
> Am So., 19. Jan. 2020 um 18:55 Uhr schrieb Chris via ffmpeg-user
> <[hidden email]>:
> >
> > What is the best way to submit a feature request for ffmpeg that will not get blown off or tossed aside?
> > I have looked at the developer mailing list and it appears to be full of patches — no feature requests.
>
> Please do not post feature requests on the development mailing list.
>
> You may open a ticket but it is better if you explain the issue here first,
> this typically includes providing a command line you tested together with
> the complete, uncut console output testing current FFmpeg git head.

If this is about v210 encoding, please explain your use-case.

Carl Eugen
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: Submitting a Feature Request

Carl Eugen Hoyos-2
In reply to this post by FFmpeg-users mailing list
Am So., 19. Jan. 2020 um 19:30 Uhr schrieb Chris via ffmpeg-user
<[hidden email]>:
>
> I described the desired feature in a post several weeks ago.

Please find out what top-posting means, avoid it here if you want support.

Is the issue you see reproducible with ffmpeg (the command line
interface), or only when using the libraries?

Are you seeing an issue with libswscale (this is what using out_range
indicate) or with the v210 encoder (this is what I remember)?

Carl Eugen
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: Submitting a Feature Request

FFmpeg-users mailing list



-----Original Message-----
From: Carl Eugen Hoyos <[hidden email]>
To: FFmpeg user questions <[hidden email]>
Sent: Sun, Jan 19, 2020 10:43 am
Subject: Re: [FFmpeg-user] Submitting a Feature Request

Am So., 19. Jan. 2020 um 19:30 Uhr schrieb Chris via ffmpeg-user
<[hidden email]>:
>
> I described the desired feature in a post several weeks ago.

Please find out what top-posting means, avoid it here if you want support.

Is the issue you see reproducible with ffmpeg (the command line
interface), or only when using the libraries?

Are you seeing an issue with libswscale (this is what using out_range
indicate) or with the v210 encoder (this is what I remember)?

Carl Eugen
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
ffmpeg with the command-line interface forces video levels to either 0 - 255 or 16 - 235, with no way of defeating this behavior. To the best of my knowledge it is not an issue with libswscale, but I could be wrong. I am requesting a feature to avoid ffmpeg's manipulation of video levels, i.e. out_range=unity.
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: Submitting a Feature Request

Carl Eugen Hoyos-2
Am So., 19. Jan. 2020 um 20:25 Uhr schrieb Chris via ffmpeg-user
<[hidden email]>:

> ffmpeg with the command-line interface forces video levels to either 0 - 255 or 16 - 235

Ok.
Could you 1) repeat the usecase for other levels and 2) post the command line
that produces a file for this use-case but with wrong video levels.

Carl Eugen
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: Submitting a Feature Request

FFmpeg-users mailing list



-----Original Message-----
From: Carl Eugen Hoyos <[hidden email]>
To: FFmpeg user questions <[hidden email]>
Sent: Sun, Jan 19, 2020 11:34 am
Subject: Re: [FFmpeg-user] Submitting a Feature Request

Am So., 19. Jan. 2020 um 20:25 Uhr schrieb Chris via ffmpeg-user
<[hidden email]>:

> ffmpeg with the command-line interface forces video levels to either 0 - 255 or 16 - 235

> Ok.
> Could you 1) repeat the usecase for other levels and 2) post the command line
> that produces a file for this use-case but with wrong video levels.

> Carl Eugen
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".


If I understand your question correctly, I am adjusting video levels by means of an external C program and writing the video frames to a file using ffmpeg for compliance with EBU R 103. This almost works but for the fact that ffmpeg is altering the video levels I have set. Is that much clear?
I am not reporting a "bug" or an "issue", but am requesting something that does not yet exist in ffmpeg.
out_range=full gives video levels in the range 0 - 255. That is the normal, expected behavior of the program and is not the issue here, hence it is not a "bug".

out_range=tv gives video levels in the range 16 - 235. That is likewise normal and expected behavior and not the issue.

I am requesting a new feature, out_range=unity, which would not alter the video levels, i.e. would not force them to 0 - 255 or 16 - 235 but instead would leave the values in the frame buffer alone.

There is no instance of ffmpeg producing the "wrong" video levels so I don't know what you would learn from the command line or the program output.

Does that make it clear?

_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: Submitting a Feature Request

Carl Eugen Hoyos-2
Am So., 19. Jan. 2020 um 21:00 Uhr schrieb Chris via ffmpeg-user
<[hidden email]>:

> > > ffmpeg with the command-line interface forces video levels to either 0 - 255 or 16 - 235
> >
> > Ok.
> > Could you 1) repeat the usecase for other levels and 2) post the command line
> > that produces a file for this use-case but with wrong video levels.
>

> If I understand your question correctly, I am adjusting video levels by means of an
> external C program and writing the video frames to a file using ffmpeg for
> compliance with EBU R 103.

How do you "write" the video frames?
Please provide the command line including the complete, uncut console output.

And please fix your mailer's quoting, Carl Eugen
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: Submitting a Feature Request

FFmpeg-users mailing list
-----Original Message-----
From: Carl Eugen Hoyos <[hidden email]>
To: FFmpeg user questions <[hidden email]>
Sent: Sun, Jan 19, 2020 12:11 pm
Subject: Re: [FFmpeg-user] Submitting a Feature Request

Am So., 19. Jan. 2020 um 21:00 Uhr schrieb Chris via ffmpeg-user
<[hidden email]>:

> ffmpeg with the command-line interface forces video levels to either 0 - 255 or 16 - 235

> Ok.
> Could you 1) repeat the usecase for other levels and 2) post the command line
> that produces a file for this use-case but with wrong video levels.


> If I understand your question correctly, I am adjusting video levels by means of an
> external C program and writing the video frames to a file using ffmpeg for
> compliance with EBU R 103.

> How do you "write" the video frames?
> Please provide the command line including the complete, uncut console output.

> And please fix your mailer's quoting, Carl Eugen
The program is functioning correctly when I write the frames, so I don't know what you're expecting to see if I post the command line and console output. Again, I'm using out_range=full and out_range=tv without issue and the program performs exactly as expected. There is no issue with the operation of the program, no bugs, no malfunction. It works exactly as expected.
That's the best I can do with the quoting._______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: Submitting a Feature Request

FFmpeg-users mailing list
In reply to this post by FFmpeg-users mailing list
-----Original Message-----
From: Carl Eugen Hoyos <[hidden email]>
To: FFmpeg user questions <[hidden email]>
Sent: Sun, Jan 19, 2020 11:34 am
Subject: Re: [FFmpeg-user] Submitting a Feature Request


> ffmpeg with the command-line interface forces video levels to either 0 - 255 or 16 - 235

> Ok.
> Could you 1) repeat the usecase for other levels and 2) post the command line
> that produces a file for this use-case but with wrong video levels.

> Carl Eugen
Here is the code that invokes ffmpeg (ffmpeg is invoked from a C language program).

// Open an input pipe from ffmpeg and an output pipe to a second instance of ffmpeg

FILE *pipein = popen("ffmpeg -i C0015.MP4 -f image2pipe -vcodec rawvideo -pix_fmt rgb24 -s 1280x720 -", "r");
FILE *pipeout = popen("ffmpeg -y -f rawvideo -vcodec rawvideo -pix_fmt rgb24 -s 1280x720 -r 59.94 -i - -f mp4 -q:v 5 -vcodec rawvideo -pix_fmt rgb24  -an  output.avi", "w");

Again, this code works perfectly fine, exactly as expected.
I want to add a feature where ffmpeg does not force the levels to 0 - 255 or 16 - 235: out_range=unity.
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: Submitting a Feature Request

Carl Eugen Hoyos-2
Am Di., 21. Jan. 2020 um 19:33 Uhr schrieb Chris via ffmpeg-user
<[hidden email]>:

> FILE *pipein = popen("ffmpeg -i C0015.MP4 -f image2pipe -vcodec rawvideo -pix_fmt rgb24 -s 1280x720 -", "r");
> FILE *pipeout = popen("ffmpeg -y -f rawvideo -vcodec rawvideo -pix_fmt rgb24 -s 1280x720 -r 59.94 -i - -f mp4 -q:v 5 -vcodec rawvideo -pix_fmt rgb24  -an  output.avi", "w");

(Complete, uncut console output missing)
Which of those two commands (why are there two?) changes the video level?
I don't think they are supposed to change the level...

Carl Eugen
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: Submitting a Feature Request

FFmpeg-users mailing list
 
 
 
-----Original Message-----
From: Carl Eugen Hoyos <[hidden email]>
To: FFmpeg user questions <[hidden email]>
Sent: Tue, Jan 21, 2020 11:03 am
Subject: Re: [FFmpeg-user] Submitting a Feature Request

Am Di., 21. Jan. 2020 um 19:33 Uhr schrieb Chris via ffmpeg-user
<[hidden email]>:

> FILE *pipein = popen("ffmpeg -i C0015.MP4 -f image2pipe -vcodec rawvideo -pix_fmt rgb24 -s 1280x720 -", "r");
> FILE *pipeout = popen("ffmpeg -y -f rawvideo -vcodec rawvideo -pix_fmt rgb24 -s 1280x720 -r 59.94 -i - -f mp4 -q:v 5 -vcodec rawvideo -pix_fmt rgb24  -an  output.avi", "w");

(Complete, uncut console output missing)
Which of those two commands (why are there two?) changes the video level?
I don't think they are supposed to change the level...

Carl Eugen
My last message contained a comment line which explains why there are two command lines:


// Open an input pipe from ffmpeg and an output pipe to a second instance of ffmpeg


One is an input pipe for reading video frames; the other is an output pipe for writing video frames.



The output pipe is the one modifying the video levels I have written in the C program.



out_range=full causes ffmpeg to force video levels to 0 - 255.


out_range=tv causes ffmpeg to force video levels to 16 - 235.



I want an option for ffmpeg to leave the video levels alone: out_range=unity. How do I submit this feature request?
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: Submitting a Feature Request

Carl Eugen Hoyos-2
Am Di., 21. Jan. 2020 um 21:45 Uhr schrieb Chris via ffmpeg-user
<[hidden email]>:

> My last message contained a comment line which explains why there are two command lines:
>
>
> // Open an input pipe from ffmpeg and an output pipe to a second instance of ffmpeg
>
>
> One is an input pipe for reading video frames; the other is an output pipe for writing video frames.
>
>
>
> The output pipe is the one modifying the video levels I have written in the C program.
>
>
>
> out_range=full causes ffmpeg to force video levels to 0 - 255.
>
>
> out_range=tv causes ffmpeg to force video levels to 16 - 235.

But you are not specifying either of these, are you?

Since there are two commands:
Which one is changing the video level? Is the issue you see (that the levels
are changed) also reproducible if only one of the commands is used?

Please fix your quoting, Carl Eugen
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: Submitting a Feature Request

FFmpeg-users mailing list
 
 
 
-----Original Message-----
From: Carl Eugen Hoyos <[hidden email]>
To: FFmpeg user questions <[hidden email]>
Sent: Tue, Jan 21, 2020 1:17 pm
Subject: Re: [FFmpeg-user] Submitting a Feature Request

Am Di., 21. Jan. 2020 um 21:45 Uhr schrieb Chris via ffmpeg-user
<[hidden email]>:

> My last message contained a comment line which explains why there are two command lines:


> // Open an input pipe from ffmpeg and an output pipe to a second instance of ffmpeg


> One is an input pipe for reading video frames; the other is an output pipe for writing video frames.



> The output pipe is the one modifying the video levels I have written in the C program.



> out_range=full causes ffmpeg to force video levels to 0 - 255.


> out_range=tv causes ffmpeg to force video levels to 16 - 235.


> But you are not specifying either of these, are you?


No I am not, as you can see from the lines I copied.
> Since there are two commands:
> Which one is changing the video level? Is the issue you see (that the levels
> are changed) also reproducible if only one of the commands is used?

The second command is changing the video levels as I explained in my previous post, viz.:

> The output pipe is the one modifying the video levels I have written in the C program.
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: Submitting a Feature Request

Carl Eugen Hoyos-2
Am Di., 21. Jan. 2020 um 22:56 Uhr schrieb Chris via ffmpeg-user
<[hidden email]>:

> The second command is changing the video levels as I explained in my previous post

This is the second command:
ffmpeg -y -f rawvideo -vcodec rawvideo -pix_fmt rgb24 -s 1280x720 -r
59.94 -i - -f mp4 -q:v 5 -vcodec rawvideo -pix_fmt rgb24  -an
output.avi

This command forces mp4 for a file called "avi" which is unusual and
uses the rawvideo codec which is not supported in mp4: Are you sure
that this command produces a readable output file?

(The bug in FFmpeg - that it produced invalid output files for above
command line - was fixed some time ago.)

Carl Eugen
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: Submitting a Feature Request

FFmpeg-users mailing list
-----Original Message-----
From: Carl Eugen Hoyos <[hidden email]>
To: FFmpeg user questions <[hidden email]>
Sent: Tue, Jan 21, 2020 2:04 pm
Subject: Re: [FFmpeg-user] Submitting a Feature Request

Am Di., 21. Jan. 2020 um 22:56 Uhr schrieb Chris via ffmpeg-user
<[hidden email]>:

> The second command is changing the video levels as I explained in my previous post

This is the second command:
ffmpeg -y -f rawvideo -vcodec rawvideo -pix_fmt rgb24 -s 1280x720 -r
59.94 -i - -f mp4 -q:v 5 -vcodec rawvideo -pix_fmt rgb24  -an
output.avi

This command forces mp4 for a file called "avi" which is unusual and
uses the rawvideo codec which is not supported in mp4: Are you sure
that this command produces a readable output file?

(The bug in FFmpeg - that it produced invalid output files for above
command line - was fixed some time ago.)

Carl Eugen
> Are you sure that this command produces a readable output file?

Yes I am, and ffmpeg is altering the video levels in the process.
How to submit a feature request or stop ffmpeg from forcing video levels to 0 - 255 or 16 - 235?
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: Submitting a Feature Request

Carl Eugen Hoyos-2
Am Mi., 22. Jan. 2020 um 00:45 Uhr schrieb Chris via ffmpeg-user
<[hidden email]>:

>
> -----Original Message-----
> From: Carl Eugen Hoyos <[hidden email]>
> To: FFmpeg user questions <[hidden email]>
> Sent: Tue, Jan 21, 2020 2:04 pm
> Subject: Re: [FFmpeg-user] Submitting a Feature Request
>
> Am Di., 21. Jan. 2020 um 22:56 Uhr schrieb Chris via ffmpeg-user
> <[hidden email]>:
>
> > The second command is changing the video levels as I explained in my previous post
>
> This is the second command:
> ffmpeg -y -f rawvideo -vcodec rawvideo -pix_fmt rgb24 -s 1280x720 -r
> 59.94 -i - -f mp4 -q:v 5 -vcodec rawvideo -pix_fmt rgb24  -an
> output.avi
>
> This command forces mp4 for a file called "avi" which is unusual and
> uses the rawvideo codec which is not supported in mp4: Are you sure
> that this command produces a readable output file?
>
> (The bug in FFmpeg - that it produced invalid output files for above
> command line - was fixed some time ago.)
>
> > Are you sure that this command produces a readable output file?
>
> Yes I am, and ffmpeg is altering the video levels in the process.

(Please look how broken your mailer's quoting is)

Then please show the complete, uncut console output, as said
your command line does not work here as it shouldn't since
there is no rawvideo codec defined for mp4.
(Note that if you find a developer who understands your request and he
implements it, current FFmpeg will not work for you and will not be
happy - but possibly poorer.)

> How to submit a feature request or stop ffmpeg from forcing video levels to 0 - 255 or 16 - 235?

You can of course submit whatever feature requests you like, a decade of
experience tells me that issues that I cannot reproduce tend to get
ignored though...

Carl Eugen
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: Submitting a Feature Request

FFmpeg-users mailing list
> Then please show the complete, uncut console output, as said
your command line does not work here as it shouldn't since
there is no rawvideo codec defined for mp4.
(Note that if you find a developer who understands your request and he
implements it, current FFmpeg will not work for you and will not be
happy - but possibly poorer.)

> How to submit a feature request or stop ffmpeg from forcing video levels to 0 - 255 or 16 - 235?

> You can of course submit whatever feature requests you like, a decade of
experience tells me that issues that I cannot reproduce tend to get
ignored though...

> Carl Eugen

I will modify my command line to one that works for you.
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: Submitting a Feature Request

FFmpeg-users mailing list
-----Original Message-----
From: Chris via ffmpeg-user <[hidden email]>
To: ffmpeg-user <[hidden email]>
Cc: Chris <[hidden email]>
Sent: Tue, Jan 21, 2020 4:15 pm
Subject: Re: [FFmpeg-user] Submitting a Feature Request

> Then please show the complete, uncut console output, as said your command line does not work here

> Carl Eugen

See if this command line works any better. It makes a playable video for me.

FILE *pipeout = popen("ffmpeg -y -f rawvideo -vcodec rawvideo -pix_fmt rgb24 -s 1280x720 -r 59.94 -i -       -vcodec mpeg2video -pix_fmt yuv420p  -vb 50M  -minrate 50M  -maxrate 50M  -c:a pcm_s16be  -f vob  output.mpg", "w");

Omitting the C language:

ffmpeg -y -f rawvideo -vcodec rawvideo -pix_fmt rgb24 -s 1280x720 -r 59.94 -i -       -vcodec mpeg2video -pix_fmt yuv420p  -vb 50M  -minrate 50M  -maxrate 50M  -c:a pcm_s16be  -f vob  output.mpg

No matter what I do to the video levels in my C program, ffmpeg forces the range to 0 - 255. I do not want the levels forced to 0 -255 or 16 - 235. I want ffmpeg to leave the video levels alone.

Here is the complete console output:

ffmpeg version 3.4.6-0ubuntu0.18.04.1 Copyright (c) 2000-2019 the FFmpeg developers
  built with gcc 7 (Ubuntu 7.3.0-16ubuntu3)
  configuration: --prefix=/usr --extra-version=0ubuntu0.18.04.1 --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --enable-gpl --disable-stripping --enable-avresample --enable-avisynth --enable-gnutls --enable-ladspa --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librubberband --enable-librsvg --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzmq --enable-libzvbi --enable-omx --enable-openal --enable-opengl --enable-sdl2 --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libopencv --enable-libx264 --enable-shared
ffmpeg version 3.4.6-0ubuntu0.18.04.1 Copyright (c) 2000-2019 the FFmpeg developers  WARNING: library configuration mismatch

  built with gcc 7 (Ubuntu 7.3.0-16ubuntu3)
  avcodec     configuration: --prefix=/usr --extra-version=0ubuntu0.18.04.1 --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --enable-gpl --disable-stripping --enable-avresample --enable-avisynth --enable-gnutls --enable-ladspa --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librubberband --enable-librsvg --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzmq --enable-libzvbi --enable-omx --enable-openal --enable-opengl --enable-sdl2 --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libopencv --enable-libx264 --enable-shared --enable-version3 --disable-doc --disable-programs --enable-libopencore_amrnb --enable-libopencore_amrwb --enable-libtesseract --enable-libvo_amrwbenc
  configuration: --prefix=/usr --extra-version=0ubuntu0.18.04.1 --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --enable-gpl --disable-stripping --enable-avresample --enable-avisynth --enable-gnutls --enable-ladspa --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librubberband --enable-librsvg --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzmq --enable-libzvbi --enable-omx --enable-openal --enable-opengl --enable-sdl2 --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libopencv --enable-libx264 --enable-shared
  WARNING: library configuration mismatch
  avcodec     configuration: --prefix=/usr --extra-version=0ubuntu0.18.04.1 --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --enable-gpl --disable-stripping --enable-avresample --enable-avisynth --enable-gnutls --enable-ladspa --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librubberband --enable-librsvg --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzmq --enable-libzvbi --enable-omx --enable-openal --enable-opengl --enable-sdl2 --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libopencv --enable-libx264 --enable-shared --enable-version3 --disable-doc --disable-programs --enable-libopencore_amrnb --enable-libopencore_amrwb --enable-libtesseract --enable-libvo_amrwbenc
  libavutil      55. 78.100 / 55. 78.100
  libavcodec     57.107.100 / 57.107.100
  libavformat    57. 83.100 / 57. 83.100
  libavdevice    57. 10.100 / 57. 10.100
  libavfilter     6.107.100 /  6.107.100
  libavresample   3.  7.  0 /  3.  7.  0
  libswscale      4.  8.100 /  4.  8.100
  libswresample   2.  9.100 /  2.  9.100
  libpostproc    54.  7.100 / 54.  7.100
  libavutil      55. 78.100 / 55. 78.100
  libavcodec     57.107.100 / 57.107.100
  libavformat    57. 83.100 / 57. 83.100
  libavdevice    57. 10.100 / 57. 10.100
  libavfilter     6.107.100 /  6.107.100
  libavresample   3.  7.  0 /  3.  7.  0
  libswscale      4.  8.100 /  4.  8.100
  libswresample   2.  9.100 /  2.  9.100
  libpostproc    54.  7.100 / 54.  7.100
Guessed Channel Layout for Input Stream #0.1 : stereo
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'C0015.MP4':
  Metadata:
    major_brand     : XAVC
    minor_version   : 16785407
    compatible_brands: XAVCmp42iso2
    creation_time   : 2019-10-24T18:04:42.000000Z
  Duration: 00:00:33.53, start: 0.000000, bitrate: 52004 kb/s
    Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709/bt709/iec61966-2-4), 1920x1080 [SAR 1:1 DAR 16:9], 49974 kb/s, 59.94 fps, 59.94 tbr, 60k tbn, 119.88 tbc (default)
    Metadata:
      creation_time   : 2019-10-24T18:04:42.000000Z
      handler_name    : Video Media Handler
      encoder         : AVC Coding
    Stream #0:1(und): Audio: pcm_s16be (twos / 0x736F7774), 48000 Hz, stereo, s16, 1536 kb/s (default)
    Metadata:
      creation_time   : 2019-10-24T18:04:42.000000Z
      handler_name    : Sound Media Handler
    Stream #0:2(und): Data: none (rtmd / 0x646D7472), 491 kb/s (default)
    Metadata:
      creation_time   : 2019-10-24T18:04:42.000000Z
      handler_name    : Timed Metadata Media Handler
      timecode        : 00:00:00:00
Stream mapping:
  Stream #0:0 -> #0:0 (h264 (native) -> rawvideo (native))
Press [q] to stop, [?] for help
Output #0, image2pipe, to 'pipe:':
  Metadata:
    major_brand     : XAVC
    minor_version   : 16785407
    compatible_brands: XAVCmp42iso2
    encoder         : Lavf57.83.100
    Stream #0:0(und): Video: rawvideo (RGB[24] / 0x18424752), rgb24, 1280x720 [SAR 1:1 DAR 16:9], q=2-31, 1325778 kb/s, 59.94 fps, 59.94 tbn, 59.94 tbc (default)
    Metadata:
      creation_time   : 2019-10-24T18:04:42.000000Z
      handler_name    : Video Media Handler
      encoder         : Lavc57.107.100 rawvideo
Input #0, rawvideo, from 'pipe:':
  Duration: N/A, start: 0.000000, bitrate: 1325776 kb/s
    Stream #0:0: Video: rawvideo (RGB[24] / 0x18424752), rgb24, 1280x720, 1325776 kb/s, 59.94 tbr, 59.94 tbn, 59.94 tbc
Stream mapping:
  Stream #0:0 -> #0:0 (rawvideo (native) -> mpeg2video (native))
[mpeg2video @ 0x56393932ea20] Automatically choosing VBV buffer size of 746 kbyte
Output #0, vob, to 'output.mpg':
  Metadata:
    encoder         : Lavf57.83.100
    Stream #0:0: Video: mpeg2video (Main), yuv420p, 1280x720, q=2-31, 50000 kb/s, 59.94 fps, 90k tbn, 59.94 tbc
    Metadata:
      encoder         : Lavc57.107.100 mpeg2video
    Side data:
      cpb: bitrate max/min/avg: 50000000/50000000/50000000 buffer size: 6111232 vbv_delay: -1
frame=   30 fps=0.0 q=-0.0 size=   81000kB time=00:00:00.50 bitrate=1325778.2kbiframe=   35 fps=0.0 q=2.0 size=    3314kB time=00:00:00.53 bitrate=50851.1kbits/frame=   67 fps= 66 q=-0.0 size=  180900kB time=00:00:01.11 bitrate=1325778.6kbiframe=   71 fps= 71 q=2.0 size=    7024kB time=00:00:01.13 bitrate=50719.9kbits/frame=  103 fps= 68 q=-0.0 size=  278100kB time=00:00:01.71 bitrate=1325778.5kbiframe=  108 fps= 72 q=2.0 size=   10838kB time=00:00:01.75 bitrate=50683.1kbits/frame=  141 fps= 70 q=-0.0 size=  380700kB time=00:00:02.35 bitrate=1325778.2kbiframe=  146 fps= 72 q=1.6 size=   14802kB time=00:00:02.38 bitrate=50826.3kbits/frame=  179 fps= 71 q=-0.0 size=  483300kB time=00:00:02.98 bitrate=1325778.1kbiframe=  185 fps= 73 q=2.0 size=   18774kB time=00:00:03.03 bitrate=50651.3kbits/frame=  216 fps= 71 q=-0.0 size=  583200kB time=00:00:03.60 bitrate=1325778.2kbiframe=  223 fps= 73 q=2.0 size=   22690kB time=00:00:03.67 bitrate=50642.8kbits/frame=  254 fps= 72 q=-0.0 size=  685800kB time=00:00:04.23 bitrate=1325778.1kbiframe=  260 fps= 73 q=2.0 size=   26504kB time=00:00:04.28 bitrate=50638.8kbits/frame=  290 fps= 71 q=-0.0 size=  783000kB time=00:00:04.83 bitrate=1325778.1kbiframe=  295 fps= 73 q=2.0 size=   30110kB time=00:00:04.87 bitrate=50633.0kbits/frame=  327 fps= 71 q=-0.0 size=  882900kB time=00:00:05.45 bitrate=1325778.2kbiframe=  332 fps= 73 q=2.0 size=   33924kB time=00:00:05.48 bitrate=50631.1kbits/frame=  364 fps= 72 q=-0.0 size=  982800kB time=00:00:06.07 bitrate=1325778.3kbiframe=  370 fps= 73 q=2.0 size=   37840kB time=00:00:06.12 bitrate=50628.0kbits/frame=  400 fps= 72 q=-0.0 size= 1080000kB time=00:00:06.67 bitrate=1325778.3kbiframe=  406 fps= 73 q=2.0 size=   41550kB time=00:00:06.72 bitrate=50625.8kbits/frame=  437 fps= 72 q=-0.0 size= 1179900kB time=00:00:07.29 bitrate=1325778.2kbiframe=  442 fps= 73 q=2.0 size=   45262kB time=00:00:07.32 bitrate=50626.2kbits/frame=  472 fps= 72 q=-0.0 size= 1274400kB time=00:00:07.87 bitrate=1325778.3kbiframe=  478 fps= 72 q=2.0 size=   48972kB time=00:00:07.92 bitrate=50624.5kbits/frame=  507 fps= 71 q=-0.0 size= 1368900kB time=00:00:08.45 bitrate=1325778.2kbiframe=  513 fps= 72 q=2.0 size=   52578kB time=00:00:08.50 bitrate=50622.1kbits/frame=  543 fps= 71 q=-0.0 size= 1466100kB time=00:00:09.05 bitrate=1325778.2kbiframe=  550 fps= 72 q=2.0 size=   56392kB time=00:00:09.12 bitrate=50621.7kbits/frame=  578 fps= 71 q=-0.0 size= 1560600kB time=00:00:09.64 bitrate=1325778.2kbiframe=  584 fps= 72 q=2.0 size=   59896kB time=00:00:09.69 bitrate=50620.7kbits/frame=  612 fps= 71 q=-0.0 size= 1652400kB time=00:00:10.21 bitrate=1325778.2kbiframe=  619 fps= 72 q=2.0 size=   63504kB time=00:00:10.27 bitrate=50620.6kbits/frame=  648 fps= 71 q=-0.0 size= 1749600kB time=00:00:10.81 bitrate=1325778.2kbiframe=  655 fps= 72 q=2.0 size=   67214kB time=00:00:10.87 bitrate=50619.6kbits/frame=  685 fps= 71 q=-0.0 size= 1849500kB time=00:00:11.42 bitrate=1325778.3kbiframe=  692 fps= 72 q=2.0 size=   71026kB time=00:00:11.49 bitrate=50618.0kbits/frame=  720 fps= 71 q=-0.0 size= 1944000kB time=00:00:12.01 bitrate=1325778.2kbiframe=  728 fps= 72 q=2.0 size=   74738kB time=00:00:12.09 bitrate=50618.6kbits/frame=  757 fps= 71 q=-0.0 size= 2043900kB time=00:00:12.62 bitrate=1325778.3kbiframe=  764 fps= 72 q=2.0 size=   78448kB time=00:00:12.69 bitrate=50617.9kbits/frame=  793 fps= 71 q=-0.0 size= 2141100kB time=00:00:13.22 bitrate=1325778.3kbiframe=  801 fps= 72 q=2.0 size=   82260kB time=00:00:13.31 bitrate=50616.6kbits/frame=  830 fps= 71 q=-0.0 size= 2241000kB time=00:00:13.84 bitrate=1325778.2kbiframe=  838 fps= 72 q=2.0 size=   86074kB time=00:00:13.93 bitrate=50616.5kbits/frame=  866 fps= 71 q=-0.0 size= 2338200kB time=00:00:14.44 bitrate=1325778.2kbiframe=  874 fps= 72 q=2.0 size=   89784kB time=00:00:14.53 bitrate=50616.0kbits/frame=  901 fps= 71 q=-0.0 size= 2432700kB time=00:00:15.03 bitrate=1325778.3kbiframe=  909 fps= 72 q=2.0 size=   93392kB time=00:00:15.11 bitrate=50616.1kbits/frame=  939 fps= 71 q=-0.0 size= 2535300kB time=00:00:15.66 bitrate=1325778.2kbiframe=  947 fps= 72 q=2.0 size=   97308kB time=00:00:15.74 bitrate=50615.5kbits/frame=  978 fps= 71 q=-0.0 size= 2640600kB time=00:00:16.31 bitrate=1325778.2kbiframe=  985 fps= 72 q=2.0 size=  101224kB time=00:00:16.38 bitrate=50615.0kbits/frame= 1015 fps= 71 q=-0.0 size= 2740500kB time=00:00:16.93 bitrate=1325778.2kbiframe= 1023 fps= 72 q=2.0 size=  105140kB time=00:00:17.01 bitrate=50614.5kbits/frame= 1052 fps= 72 q=-0.0 size= 2840400kB time=00:00:17.55 bitrate=1325778.2kbiframe= 1060 fps= 72 q=2.0 size=  108954kB time=00:00:17.63 bitrate=50614.5kbits/frame= 1088 fps= 72 q=-0.0 size= 2937600kB time=00:00:18.15 bitrate=1325778.2kbiframe= 1097 fps= 72 q=2.0 size=  112768kB time=00:00:18.25 bitrate=50614.6kbits/frame= 1126 fps= 72 q=-0.0 size= 3040200kB time=00:00:18.78 bitrate=1325778.2kbiframe= 1135 fps= 72 q=2.0 size=  116684kB time=00:00:18.88 bitrate=50614.1kbits/frame= 1162 fps= 72 q=-0.0 size= 3137400kB time=00:00:19.38 bitrate=1325778.2kbiframe= 1171 fps= 72 q=2.0 size=  120394kB time=00:00:19.48 bitrate=50613.8kbits/frame= 1197 fps= 72 q=-0.0 size= 3231900kB time=00:00:19.96 bitrate=1325778.2kbiframe= 1206 fps= 72 q=2.0 size=  124002kB time=00:00:20.07 bitrate=50613.9kbits/frame= 1234 fps= 72 q=-0.0 size= 3331800kB time=00:00:20.58 bitrate=1325778.2kbiframe= 1243 fps= 72 q=2.0 size=  127814kB time=00:00:20.68 bitrate=50613.2kbits/frame= 1268 fps= 71 q=-0.0 size= 3423600kB time=00:00:21.15 bitrate=1325778.2kbiframe= 1278 fps= 72 q=2.0 size=  131422kB time=00:00:21.27 bitrate=50613.3kbits/frame= 1304 fps= 71 q=-0.0 size= 3520800kB time=00:00:21.75 bitrate=1325778.2kbiframe= 1314 fps= 72 q=2.0 size=  135132kB time=00:00:21.87 bitrate=50613.0kbits/frame= 1338 fps= 71 q=-0.0 size= 3612600kB time=00:00:22.32 bitrate=1325778.2kbiframe= 1349 fps= 72 q=2.0 size=  138740kB time=00:00:22.45 bitrate=50613.2kbits/frame= 1374 fps= 71 q=-0.0 size= 3709800kB time=00:00:22.92 bitrate=1325778.2kbiframe= 1385 fps= 72 q=2.0 size=  142450kB time=00:00:23.05 bitrate=50612.9kbits/frame= 1407 fps= 71 q=-0.0 size= 3798900kB time=00:00:23.47 bitrate=1325778.2kbiframe= 1419 fps= 71 q=2.0 size=  145954kB time=00:00:23.62 bitrate=50612.7kbits/frame= 1442 fps= 71 q=-0.0 size= 3893400kB time=00:00:24.05 bitrate=1325778.2kbiframe= 1454 fps= 71 q=1.6 size=  149580kB time=00:00:24.20 bitrate=50618.9kbits/frame= 1478 fps= 71 q=-0.0 size= 3990600kB time=00:00:24.65 bitrate=1325778.2kbiframe= 1489 fps= 71 q=2.0 size=  153168kB time=00:00:24.79 bitrate=50612.3kbits/frame= 1513 fps= 71 q=-0.0 size= 4085100kB time=00:00:25.24 bitrate=1325778.2kbiframe= 1523 fps= 71 q=2.0 size=  156672kB time=00:00:25.35 bitrate=50612.1kbits/frame= 1547 fps= 71 q=-0.0 size= 4176900kB time=00:00:25.80 bitrate=1325778.2kbiframe= 1560 fps= 71 q=2.0 size=  160486kB time=00:00:25.97 bitrate=50612.2kbits/frame= 1584 fps= 71 q=-0.0 size= 4276800kB time=00:00:26.42 bitrate=1325778.2kbiframe= 1597 fps= 71 q=2.0 size=  164300kB time=00:00:26.59 bitrate=50612.3kbits/frame= 1617 fps= 71 q=-0.0 size= 4365900kB time=00:00:26.97 bitrate=1325778.2kbiframe= 1630 fps= 71 q=2.0 size=  167700kB time=00:00:27.14 bitrate=50611.9kbits/frame= 1652 fps= 71 q=-0.0 size= 4460400kB time=00:00:27.56 bitrate=1325778.2kbiframe= 1665 fps= 71 q=2.0 size=  171308kB time=00:00:27.72 bitrate=50612.0kbits/frame= 1686 fps= 71 q=-0.0 size= 4552200kB time=00:00:28.12 bitrate=1325778.2kbiframe= 1699 fps= 71 q=2.0 size=  174812kB time=00:00:28.29 bitrate=50611.9kbits/frame= 1719 fps= 71 q=-0.0 size= 4641300kB time=00:00:28.67 bitrate=1325778.2kbiframe= 1734 fps= 71 q=2.0 size=  178418kB time=00:00:28.87 bitrate=50611.4kbits/frame= 1757 fps= 71 q=-0.0 size= 4743900kB time=00:00:29.31 bitrate=1325778.2kbiframe= 1771 fps= 71 q=2.0 size=  182232kB time=00:00:29.49 bitrate=50611.5kbits/frame= 1794 fps= 71 q=-0.0 size= 4843800kB time=00:00:29.92 bitrate=1325778.2kbiframe= 1809 fps= 71 q=2.0 size=  186170kB time=00:00:30.13 bitrate=50617.3kbits/frame= 1830 fps= 71 q=-0.0 size= 4941000kB time=00:00:30.53 bitrate=1325778.2kbiframe= 1844 fps= 71 q=2.0 size=  189842kB time=00:00:30.71 bitrate=50634.4kbits/frame= 1866 fps= 71 q=-0.0 size= 5038200kB time=00:00:31.13 bitrate=1325778.2kbiframe= 1880 fps= 71 q=2.0 size=  193466kB time=00:00:31.31 bitrate=50611.3kbits/frame= 1903 fps= 71 q=-0.0 size= 5138100kB time=00:00:31.74 bitrate=1325778.2kbiframe= 1916 fps= 71 q=2.6 size=  197500kB time=00:00:31.91 bitrate=50694.3kbits/frame= 1940 fps= 71 q=-0.0 size= 5238000kB time=00:00:32.36 bitrate=1325778.2kbiframe= 1953 fps= 71 q=2.0 size=  201104kB time=00:00:32.53 bitrate=50639.9kbits/frame= 1975 fps= 71 q=-0.0 size= 5332500kB time=00:00:32.94 bitrate=1325778.2kbiframe= 1987 fps= 71 q=2.0 size=  204594kB time=00:00:33.09 bitrate=50635.9kbits/frame= 2010 fps= 71 q=-0.0 size= 5427000kB time=00:00:33.53 bitrate=1325778.2kbiframe= 2010 fps= 71 q=-0.0 Lsize= 5427000kB time=00:00:33.53 bitrate=1325778.2kbits/s speed=1.18x   
video:5427000kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.000000%
frame= 2010 fps= 71 q=2.0 Lsize=  207074kB time=00:00:33.50 bitrate=50637.1kbits/s speed=1.18x   
video:204588kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 1.214963%
chris@Linux-Mint:~/Videos/Legalizer$

_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
12