Recherche avancée

Sur d’autres sites (6852)

• Revision 478fbc8f23 : Update to speed 5 non-rd mode partition search. If the pre-selected partition s

  7 juillet 2015, par Marco

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

  
  
  Update to speed 5 non-rd mode partition search.

  If the pre-selected partition size (from variance partition) is
  32x32, also apply nonrd partition search for 32x32 and 16x16 size.

  Overall small positive gain in metrics, average 1%.
  Some visual improvement, for lower resolutions.

  Change-Id : I69cb425bda94f7d13d34c451ab30e9276335a30e

• ffmpeg status & quality / cuda (CPU/GPU)

  18 avril 2015, par cocco

  ffmpeg am i doing it right ?

  So much time has passed since i use ffmpeg to convert clips on my home web server, now that mp4 (h264 & aac) is the current overall standard (works on every console, smartphone, smartTV, pc) i decided to convert my old clips from various digital cameras to to this new container/codecs.

  1. less space & the same quality.
  2. compatibility
  3. support for tags (subler for mac)

  after some research i opted for ffmpeg because of various reasons

  1. commandline (i made my simple web interface with default settings wich i execute with php’s exec)
  2. the quality/size amount

  I read that many expensive video conversion softwares are not able to handle low bitrate videos properly. I also tested some of them and personally i could not find the proper export settings or i was not impressed by the results... some had fixed default export setings, most had a lower video quality at the same filesize. ffmpeg allows me to set the -crf (18-24 usually) and -preset (veryslow, fast..) witch allows me to reduce the filesize drastically mantaining the same
  visible quality.

  Said that i’m using the preset at veryslow.(there is also placebo but the final video file is only 1% smaller in size).

  And here is the command i use

  ffmpeg
  
  -y //overwrite the file if it exists
  
  
  
  -i INPUTFILE // replace with the input file
  
  
  
  -metadata title=THETITLE // set a nice title, visible on modern devices
  
  -metadata date=THEDATE // set a nice title, visible on modern devices
  
  
  
  -c:v libx264 // use the h264 codec
  
   -crf 21 // try different numbers between 18-26
  
   -preset veryslow // placebo,slow,fast,ultrafast==big file 
  
   -tune film // tune it a little
  
   -pix_fmt yuv420p // preferred on most modern devices
  
   -profile:v main // preferred on most modern devices
  
   -level 3.1 // preferred on most modern devices 
  
   -refs 4 // preferred on most modern devices
  
  
  
  -c:a libfdk_aac // use aac
  
   -metadata:s:a language=eng // set a language, visible on modern devices 
  
   -b:a 128k // audio bitrate 128k is like mp3 192k
  
   -ar 48000 // 44100 ... whatever
  
   -ac 2 // audiochannels
  
   -movflags +faststart //move the metadata in the front of the video so it loads faster
  
  
  
  OUTPUTFILE

  some camcorder clips with m2ts already have the avc/h264 compatible codec so i just copy the stream.
  some have the ac3/dolby sorround audio. I convert the audio but keep the ac3 as second audio track mapping the ffmpeg streams.this allows me to watch the mp4 on browsers and mobile devices but i’m able to keep the surround sound to playback on some tv’s, advanced media players or devices like apple tv.

  not that i’m not happy with the speed (using quad core’s) but i recently read again about cuda opencl and there is also the simple fact that i’m not using other converters than ffmpeg since alot of time.

  Is ffmpeg (with the setting i use) a good converter to keep the same video quality than the source reducing the space occupied by and average of 30-40% ?

  Is GPU conversion really that bad (cuda .. testing a gtx970) ?
  it would be nice to add some more speed to the conversions by using both the gpu and the cpu..but for my understanding they cannot work together ??? and using only gpu is a drastical quality loss...cpu si more precise, gpu is faster in calculation are too imprecise from what i read.. so expensive softwares use cuda only for preview purpose... right ?

  Is ffmpeg or another software compatible with CPU+GPU encoding ?
  i really don’t remember where, but i read that the ffmpeg is not a good videoconverter.

  i’m really happy with the size/quality, i gained an average of 30% in space with no visible quality loss. With some extra parameters i can adjust some really old analog videos that are deinterlaced in a really bad way.

  maybe i could gain more size/quality with another software ???

  note : i like ffmpeg.it’s free and it has commandline so i can create my own interface with php html & js and use it on various machines without the need to install it in every device i use. i uplad the idevice clips directly to the ffmpeg server.

  btw. : explain the downvotes...

  EDIT :

  @talonmies ...cuda tag removed :

  http://www.nvidia.com/object/cuda_home_new.html

  CUDA® is a parallel computing platform and programming model invented
  by NVIDIA. It enables dramatic increases in computing performance by
  harnessing the power of the graphics processing unit (GPU). With
  millions of CUDA-enabled GPUs sold to date, software developers,
  scientists and researchers are finding broad-ranging uses for GPU
  computing with CUDA. Here are a few examples : - See more at :
  http://www.nvidia.com/object/cuda_home_new.html#sthash.dEYaqae7.dpuf

  isn’t cuda the programming model that a theoretical ffmpeg library should support to handle GPU encoding on nvidia cards like the gtx 970 ?? like the badaboom software http://www.geforce.com/games-applications/pc-applications/badaboom-media-converter.

• Revision 9349a28e80 : Enable mode search threshold update in non-RD coding mode Adaptively adjust the

  28 octobre 2014, par Jingning Han

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

  
   Modify /vp9/encoder/vp9_rd.c

  
   Modify /vp9/encoder/vp9_rd.h

  
   Modify /vp9/encoder/vp9_rdopt.c

  
   Modify /vp9/encoder/vp9_speed_features.c

  
  
  Enable mode search threshold update in non-RD coding mode

  Adaptively adjust the mode thresholds after each mode search round
  to skip checking less likely selected modes. Local tests indicate
  5% - 10% speed-up in speed -5 and -6. Average coding performance
  loss is -1.055%.

  speed -5
  vidyo1 720p 1000 kbps
  16533 b/f, 40.851 dB, 12607 ms -> 16556 b/f, 40.796 dB, 11831 ms

  nik 720p 1000 kbps
  33229 b/f, 39.127 dB, 11468 ms -> 33235 b/f, 39.131 dB, 10919 ms

  speed -6
  vidyo1 720p 1000 kbps
  16549 b/f, 40.268 dB, 10138 ms -> 16538 b/f, 40.212 dB, 8456 ms

  nik 720p 1000 kbps
  33271 b/f, 38.433 dB, 7886 ms -> 33279 b/f, 38.416 dB, 7843 ms

  Change-Id : I2c2963f1ce4ed9c1cf233b5b2c880b682e1c1e8b