Recherche avancée

Sur d’autres sites (5692)

• Generate a thumbnail from a stream with NodeJs

  12 octobre 2020, par Pedro Zenha

  So I've been banging my head with this issue that I'm facing at the moment. Basically my Node API is handling video/images upload and saving those to a S3 bucket. What I want to do now is generate a thumbnail for each of the uploaded videos and also save them to the S3.

  


  I'm using FFMPEG to generate the thumbnails, more specifically the 'simple-thumbnail' package [https://github.com/ScottyFillups/simple-thumbnail][1]

  


  The problem is that I cannot pass a readable Stream as an argument, if I pass the S3 URL for the video it generates the thumbnail but if I pass the input stream of the same video it just gets stuck with no errors. Also FFMPEG does not accept readable Streams to its method "screenshots" that is meant to generate thumbnails.

  


  thumbS3 = createWriteStorage(`tmp/thumbnail-${upload._id}-${filename}`, {'Content-Type': 'image/png'})
   try{
     await genThumbnail(source,thumbS3,'250x?')
   }catch(err){
     console.log(err)
   }


  


  I also tried the following according to the package documentation :

  


  source.pipe(genThumbnail(null,null,'250x?')).pipe(thumbS3)


  


  But get the following error :

  


  Error: write EPIPE
    at WriteWrap.onWriteComplete [as oncomplete] (internal/stream_base_commons.js:92:16)
Emitted 'error' event on Duplexify instance at:
    at errorOrDestroy (internal/streams/destroy.js:108:12)
    at Duplexify.onerror (_stream_readable.js:752:7)
    at Duplexify.emit (events.js:315:20)
    at Duplexify.EventEmitter.emit (domain.js:483:12)


  


  I also tried using only FFMPEG but dont really understand why it doesnt work and why it doesnt return any type of error

  


  const args = [
    '-vframes 1',
    `~/output/image4.jpg`
  ]
   ffmpeg(input)
  .inputOptions(args)
  .then((thumb) => console.log(thumb))
  .catch((err) => console.log(err))


  


  If someone knows how to work with readable streams to generate thumbails I would appreciate a lot. Thank you
[1] : https://github.com/ScottyFillups/simple-thumbnail

  


• doc/developer : revise mailing list section

  4 décembre 2017, par Jim DeLaHunt

  doc/developer : revise mailing list section
  The Developer Documentation had instructions to
  
  subscribe to the ffmpeg-cvslog email list. But that is
  
  no longer accurate. For the purposes in this section —
  
  review of patches, discussion of development issues —
  
  ffmpeg_devel is the appropriate email list. Some developers
  
  may want to monitor ffmpeg-cvslog, but it is not mandatory.
  This is v3 of this doc, based on discussion in thread
  
  <https://ffmpeg.org/pipermail/ffmpeg-devel/2017-November/220528.html> ;
  
  and in response to docs Maintainer comments in
  
  <https://ffmpeg.org/pipermail/ffmpeg-devel/2017-December/221596.html>.
  1. In doc/developer.texi, add a new section about
  
  ffmpeg-devel, based on existing text from ffmpeg-cvslog
  
  section regarding discussion of patches and of
  
  development issues. Reflect wording from discussion at
  
  <https://ffmpeg.org/pipermail/ffmpeg-devel/2017-November/221199.html> ;
  
  but with copy-editing to make wording more concise.
  2. In doc/developer.texi, rewrite the ffmpeg-cvslog section
  
  to match the current usage of ffmpeg-cvslog. Some
  
  developers choose to follow this list, but it is not
  
  mandatory.
  There are a lot of improvements possible to the
  
  Developer Documentation page, beyond this refactoring.
  
  However, making those improvements is a much bigger
  
  and more difficult task.  This change is "low hanging
  
  fruit".
  Signed-off-by : Jim DeLaHunt <from.ffmpeg-dev@jdlh.com>
  
  Signed-off-by : Timothy Gu <timothygu99@gmail.com>
  

  • [DH] doc/developer.texi

• Revision f295774d43 : vp9_rd_pick_inter_mode_sb : fix uninitialized value 'skippable' can remain unset

  10 août 2013, par James Zern

  Changed Paths :
   Modify /vp9/encoder/vp9_rdopt.c

  
  
  vp9_rd_pick_inter_mode_sb : fix uninitialized value

  'skippable' can remain unset and negatively affect later decisions

  address one aspect of issue #599

  Change-Id : Iffdf0ac2e49ac481c27dc27c87fa546d4167bb28