Recherche avancée

Sur d’autres sites (16728)

• FFMpeg No such filter (filter empty) ... how to know it ?

  14 septembre 2015, par FlamingMoe

  I’m trying to resize a video to 480pixels ... I have no problems with a lot of videos converted before with same command, but with this specific video I’m getting an error in which there’s no clue to know what filter refers to.

  $ /usr/local/bin/ffmpeg -y -i 20140530_094843.mp4 -vf ",scale=480:trunc(ow/a/2)*2"  20140530_094843_480.mp4
  
  ffmpeg version 2.2.4-tessus Copyright (c) 2000-2014 the FFmpeg developers
  
    built on Jun 29 2014 16:35:46 with clang version 3.3 (tags/RELEASE_33/final)
  
    configuration: --cc=/opt/local/bin/clang-mp-3.3 --prefix=/Users/tessus/data/ext/ffmpeg/sw --as=yasm --extra-version=tessus --disable-shared --enable-static --disable-ffplay --enable-gpl --enable-pthreads --enable-postproc --enable-libmp3lame --enable-libtheora --enable-libvorbis --enable-libx264 --enable-libx265 --enable-libxvid --enable-libspeex --enable-bzlib --enable-zlib --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libxavs --enable-version3 --enable-libvo-aacenc --enable-libvo-amrwbenc --enable-libvpx --enable-libgsm --enable-libopus --enable-libmodplug --enable-fontconfig --enable-libfreetype --enable-libass --enable-libbluray --enable-filters --disable-indev=qtkit --enable-runtime-cpudetect
  
    libavutil      52. 66.100 / 52. 66.100
  
    libavcodec     55. 52.102 / 55. 52.102
  
    libavformat    55. 33.100 / 55. 33.100
  
    libavdevice    55. 10.100 / 55. 10.100
  
    libavfilter     4.  2.100 /  4.  2.100
  
    libswscale      2.  5.102 /  2.  5.102
  
    libswresample   0. 18.100 /  0. 18.100
  
    libpostproc    52.  3.100 / 52.  3.100
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '20140530_094843.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 0
  
      compatible_brands: isom3gp4
  
      creation_time   : 2014-05-30 07:49:24
  
    Duration: 00:00:39.51, start: 0.000000, bitrate: 2705 kb/s
  
      Stream #0:0(eng): Video: h264 (Baseline) (avc1 / 0x31637661), yuv420p, 640x480, 2655 kb/s, SAR 1:1 DAR 4:3, 25.98 fps, 52.08 tbr, 90k tbn, 180k tbc (default)
  
      Metadata:
  
        rotate          : 180
  
        creation_time   : 2014-05-30 07:49:24
  
        handler_name    : VideoHandle
  
      Stream #0:1(eng): Audio: aac (mp4a / 0x6134706D), 48000 Hz, mono, fltp, 62 kb/s (default)
  
      Metadata:
  
        creation_time   : 2014-05-30 07:49:24
  
        handler_name    : SoundHandle
  
  [AVFilterGraph @ 0x101f0a260] No such filter: ''
  
  Error opening filters!
  
  Conversion failed!

  I’ve been looking but other people reports always shows an specific filter, but I have no filter in "No such filter ’’" message

• Webm streaming issue with ffmpeg/ffserver

  10 octobre 2014, par ihnatkuk

  I am trying to play the stream from ip camera in the browser. I am using ffmpeg and ffserver stack for that (both 2.4.2).

  For now I can easily play video stream in browser using flash. But I would like to have ability to play it in native html5 player. And I need webm format to do that.

  ffserver config snippet :

   <feed>
  
  File /tmp/0_webm.ffm
  
  FileMaxSize 5M
  
  ACL allow localhost
  
  </feed>
  
  
  
  <stream>
  
  Feed 0_webm.ffm
  
  Format webm
  
  NoAudio
  
  </stream>
  
  
  
  <stream>
  
  Feed feed2.ffm
  
  Format swf
  
  VideoCodec flv
  
  VideoFrameRate 30
  
  VideoBufferSize 50000
  
  VideoBitRate 100
  
  VideoQMin 1
  
  VideoQMax 5
  
  VideoSize 352x288
  
  PreRoll 0
  
  Noaudio
  
  </stream>

  I execute this command to get stream from camera and pass it to a client through ffserver :

  ffmpeg -rtsp_transport tcp -i rtsp://admin:admin@192.168.10.76:80 -vcodec libvpx r 10 -f webm http://localhost:8090/0_webm.ffm

  But get "Broken pipe" error message (full ffmeg output) :

  ffmpeg version 2.4.2 Copyright (c) 2000-2014 the FFmpeg developers
  
    built on Oct  6 2014 17:33:05 with gcc 4.8 (Ubuntu 4.8.2-19ubuntu1)
  
    configuration: --prefix=/opt/ffmpeg --libdir=/opt/ffmpeg/lib/ --enable-shared --enable-avresample --disable-stripping --enable-gpl --enable-version3 --enable-runtime-cpudetect --build-suffix=.ffmpeg --enable-postproc --enable-x11grab --enable-libcdio --enable-vaapi --enable-vdpau --enable-bzlib --enable-gnutls --enable-libgsm --enable-libschroedinger --enable-libspeex --enable-libtheora --enable-libvorbis --enable-libfaac --enable-libvo-aacenc --enable-nonfree --enable-libmp3lame --enable-libx264 --enable-libx265 --enable-libxvid --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libfdk_aac --enable-libopus --enable-pthreads --enable-zlib --enable-libvpx --enable-libfreetype --enable-libpulse --enable-debug=3
  
    libavutil      54.  7.100 / 54.  7.100
  
    libavcodec     56.  1.100 / 56.  1.100
  
    libavformat    56.  4.101 / 56.  4.101
  
    libavdevice    56.  0.100 / 56.  0.100
  
    libavfilter     5.  1.100 /  5.  1.100
  
    libavresample   2.  1.  0 /  2.  1.  0
  
    libswscale      3.  0.100 /  3.  0.100
  
    libswresample   1.  1.100 /  1.  1.100
  
    libpostproc    53.  0.100 / 53.  0.100
  
  Guessed Channel Layout for  Input Stream #0.1 : mono
  
  Input #0, rtsp, from 'rtsp://admin:admin@192.168.10.76:80':
  
    Metadata:
  
      title           : RTSP Session/2.0
  
    Duration: N/A, start: 0.000000, bitrate: 128 kb/s
  
      Stream #0:0: Video: h264 (High), yuvj420p(pc, bt709), 1280x720 [SAR 1:1 DAR 16:9], 25 fps, 25 tbr, 90k tbn, 50 tbc
  
      Stream #0:1: Audio: pcm_alaw, 16000 Hz, 1 channels, s16, 128 kb/s
  
  [swscaler @ 0xcf97a0] deprecated pixel format used, make sure you did set range correctly
  
  [libvpx @ 0xd86fc0] v1.3.0
  
  Output #0, webm, to 'http://localhost:8090/0_webm.ffm':
  
    Metadata:
  
      title           : RTSP Session/2.0
  
      encoder         : Lavf56.4.101
  
      Stream #0:0: Video: vp8 (libvpx), yuv420p, 1280x720 [SAR 1:1 DAR 16:9], q=-1--1, 200 kb/s, 10 fps, 1k tbn, 10 tbc
  
      Metadata:
  
        encoder         : Lavc56.1.100 libvpx
  
      Stream #0:1: Audio: vorbis (libvorbis), 16000 Hz, mono, fltp
  
      Metadata:
  
        encoder         : Lavc56.1.100 libvorbis
  
  Stream mapping:
  
    Stream #0:0 -> #0:0 (h264 (native) -> vp8 (libvpx))
  
    Stream #0:1 -> #0:1 (pcm_alaw (native) -> vorbis (libvorbis))
  
  Press [q] to stop, [?] for help
  
  av_interleaved_write_frame(): Broken pipe
  
      Last message repeated 1 times
  
  frame=    2 fps=0.0 q=0.0 Lsize=      40kB time=00:00:00.23 bitrate=1371.2kbits/s    
  
  video:36kB audio:1kB subtitle:0kB other streams:0kB global headers:3kB muxing overhead: 7.514220%
  
  Conversion failed!

  If I run the same command without -f webm, I get no error and it looks like working. But in this case I can’t play it in browser (Chrome for instance).

  Does anybody know how to fix "Broken pipe issue" ? Will be happy to get any your help or advises. Thanks in advance.

• 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.