Recherche avancée

Sur d’autres sites (9607)

• Image files as inputs with AWS Elastic Transcoder ?

  7 décembre 2017, par Geuis

  Here’s my situation. I’ve been working on building a service at work that takes dynamically generated images and outputs animations as mp4 or gif. The user has the options of setting dimensions, time for each frame, etc.

  I have this working currently with ffmpeg. It works ok, but is difficult (and potentially expensive) to scale due largely to the cpu/memory requirements that ffmpeg needs.

  I just spent some time experimenting with AWS’s Elastic Transcoder. It doesn’t seem to like static image files (jpg, png) as source material in jobs. The file types aren’t listed under the available Preset options either.

  I’m sure that I could adapt the existing architecture to save the static images as video files (sound isn’t needed) and upload those. That will still require ffmpeg to be in the pipeline though.

  Are there any other AWS services that might work with my needs and allow the use of Elastic Transcoder ?

• Improve LPC order guess

  3 décembre 2014, par Martijn van Beurden

  Improve LPC order guess
  The recent compression preset retuning improved upon most material
  
  but it the few tracks that show regression are usually classical
  
  music. This patch improves compression by improving the LPC order
  
  guess, of which classical music benefits most.
  Improvement is 0.007% on average but up to 0.1%. I haven’t seen
  
  regressions for any of my test samples.
  Signed-off-by : Erik de Castro Lopo <erikd@mega-nerd.com>
  

  • [DH] src/libFLAC/lpc.c

• Revision effd974b16 : Limit arf interval for low fpf clips. This patch limits the maximum arf interv

  16 avril 2015, par paulwilkins

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

  
   Modify /vp9/encoder/vp9_ratectrl.c

  
  
  Limit arf interval for low fpf clips.

  This patch limits the maximum arf interval length to
  approximately half a second. In some low fps animations in
  particular the existing code was selecting an overly long interval
  which was hurting visual quality. For a sample problem test clip
  (360P animation , 15fps, 200Kbit/s) this change also improved
  metrics by >0.5 db.

  There may be some clips where this hurts metrics a little, but the
  worst case impact visually is likely to be less than having an
  interval that is much too long. On more normal material at 24
  fps or higher, the impact is likely to be nil/minimal.

  Change-Id : Id8b57413931a670c861213ea91d7cc596375a297