Re: [FFmpeg-user] Submitting a Feature Request
ize= 5146200kB time=00:00:31.79 bitrate=1325778.2kbiframe= 1911 fps= 29 q=15.0 size= 193792kB time=00:00:30.89 bitrate=51380.8kbitsframe= 1918 fps= 29 q=-0.0 size= 5178600kB time=00:00:31.99 bitrate=1325778.2kbiframe= 1922 fps= 29 q=15.0 size= 195072kB time=00:00:31.08 bitrate=51414.7kbitsframe= 1929 fps= 29 q=-0.0 size= 5208300kB time=00:00:32.18 bitrate=1325778.2kbiframe= 1935 fps= 29 q=15.0 size= 196864kB time=00:00:31.29 bitrate=51527.5kbitsframe= 1939 fps= 29 q=-0.0 size= 5235300kB time=00:00:32.34 bitrate=1325778.2kbiframe= 1943 fps= 29 q=15.0 size= 197888kB time=00:00:31.43 bitrate=51575.6kbitsframe= 1949 fps= 29 q=-0.0 size= 5262300kB time=00:00:32.51 bitrate=1325778.2kbiframe= 1955 fps= 29 q=15.0 size= 199424kB time=00:00:31.63 bitrate=51647.0kbitsframe= 1962 fps= 29 q=-0.0 size= 5297400kB time=00:00:32.73 bitrate=1325778.2kbiframe= 1969 fps= 29 q=15.0 size= 200960kB time=00:00:31.86 bitrate=51663.3kbitsframe= 1977 fps= 29 q=-0.0 size= 5337900kB time=00:00:32.98 bitrate=1325778.2kbiframe= 1985 fps= 29 q=15.0 size= 202752kB time=00:00:32.13 bitrate=51690.9kbitsframe= 1991 fps= 29 q=-0.0 size= 5375700kB time=00:00:33.21 bitrate=1325778.2kbiframe= 1999 fps= 29 q=15.0 size= 204544kB time=00:00:32.36 bitrate=51771.5kbitsframe= 2007 fps= 29 q=-0.0 size= 5418900kB time=00:00:33.48 bitrate=1325778.2kbiframe= 2010 fps= 29 q=-0.0 Lsize= 5427000kB time=00:00:33.53 bitrate=1325778.2kbits/s speed=0.479x video:5427000kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.00% frame= 2010 fps= 28 q=-1.0 Lsize= 210985kB time=00:00:33.48 bitrate=51619.0kbits/s speed=0.471x video:210958kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.012666% [libx264 @ 0x5624de940a00] frame I:9 Avg QP: 5.06 size:391071 [libx264 @ 0x5624de940a00] frame P:515 Avg QP: 8.17 size:212607 [libx264 @ 0x5624de940a00] frame B:1486 Avg QP:11.46 size: 69319 [libx264 @ 0x5624de940a00] consecutive B-frames: 1.0% 0.9% 1.2% 96.9% [libx264 @ 0x5624de940a00] mb I I16..4: 17.8% 35.1% 47.1% [libx264 @ 0x5624de940a00] mb P I16..4: 6.8% 23.3% 4.7% P16..4: 22.2% 22.6% 20.0% 0.0% 0.0% skip: 0.4% [libx264 @ 0x5624de940a00] mb B I16..4: 1.3% 7.5% 0.6% B16..8: 27.7% 17.0% 10.5% direct:15.8% skip:19.7% L0:57.1% L1:19.7% BI:23.2% [libx264 @ 0x5624de940a00] final ratefactor: 6.05 [libx264 @ 0x5624de940a00] 8x8 transform intra:71.5% inter:31.4% [libx264 @ 0x5624de940a00] coded y,uvDC,uvAC intra: 99.3% 99.4% 99.1% inter: 66.0% 53.2% 41.1% [libx264 @ 0x5624de940a00] i16 v,h,dc,p: 2% 4% 19% 75% [libx264 @ 0x5624de940a00] i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 8% 17% 50% 4% 3% 2% 4% 3% 8% [libx264 @ 0x5624de940a00] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 13% 17% 31% 7% 7% 5% 7% 5% 8% [libx264 @ 0x5624de940a00] i8c dc,h,v,p: 69% 15% 9% 7% [libx264 @ 0x5624de940a00] Weighted P-Frames: Y:6.8% UV:1.7% [libx264 @ 0x5624de940a00] ref P L0: 53.6% 8.4% 27.6% 10.3% 0.1% [libx264 @ 0x5624de940a00] ref B L0: 91.3% 7.3% 1.4% [libx264 @ 0x5624de940a00] ref B L1: 93.9% 6.1% [libx264 @ 0x5624de940a00] kb/s:51535.40 chris@Linux-Mint:~/Videos/Legalizer$ -Original Message-From: Carl Eugen Hoyos To: FFmpeg user questions Sent: Thu, Jan 23, 2020 5:12 am Subject: Re: [FFmpeg-user] Submitting a Feature Request Am Do., 23. Jan. 2020 um 11:27 Uhr schrieb Chris via ffmpeg-user : > > > Did you test yesterdays command line with "-f mov"? I would expect > > that to keep the levels you need. > >Your first test would be to replace "-f mp4" in the command line you showed us with "-f mov". Carl Eugen ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Submitting a Feature Request
> Did you test yesterdays command line with "-f mov"? I would expect that to keep the levels you need. > In case I forgot so far: Only current FFmpeg git head is supported on this mailing list. > Carl Eugen Which video codec do I want to use with "-f mov"? ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Submitting a Feature Request
-Original Message-
From: Chris via ffmpeg-user
To: ffmpeg-user
Cc: Chris
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 --e
Re: [FFmpeg-user] Submitting a Feature Request
> 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 ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Submitting a Feature Request
-Original Message- From: Carl Eugen Hoyos To: FFmpeg user questions 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 : > 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 ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Submitting a Feature Request
-Original Message- From: Carl Eugen Hoyos To: FFmpeg user questions 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 : > 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 ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Submitting a Feature Request
-Original Message-
From: Carl Eugen Hoyos
To: FFmpeg user questions
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
:
> 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
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Submitting a Feature Request
-Original Message-
From: Carl Eugen Hoyos
To: FFmpeg user questions
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
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Submitting a Feature Request
-Original Message- From: Carl Eugen Hoyos To: FFmpeg user questions 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 : > 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 ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Submitting a Feature Request
-Original Message- From: Carl Eugen Hoyos To: FFmpeg user questions 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 : > 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 ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org 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 ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Submitting a Feature Request
-Original Message- From: Carl Eugen Hoyos To: FFmpeg user questions 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 : > > 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 ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org 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 ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Submitting a Feature Request
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 To: FFmpeg user questions 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 : > > 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 ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
[FFmpeg-user] Submitting a Feature Request
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 ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] ffmpeg Changing Video Levels
> It's not exactly complicated to remove a few "av_clip()" from the > v210 encoder. Where do I look? Which file? ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] ffmpeg Changing Video Levels
Ideally I would like to have both: out_range=unity and out_range=r103. This would be the most flexible. ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] ffmpeg Changing Video Levels
> Thanks for the direct answer. That makes ffmpeg useless for my purposes. > Could you elaborate? 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 this impossible when it overrides the video levels my program sets. Alternatively you could have out_range=r103. The risk here is that EBU could change the values at some point in the future. https://tech.ebu.ch/docs/r/r103.pdf I am reluctant to delve into the source code - it's very complicated! ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] ffmpeg Changing Video Levels
"FFmpeg's v210 encoder surprisingly limits the video levels, if you want to change this, you have to edit the FFmpeg source code." Thanks for the direct answer. That makes ffmpeg useless for my purposes. It would be nice if ffmpeg had an option to defeat this behavior. i.e. "unity gain". ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
[FFmpeg-user] ffmpeg Changing Video Levels
Is there a way for ffmpeg to encode video without altering the video levels? I know about full- (0 - 255) and limited- (16 - 235) range video. I am working on a C program to modify video levels, using ffmpeg to read video frames into my program and to write them out. No matter what I do, ffmpeg modifies the output video levels to either 16 - 235 or 0 - 255 and this defeats what I'm trying to do. Is there any way to defeat this behavior in ffmpeg? Ideally I would like to have an encoded video file with levels in a range other than 16 -235 or 0 - 255. Thank you. ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
[FFmpeg-user] Copying Audio
I have a file with audio in the format pcm_s16be. When I try to copy this audio to another file using -c:a copy, it copies the audio but also transcodes it to AAC. If it's literally a copy, shouldn't the copy be pcm_s16be as well? How can I do this and wind up with a pcm copy of the original audio? I've tried -c:a pcm_s16be and it fails. The complete command is: "ffmpeg.exe","-y -i short.mp4 -i short.mp4 -c:a pcm_s16be married.mp4" I am overwriting the audio on short.mp4 and it works well except for the transcoding to AAC. ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
