[FFmpeg-user] Submitting a Feature Request

[Carl Eugen Hoyos]

Am Mi., 22. Jan. 2020 um 00:45 Uhr schrieb Chris via ffmpeg-user
<ffmpeg-user at ffmpeg.org>:
>
> -----Original Message-----
> From: Carl Eugen Hoyos <ceffmpeg at gmail.com>
> To: FFmpeg user questions <ffmpeg-user at ffmpeg.org>
> 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
> <ffmpeg-user at ffmpeg.org>:
>
> > 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