Re: [FFmpeg-user] Problem with -vf fillborders on 16 bit image
On 12-03-2019 01:04 AM, Ulf Zibis wrote:
Am 11.03.19 um 20:27 schrieb Paul B Mahol:
On 3/11/19, Ulf Zibis wrote:
Am 09.03.19 um 09:39 schrieb Paul B Mahol:
On 3/9/19, Ulf Zibis wrote:
Another question is, why the fillborders doesn't check if the input is
writable, as suggested in doc/writing_filters.txt.
Because it request writtable frames.
Hey Paul, how is this managed?
I don't see something like "get writable frame".
It is at bottom.
Do you mean
.flags = AVFILTER_FLAG_SUPPORT_TIMELINE_GENERIC,
No, in here:
static const AVFilterPad fillborders_inputs[] = {
{
.name = "default",
.type = AVMEDIA_TYPE_VIDEO,
.config_props = config_input,
.filter_frame = filter_frame,
.needs_writable = 1,
},
{ NULL }
};
Gyan
___
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] Changing -X264 Parameters on the fly
follow up On Mon, Mar 11, 2019 at 10:54 PM Sai Balaji wrote: > Can I change the values of x264 parameters on the fly? The only parameter > which I want to change is keyint. > > ffmpeg -f avfoundation -video_size 800x600 -framerate 30 -i 0 -vcodec > libx264 -x264-params keyint=30:scenecut=0 -acodec aac -b:v 1M -b:a 192k > -f dash -use_template 0 -use_timeline 0 -single_file 0 -streaming 1 > -seg_duration 1 sairam.mpd > > > This is the command which I am using right now. > ___ 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] Growing file processing
On Sun, Mar 10, 2019, at 3:05 AM, Bouke wrote: > > I reverted to webmail, and missed some stuff here and there. (One of my > accounts bounces a lot of mails from the FF list for some reason.) If I recall correctly it is related to the DMARC policy of your mail provider. I made a change last week that may help with that. ___ 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] Problem with -vf fillborders on 16 bit image
Am 11.03.19 um 20:43 schrieb Carl Eugen Hoyos: > Our jpeg encoder only supports 8-bit yuv Ok, that's the reason, thanks. > No need to post Mediainfo output, all necessary information > is in the FFmpeg console output. Maybe for you. ;-) For me it is not obvious. I guess you mean the info could be read from gray16le(bt470bg/unknown/unknown) ./. yuvj444p(pc) -Ulf ___ 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] Problem with -vf fillborders on 16 bit image
2019-03-11 20:31 GMT+01:00, Ulf Zibis : > > Am 11.03.19 um 20:14 schrieb Carl Eugen Hoyos: >> 2019-03-11 20:05 GMT+01:00, Ulf Zibis : >>> Am 09.03.19 um 10:58 schrieb Carl Eugen Hoyos: 2019-03-09 10:44 GMT+01:00, Ulf Zibis : > Which format should I use with option -f ? You should never need the option -f (except when reading raw g.729 and similar rare raw formats), what did you try? >>> When I use >>> $ ffmpeg -i 16.jpg -vf fillborders=25:25:25:25:mirror 16_mirror-25.jpg >>> then the output is 8-bit rgb. >> This seems unlikely as our "jpg" encoder does not support >> encoding rgb. > Oops, I partly was in error. But the output is 8-bit instead 16-bit and > yuv instead y. Our jpeg encoder only supports 8-bit yuv No need to post Mediainfo output, all necessary information is in the FFmpeg console output. 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".
Re: [FFmpeg-user] Problem with -vf fillborders on 16 bit image
Am 11.03.19 um 20:27 schrieb Paul B Mahol: > On 3/11/19, Ulf Zibis wrote: >> Am 09.03.19 um 09:39 schrieb Paul B Mahol: >>> On 3/9/19, Ulf Zibis wrote: Another question is, why the fillborders doesn't check if the input is writable, as suggested in doc/writing_filters.txt. >>> Because it request writtable frames. >> Hey Paul, how is this managed? >> I don't see something like "get writable frame". > It is at bottom. Do you mean .flags = AVFILTER_FLAG_SUPPORT_TIMELINE_GENERIC, ? -Ulf ___ 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] Problem with -vf fillborders on 16 bit image
Am 11.03.19 um 20:14 schrieb Carl Eugen Hoyos: > 2019-03-11 20:05 GMT+01:00, Ulf Zibis : >> Am 09.03.19 um 10:58 schrieb Carl Eugen Hoyos: >>> 2019-03-09 10:44 GMT+01:00, Ulf Zibis : Which format should I use with option -f ? >>> You should never need the option -f (except when reading >>> raw g.729 and similar rare raw formats), what did you try? >> When I use >> $ ffmpeg -i 16.jpg -vf fillborders=25:25:25:25:mirror 16_mirror-25.jpg >> then the output is 8-bit rgb. > This seems unlikely as our "jpg" encoder does not support > encoding rgb. Oops, I partly was in error. But the output is 8-bit instead 16-bit and yuv instead y. What I have to do, if I want the same format for the output, as it is for the input? $ ./ffmpeg -i debug/16.jpg -vf fillborders=25:25:25:25:mirror debug/16_mirror-25.jpg ffmpeg version N-93301-gf95aee2b72 Copyright (c) 2000-2019 the FFmpeg developers built with gcc 7 (Ubuntu 7.3.0-27ubuntu1~18.04) configuration: libavutil 56. 26.100 / 56. 26.100 libavcodec 58. 47.103 / 58. 47.103 libavformat 58. 26.101 / 58. 26.101 libavdevice 58. 6.101 / 58. 6.101 libavfilter 7. 48.100 / 7. 48.100 libswscale 5. 4.100 / 5. 4.100 libswresample 3. 4.100 / 3. 4.100 Input #0, image2, from 'debug/16.jpg': Duration: 00:00:00.04, start: 0.00, bitrate: 103852 kb/s Stream #0:0: Video: mjpeg (Lossless), gray16le(bt470bg/unknown/unknown), 640x480 [SAR 96:96 DAR 4:3], lossless, 25 tbr, 25 tbn, 25 tbc File 'debug/16_mirror-25.jpg' already exists. Overwrite ? [y/N] y Stream mapping: Stream #0:0 -> #0:0 (mjpeg (native) -> mjpeg (native)) Press [q] to stop, [?] for help [swscaler @ 0x555de22ba600] deprecated pixel format used, make sure you did set range correctly Output #0, image2, to 'debug/16_mirror-25.jpg': Metadata: encoder : Lavf58.26.101 Stream #0:0: Video: mjpeg, yuvj444p(pc), 640x480 [SAR 1:1 DAR 4:3], q=2-31, 200 kb/s, 25 fps, 25 tbn, 25 tbc Metadata: encoder : Lavc58.47.103 mjpeg Side data: cpb: bitrate max/min/avg: 0/0/20 buffer size: 0 vbv_delay: -1 frame= 1 fps=0.0 q=6.0 Lsize=N/A time=00:00:00.04 bitrate=N/A speed=0.448x video:33kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown $ mediainfo debug/16.jpg General Complete name : debug/16.jpg Format : JPEG File size : 507 KiB Image Format : JPEG Width : 640 pixels Height : 480 pixels Color space : Y Bit depth : 16 bits Compression mode : Lossy Stream size : 507 KiB (100%) $ mediainfo debug/16_mirror-25.jpg General Complete name : debug/16_mirror-25.jpg Format : JPEG File size : 33.5 KiB Image Format : JPEG Width : 640 pixels Height : 480 pixels Color space : YUV Bit depth : 8 bits Compression mode : Lossy Stream size : 33.5 KiB (100%) -Ulf ___ 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] Problem with -vf fillborders on 16 bit image
On 3/11/19, Ulf Zibis wrote: > > Am 09.03.19 um 09:39 schrieb Paul B Mahol: >> On 3/9/19, Ulf Zibis wrote: >>> Another question is, why the fillborders doesn't check if the input is >>> writable, as suggested in doc/writing_filters.txt. >>> >> Because it request writtable frames. > > Hey Paul, how is this managed? > I don't see something like "get writable frame". It is at bottom. ___ 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] Problem with -vf fillborders on 16 bit image
Am 09.03.19 um 09:39 schrieb Paul B Mahol: > On 3/9/19, Ulf Zibis wrote: >> Another question is, why the fillborders doesn't check if the input is >> writable, as suggested in doc/writing_filters.txt. >> > Because it request writtable frames. Hey Paul, how is this managed? I don't see something like "get writable frame". -Ulf ___ 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] Problem with -vf fillborders on 16 bit image
2019-03-11 20:05 GMT+01:00, Ulf Zibis : > > Am 09.03.19 um 10:58 schrieb Carl Eugen Hoyos: >> 2019-03-09 10:44 GMT+01:00, Ulf Zibis : >>> Which format should I use with option -f ? >> You should never need the option -f (except when reading >> raw g.729 and similar rare raw formats), what did you try? > When I use > $ ffmpeg -i 16.jpg -vf fillborders=25:25:25:25:mirror 16_mirror-25.jpg > then the output is 8-bit rgb. This seems unlikely as our "jpg" encoder does not support encoding rgb. 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".
Re: [FFmpeg-user] Problem with -vf fillborders on 16 bit image
Am 09.03.19 um 10:58 schrieb Carl Eugen Hoyos: > 2019-03-09 10:44 GMT+01:00, Ulf Zibis : >> Which format should I use with option -f ? > You should never need the option -f (except when reading > raw g.729 and similar rare raw formats), what did you try? When I use $ ffmpeg -i 16.jpg -vf fillborders=25:25:25:25:mirror 16_mirror-25.jpg then the output is 8-bit rgb. >> The files from ticket #503 are only gray, > Yes. > >> and the JPEG's from ticket #855 seem corrupted > They are not corrupted as you can easily test with FFmpeg. > > (The way I understood your question you asked for 16bit > images that can be read with FFmpeg, not for 16 bit > images that can be read with other software which is > much more difficult.) Thanks again for the hints, I now can use these picts for my testing. -Ulf ___ 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] Meaning of ffprobe output
2019-03-11 19:53 GMT+01:00, Ulf Zibis : > > Am 11.03.19 um 11:58 schrieb Carl Eugen Hoyos: >>> Is native vs. x264 encoder something different? >> The native (FFmpeg-internal) encoders may be a little less >> sophisticated than x264 (and they don't know a special >> adaptive interlaced setting because it didn't exist in earlier >> formats). > Does ffmpeg still use the native encoder when omitting > the -c:v libx264 option? There is no internal h264 encoder, there are encoders for mpeg1video/mpeg2video/h263/mpeg4video etc. 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".
Re: [FFmpeg-user] Meaning of ffprobe output
Am 11.03.19 um 11:58 schrieb Carl Eugen Hoyos: > So our suspicion after visual inspection was right. Yes, indeed. >> So I buyed the DVD now. Except that it has 3 audio tracks to choose and >> the VHS head switching artefacts are missing, it unfortunately has the >> equal bad quality than my DVD recorder copy, but even has a worst colour >> quality than my copy. The purchased DVD is not a direct telecined copy >> from the 36 mm material (disappointing), it seem to be a capture of the >> in earlier times provided VHS cassette, but with a better adjusted VHS >> player, so the head switching artefacts are missing. > Thank you for the info! > Maybe you should buy a copy of the film? Hey hey, and additionally a telecine machine to have a digital copy. ;-) >> Is native vs. x264 encoder something different? > The native (FFmpeg-internal) encoders may be a little less > sophisticated than x264 (and they don't know a special > adaptive interlaced setting because it didn't exist in earlier > formats). Does ffmpeg still use the native encoder when omitting the -c:v libx264 option? I don't see any difference in the terminal output of ffmpeg or in the results with ffprobe. Or in other words, how can I determine, which encoder was used for transcoding or a given mp4? -Ulf ___ 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] Changing -X264 Parameters on the fly
Can I change the values of x264 parameters on the fly? The only parameter which I want to change is keyint. ffmpeg -f avfoundation -video_size 800x600 -framerate 30 -i 0 -vcodec libx264 -x264-params keyint=30:scenecut=0 -acodec aac -b:v 1M -b:a 192k -f dash -use_template 0 -use_timeline 0 -single_file 0 -streaming 1 -seg_duration 1 sairam.mpd This is the command which I am using right now. ___ 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] PTS and DTS sync accross multiple output streams.
Hello, I have a setup where I am transcoding live feeds from OTA broadcasts to H264 using the Nvidia NVENC encoder. I am also transcoding the audio to AAC. We are trying to output 3 cbr streams and various bitrates. The problem I am running into is that the PTS and DTS on the multiple outputs are not aligning which is critical for our use case. I am hoping there is an easy fix to this but I have not yet been able to locate one. Any thoughts on how to accomplish this? ===> Source Feed <=== ffprobe udp://@238.224.1.5:59005 ffprobe version N-93005-gd92f06e Copyright (c) 2007-2019 the FFmpeg developers built with gcc 7 (Ubuntu 7.3.0-27ubuntu1~18.04) configuration: --prefix=/home/circle/ffmpeg_build --pkg-config-flags=--static --extra-cflags=-I/home/circle/ffmpeg_build/include --extra-ldflags=-L/home/circle/ffmpeg_build/lib --extra-libs='-lpthread -lm' --bindir=/home/circle/bin --enable-gpl --enable-libaom --enable-libass --enable-libfdk-aac --enable-libfreetype --enable-libmp3lame --enable-libopus --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-nonfree --enable-nvenc libavutil 56. 26.100 / 56. 26.100 libavcodec 58. 44.100 / 58. 44.100 libavformat58. 26.100 / 58. 26.100 libavdevice58. 6.101 / 58. 6.101 libavfilter 7. 48.100 / 7. 48.100 libswscale 5. 4.100 / 5. 4.100 libswresample 3. 4.100 / 3. 4.100 libpostproc55. 4.100 / 55. 4.100 [mpeg2video @ 0x558e5a80fa40] Invalid frame dimensions 0x0. Last message repeated 22 times Input #0, mpegts, from 'udp://@238.224.1.5:59005: Duration: N/A, start: 89037.540778, bitrate: N/A Program 3 Stream #0:0[0x31]: Video: mpeg2video (Main) ([2][0][0][0] / 0x0002), yuv420p(tv, progressive), 1280x720 [SAR 1:1 DAR 16:9], Closed Captions, 59.94 fps, 59.94 tbr, 90k tbn, 119.88 tbc Stream #0:1[0x34](eng): Audio: ac3 ([129][0][0][0] / 0x0081), 48000 Hz, 5.1(side), fltp, 384 kb/s Stream #0:2[0x35](spa): Audio: ac3 ([129][0][0][0] / 0x0081), 48000 Hz, stereo, fltp, 192 kb/s ===> Command I am currently running to transcode <=== screen -d -m ffmpeg -i 'udp://@238.224.1.5:59005?fifo_size=100_nonfatal=1' \ -vcodec h264_nvenc -bf:v 2 -g 120 -rc cbr -b:v 6000K -profile:v high -level 4.0 -acodec aac -ac 2 -b:a 128k -ar 44100 -f mpegts -metadata service_name="test6000" -metadata service_provider="test" 'udp://@239.1.1.1:59001?pkt_size=1316' \ -vcodec h264_nvenc -bf:v 2 -g 120 -rc cbr -b:v 3500K -profile:v high -level 4.0 -acodec aac -ac 2 -b:a 128k -ar 44100 -f mpegts -metadata service_name="test3500" -metadata service_provider="test" 'udp://@239.1.1.2:59002?pkt_size=1316' \ -vcodec h264_nvenc -bf:v 2 -g 120 -rc cbr -b:v 1500K -profile:v high -level 4.0 -acodec aac -ac 2 -b:a 128k -ar 44100 -f mpegts -metadata service_name="test1500" -metadata service_provider="test" 'udp://@239.1.1.3:59003?pkt_size=1316' Let me know what other info may be needed. Thanks in advance to any replies. CONFIDENTIALITY NOTICE: This e-mail including attachments is covered by the Electronic Communications Privacy Act, 18 U.S.C. §§2510-2521, is confidential and may contain information that is privileged, confidential or otherwise protected from use and disclosure. If you are not the intended recipient, you are hereby notified that any review, disclosure, copying, or dissemination of this transmission, or taking of any action in reliance on its contents, or other use is strictly prohibited. If you have received this transmission in error, please reply to the sender listed above immediately and permanently delete this message from your inbox. ___ 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] Meaning of ffprobe output
2019-02-21 11:31 GMT+01:00, Ulf Zibis : > > Am 21.02.19 um 01:41 schrieb Carl Eugen Hoyos: >> 2019-02-04 23:29 GMT+01:00, Ulf Zibis : >>> Now I've checked the files with mediainfo: >>> - The vob file is stated as interlaced top first. (I know, this does >>> nothing say about the content, only the flag is evaluated.) >> Doesn't FFmpeg also report this? >> (I believe it should.) > This is what I had asked several times, what the meaning of the string > "top first" on the vob input is. It's just the indication of the flag or > something else? I believe you are right, I missed / forgot this. I expect it is not shown for all interlaced encoded (x264) streams though. >>> - The transcoded mp4 is stated as progressive. >> Did you specify that you want x264 to encode using >> algorithms for interlaced input material? >> Should be "-flags +idct" > Aha, this appears to be the long awaited answer to my question what you > mean by "encoded interlaced". The x264 encoder has a special > mode/optimization for interlaced material, which should be enabled > manually, as the encoder can't detect the nature of the input material > automatically. Correct. > So I guess, the interlaced flag is set automatically when > "-flags +idct" is used, but never just copied from the input stream. It shouldn't. >>> I don't know, why libx264 doesn't retain the flag, maybe it evaluates >> Again (afair, I already wrote that at some point): >> x264 neither retains nor drops "the flag", it doesn't know >> about the input content, it cannot "evaluate" its content. > > Hm, as mediainfo shows, the flag "interlaced top first" was dropped when > transcoding from vob to mp4, which seems to be the same what > ffmpeg/ffprobe states by the string "top first". It wasn't dropped: It is a property of the input stream (only). >>> I still must admid, that I don't really understand what is meant by >>> "encoded interlaced", is it the same than "has the interlaced flag set"? >>> I see no reason why ffmpeg "cannot know" this flag. >> Of course it knows this flag but since the flag is completely useless >> (for encoding, it may be needed to decode correctly) it cannot be >> used to determine correct settings for encoding. >> >> Allow me to repeat: Except for the intro, the video you provided >> is not interlaced, it has artefacts that may or may not be easier >> to encode when using interlaced encoding. >> (Because of the given quality, this is mostly a moot discussion: >> Just use a low quantiser or keep the "originals", if you are really >> interested in the movie buy a dvd that will beat the quality of >> your recording by far.) > In the meantime I had the chance to phone with the original producer > Moritz Boerner. The film was recorded with 36 mm celluloid and he had > above 250.000 DM, not 20.000 DM to produce the film. So our suspicion after visual inspection was right. > So I buyed the DVD now. Except that it has 3 audio tracks to choose and > the VHS head switching artefacts are missing, it unfortunately has the > equal bad quality than my DVD recorder copy, but even has a worst colour > quality than my copy. The purchased DVD is not a direct telecined copy > from the 36 mm material (disappointing), it seem to be a capture of the > in earlier times provided VHS cassette, but with a better adjusted VHS > player, so the head switching artefacts are missing. Thank you for the info! Maybe you should buy a copy of the film? >> PS: Rethinking, it may be a good idea to add the flags for >> your x264 encoding, I believe the encoder is smart enough >> to decide when / how to use it. I suspect it won't make a >> difference for the native FFmpeg video encoders though. > > Is native vs. x264 encoder something different? The native (FFmpeg-internal) encoders may be a little less sophisticated than x264 (and they don't know a special adaptive interlaced setting because it didn't exist in earlier formats). 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".
Re: [FFmpeg-user] Timestamps are unset
2019-02-26 10:40 GMT+01:00, Tom Worton : > In your last email you said that I was missing the complete uncut console > output. If I am doing it correct. I replied with the missing information. Do > you have any further advice? No. You are not the recipient of the warning message. If your output file is fine, there is nothing you can do. > Aside from stating that I did not include the console output information, > you said "If you are just worried about a warning message: > You are not the intended recipient (and there is > nothing you can do about it)." I dont understand what you are saying here. > Are you saying that the warning is just a warning and the data is really > fine or there are legitimate errors and there is nothing I can do? I said that there is nothing you can do about the warning. If you have no issues with the output file, there should be nothing wrong. Please avoid top-posting on this mailing list. 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".
Re: [FFmpeg-user] How to correct dark video with bright background
Am 11.03.2019 um 09:01 schrieb Gerardo Ballabio: Ok, thank you Michael. I'll try haldclut then. This means I have to do some research into Gimp too... For the described workflow you can also use any other graphics program, if it can read and write uncompressed or lossless compressed images (like BMP or PNG). It doesn't work with lossy JPG compression. In your example, begin with a high gamma correction. Michael ___ 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] Filter to detect video glitches
On Sun, 10 Mar 2019, 07:29 Venkateswaran.S, wrote: > Hi all, > > I wants to detect glitches in my video. Is there any filter to achieve it.? > Have you looked into the signalstats filter? It is often used in the QCTools application in order to find glitches in digitised/migrated analogue/digital videotapes. It looks like your example image might have a spike in UV values and maybe even a spike in saturation. It could be worth analysing a glitchy video in QCTools,figuring out which stats seem to be triggered by the glitches you encounter,then add the appropriate calls to your API usage. The qct-parse python tool tries something somewhat similar https://github.com/FutureDays/qct-parse/blob/master/README.md Best, Kieran. ___ > 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] How to correct dark video with bright background
Ok, thank you Michael. I'll try haldclut then. This means I have to do some research into Gimp too... Gerardo Il giorno dom 10 mar 2019 alle ore 22:20 Michael Koch ha scritto: > > Am 10.03.2019 um 22:05 schrieb Michael Koch: > > Am 10.03.2019 um 21:33 schrieb Gerardo Ballabio: > >> Thank you Michael -- but that means I still have to find good values > >> of brightness, contrast, gamma, saturation and hue to use with Gimp. > >> When I've done that, then couldn't I just apply the same values in > >> ffmpeg using the "eq" filter? > > > > That won't work because in most cases the values for brightness, > > contrast, saturation and so on don't have the same units in different > > programs. > > Also you can't be sure that different programs apply the filters in the > same order. Applying brightness before contrast doesn't give the same > result as contrast before brightness. It's an addition and a > multiplication, and it's important what's done first. > > Michael > > ___ > 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".
