Re: [FFmpeg-user] yadif-cuda issues
I worked with Rodger to address this, and it's been resolved in his patch 'compat/cuda/ptx2c: fix BSD sed compatibility' It's sitting in the devel list, but hopefully it'll be committed soon to fix this. ___ 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] question about fps filter
using this version created today using https://github.com/rdp/ffmpeg-windows-build-helpers ffmpeg.exe -version ffmpeg version N-97877-g1e8ed181e3-ffmpeg-windows-build-helpers Copyright (c) 2000-2020 the FFmpeg developers built with gcc 8.3.0 (GCC) configuration: --pkg-config=pkg-config --pkg-config-flags=--static --extra-version=ffmpeg-windows-build-helpers --enable-version3 --disable-debug --disable-w32threads --arch=x86_64 --target-os=mingw32 --cross-prefix=/home/asheimo/ffmpeg-windows-build-helpers/sandbox/cross_compilers/mingw-w64-x86_64/bin/x86_64-w64-mingw32- --enable-libcaca --enable-gray --enable-libtesseract --enable-fontconfig --enable-gmp --enable-gnutls --enable-libass --enable-libbluray --enable-libbs2b --enable-libflite --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopus --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvo-amrwbenc --enable-libvorbis --enable-libwebp --enable-libzimg --enable-libzvbi --enable-libmysofa --enable-libopenjpeg --enable-libopenh264 --enable-liblensfun --enable-libvmaf --enable-libsrt --enable-demuxer=dash --enable-libxml2 --enable-opengl --enable-libdav1d --enable-cuda-llvm --enable-libsvthevc --enable-libaom --enable-libvpx --enable-nvenc --enable-nvdec --extra-libs=-lharfbuzz --extra-libs=-lm --extra-libs=-lpthread --extra-cflags=-DLIBTWOLAME_STATIC --extra-cflags=-DMODPLUG_STATIC --extra-cflags=-DCACA_STATIC --enable-amf --enable-libmfx --enable-gpl --enable-frei0r --enable-filter=frei0r --enable-librubberband --enable-libvidstab --enable-libx264 --enable-libx265 --enable-libxvid --enable-libxavs --enable-avresample --extra-cflags='-mtune=generic' --extra-cflags=-O3 --enable-static --disable-shared --prefix=/home/asheimo/ffmpeg-windows-build-helpers/sandbox/cross_compilers/mingw-w64-x86_64/x86_64-w64-mingw32 libavutil 56. 46.100 / 56. 46.100 libavcodec 58. 87.100 / 58. 87.100 libavformat58. 43.100 / 58. 43.100 libavdevice58. 9.103 / 58. 9.103 libavfilter 7. 82.100 / 7. 82.100 libavresample 4. 0. 0 / 4. 0. 0 libswscale 5. 6.101 / 5. 6.101 libswresample 3. 6.100 / 3. 6.100 libpostproc55. 6.100 / 55. 6.100 On Fri, May 22, 2020 at 6:24 PM Dennis Mungai wrote: > On Sat, 23 May 2020 at 01:07, Andy Sheimo wrote: > > > I am using the command line seen here but the fps filter is being > ignored. > > > > ffmpeg.exe -loglevel debug -stats -hwaccel cuda -hwaccel_output_format > cuda > > -i "Evanescence - Anywhere but Home.mkv" -map 0:0 -filter:v > > yadif_cuda=deint=interlaced,fps=24000/1001 -c:v h264_nvenc -b:v 2000k > > -maxrate:v 6000k -rc:v vbr_hq -spatial-aq:v 1 -temporal-aq:v 1 -profile:v > > high -color_primaries:v smpte170m -color_trc:v bt709 -colorspace:v > > smpte170m -metadata:s:v title= -disposition:v default -map 0:1 -c:a:0 > eac3 > > -b:a:0 256k -metadata:s:a:0 title= -disposition:a:0 default -map 0:2 > -c:a:1 > > copy -metadata:s:a:1 title= -disposition:a:1 0 -sn -metadata:g title= > > "Evanescence - Anywhere but Home 2.mkv" > > > > I found this in the debug output and am not sure why it sees what was > > passed by the command line but then is ignored in the filter graph can > > someone help me understand please? The complete debug output is available > > but too big to include here. > > > > [Parsed_yadif_cuda_0 @ 0220ac5561c0] Setting 'deint' to value > > 'interlaced' > > [Parsed_fps_1 @ 0220ac74a500] Setting 'fps' to value '24000/1001' > > [Parsed_fps_1 @ 0220ac74a500] fps=24000/1001 > > [graph 0 input from stream 0:0 @ 0220ac749f40] Setting 'video_size' > to > > value '720x480' > > [graph 0 input from stream 0:0 @ 0220ac749f40] Setting 'pix_fmt' to > > value '119' > > [graph 0 input from stream 0:0 @ 0220ac749f40] Setting 'time_base' to > > value '1/1000' > > [graph 0 input from stream 0:0 @ 0220ac749f40] Setting 'pixel_aspect' > > to value '186/157' > > [graph 0 input from stream 0:0 @ 0220ac749f40] Setting 'frame_rate' > to > > value '3/1001' > > [graph 0 input from stream 0:0 @ 0220ac749f40] w:720 h:480 > pixfmt:cuda > > tb:1/1000 fr:3/1001 sar:186/157 > > [format @ 0220ac74bac0] Setting 'pix_fmts' to value > > 'yuv420p|nv12|p010le|yuv444p|p016le|yuv444p16le|bgr0|rgb0|cuda|d3d11' > > [AVFilterGraph @ 0220ac511d80] query_formats: 5 queried, 4 merged, 0 > > already done, 0 delayed > > [h264_nvenc @ 0220ac561540] Using input frames context (format cuda) > > with h264_nvenc encoder. > > ___ > > > > What version of ffmpeg are you using? > There have been recent updates to the NVENC encoder's implementation in > ffmpeg that better handle frame rate, such as this commit: > > https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/b18fd2b95b2fea10f0b5381333a1b4c032f010bc > Use the latest build and retest. >
Re: [FFmpeg-user] question about fps filter
On Sat, 23 May 2020 at 01:07, Andy Sheimo wrote: > I am using the command line seen here but the fps filter is being ignored. > > ffmpeg.exe -loglevel debug -stats -hwaccel cuda -hwaccel_output_format cuda > -i "Evanescence - Anywhere but Home.mkv" -map 0:0 -filter:v > yadif_cuda=deint=interlaced,fps=24000/1001 -c:v h264_nvenc -b:v 2000k > -maxrate:v 6000k -rc:v vbr_hq -spatial-aq:v 1 -temporal-aq:v 1 -profile:v > high -color_primaries:v smpte170m -color_trc:v bt709 -colorspace:v > smpte170m -metadata:s:v title= -disposition:v default -map 0:1 -c:a:0 eac3 > -b:a:0 256k -metadata:s:a:0 title= -disposition:a:0 default -map 0:2 -c:a:1 > copy -metadata:s:a:1 title= -disposition:a:1 0 -sn -metadata:g title= > "Evanescence - Anywhere but Home 2.mkv" > > I found this in the debug output and am not sure why it sees what was > passed by the command line but then is ignored in the filter graph can > someone help me understand please? The complete debug output is available > but too big to include here. > > [Parsed_yadif_cuda_0 @ 0220ac5561c0] Setting 'deint' to value > 'interlaced' > [Parsed_fps_1 @ 0220ac74a500] Setting 'fps' to value '24000/1001' > [Parsed_fps_1 @ 0220ac74a500] fps=24000/1001 > [graph 0 input from stream 0:0 @ 0220ac749f40] Setting 'video_size' to > value '720x480' > [graph 0 input from stream 0:0 @ 0220ac749f40] Setting 'pix_fmt' to > value '119' > [graph 0 input from stream 0:0 @ 0220ac749f40] Setting 'time_base' to > value '1/1000' > [graph 0 input from stream 0:0 @ 0220ac749f40] Setting 'pixel_aspect' > to value '186/157' > [graph 0 input from stream 0:0 @ 0220ac749f40] Setting 'frame_rate' to > value '3/1001' > [graph 0 input from stream 0:0 @ 0220ac749f40] w:720 h:480 pixfmt:cuda > tb:1/1000 fr:3/1001 sar:186/157 > [format @ 0220ac74bac0] Setting 'pix_fmts' to value > 'yuv420p|nv12|p010le|yuv444p|p016le|yuv444p16le|bgr0|rgb0|cuda|d3d11' > [AVFilterGraph @ 0220ac511d80] query_formats: 5 queried, 4 merged, 0 > already done, 0 delayed > [h264_nvenc @ 0220ac561540] Using input frames context (format cuda) > with h264_nvenc encoder. > ___ > What version of ffmpeg are you using? There have been recent updates to the NVENC encoder's implementation in ffmpeg that better handle frame rate, such as this commit: https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/b18fd2b95b2fea10f0b5381333a1b4c032f010bc Use the latest build and retest. ___ 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] question about fps filter
I am using the command line seen here but the fps filter is being ignored. ffmpeg.exe -loglevel debug -stats -hwaccel cuda -hwaccel_output_format cuda -i "Evanescence - Anywhere but Home.mkv" -map 0:0 -filter:v yadif_cuda=deint=interlaced,fps=24000/1001 -c:v h264_nvenc -b:v 2000k -maxrate:v 6000k -rc:v vbr_hq -spatial-aq:v 1 -temporal-aq:v 1 -profile:v high -color_primaries:v smpte170m -color_trc:v bt709 -colorspace:v smpte170m -metadata:s:v title= -disposition:v default -map 0:1 -c:a:0 eac3 -b:a:0 256k -metadata:s:a:0 title= -disposition:a:0 default -map 0:2 -c:a:1 copy -metadata:s:a:1 title= -disposition:a:1 0 -sn -metadata:g title= "Evanescence - Anywhere but Home 2.mkv" I found this in the debug output and am not sure why it sees what was passed by the command line but then is ignored in the filter graph can someone help me understand please? The complete debug output is available but too big to include here. [Parsed_yadif_cuda_0 @ 0220ac5561c0] Setting 'deint' to value 'interlaced' [Parsed_fps_1 @ 0220ac74a500] Setting 'fps' to value '24000/1001' [Parsed_fps_1 @ 0220ac74a500] fps=24000/1001 [graph 0 input from stream 0:0 @ 0220ac749f40] Setting 'video_size' to value '720x480' [graph 0 input from stream 0:0 @ 0220ac749f40] Setting 'pix_fmt' to value '119' [graph 0 input from stream 0:0 @ 0220ac749f40] Setting 'time_base' to value '1/1000' [graph 0 input from stream 0:0 @ 0220ac749f40] Setting 'pixel_aspect' to value '186/157' [graph 0 input from stream 0:0 @ 0220ac749f40] Setting 'frame_rate' to value '3/1001' [graph 0 input from stream 0:0 @ 0220ac749f40] w:720 h:480 pixfmt:cuda tb:1/1000 fr:3/1001 sar:186/157 [format @ 0220ac74bac0] Setting 'pix_fmts' to value 'yuv420p|nv12|p010le|yuv444p|p016le|yuv444p16le|bgr0|rgb0|cuda|d3d11' [AVFilterGraph @ 0220ac511d80] query_formats: 5 queried, 4 merged, 0 already done, 0 delayed [h264_nvenc @ 0220ac561540] Using input frames context (format cuda) with h264_nvenc encoder. ___ 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] yadif-cuda issues
I'm able to reproduce this, and I believe it's due to building the CUDA modules with clang. Will update when I learn more, but thank you for the report Andy. ___ 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 control quality of subtitles
Am Fr., 22. Mai 2020 um 16:01 Uhr schrieb Peter Münster : > I would like to learn, how to control the quality of the displayed > subtitles. It is indeed possible to force a palette for dvd subtitles but only on decoding because many sources miss the palette, your command line should produce an output file with dvdsub palette. > This is how I create the video: > > ffmpeg -i input.ts -map 0:0 -map 0:1 -map 0:2 -c:v libx264 -c:a copy >-c:s dvdsub output.mkv Complete, uncut console output missing. > This looks nice with VLC: http://pmrb.free.fr/tmp/ffmpeg-test/vlc.jpg > But very ugly with a Samsung TV: Looks like an issue of the Samsung TV but feel free to compare with other players. 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] yadif-cuda issues
On 5/22/2020 9:33 AM, Kyle Schwarz wrote: You don't even need the build script though, you could easily cross-compile with Cygwin as you really only need the nv-codec-headers. MinGW-64? I've used that build ffmpeg w/ decklink and IIRC it was pretty much without problems once I had the necessary packages installed and the right configure cmd line. "You are in a maze of twisty huge windows build systems" z! ___ 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] yadif-cuda issues
On Fri, May 22, 2020 at 12:21 PM Andy Sheimo wrote: > I've been trying those scripts and been getting errors which I have a > ticket open on. Roger will need to help with that, but I'd strongly recommend not using WSL (pretty much ever) and set up a VirtualBox VM. You don't even need the build script though, you could easily cross-compile with Cygwin as you really only need the nv-codec-headers. ___ 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] yadif-cuda issues
I've been trying those scripts and been getting errors which I have a ticket open on. On Fri, May 22, 2020 at 11:43 AM Kyle Schwarz wrote: > On Fri May 22 2020 at 06:44:40 Andy Sheimo wrote: > > I tried to report this issue to Zeranoe's forums but they have since > closed > > down and a message pointing to the official ffmpeg contact messages is in > > the forums place. Could you please advise if official support for > > Zeranoe's builds is available here or are windows users trying to use > those > > builds out of luck? > > So far I'm unable to reproduce this as apparently my GTX 1060 "is lacking > required capabilities". I tried: > > ffmpeg -hwaccel nvdec -hwaccel_output_format cuda -i i.mkv -vf > yadif_cuda=0:-1:1 -c:v h264_nvenc o.mkv > > On Tue Apr 21 2020 at 00:43:07, Dennis Mungai > wrote: > > I've seen a similar issue here on the "CUDA_ERROR_INVALID_IMAGE: device > > kernel image is invalid error" posted on this mailing list related to > > Zeranoe's builds. > > I'm not able to find other mailing list posts that contain > "CUDA_ERROR_INVALID_IMAGE" related to the Zeranoe builds. There is however > an > open bug that contains it (https://trac.ffmpeg.org/ticket/8457), which is > not > Windows related. > > If this is indeed a Windows/Zeranoe issue, it's rather specific and would > implicate my cross-compiler itself. I'll need to be able to reproduce this > to > confirm, but you could try Rogers build script to see if it happens there > too. > ___ > 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] yadif-cuda issues
On Fri May 22 2020 at 06:44:40 Andy Sheimo wrote: > I tried to report this issue to Zeranoe's forums but they have since closed > down and a message pointing to the official ffmpeg contact messages is in > the forums place. Could you please advise if official support for > Zeranoe's builds is available here or are windows users trying to use those > builds out of luck? So far I'm unable to reproduce this as apparently my GTX 1060 "is lacking required capabilities". I tried: > ffmpeg -hwaccel nvdec -hwaccel_output_format cuda -i i.mkv -vf > yadif_cuda=0:-1:1 -c:v h264_nvenc o.mkv On Tue Apr 21 2020 at 00:43:07, Dennis Mungai wrote: > I've seen a similar issue here on the "CUDA_ERROR_INVALID_IMAGE: device > kernel image is invalid error" posted on this mailing list related to > Zeranoe's builds. I'm not able to find other mailing list posts that contain "CUDA_ERROR_INVALID_IMAGE" related to the Zeranoe builds. There is however an open bug that contains it (https://trac.ffmpeg.org/ticket/8457), which is not Windows related. If this is indeed a Windows/Zeranoe issue, it's rather specific and would implicate my cross-compiler itself. I'll need to be able to reproduce this to confirm, but you could try Rogers build script to see if it happens there too. ___ 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] how to control quality of subtitles
Hi, I would like to learn, how to control the quality of the displayed subtitles. This is how I create the video: ffmpeg -i input.ts -map 0:0 -map 0:1 -map 0:2 -c:v libx264 -c:a copy -c:s dvdsub output.mkv This looks nice with VLC: http://pmrb.free.fr/tmp/ffmpeg-test/vlc.jpg But very ugly with a Samsung TV: http://pmrb.free.fr/tmp/ffmpeg-test/samsung.jpg How could I get nice looking subtitles on this kind of Samsung TV please? Thanks in advance for any hints, -- Peter ___ 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] Resizing result with nearest neighbour is highly compressed
Nearest neighbor will make it blocky. Maybe you want bilinear? > On May 22, 2020, at 5:15 AM, Moritz Barsnick wrote: > > On Fri, May 22, 2020 at 13:52:40 +0200, Nick wrote: >> I'm trying to resize a .mp4 video with FFmpeg but the result is artifacted >> to hell and back, how can I fix it? > > To be honest, I see the same artifacts in the original. > (I dumped single frames losslessly to PNG and viewed them full-screen. > Note that that last step of full-screen scaling obviously also uses > some algorithm. But regardless of smoothing or not, I see artifacts.) > >>> ffmpeg -i C:\Users\Asus\Desktop\0001-0024.mp4 -vf >>> scale=1120:1120:flags=neighbor C:\Users\Asus\Desktop\out.mp4 -aac_tns > > We usually appreciate the complete, uncut console output, which also > saves us from actually reproducing, just to see e.g. that you are > scaling *up*). > > And that "-aac_tns" in your command line surely is a mistake. ;-) > > Moritz > ___ > 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] Resizing result with nearest neighbour is highly compressed
On Fri, May 22, 2020 at 13:52:40 +0200, Nick wrote: > I'm trying to resize a .mp4 video with FFmpeg but the result is artifacted > to hell and back, how can I fix it? To be honest, I see the same artifacts in the original. (I dumped single frames losslessly to PNG and viewed them full-screen. Note that that last step of full-screen scaling obviously also uses some algorithm. But regardless of smoothing or not, I see artifacts.) > > ffmpeg -i C:\Users\Asus\Desktop\0001-0024.mp4 -vf > > scale=1120:1120:flags=neighbor C:\Users\Asus\Desktop\out.mp4 -aac_tns We usually appreciate the complete, uncut console output, which also saves us from actually reproducing, just to see e.g. that you are scaling *up*). And that "-aac_tns" in your command line surely is a mistake. ;-) Moritz ___ 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] preserving metadata from .mp4 to .jpg/.png frames
On Fri, May 22, 2020 at 07:52:14 +0200, Michael Koch wrote: > here is an example of a JPG for which exiftool (version 11.26) reports 6 > dates/times: > http://www.astro-electronic.de/IMG_1343.jpg Yes, that file contains actual EXIF metadata, including date tags. That doesn't change the fact that ffmpeg currently isn't able to create EXIF metadata, even if it is able to parse it from some formats. Moritz ___ 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] preserving metadata from .mp4 to .jpg/.png frames
Am 22.05.2020 um 11:52 schrieb Nicolas George: Michael Koch (12020-05-22): here is an example of a JPG for which exiftool (version 11.26) reports 6 dates/times: http://www.astro-electronic.de/IMG_1343.jpg File Modification Date/Time : 2020:05:22 07:46:54+02:00 File Access Date/Time : 2020:05:22 11:51:04+02:00 File Inode Change Date/Time : 2020:05:22 11:51:00+02:00 Spot the difference with your version? This is what my version of exiftool reports: C:\Users\mKoch\Desktop>c:\ffmpeg\exiftool C:\Users\mKoch\Desktop\IMG_1343.jpg -u ExifTool Version Number : 11.26 File Name : IMG_1343.jpg Directory : C:/Users/mKoch/Desktop File Size : 3.4 MB File Modification Date/Time : 2020:05:22 07:15:10+02:00<--- File Access Date/Time : 2020:05:22 13:06:37+02:00 <--- File Creation Date/Time : 2020:05:22 13:06:37+02:00 <--- File Permissions : rw-rw-rw- File Type : JPEG File Type Extension : jpg MIME Type : image/jpeg Exif Byte Order : Little-endian (Intel, II) Image Description : Make : Canon Camera Model Name : Canon IXUS 107 Orientation : Horizontal (normal) X Resolution : 180 Y Resolution : 180 Resolution Unit : inches Modify Date : 2020:05:22 07:15:10<--- Y Cb Cr Positioning : Co-sited Exposure Time : 1/60 F Number : 2.8 ISO : 200 Exif Version : 0221 Date/Time Original : 2020:05:22 07:15:10<--- Create Date : 2020:05:22 07:15:10 <--- Components Configuration : Y, Cb, Cr, - Compressed Bits Per Pixel : 3 Shutter Speed Value : 1/60 Aperture Value : 2.8 Max Aperture Value : 2.8 Flash : Auto, Did not fire Focal Length : 5.0 mm Macro Mode : Normal Self Timer : Off Quality : Fine Canon Flash Mode : Auto Continuous Drive : Single Focus Mode : Single Record Mode : JPEG Canon Image Size : Large Easy Mode : Night Snapshot Digital Zoom : None Contrast : Normal Saturation : Normal Sharpness : 0 Camera ISO : Auto Metering Mode : Evaluative Focus Range : Auto AF Point : Manual AF point selection Canon Exposure Mode : Easy Lens Type : n/a Max Focal Length : 20 mm Min Focal Length : 5 mm Focal Units : 1000/mm Max Aperture : 2.8 Min Aperture : 8 Flash Bits : (none) Focus Continuous : Single AE Setting : Normal AE Image Stabilization : Shoot Only Zoom Source Width : 4000 Zoom Target Width : 4000 Spot Metering Mode : Center Manual Flash Output : n/a Focal Type : Zoom Focal Plane X Size : 6.30 mm Focal Plane Y Size : 4.72 mm Canon Flash Info : 0 0 0 0 Auto ISO : 192 Base ISO : 100 Measured EV : 8.81 Target Aperture : 2.8 Target Exposure Time : 1/60 Exposure Compensation : 0 White Balance : Auto Slow Shutter : Off Shot Number In Continuous Burst : 0 Optical Zoom Code : 0 Flash Guide Number : 0 Flash Exposure Compensation : 0 Auto Exposure Bracketing : Off AEB Bracket Value : 0 Control Mode : Camera Local Control Focus Distance Upper : 1.6 m Focus Distance Lower : 0 m Bulb Duration : 0 Camera Type : Compact Auto Rotate : None ND Filter : Off Self Timer 2 : 0 Flash Output : 0 Canon Image Type : IMG:IXUS 107 JPEG Canon Firmware Version : Firmware Version 1.00 File Number : 164-1343 Owner Name : Rotation : 0 Camera Temperature : 18 C Canon Model ID : PowerShot SD1300 IS / IXUS 105 / IXY 200F AF Info Size : 98 AF Area Mode : Single-point AF Num AF Points : 9 Valid AF Points : 1 Canon
Re: [FFmpeg-user] [ffmpeg] preserving metadata from .mp4 to .jpg/.png frames
Michael Koch (12020-05-22): > here is an example of a JPG for which exiftool (version 11.26) reports 6 > dates/times: > http://www.astro-electronic.de/IMG_1343.jpg File Modification Date/Time : 2020:05:22 07:46:54+02:00 File Access Date/Time : 2020:05:22 11:51:04+02:00 File Inode Change Date/Time : 2020:05:22 11:51:00+02:00 Spot the difference with your version? Regards, -- Nicolas George signature.asc Description: PGP signature ___ 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".
