Recherche avancée

Sur d’autres sites (10148)

• Can't Titan Black use NVENC ?

  13 mars 2016, par SPWW

  I compiled FFMPEG with —enable-nvenc and want to encode with NVENC encoder, but I got this error message when running ffmpeg.

  [nvenc_h264 @ 0x8ed020] 4 CUDA capable devices found
  
  [nvenc_h264 @ 0x8ed020] [ GPU #0 - < GeForce GTX TITAN Black > has Compute SM 3.5, NVENC Not Available ]
  
  [nvenc_h264 @ 0x8ed020] [ GPU #1 - < GeForce GTX TITAN Black > has Compute SM 3.5, NVENC Not Available ]
  
  [nvenc_h264 @ 0x8ed020] [ GPU #2 - < GeForce GTX TITAN Black > has Compute SM 3.5, NVENC Not Available ]
  
  [nvenc_h264 @ 0x8ed020] [ GPU #3 - < GeForce GTX TITAN Black > has Compute SM 3.5, NVENC Not Available ]
  
  [nvenc_h264 @ 0x8ed020] No NVENC capable devices found

  I have titan black gpu and as the official document said it should be supported.

  my nvenc-sdk version is 5.0

  and the nvidia-smi info is listed below.

  ~> nvidia-smi
  
  Wed Jan  6 16:36:55 2016
  
  +------------------------------------------------------+
  
  | NVIDIA-SMI 352.39     Driver Version: 352.39         |
  
  |-------------------------------+----------------------+----------------------+
  
  | GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
  
  | Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
  
  |===============================+======================+======================|
  
  |   0  GeForce GTX TIT...  Off  | 0000:02:00.0     Off |                  N/A |
  
  | 54%   82C    P2   215W / 250W |   4422MiB /  6143MiB |     77%      Default |
  
  +-------------------------------+----------------------+----------------------+
  
  |   1  GeForce GTX TIT...  Off  | 0000:04:00.0     Off |                  N/A |
  
  | 55%   82C    P2   160W / 250W |   5926MiB /  6143MiB |     84%      Default |
  
  +-------------------------------+----------------------+----------------------+
  
  |   2  GeForce GTX TIT...  Off  | 0000:83:00.0     Off |                  N/A |
  
  | 58%   83C    P2   147W / 250W |   5926MiB /  6143MiB |     68%      Default |
  
  +-------------------------------+----------------------+----------------------+
  
  |   3  GeForce GTX TIT...  Off  | 0000:84:00.0     Off |                  N/A |
  
  | 53%   83C    P2   191W / 250W |   3155MiB /  6143MiB |     85%      Default |
  
  +-------------------------------+----------------------+----------------------+

• avformat/dashenc : Added support for Low-latency HLS(Experimental)

  12 décembre 2018, par kjeyapal@akamai.com

  avformat/dashenc : Added support for Low-latency HLS(Experimental)
  Apple doesn't have an official spec for LHLS. Meanwhile hls.js player folks are
  
  trying to standardize a open LHLS spec. The draft spec is available in https://github.com/video-dev/hlsjs-rfcs/blob/lhls-spec/proposals/0001-lhls.md
  
  This option will also try to comply with the above open spec, till Apple's spec officially supports it.
  
  Applicable only when @varstreaming and @varhls_playlist options are enabled.
  

  • [DH] doc/muxers.texi
  • [DH] libavformat/dashenc.c

• FFMPEG memory leak on FLV video frame decoding

  10 août 2014, par Michael IV

  I am decoding FLV video on Windows using FFMPEG latest dev version(20140810) .Monitoring memory consumption of my program process I found the memory footprint constantly increasing.I do packet deallocation and also tried to delete and then reallocate the AVFrame anew on each decode.But it doesn’t help.I read on some threads people pointing out there is an internal memory leak in H264 decoder but I have seen no official confirmation of it nor any solution.
  Here is how I decode a frame :

  AVPacket packet;
  
  av_read_frame(_ifmt_ctx, &packet);
  
  
  
  if (packet.stream_index == _in_video_stream->index) 
  
  {
  
      int isGotVideoFrame = 0;
  
  
  
      // Decode video frame
  
      ret = avcodec_decode_video2(_dec_in_video_ctx, _src_video_frame,
  
                     &isGotVideoFrame, &packet);
  
  
  
      if (1 == isGotVideoFrame) 
  
      {
  
          sws_scale(_sws_ctx, (const uint8_t * const*) _src_video_frame->data,
  
                    _src_video_frame->linesize, 0,_inVideoHeight, 
  
                    _dst_video_frame->data, _dst_video_frame->linesize);
  
  
  
          uint8_t* dest = new uint8_t[_numBytes];
  
          memcpy(dest, _dst_video_frame->data[0], _numBytes);
  
  
  
          av_free_packet(&packet);
  
          _frames_cache.push_back(dest);
  
      }
  
  
  
      av_frame_unref(_src_video_frame);
  
      av_frame_free(&_src_video_frame);
  
      _src_video_frame = av_frame_alloc();
  
  }

  Then in another place on each frame I delete ’dest’ from the vector :

      uint8_t * fr = _frames_cache.front();
  
      _frames_cache.erase(_frames_cache.begin());
  
      delete [] fr ;