Recherche avancée

Sur d’autres sites (4967)

• ffmpeg nvdec not available when adding subtitles to mp4

  17 février 2019, par whatdoineed2do

  I have a mp4 video that I want to BURN-IN subtitles (from a .ass file and via -vf ass=/tmp/conf-notes.ass) with ffmpeg on a machine with a GTX1060 card however ffmpeg reports that it fails to create the NVDEC decoder.

  [h264 @ 0xcb9380] Error creating a NVDEC decoder: 1
  
  [h264 @ 0xcb9380] Failed setup for format cuda: hwaccel initialisation returned error.

  The output file is generated ok but during the creation the CPU is used heavily (I assume for decode) - if I drop the -vf ass=/tmp/conf-notes.ass and perform an mp4->mp4 reencode there are no problems.

  I want to know what I am missing from my command to allow the GPU to perform the decode when an .ass file is added to the chain.

  $ ffmpeg -hwaccel cuvid -i 2019-01-conferance.mp4 -vf ass=/tmp/conf-notes.ass -c:a copy -preset llhq -rc vbr_hq -vb 2M -minrate 500k -maxrate 12M -c:v h264_nvenc export.mp4
  
  ffmpeg version 4.0.2 Copyright (c) 2000-2018 the FFmpeg developers
  
    built with gcc 8 (GCC)
  
    configuration: --arch=x86_64 --bindir=/usr/bin --datadir=/usr/share/ffmpeg --disable-debug --disable-static --disable-stripping --enable-alsa --enable-avfilter --enable-avresample --enable-bzlib --enable-decklink --enable-doc --enable-fontconfig --enable-frei0r --enable-gnutls --enable-gpl --enable-iconv --enable-libass --enable-libbluray --enable-libcdio --enable-libdc1394 --enable-libdrm --enable-libfdk-aac --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libilbc --enable-libkvazaar --enable-libmfx --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenh264 --enable-libopenjpeg --enable-libopus --enable-libpulse --enable-librsvg --enable-librtmp --enable-librubberband --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtesseract --enable-libtheora --enable-libtwolame --enable-libv4l2 --enable-libvidstab --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxcb --enable-libxcb-shm --enable-libxcb-xfixes --enable-libxcb-shape --enable-libxml2 --enable-libxvid --enable-libzvbi --enable-lv2 --enable-lzma --enable-libndi_newtek --enable-nonfree --enable-openal --enable-opencl --enable-opengl --enable-postproc --enable-pthreads --enable-sdl2 --enable-shared --enable-version3 --enable-xlib --enable-zlib --extra-cflags=-I/usr/include/cuda --incdir=/usr/include/ffmpeg --libdir=/usr/lib64 --mandir=/usr/share/man --optflags='-O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection' --prefix=/usr --shlibdir=/usr/lib64 --enable-cuda --enable-cuvid --enable-libnpp --enable-nvdec --enable-nvenc --enable-runtime-cpudetect
  
    libavutil      56. 14.100 / 56. 14.100
  
    libavcodec     58. 18.100 / 58. 18.100
  
    libavformat    58. 12.100 / 58. 12.100
  
    libavdevice    58.  3.100 / 58.  3.100
  
    libavfilter     7. 16.100 /  7. 16.100
  
    libavresample   4.  0.  0 /  4.  0.  0
  
    libswscale      5.  1.100 /  5.  1.100
  
    libswresample   3.  1.100 /  3.  1.100
  
    libpostproc    55.  1.100 / 55.  1.100
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '2019-01-conferance.mp4':
  
    Metadata:
  
      major_brand     : mp42
  
      minor_version   : 0
  
      compatible_brands: isommp42
  
      creation_time   : 2019-01-12T00:00:06.000000Z
  
    Duration: 00:00:24.07, start: 0.000000, bitrate: 11542 kb/s
  
      Stream #0:0(eng): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], 11350 kb/s, 23.98 fps, 23.98 tbr, 24k tbn, 47.95 tbc (default)
  
      Metadata:
  
        creation_time   : 2019-01-12T00:00:07.000000Z
  
        handler_name    : Mainconcept MP4 Video Media Handler
  
        encoder         : AVC Coding
  
      Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 189 kb/s (default)
  
      Metadata:
  
        creation_time   : 2019-01-12T00:00:07.000000Z
  
        handler_name    : Mainconcept MP4 Sound Media Handler
  
  Stream mapping:
  
    Stream #0:0 -> #0:0 (h264 (native) -> h264 (h264_nvenc))
  
    Stream #0:1 -> #0:1 (copy)
  
  Press [q] to stop, [?] for help
  
  [h264 @ 0xcb9380] Error creating a NVDEC decoder: 1
  
  [h264 @ 0xcb9380] Failed setup for format cuda: hwaccel initialisation returned error.
  
  [Parsed_ass_0 @ 0x1241c00] Shaper: FriBidi 1.0.2 (SIMPLE) HarfBuzz-ng 1.7.5 (COMPLEX)
  
  [Parsed_ass_0 @ 0x1241c00] Using font provider fontconfig
  
  [Parsed_ass_0 @ 0x1241c00] Added subtitle file: '/tmp/conf-notes.ass' (2 styles, 101 events)

  The .ass file has been generated from a .srt file via ffmpeg -i foo.srt foo.ass

• Carrierwave-video "Process hung" error while encoding uncompressed video files

  28 avril 2014, par Cramps

  I have an API for a mobile app that accepts video uploads. This app is for both iOS and Android devices, so for video compatibility’s sake these videos are encoded to H.264 once uploaded to the server using carrierwave-video (ffmpeg wrapper gem for Ruby on Rails). Right now this seems to be working, and videos are uploaded and encoded and can be played in both Android and iOS devices. However, sometimes the process hangs while encoding heavy (uncompressed ?) video files, usually 10+ seconds long. This is the output of ffmpeg :

  Failed to transcode with FFmpeg.
  
  Check ffmpeg install and verify video is not corrupt or cut short.
  
  Original error: Process hung. Full output: 

  (That’s it, the full output seems empty.)

  These are the encoding parameters I’m using in my Carrierwave Uploader :

  encode_video(:mp4, custom: '-y -vcodec libx264 -acodec libfaac -vpre ultrafast 2> /home/user/log/ffmpeg.log, resolution: '640x640')

  According to the SuperUser question I linked above a solution would be to encode the video twice, once to AVI for compression(?) and then encode to MP4. I don’t know if that would work, but I don’t know how to do this either in my uploader. I would have to encode the output video file of my first (AVI) encoding process.

  Now that there’s some context, my question is : How can I solve this "Process hung" error ?

  In case the answer to that is to go with this double encoding method suggested, how can I achieve this using Carrierwave-video ?

  One last note is that if I try to encode these videos using ffmpeg straight from command-line the videos encode and playback successfully.

  Thank you for your time !

  PD : Wasn’t sure if I should add ruby-on-rails tag. I’ll remove it if necessary !

  Edit
  This is what I get from ffmpeg -i filename.mp4

  ffmpeg version 0.10.3 Copyright (c) 2000-2012 the FFmpeg developers
  
    built on Apr 30 2013 11:26:53 with gcc 4.5.4
  
    configuration: --prefix=/usr --libdir=/usr/lib64 --shlibdir=/usr/lib64 --mandir=/usr/share/man --enable-shared --cc=x86_64-pc-linux-gnu-gcc --cxx=x86_64-pc-linux-gnu-g++ --ar=x86_64-pc-linux-gnu-ar --optflags='-O2 -march=athlon64 -pipe' --extra-cflags='-O2 -march=athlon64 -pipe' --extra-cxxflags='-O2 -march=athlon64 -pipe' --disable-static --enable-gpl --enable-version3 --enable-postproc --enable-avfilter --disable-stripping --disable-debug --disable-doc --disable-vaapi --disable-vdpau --disable-ffplay --enable-openssl --enable-nonfree --enable-libmp3lame --enable-libvo-aacenc --enable-libvo-amrwbenc --enable-libtheora --enable-libvorbis --enable-libx264 --enable-libxvid --enable-libaacplus --enable-nonfree --enable-libfaac --enable-nonfree --disable-indev=v4l --disable-indev=v4l2 --disable-indev=alsa --disable-indev=oss --disable-indev=jack --disable-outdev=alsa --disable-outdev=oss --disable-outdev=sdl --enable-pthreads --enable-libopencore-amrwb --enable-libopencore-amrnb --enable-libvpx --enable-libope  libavutil      51. 35.100 / 51. 35.100
  
    libavcodec     53. 61.100 / 53. 61.100
  
    libavformat    53. 32.100 / 53. 32.100
  
    libavdevice    53.  4.100 / 53.  4.100
  
    libavfilter     2. 61.100 /  2. 61.100
  
    libswscale      2.  1.100 /  2.  1.100
  
    libswresample   0.  6.100 /  0.  6.100
  
    libpostproc    52.  0.100 / 52.  0.100
  
  
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/home/user/api/uploads/tmp/e54zfghzt9.mp4':
  
  
  
  
  
  Metadata:
  
      major_brand     : isom
  
      minor_version   : 0
  
      compatible_brands: isom3gp4
  
      creation_time   : 2014-04-23 14:56:19
  
    Duration: 00:00:14.27, start: 0.000000, bitrate: 20757 kb/s
  
      Stream #0:0(eng): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 1920x1080, 20993 kb/s, SAR 65536:65536 DAR 16:9, 30 fps, 30 tbr, 90k tbn, 180k tbc
  
  
  
  
  
  Metadata:
  
        creation_time   : 2014-04-23 14:56:19
  
        handler_name    : VideoHandle
  
      Stream #0:1(eng): Audio: aac (mp4a / 0x6134706D), 48000 Hz, stereo, s16, 190 kb/s
  
  
  
  
  
  Metadata:
  
        creation_time   : 2014-04-23 14:56:19
  
        handler_name    : SoundHandle

  Then it just starts buffering as such :

  time=00:00:13.20 bitrate=2533.2kbits/s    
  
  frame=  405 fps=  7 q=24.0 size=    4083kB time=00:00:13.20 bitrate=2533.2kbits/s    
  
  frame=  407 fps=  7 q=24.0 size=    4083kB time=00:00:13.20 bitrate=2533.2kbits/s    
  
  frame=  409 fps=  7 q=24.0 size=    4083kB time=00:00:13.20 bitrate=2533.2kbits/s    
  
  frame=  412 fps=  7 q=24.0 size=    4083kB time=00:00:13.20 bitrate=2533.2kbits/s    
  
  frame=  417 fps=  7 q=24.0 size=    4083kB time=00:00:13.20 bitrate=2533.2kbits/s    
  
  frame=  417 fps=  7 q=24.0 Lsize=    4194kB time=00:00:13.90 bitrate=2471.5kbits/s    
  
  video:3957kB audio:223kB global headers:0kB muxing overhead 0.310939%
  
  [libx264 @ 0x7f28327ccc50] frame I:2     Avg QP:21.50  size: 25120
  
  [libx264 @ 0x7f28327ccc50] frame P:415   Avg QP:25.32  size:  9642
  
  [libx264 @ 0x7f28327ccc50] mb I  I16..4: 35.8%  0.0% 64.2%
  
  [libx264 @ 0x7f28327ccc50] mb P  I16..4:  8.4%  0.0%  3.2%  P16..4: 43.6% 19.0%  5.6%  0.0%  0.0%    skip:20.2%
  
  [libx264 @ 0x7f28327ccc50] coded y,uvDC,uvAC intra: 45.2% 53.6% 27.3% inter: 39.4% 27.6% 2.7%
  
  [libx264 @ 0x7f28327ccc50] i16 v,h,dc,p: 28% 57% 11%  5%
  
  [libx264 @ 0x7f28327ccc50] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 14% 66% 11%  1%  1%  1%  2%  1%  2%
  
  [libx264 @ 0x7f28327ccc50] i8c dc,h,v,p: 23% 58% 17%  3%
  
  [libx264 @ 0x7f28327ccc50] kb/s:2331.88

  `

• Generating test data – Introducing the Piwik Platform

  9 octobre 2014, par Thomas Steur — Development

  This is the next post of our blog series where we introduce the capabilities of the Piwik platform (our previous post was How to create a command). This time you’ll learn how to generate test data.

  Developers are developing on their local Piwik instance which usually does not contain useful data compared to a real Piwik installation in production (only a few test visits and a few tests users and websites). The ‘VisitorGenerator’ plugin lets you generate any number of visits, websites, users, goals and more. The generator makes sure there will be data for each report so you can easily test anything.

  Getting started

  In this series of posts, we assume that you have already installed Piwik. If not, visit the Piwik Developer Zone where you’ll find the Installation guide for developers.

  Installing the VisitorGenerator plugin

  The easiest way to install the plugin is by using the Marketplace in Piwik itself. It is accessible via Settings => Marketplace => Get new functionality. There you’ll find the plugin “VisitorGenerator” which you can install and activate in one click.

  If your Piwik instance is not connected to the internet you can download the plugin from the VisitorGenerator page on the Marketplace. Afterwards you can install the plugin by going to Settings => Marketplace => Uploading a plugin and uploading the previously downloaded ZIP file.

  If you have already installed the plugin make sure it is activated by going to Settings => Plugins.

  Generating websites

  After you have installed the plugin you can add as many websites as you need. This is useful for instance when you want to test something that affects many websites such as the ‘All Websites’ dashboard or the Websites manager. To generate any number of websites use the following command :

  ./console visitorgenerator:generate-website --limit=10

  This will generate 10 websites. If you need more websites simply specify a higher limit. In case you are wondering the names and URLs of the websites are randomly generated by the Faker PHP library.

  Generating goals

  In case you want to test anything related to Goals you should execute the following command :

  ./console visitorgenerator:generate-goals --idsite=1

  This will generate a few goals for the specified site. The generated goals are defined in a way to make sure there will be conversions when generating the visits in the next step.

  Generating visits

  To generate visits there are two possibilities. Either via the Piwik UI by going to Settings => Visitor Generator or by using the command line. The UI is a bit limited in generating visits so we recommend to use the command line. There you can generate visits as follows :

  ./console visitorgenerator:generate-visits --idsite=1

  This will generate many different visits for the current day. Don’t worry if it takes a while, it will insert quite a few visits by default.

  In case you want to generate visits for multiple days in the past as well you can specify the --days option.

  ./console visitorgenerator:generate-visits --idsite=1 --days=5

  Providing your own logs

  Half of the generated visits are randomly generated and half of the visits are based on real logs to make sure there is data for each report. If you want to generate visits based on your own logs for a more realistic testing just place your log files in the plugins/VisitorGenerator/data folder and make sure the file name ends with .log. You can find a few examples in the VisitorGenerator data folder.

  To generate visits based only on real log files then use the --no-fake option.

  ./console visitorgenerator:generate-visits --idsite=1 --no-fake

  All generated visits will come from the logs and no random visits nor random fake data will be used.

  Advanced features

  We are regularly adding new commands, tools and runtime checks to make your life as a developer easier. For instance you can also generate users and annotations. In the future we want to extend the plugin to create visits in the background to make sure there will be constantly new actions in the real time report.

  Are you missing any kind of generator or any other feature to make your life as a developer easier ? Let us know by email, we are listening !

  Would you like to know more about the Piwik platform ? Go to our Piwik Developer Zone where you’ll find guides and references on how to develop plugin and themes.