Recherche avancée

Sur d’autres sites (8682)

• avcodec/vc1dec : Re-order init to avoid initting hwaccel too early

  8 août 2015, par Philip Langdale

  avcodec/vc1dec : Re-order init to avoid initting hwaccel too early
  At least for vdpau, the hwaccel init code tries to check the video
  
  profile and ensure that there is a matching vdpau profile available.
  If it can’t find a match, it will fail to initialise.
  In the case of wmv3/vc1, I observed initialisation to fail all the
  
  time. It turns out that this is due to the hwaccel being initialised
  
  very early in the codec init, before the profile has been extracted
  
  and set.
  Conceptually, it’s a simple fix to reorder the init code, but it gets
  
  messy really fast because ff_get_format(), which is what implicitly
  
  trigger hwaccel init, is called multiple times through various shared
  
  init calls from h263, etc. It’s incredibly hard to prove to my own
  
  satisfaction that it’s safe to move the vc1 specific init code
  
  ahead of this generic code, but all the vc1 fate tests pass, and I’ve
  
  visually inspected a couple of samples and things seem correct.
  Signed-off-by : Philip Langdale <philipl@overt.org>
  

  • [DH] libavcodec/vc1dec.c

• How can I learn the effective quality of the h264_nvenc encoder ?

  24 septembre 2020, par pfdint2

  I seek to ascertain the end-product quality of various cq ("constant quality") values for the h264_nvenc video encoder.

  


  To use the h264_nvenc encoder through ffmpeg and with a target quality, I follow the instructions in Nvidia's documentation, last paragraph of the linked anchor.

  


  I specify a Variable Bit Rate rate control mode (rc=vbr_hq) and a target quality (cq=). This should be enough to test various values of cq. The story should end there.

  


  HOWEVER, that only outputs the same perfect quality video of extremely large size for any cq value. (Using cq=1, cq=20, and cq=51 all output a file with the same hash.)

  


  Per documentation, I can also specify a maxBitRate (maxrate=). If I don't specify a maxrate, the documentation indicates :

  


  


  If maxBitRate is not specified, the encoder will use as many bits as needed to achieve the target quality.

  


  


  But that's not the behavior I'm observing. I'm seeing the encoder use as many bits as possible, not as many bits as needed. The resultant video has an overall bitrate of 100Mb/s. Double the source video.

  


  If I do set a maxrate, it is observed by the encoder. But if I have to set the bitrate correctly for every cq value, what is the point of the cq value ? I would just set cq=1 and test various bitrates, which would then only be applicable to a specific video.

  


  Is there some warning or output that notes that the bitrate was insufficient to reach the target quality that I'm not seeing ? That would at least allow me to brute force this.

  


  Or am I misunderstanding the relationship between these settings ?

  


• How can I learn the effective quality of the h264_nvenc encoder ?

  24 septembre 2020, par pfdint2

  I seek to ascertain the end-product quality of various cq ("constant quality") values for the h264_nvenc video encoder.

  


  To use the h264_nvenc encoder through ffmpeg and with a target quality, I follow the instructions in Nvidia's documentation, last paragraph of the linked anchor.

  


  I specify a Variable Bit Rate rate control mode (rc=vbr_hq) and a target quality (cq=). This should be enough to test various values of cq. The story should end there.

  


  HOWEVER, that only outputs the same perfect quality video of extremely large size for any cq value. (Using cq=1, cq=20, and cq=51 all output a file with the same hash.)

  


  Per documentation, I can also specify a maxBitRate (maxrate=). If I don't specify a maxrate, the documentation indicates :

  


  


  If maxBitRate is not specified, the encoder will use as many bits as needed to achieve the target quality.

  


  


  But that's not the behavior I'm observing. I'm seeing the encoder use as many bits as possible, not as many bits as needed. The resultant video has an overall bitrate of 100Mb/s. Double the source video.

  


  If I do set a maxrate, it is observed by the encoder. But if I have to set the bitrate correctly for every cq value, what is the point of the cq value ? I would just set cq=1 and test various bitrates, which would then only be applicable to a specific video.

  


  Is there some warning or output that notes that the bitrate was insufficient to reach the target quality that I'm not seeing ? That would at least allow me to brute force this.

  


  Or am I misunderstanding the relationship between these settings ?