Recherche avancée

Sur d’autres sites (8395)

• Perspective transformations

  9 juin 2010, par Mikko Koppanen — Imagick, PHP stuff

  Finally (after a long break) I managed to force myself to update the PHP documentation and this time it was distortImage code example. Things have been hectic lately but that does not quite explain the 6 months(?) break between this and the previous post. As a matter of a fact there is no excuse for such a long silence so I will try to update this blog a bit more often from now on.

  Back in the day I used to blog the examples and update the documentation if I remembered but I am trying to fix this bad habit. Most of the latest examples have been updated in to the manual. In the case of the two last examples I updated the documentation first and then blogged on the subject.

  I took some time to actually understand the perspective transformations properly using the excellent ImageMagick examples (mainly created by Anthony Thyssen) as a reference. The basic idea of perspective distortion seems simple : to distort the control points to new locations. Grabbing the syntax for Imagick was easy, an array of control point pairs in the form of :

  php

  < view plain text >

  1. array(source_x, source_y, dest_x, dest_y ... )

  The following example uses the built-in checkerboard pattern to demonstrate perspective distortion :

  php

  < view plain text >

  1. < ?php
  2. /* Create new object */
  3. $im = new Imagick() ;
  4.  
  5. /* Create new checkerboard pattern */
  6. $im->newPseudoImage(100, 100, "pattern:checkerboard") ;
  7.  
  8. /* Set the image format to png */
  9. $im->setImageFormat(’png’) ;
  10.  
  11. /* Fill background area with transparent */
  12. $im->setImageVirtualPixelMethod(Imagick: :VIRTUALPIXELMETHOD_TRANSPARENT) ;
  13.  
  14. /* Activate matte */
  15. $im->setImageMatte(true) ;
  16.  
  17. /* Control points for the distortion */
  18. $controlPoints = array( 10, 10,
  19.             10, 5,
  20.  
  21.             10, $im->getImageHeight() - 20,
  22.             10, $im->getImageHeight() - 5,
  23.  
  24.             $im->getImageWidth() - 10, 10,
  25.             $im->getImageWidth() - 10, 20,
  26.  
  27.             $im->getImageWidth() - 10, $im->getImageHeight() - 10,
  28.             $im->getImageWidth() - 10, $im->getImageHeight() - 30) ;
  29.  
  30. /* Perform the distortion */ 
  31. $im->distortImage(Imagick: :DISTORTION_PERSPECTIVE, $controlPoints, true) ;
  32.  
  33. /* Ouput the image */ 
  34. header("Content-Type : image/png") ;
  35. echo $im ;
  36.  ?>

  Here is the source image :
  

  And the result :
  

• lavc : Deprecate avctx.rtp_callback field

  19 novembre 2015, par Vittorio Giovara

  lavc : Deprecate avctx.rtp_callback field
  This function returns the encoded data of a frame, one slice at a time
  
  directly when that slice is encoded, instead of waiting for the full
  
  frame to be done. However this field has a debatable usefulness, since
  
  it looks like it is just a convoluted way to get data at lowest
  
  possible latency, or a somewhat hacky way to store h263 in RFC-2190
  
  rtp encapsulation.
  Moreover when multi-threading is enabled (which is by default) the order
  
  of returned slices is not deterministic at all, making the use of this
  
  function not reliable at all (or at the very least, more complicated
  
  than it should be).
  So, for the reasons stated above, and being used by only a single encoder
  
  family (mpegvideo), this field is deemed unnecessary, overcomplicated,
  
  and not really belonging to libavcodec. Libavformat features a complete
  
  implementation of RFC-2190, for any other case.
  Signed-off-by : Vittorio Giovara <vittorio.giovara@gmail.com>
  

  • [DBH] doc/APIchanges
  • [DBH] libavcodec/avcodec.h
  • [DBH] libavcodec/mpegvideo_enc.c
  • [DBH] libavcodec/version.h

• FFMPEG H264 with custom overlay per frame

  4 octobre 2020, par La bla bla

  We have a stream that is stored in the cloud (Amazon S3) as individual H264 frames. The frames are stored as framexxxxxx.264, the numbering doesn't start from 0 but rather from some larger number, say 1000 (so, frame001000.264)

  &#xA;

  The goal is to create a mp4 clip which is either timelapse or just faster for inspection and other checking (much faster, compressing around 3 hours of video down to < 20 minutes), this also requires we overlay the frame number (the filename) on the frame itself

  &#xA;

  At first I was creating a timelapse by pulling from S3 only the keyframes (i-frames ? still rather new to codecs & stuff) and overlaying the filename on them and saving as png (which probably isn't needed, but that's what I did) using (this command is used inside a python script)

  &#xA;

  ffmpeg -y -i {h264_name} -vf \"scale=1920:-1, 
drawtext=fontfile=/usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-B.ttf:fontsize=34:text={txt}:fontcolor=white:x=50:y=50:bordercolor=black:borderw=2\" 
-c:a copy -pix_fmt yuv420p {basename}.png


  &#xA;

  after this I combined all the frames by using python to convert the lowest numbered frame to 0.png and incrementing (so it would be continuous, because I only used keyframes the numbers originally weren't sequential) and running

  &#xA;

  ffmpeg -y -f image2 -i %d.png -r {self.params.fps} -vcodec libx264 -crf {self.params.crf} -pix_fmt yuv420p {out_file}


  &#xA;

  and this worked great, but the difference between keyframes was too long to allow for proper inspection

  &#xA;

  so now for the question(s)

  &#xA;

  since I know frames that are not keyframes (p-frames ?) can't be used alone by ffmpeg, the method of overlaying the file name and converting it to png (or keep as h264, same thing) won't work, or at least, I couldn't find a way for it to work, maybe there's a way to specify a frame's keyframe ?, how can one overlay the filename (and not the frame number as shown here for example)

  &#xA;

  Also, is it possible to skip some p-frames between the keyframes ? (so if a keyframe is every 30 frames, we would take a keyframe, a frame 15 frames later, and next another keyframe)

  &#xA;

  I thought about using ffmpeg's pipe option to feed it with the files as they're being downloaded, but I'm not sure if I can specify drawtext this way

  &#xA;

  Also, if there's another alternative that can achieve that (at first I was converting to png, using python and OpenCV to add the filename and then merging the pngs to mp4, but then I found drawtext can do that in a single command so I used it)

  &#xA;