Recherche avancée

Sur d’autres sites (11162)

• How to encode KLV stream into MPEGTS with FFMPEG ?

  27 février 2018, par gediminasgu

  I’m playing with muxing h264 video with KLV data into mpegts to make video with included KLV data like in ffmpeg samples http://samples.ffmpeg.org/MPEG2/mpegts-klv/Day%20Flight.mpg

  My command line :

  ffmpeg.exe -re -f lavfi -i testsrc=rate=30 -re -f data -i out_day.klv -map 0:0 -map 1:0 -c:v h264 -c:d klv -f mpegts test.ts

  It creates video, but data is encoded with bin_data code, but not klv :

  > ffmpeg.exe -i test.ts
ffmpeg version 3.4.2 Copyright (c) 2000-2018 the FFmpeg developers
 built with gcc 7.3.0 (GCC)
 configuration: --enable-gpl --enable-version3 --enable-sdl2 --enable-bzlib --enable-fontconfig --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libtheora --enable-libtwolame --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libzimg --enable-lzma --enable-zlib --enable-gmp --enable-libvidstab --enable-libvorbis --enable-libvo-amrwbenc --enable-libmysofa --enable-libspeex --enable-libxvid --enable-libmfx --enable-cuda --enable-cuvid --enable-d3d11va --enable-nvenc --enable-dxva2 --enable-avisynth
 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
 libswscale      4.  8.100 /  4.  8.100
 libswresample   2.  9.100 /  2.  9.100
 libpostproc    54.  7.100 / 54.  7.100
[mpegts @ 0000017fad6124a0] start time for stream 1 is not set in estimate_timings_from_pts
Input #0, mpegts, from 'test.ts':
 Duration: 00:00:04.93, start: 1.466667, bitrate: 78 kb/s
 Program 1
   Metadata:
     service_name    : Service01
     service_provider: FFmpeg
   Stream #0:0[0x100]: Video: h264 (High 4:4:4 Predictive) ([27][0][0][0] / 0x001B), yuv444p(progressive), 320x240 [SAR 1:1 DAR 4:3], 30 fps, 30 tbr, 90k tbn, 60 tbc
   Stream #0:1[0x101]: Data: bin_data ([6][0][0][0] / 0x0006)
At least one output file must be specified

  How to set data stream codec to KLV ?

  p.s. out_day.klv is extracted from Day Flight.mpg with command ffmpeg -i "Day Flight.mpg" -map data-re -codec copy -f data out_day.klv

  Thank you

• How can I retain 2x pixel density when encoding Retina screen capture with ffmpeg ?

  26 février 2018, par hfossli

  Whenever I use ffmpeg to encode a HiDPI/Retina screen recording, the video plays at 2x the size, so it looks fuzzy, because the pixel density is not retained.

  How can I retain the original pixel density of HiDPI screen recordings with ffmpeg ?

  How to reproduce :

  1. Use QuickTime Player to create a Screen Recording on a Retina Mac.
  2. Play the video you recorded in QuickTime Player using the ⌘1 Actual Size view. Notice that it’s playing 2:1 on your Retina Display, so the video looks sharp. It’s playing in half the space of the actual recorded pixels.

  3. Use ffmpeg to encode the video using a command like this :

     ffmpeg -i haha.mov -c:v libx264 -crf 23 haha-lg.mov

  4. Play the new ffmpeg-compressed video in QuickTime Player using the ⌘1 Actual Size view. Notice that it’s playing 1:1, so the video looks fuzzy.

  To clarify, the video does not look blurry because it was compressed. Rather, it looks blurry because the video is being played twice as big as it should be, at a 1:1 pixel density, instead of the required 2:1 pixel density, presumably because some metadata is being discarded when encoding.

  For the record, VLC plays both videos too big (blurry). So being able to play HiDPI videos seems to be a feature of QuickTime Player.

  Here is the detailed information ffmpeg shows for the original screen recording :

  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'haha.mov':
  
    Metadata:
  
      major_brand     : qt  
  
      minor_version   : 0
  
      compatible_brands: qt  
  
      creation_time   : 2018-02-26T16:46:00.000000Z
  
      com.apple.quicktime.make: Apple
  
      com.apple.quicktime.model: iMac18,3
  
      com.apple.quicktime.software: Mac OS X 10.13.3 (17D102)
  
      com.apple.quicktime.creationdate: 2018-02-26T10:45:50-0600
  
    Duration: 00:00:04.35, start: 0.000000, bitrate: 10947 kb/s
  
      Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p(tv, bt709), 1396x928 [SAR 1:1 DAR 349:232], 10701 kb/s, 60 fps, 60 tbr, 6k tbn, 12k tbc (default)
  
      Metadata:
  
        creation_time   : 2018-02-26T16:46:00.000000Z
  
        handler_name    : Core Media Data Handler
  
        encoder         : H.264

  And here is the information for the ffmpeg-compressed version :

  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'haha-lg.mov':
  
    Metadata:
  
      major_brand     : qt  
  
      minor_version   : 512
  
      compatible_brands: qt  
  
      encoder         : Lavf57.83.100
  
    Duration: 00:00:04.35, start: 0.000000, bitrate: 1923 kb/s
  
      Stream #0:0(eng): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 1396x928 [SAR 1:1 DAR 349:232], 1783 kb/s, 60 fps, 60 tbr, 15360 tbn, 120 tbc (default)
  
      Metadata:
  
        handler_name    : DataHandler
  
        encoder         : Lavc57.107.100 libx264

• How can I retain 2x pixel density when encoding Retina screen capture with ffmpeg ?

  26 février 2018, par hfossli

  Whenever I use ffmpeg to encode a HiDPI/Retina screen recording, the video plays at 2x the size, so it looks fuzzy, because the pixel density is not retained.

  How can I retain the original pixel density of HiDPI screen recordings with ffmpeg ?

  How to reproduce :

  1. Use QuickTime Player to create a Screen Recording on a Retina Mac.
  2. Play the video you recorded in QuickTime Player using the ⌘1 Actual Size view. Notice that it’s playing 2:1 on your Retina Display, so the video looks sharp. It’s playing in half the space of the actual recorded pixels.

  3. Use ffmpeg to encode the video using a command like this :

     ffmpeg -i haha.mov -c:v libx264 -crf 23 haha-lg.mov

  4. Play the new ffmpeg-compressed video in QuickTime Player using the ⌘1 Actual Size view. Notice that it’s playing 1:1, so the video looks fuzzy.

  To clarify, the video does not look blurry because it was compressed. Rather, it looks blurry because the video is being played twice as big as it should be, at a 1:1 pixel density, instead of the required 2:1 pixel density, presumably because some metadata is being discarded when encoding.

  For the record, VLC plays both videos too big (blurry). So being able to play HiDPI videos seems to be a feature of QuickTime Player.

  Here is the detailed information ffmpeg shows for the original screen recording :

  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'haha.mov':
  
    Metadata:
  
      major_brand     : qt  
  
      minor_version   : 0
  
      compatible_brands: qt  
  
      creation_time   : 2018-02-26T16:46:00.000000Z
  
      com.apple.quicktime.make: Apple
  
      com.apple.quicktime.model: iMac18,3
  
      com.apple.quicktime.software: Mac OS X 10.13.3 (17D102)
  
      com.apple.quicktime.creationdate: 2018-02-26T10:45:50-0600
  
    Duration: 00:00:04.35, start: 0.000000, bitrate: 10947 kb/s
  
      Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p(tv, bt709), 1396x928 [SAR 1:1 DAR 349:232], 10701 kb/s, 60 fps, 60 tbr, 6k tbn, 12k tbc (default)
  
      Metadata:
  
        creation_time   : 2018-02-26T16:46:00.000000Z
  
        handler_name    : Core Media Data Handler
  
        encoder         : H.264

  And here is the information for the ffmpeg-compressed version :

  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'haha-lg.mov':
  
    Metadata:
  
      major_brand     : qt  
  
      minor_version   : 512
  
      compatible_brands: qt  
  
      encoder         : Lavf57.83.100
  
    Duration: 00:00:04.35, start: 0.000000, bitrate: 1923 kb/s
  
      Stream #0:0(eng): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 1396x928 [SAR 1:1 DAR 349:232], 1783 kb/s, 60 fps, 60 tbr, 15360 tbn, 120 tbc (default)
  
      Metadata:
  
        handler_name    : DataHandler
  
        encoder         : Lavc57.107.100 libx264