Recherche avancée

Sur d’autres sites (12830)

• sws_scale screws up last pixel row in smaller x264 mp4 encoding

  23 juillet 2012, par TheSHEEEP

  I am muxing pictures in the PIX_FMT_ARGB format into an mp4 video.

  All of it works well, except that the last pixel row of the outgoing image is screwed up, in most cases the last row is completely black, sometimes there are other colors, it seems somehow dependant on the machine it runs on.

  I am absolutely sure that the error must be in sws_scale, as I am saving the images before and after the scaling. The input images do not have the error, but after the sws_scale() I save the yuv image and the error is apparent.

  Here is an example :

  Original

  

  Yuvfile (after sws_scale)

  

  At the bottom of the Yuvfile, you will see the black row.

  This is how I do the scaling (it is after the official ffmpeg examples, more or less) :

  static int sws_flags = SWS_FAST_BILINEAR | SWS_ACCURATE_RND;
  
  
  
  if (img_convert_ctx == NULL)
  
  {
  
     img_convert_ctx = sws_getContext( srcWidth, srcHeight,
  
             PIX_FMT_ARGB,
  
             codecContext->width, codecContext->height,
  
             codecContext->pix_fmt,
  
             sws_flags, NULL, NULL, NULL );
  
     if (img_convert_ctx == NULL)
  
     {
  
        av_log(c, AV_LOG_ERROR, "%s","Cannot initialize the conversion context\n");
  
        exit(1);
  
     }
  
  }
  
  fill_image(tmp_picture, pic, pic_size, frame_count, ptr->srcWidth, ptr->srcHeight );
  
  
  
  sws_scale(img_convert_ctx, tmp_picture->data, tmp_picture->linesize,
  
          0, srcHeight, picture->data, picture->linesize);

  I also tried a number of different SWS_ flags, but all yield the same result.

  Could this be a bug in sws_scale or am I doing something wrong ? I am using the latest version of the ffmpeg libraries.

• ffmpeg - Unrecognized option lavfi_complex

  4 février 2019, par Milan

  I’m working with headphone filter command from official documentation - https://ffmpeg.org/ffmpeg-filters.html#Examples-20

  ffmpeg -i input.wav -lavfi-complex "amovie=azi_270_ele_0_DFC.wav[sr],amovie=azi_90_ele_0_DFC.wav[sl],amovie=azi_225_ele_0_DFC.wav[br],amovie=azi_135_ele_0_DFC.wav[bl],amovie=azi_0_ele_0_DFC.wav,asplit[fc][lfe],amovie=azi_35_ele_0_DFC.wav[fl],amovie=azi_325_ele_0_DFC.wav[fr],[a:0][fl][fr][fc][lfe][bl][br][sl][sr]headphone=FL|FR|FC|LFE|BL|BR|SL|SR"
  
  output.wav

  but I’m getting error

   Unrecognized option 'lavfi-complex'.

  Here is my ffmpeg version info -

  ffmpeg -version
  
  ffmpeg version N-92377-g0c6d4e7ba4 Copyright (c) 2000-2018 the FFmpeg developers
  
  built with gcc 8.2.1 (GCC) 20181017
  
  configuration: --enable-gpl --enable-version3 --enable-sdl2 --enable-fontconfig --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libtheora --enable-libtwolame --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libzimg --enable-lzma --enable-zlib --enable-gmp --enable-libvidstab --enable-libvorbis --enable-libvo-amrwbenc --enable-libmysofa --enable-libspeex --enable-libxvid --enable-libaom --enable-libmfx --enable-amf --enable-ffnvcodec --enable-cuvid --enable-d3d11va --enable-nvenc --enable-nvdec --enable-dxva2 --enable-avisynth
  
  libavutil      56. 23.101 / 56. 23.101
  
  libavcodec     58. 39.100 / 58. 39.100
  
  libavformat    58. 22.100 / 58. 22.100
  
  libavdevice    58.  6.100 / 58.  6.100
  
  libavfilter     7. 43.100 /  7. 43.100
  
  libswscale      5.  4.100 /  5.  4.100
  
  libswresample   3.  4.100 /  3.  4.100
  
  libpostproc    55.  4.100 / 55.  4.100

• NVidia driver libraries in nvidia/cuda image

  16 février 2018, par Islam Sabyrgaliyev

  I want to run ffmpeg with cuvid hw-accelerated decoding in the container based on official nvidia/cuda image. Ffmpeg is not able to find libnvcuvid.so, although there are all required cuda libs.
  The output of ldconfig -p | grep libnv from the container :

  libnvrtc.so (libc6,x86-64) => /usr/local/cuda-9.0/targets/x86_64-linux/lib/libnvrtc.so
  
  libnvrtc-builtins.so (libc6,x86-64) => /usr/local/cuda-9.0/targets/x86_64-linux/lib/libnvrtc-builtins.so
  
  libnvidia-ptxjitcompiler.so.1 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libnvidia-ptxjitcompiler.so.1
  
  libnvidia-opencl.so.1 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libnvidia-opencl.so.1
  
  libnvidia-ml.so.1 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libnvidia-ml.so.1
  
  libnvidia-fatbinaryloader.so.390.12 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libnvidia-fatbinaryloader.so.390.12
  
  libnvidia-compiler.so.390.12 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libnvidia-compiler.so.390.12
  
  libnvidia-cfg.so.1 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libnvidia-cfg.so.1
  
  libnvgraph.so (libc6,x86-64) => /usr/local/cuda-9.0/targets/x86_64-linux/lib/libnvgraph.so
  
  libnvblas.so (libc6,x86-64) => /usr/local/cuda-9.0/targets/x86_64-linux/lib/libnvblas.so
  
  libnvToolsExt.so (libc6,x86-64) => /usr/local/cuda-9.0/targets/x86_64-linux/lib/libnvToolsExt.so

  Should I just copy libnvcuvid.so from the host ? Wouldn’t it break if underlying driver version changes ?