Sur d’autres sites (12594)

• avcodec : add common fflcms2 boilerplate

  28 juin 2022, par Niklas Haas

  avcodec : add common fflcms2 boilerplate
  Handling this in general code makes more sense than handling it in
  
  individual codec files, because it would be a lot of unnecessary code
  
  duplication for the plenty of formats that support exporting ICC
  
  profiles (jpg, png, tiff, webp, jxl, ...).
  encode.c and decode.c will be in charge of initializing this state as
  
  needed, so we merely need to make sure to uninit it afterwards from the
  
  common destructor path.
  Signed-off-by : Niklas Haas <git@haasn.dev>
  

  • [DH] configure
  • [DH] libavcodec/Makefile
  • [DH] libavcodec/avcodec.c
  • [DH] libavcodec/decode.c
  • [DH] libavcodec/internal.h

• ffmpeg h264 to mp4 conversion from multiple files fails to preserve in-sequence resolution changes

  1er juillet 2023, par LB2

  This will be a long post, so I thank you in advance for your patience in digesting it.

  


  Context

  


  I have different sources that generate visual content that eventually need to be all composed into a single .mp4 file. The sources are :

  


  

  • H.264 video (encoded using CUDA NVENC).

    

    • This video can have in-sequence resolution change that is natively supported by H.264 codec.

    


    • I.e. stream may start as HxW resolution and mid-stream change to WxH. This behavior happens because it comes from a camera device that can be rotated and flipped between portrait and landscape (e.g. think of a phone camera recording video and phone being flipped from one orientation to another, and video recording adjusting its encoding for proper video scaling and orientation).

    


    • When rotation occurs, most of the time H & W are just swaps, but may actually be entirely new values — e.g. in some cases 1024x768 will switch to 768x1024, but in other cases 1024x768 may become 460x640 (depends on source camera capabilities that I have no control over).

    


    


  


  • JPEGs. A series (a.k.a. batch) of still JPEGs.

    

    • The native resolution of JPEGs may or may not match the video resolution in the earlier bullet.

    


    • JPEGs can also reflect rotation of device and so some JPEGs in a sequence may start at HxW resolution and then from some arbitrary JPEG file can flip and become WxH. Similar to video, resolution dimensions are likely to be just a swap, but may become altogether different values.

    


    


  


  • There can be any number of batches and intermixes between video and still sources. E.g. V₁ + S₂ + S₃ + V₄ + V₅ + V₆ + S₇ + ...

  


  • There can be any number of resolution changes between or within batches. e.g. V_1 ;r1 + V_1 ;r2 + S_2 ;r1 + S_2 ;r3 + V_3 ;r2 + ... (where first subscript is batch sequence ; rX is resolution)

  


  


  Problem

  


  I'm attempting to do this conversion with ffmpeg and can't quite get it right. The problem is that I can't get output to respect source resolutions, and it just squishes all into a single output resolution.

  


  

  


  As already mentioned above, H.264 supports resolution changes in-sequence (mid-stream), and it should be possible to convert and concatenate all the content and have final output contain in-sequence resolution changes.

  


  Since MP4 is just a container, I'm assuming that MP4 files can do so as well ?

  


  Attempts so far

  


  The approach thus far has been to take each batch of content (i.e. .h264 video or a set of JPEGs), and individually convert to .mp4. Video is converted using -c copy to ensure it doesn't try to transcode, e.g. :

  


  ffmpeg -hide_banner -i videoX.h264 -c copy -vsync vfr -video_track_timescale 90000 intermediateX.mp4


  


  ... and JPEGs are converted using -f concat

  


  ffmpeg -hide_banner -f concat -safe 0 -i jpegsX.txt -vf 'scale=trunc(iw/2)*2:trunc(ih/2)*2' -r 30 -vsync vfr -video_track_timescale 90000 intermediateX.mp4


  


  ... and then all the intermediates concatenated together

  


  ffmpeg -hide_banner -f concat -safe 0 -i final.txt -pix_fmt yuv420p -c copy -vsync vfr -video_track_timescale 90000 -metadata title='yabadabadoo' -fflags +bitexact -flags:v +bitexact -flags:a +bitexact final.mp4


  


  This concatenates, but if resolution changes at some mid point, then that part of content comes up squished/stretched in final output.

  


  Use h.264 as intermediates

  


  All the intermediates are produced the same, except as .h264. All intermediate .h264 are cat'ed together like `cat intermediate1.h264 intermediate2.264 > final.h264.

  


  If final output is final.mp4, the output is incorrect and images are squished/stretched.

  


  If final.h264, then at least it seems to be respecting aspect ratios of input and managing to produce correctly looking output. However, examining with ffprobe it seems that it uses SAR weird ratios, where first frames are width=1440 height=3040 sample_aspect_ratio=1:1, but later SAR takes on values like width=176 height=340 sample_aspect_ratio=1545:176, which I suspect isn't right, since all original input was with "square pixels". I think the reason for it is that it was composed out of different sized JPEGs, and concat filter somehow caused ffmpeg to manipulate SAR "to get things fit".

  


  But at least it renders respectably, though hard to say with ffplay if player would actually see resolution change and resize accordingly .

  


  And, that's .h264 ; and I need final output to be .mp4.

  


  Use -vf filter

  


  I tried enforcing SAR using -vf 'scale=trunc(iw/2)*2:trunc(ih/2)*2,setsar=1:1' (scaling is to deal with odd dimension JPEGs), but it still produces frames with SAR like stated earlier.

  


  Other thoughts

  


  For now, while I haven't given up, I'm trying to avoid in my code examining each individual JEPG in a batch to see if there are differing sizes, and splitting batch so that each sub-batch is homogenous resolution-wise, and generating individual intermediate .h264 so that SAR remains sane, and keep fingers crossed that the final would work correctly. It'll be very slow, unfortunately.

  


  Question

  


  What's the right way to deal with all that using ffmpeg, and how to concatenate mulitple varying resolution sources into a final mp4 so that it respects resolution changes mid-stream ?

  


• aarch64 : Use regular hwcaps flags instead of HWCAP_CPUID for CPU feature detection...

  14 février 2024, par Martin Storsjö

  aarch64 : Use regular hwcaps flags instead of HWCAP_CPUID for CPU feature detection on Linux
  This makes the code much simpler (especially for adding support
  
  for other instruction set extensions), avoids needing inline
  
  assembly for this feature, and generally is more of the canonical
  
  way to do this.
  The CPU feature detection was added in
  
  493fcde50a84cb23854335bcb0e55c6f383d55db, using HWCAP_CPUID.
  The argument for using that, was that HWCAP_CPUID was added much
  
  earlier in the kernel (in Linux v4.11), while the HWCAP flags for
  
  individual features always come later. This allows detecting support
  
  for new CPU extensions before the kernel exposes information about
  
  them via hwcap flags.
  However in practice, there's probably quite little advantage in this.
  
  E.g. HWCAP2_I8MM was added in Linux v5.10 - long after HWCAP_CPUID,
  
  but there's probably very little practical cases where one would
  
  run a kernel older than that on a CPU that supports those instructions.
  Additionally, we provide our own definitions of the flag values to
  
  check (as they are fixed constants anyway), with names not conflicting
  
  with the ones from system headers. This reduces the number of ifdefs
  
  needed, and allows detecting those features even if building with
  
  userland headers that are lacking the definitions of those flags.
  Also, slightly older versions of QEMU, e.g. 6.2 in Ubuntu 22.04,
  
  do expose support for these features via HWCAP flags, but the
  
  emulated cpuid registers are missing the bits for exposing e.g. I8MM.
  
  (This issue is fixed in later versions of QEMU though.)
  Signed-off-by : Martin Storsjö <martin@martin.st>
  

  • [DH] libavutil/aarch64/cpu.c