Recherche avancée

Sur d’autres sites (3590)

• FFMPEG avi to streaming mp4

  29 mai 2013, par Vprnl

  I'm trying to get ffmpeg to encode various AVI files to mp4 for streaming purposes but my inexperience with the subject matter is making me doubt I'll ever get this to work.

  I use this commandline :

  ffmpeg -i test.avi -vcodec libx264 -r 24 -ac 2 -acodec ac3 -ab 128k -bt 240k -preset    fast -strict -2 -b:v 320K -bufsize 62000 -maxrate 62000 -movflags frag_keyframe+empty_moov test.mp4

  I use the " -movflags frag_keyframe+empty_moov" to make it possible to serve a fragmented mp4

  And this is the log I get :

      file conversion error ffmpeg version N-53577-gced0307 Copyright (c) 2000-2013 the FFmpeg developers
  
        built on May 28 2013 12:21:54 with gcc 4.7.3 (GCC)
  
        configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0
  
      r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libcaca --enable-libfreetype --enable-libgsm --enable-libil
  
      bc --enable-libmodplug --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus -
  
      -enable-librtmp --enable-libschroedinger --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvo-aacenc
  
       --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib
  
        libavutil      52. 34.100 / 52. 34.100
  
        libavcodec     55. 12.100 / 55. 12.100
  
        libavformat    55.  7.100 / 55.  7.100
  
        libavdevice    55.  1.101 / 55.  1.101
  
        libavfilter     3. 72.100 /  3. 72.100
  
        libswscale      2.  3.100 /  2.  3.100
  
        libswresample   0. 17.102 /  0. 17.102
  
        libpostproc    52.  3.100 / 52.  3.100
  
      [avi @ 002ce8c0] non-interleaved AVI
  
      Input #0, avi, from 'C:/temp/test.avi':
  
        Metadata:
  
          encoder         : MEncoder Sherpya-MT-SVN-r31027-4.2.5
  
        Duration: 01:15:15.47, start: 0.000000, bitrate: 4798 kb/s
  
          Stream #0:0: Video: mpeg4 (Simple Profile) (XVID / 0x44495658), yuv420p, 1280x720 [SAR 1:1 DAR 16:9], 23.98 fps, 23.98 tbr, 23.98 tb
  
      n, 24k tbc
  
          Stream #0:1: Audio: ac3 ([0] [0][0] / 0x2000), 48000 Hz, 5.1(side), fltp, 640 kb/s
  
      [libx264 @ 03c57020] max bitrate less than average bitrate, assuming CBR
  
      [libx264 @ 03c57020] using SAR=1/1
  
      [libx264 @ 03c57020] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.1 Cache64
  
      [libx264 @ 03c57020] profile High, level 3.1
  
      [libx264 @ 03c57020] 264 - core 133 r2334 a3ac64b - H.264/MPEG-4 AVC codec - Copyleft 2003-2013 - http://www.videolan.org/x264.html - op
  
      tions: cabac=1 ref=2 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=6 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1
  
       8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=3 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 interlace
  
      d=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=1 keyint=250 keyi
  
      nt_min=24 scenecut=40 intra_refresh=0 rc_lookahead=30 rc=cbr mbtree=1 bitrate=320 ratetol=1.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 vbv_m
  
      axrate=320 vbv_bufsize=62 nal_hrd=none ip_ratio=1.40 aq=1:1.00
  
      Output #0, mp4, to 'pipe:1':
  
        Metadata:
  
          encoder         : Lavf55.7.100
  
          Stream #0:0: Video: h264 (libx264) ([33][0][0][0] / 0x0021), yuv420p, 1280x720 [SAR 1:1 DAR 16:9], q=-1--1, 320 kb/s, 12288 tbn, 24
  
      tbc
  
          Stream #0:1: Audio: ac3 ([165][0][0][0] / 0x00A5), 48000 Hz, stereo, fltp, 128 kb/s
  
      Stream mapping:
  
        Stream #0:0 -> #0:0 (mpeg4 -> libx264)
  
        Stream #0:1 -> #0:1 (ac3 -> ac3)
  
      Press [q] to stop, [?] for help
  
      frame=   37 fps=0.0 q=0.0 size=       1kB time=00:00:01.97 bitrate=   4.7kbits/s
  
      frame=   41 fps= 36 q=27.0 size=       1kB time=00:00:01.97 bitrate=   4.7kbits/s
  
      frame=   51 fps= 31 q=22.0 size=       1kB time=00:00:02.49 bitrate=   3.7kbits/s
  
      frame=   63 fps= 27 q=21.0 size=       1kB time=00:00:02.97 bitrate=   3.1kbits/s
  
      frame=   82 fps= 29 q=21.0 size=       1kB time=00:00:03.48 bitrate=   2.7kbits/s
  
      frame=   91 fps= 26 q=21.0 size=       1kB time=00:00:03.99 bitrate=   2.3kbits/s
  
      frame=  101 fps= 25 q=23.0 size=       1kB time=00:00:04.47 bitrate=   2.1kbits/s
  
      frame=  114 fps= 25 q=21.0 size=       1kB time=00:00:04.98 bitrate=   1.9kbits/s
  
      frame=  128 fps= 25 q=26.0 size=       1kB time=00:00:05.46 bitrate=   1.7kbits/s
  
      frame=  135 fps= 24 q=38.0 size=       1kB time=00:00:05.97 bitrate=   1.6kbits/s
  
      frame=  141 fps= 23 q=45.0 size=       1kB time=00:00:05.97 bitrate=   1.6kbits/s

  I hope someone can point me in the right direction. The goal is to serve the file to a html5 player. But sadly that has not yet worked.
  Thanks !

  [EDIT]

  Sorry if I'm being unclear. I have two issues. First FFMPEG gives me an error (as you can see in the log) but I'm uncertain why I get this error and secondly, the stream does not actually work. The tanscoding starts, but the player never receives the video

• FFmpeg - feed raw frames via pipe - FFmpeg does not detect pipe closure

  8 septembre 2018, par Rumble

  Im trying to follow these examples from C++ in Windows. Phyton Example C# Example

  I have an application that produces raw frames that shall be encoded with FFmpeg.
  The raw frames are transfered via IPC pipe to FFmpegs STDIN. That is working as expected, FFmpeg even displays the number of frames currently available.

  The problem occours when we are done sending frames. When I close the write end of the pipe I would expect FFmpeg to detect that, finish up and output the video. But that does not happen. FFmpeg stays open and seems to wait for more data.

  I made a small test project in VisualStudio.

  #include "stdafx.h" 
  
  //// stdafx.h 
  
  //#include "targetver.h"
  
  //#include 
  
  //#include 
  
  //#include <iostream>
  
  
  
  #include "Windows.h"
  
  #include <cstdlib>
  
  
  
  using namespace std;
  
  
  
  bool WritePipe(void* WritePipe, const UINT8 *const Buffer, const UINT32 Length)
  
  {
  
      if (WritePipe == nullptr || Buffer == nullptr || Length == 0)
  
      {
  
          cout &lt;&lt; __FUNCTION__ &lt;&lt; ": Some input is useless";
  
          return false;
  
      }
  
  
  
      // Write to pipe
  
      UINT32 BytesWritten = 0;
  
      UINT8 newline = '\n';
  
      bool bIsWritten = WriteFile(WritePipe, Buffer, Length, (::DWORD*)&amp;BytesWritten, nullptr);
  
      cout &lt;&lt; __FUNCTION__ &lt;&lt; " Bytes written to pipe " &lt;&lt; BytesWritten &lt;&lt; endl;
  
      //bIsWritten = WriteFile(WritePipe, &amp;newline, 1, (::DWORD*)&amp;BytesWritten, nullptr); // Do we need this? Actually this should destroy the image.
  
  
  
      FlushFileBuffers(WritePipe); // Do we need this?
  
  
  
      return bIsWritten;
  
  }
  
  
  
  #define PIXEL 80 // must be multiple of 8. Otherwise we get warning: Bytes are not aligned
  
  
  
  int main()
  
  {
  
      HANDLE PipeWriteEnd = nullptr;
  
      HANDLE PipeReadEnd = nullptr;
  
      {
  
          // create us a pipe for inter process communication
  
          SECURITY_ATTRIBUTES Attr = { sizeof(SECURITY_ATTRIBUTES), NULL, true };
  
          if (!CreatePipe(&amp;PipeReadEnd, &amp;PipeWriteEnd, &amp;Attr, 0))
  
          {
  
              cout &lt;&lt; "Could not create pipes" &lt;&lt; ::GetLastError() &lt;&lt; endl;
  
              system("Pause");
  
              return 0;
  
          }
  
      }
  
  
  
      // Setup the variables needed for CreateProcess
  
      // initialize process attributes
  
      SECURITY_ATTRIBUTES Attr;
  
      Attr.nLength = sizeof(SECURITY_ATTRIBUTES);
  
      Attr.lpSecurityDescriptor = NULL;
  
      Attr.bInheritHandle = true;
  
  
  
      // initialize process creation flags
  
      UINT32 CreateFlags = NORMAL_PRIORITY_CLASS;
  
      CreateFlags |= CREATE_NEW_CONSOLE;
  
  
  
      // initialize window flags
  
      UINT32 dwFlags = 0;
  
      UINT16 ShowWindowFlags = SW_HIDE;
  
  
  
      if (PipeWriteEnd != nullptr || PipeReadEnd != nullptr)
  
      {
  
          dwFlags |= STARTF_USESTDHANDLES;
  
      }
  
  
  
      // initialize startup info
  
      STARTUPINFOA StartupInfo = {
  
          sizeof(STARTUPINFO),
  
          NULL, NULL, NULL,
  
          (::DWORD)CW_USEDEFAULT,
  
          (::DWORD)CW_USEDEFAULT,
  
          (::DWORD)CW_USEDEFAULT,
  
          (::DWORD)CW_USEDEFAULT,
  
          (::DWORD)0, (::DWORD)0, (::DWORD)0,
  
          (::DWORD)dwFlags,
  
          ShowWindowFlags,
  
          0, NULL,
  
          HANDLE(PipeReadEnd),
  
          HANDLE(nullptr),
  
          HANDLE(nullptr)
  
      };
  
  
  
      LPSTR ffmpegURL = "\"PATHTOFFMPEGEXE\" -y -loglevel verbose -f rawvideo -vcodec rawvideo -framerate 1 -video_size 80x80 -pixel_format rgb24 -i - -vcodec mjpeg -framerate 1/4 -an \"OUTPUTDIRECTORY\"";
  
  
  
      // Finally create the process
  
      PROCESS_INFORMATION ProcInfo;
  
      if (!CreateProcessA(NULL, ffmpegURL, &amp;Attr, &amp;Attr, true, (::DWORD)CreateFlags, NULL, NULL, &amp;StartupInfo, &amp;ProcInfo))
  
      {
  
          cout &lt;&lt; "CreateProcess failed " &lt;&lt; ::GetLastError() &lt;&lt; endl;
  
      }
  
      //CloseHandle(ProcInfo.hThread);
  
  
  
  
  
          // Create images and write to pipe
  
  #define MYARRAYSIZE (PIXEL*PIXEL*3) // each pixel has 3 bytes
  
  
  
      UINT8* Bitmap = new UINT8[MYARRAYSIZE];
  
  
  
      for (INT32 outerLoopIndex = 9; outerLoopIndex >= 0; --outerLoopIndex)   // frame loop
  
      {
  
          for (INT32 innerLoopIndex = MYARRAYSIZE - 1; innerLoopIndex >= 0; --innerLoopIndex) // create the pixels for each frame
  
          {
  
              Bitmap[innerLoopIndex] = (UINT8)(outerLoopIndex * 20); // some gray color
  
          }
  
          system("pause");
  
          if (!WritePipe(PipeWriteEnd, Bitmap, MYARRAYSIZE))
  
          {
  
              cout &lt;&lt; "Failed writing to pipe" &lt;&lt; endl;
  
          }
  
      }
  
  
  
      // Done sending images. Tell the other process. IS THIS NEEDED? HOW TO TELL FFmpeg WE ARE DONE?
  
      //UINT8 endOfFile = 0xFF; // EOF = -1 == 1111 1111 for uint8
  
      //if (!WritePipe(PipeWriteEnd, &amp;endOfFile, 1))
  
      //{
  
      //  cout &lt;&lt; "Failed writing to pipe" &lt;&lt; endl;
  
      //}
  
      //FlushFileBuffers(PipeReadEnd); // Do we need this?
  
  
  
      delete Bitmap;
  
  
  
  
  
      system("pause");
  
  
  
      // clean stuff up
  
      FlushFileBuffers(PipeWriteEnd); // Do we need this?
  
  
  
      if (PipeWriteEnd != NULL &amp;&amp; PipeWriteEnd != INVALID_HANDLE_VALUE)
  
      {
  
          CloseHandle(PipeWriteEnd);
  
      }
  
  
  
      // We do not want to destroy the read end of the pipe? Should not as that belongs to FFmpeg
  
      //if (PipeReadEnd != NULL &amp;&amp; PipeReadEnd != INVALID_HANDLE_VALUE)
  
      //{
  
      //  ::CloseHandle(PipeReadEnd);
  
      //}
  
  
  
  
  
      return 0;
  
  
  
  }
  
  </cstdlib></iostream>

  And here the output of FFmpeg

  ffmpeg version 3.4.1 Copyright (c) 2000-2017 the FFmpeg developers
  
    built with gcc 7.2.0 (GCC)
  
    configuration: --enable-gpl --enable-version3 --enable-sdl2 --enable-bzlib --enable-fontconfig --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libfreetype --enable-libmp3lame --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-cuda --enable-cuvid --enable-d3d11va --enable-nvenc --enable-dxva2 --enable-avisynth --enable-libmfx
  
    libavutil      55. 78.100 / 55. 78.100
  
    libavcodec     57.107.100 / 57.107.100
  
    libavformat    57. 83.100 / 57. 83.100
  
    libavdevice    57. 10.100 / 57. 10.100
  
    libavfilter     6.107.100 /  6.107.100
  
    libswscale      4.  8.100 /  4.  8.100
  
    libswresample   2.  9.100 /  2.  9.100
  
    libpostproc    54.  7.100 / 54.  7.100
  
  [rawvideo @ 00000221ff992120] max_analyze_duration 5000000 reached at 5000000 microseconds st:0
  
  Input #0, rawvideo, from 'pipe:':
  
    Duration: N/A, start: 0.000000, bitrate: 153 kb/s
  
      Stream #0:0: Video: rawvideo, 1 reference frame (RGB[24] / 0x18424752), rgb24, 80x80, 153 kb/s, 1 fps, 1 tbr, 1 tbn, 1 tbc
  
  Stream mapping:
  
    Stream #0:0 -> #0:0 (rawvideo (native) -> mjpeg (native))
  
  [graph 0 input from stream 0:0 @ 00000221ff999c20] w:80 h:80 pixfmt:rgb24 tb:1/1 fr:1/1 sar:0/1 sws_param:flags=2
  
  [auto_scaler_0 @ 00000221ffa071a0] w:iw h:ih flags:'bicubic' interl:0
  
  [format @ 00000221ffa04e20] auto-inserting filter 'auto_scaler_0' between the filter 'Parsed_null_0' and the filter 'format'
  
  [swscaler @ 00000221ffa0a780] deprecated pixel format used, make sure you did set range correctly
  
  [auto_scaler_0 @ 00000221ffa071a0] w:80 h:80 fmt:rgb24 sar:0/1 -> w:80 h:80 fmt:yuvj444p sar:0/1 flags:0x4
  
  Output #0, mp4, to 'c:/users/vr3/Documents/Guenni/sometest.mp4':
  
    Metadata:
  
      encoder         : Lavf57.83.100
  
      Stream #0:0: Video: mjpeg, 1 reference frame (mp4v / 0x7634706D), yuvj444p(pc), 80x80, q=2-31, 200 kb/s, 1 fps, 16384 tbn, 1 tbc
  
      Metadata:
  
        encoder         : Lavc57.107.100 mjpeg
  
      Side data:
  
        cpb: bitrate max/min/avg: 0/0/200000 buffer size: 0 vbv_delay: -1
  
  frame=   10 fps=6.3 q=1.6 size=       0kB time=00:00:09.00 bitrate=   0.0kbits/s speed=5.63x

  As you can see in the last line of te FFmpeg output, the images got trough. 10 frames are available. But after closing the pipe, FFmpeg does not close, still expecting input.

  As the linked examples show, this should be a valid method.

  Trying for a week now...

• How to make Matomo GDPR compliant in 12 steps

  3 avril 2018, par InnoCraft

  Important note : this blog post has been written by digital analysts, not lawyers. The purpose of this article is to briefly show you where Matomo is entering into play within the GDPR process. This work comes from our interpretation of the UK privacy commission : ICO. It cannot be considered as professional legal advice. So as GDPR, this information is subject to change. We strongly advise you to have a look at the different privacy authorities in order to have up to date information.

  The General Data Protection Regulation (EU) 2016/679, also referred to RGPD in French, Datenschutz-Grundverordnung, DS-GVO in German, is a regulation on data protection and privacy for all individuals within the European Union. It concerns organizations worldwide dealing with EU citizens and will come into force on the 25th May 2018.

  The GDPR applies to ‘personal data’ meaning any information relating to an identifiable person who can be directly or indirectly identified in particular by reference to an identifier. It includes cookies, IP addresses, User ID, location, and any other data you may have collected.

  We will list below the 12 steps recommended by the UK privacy commissioner in order to be GDPR compliant and what you need to do for each step.

  The 12 steps of GDPR compliance according to ICO and how it fit with Matomo

  As mentioned in one of our previous blog post about GDPR, if you are not collecting any personal data with Matomo, then you are not concerned about what is written below.

  If you are processing personal data in any way, here are the 12 steps to follow along with some recommendations on how to be GDPR compliant with Matomo :

  1 – Awareness

  Make sure that people within your organization know that you are using Matomo in order to analyze traffic on the website/app. If needed, send them the link to the “What is Matomo ?” page.

  2 – Information you hold

  List all the personal data you are processing with Matomo within your record of processing activities. We are personally using the template provided by ICO which is composed of a set of 30 questions you need to answer regarding your use of Matomo. We have published an article which walks you through the list of questions specifically in the use case of Matomo Analytics. Please be aware that personal data may be also tracked in non-obvious ways for example as part of page URLs or page titles.

  3 – Communicating privacy information

  a – Add a privacy notice

  Add a privacy notice wherever you are using Matomo in order to collect personal data. Please refer to the ICO documentation in order to learn how to write a privacy notice. You can learn more in our article about creating your privacy notice for Matomo Analytics. Make sure that a privacy policy link is always available on your website or app.

  b – Add Matomo to your privacy policy page

  Add Matomo to the list of technologies you are using on your privacy policy page and add all the necessary information to it as requested in the following checklist. To learn more check out our article about Privacy policy.

  4 – Individuals’ rights

  Make sure that your Matomo installation respects all the individuals’ rights. To make it short, you will need to know the features in Matomo that you need to use to respect user rights (right of access, right of rectification, right of erasure…). These features are available starting in Matomo 3.5.0 released on May 8th : GDPR tools for Matomo (User guide).

  5 – Subject access requests

  Make sure that you are able to answer an access request from a data subject for Matomo. For example, when a person would like to access her or his personal data that you have collected about her or him, then you will need to be you able to provide her or him with this information. We recommend you design a process for this like “Who is dealing with it ?” and check that it is working. If you can answer to the nightmare letter, then you are ready. The needed features for this in Matomo will be available soon.

  6 – Lawful basis for processing personal data

  There are different lawful basis you can use under GDPR. It can be either “Legitimate interest” or “Explicit consent”. Do not forget to mention it within your privacy policy page. Read more in our article about lawful basis.

  7 – Consent

  Users should be able to remove their consent at any time. By chance, Matomo is providing a feature in order to do just that : add the opt-out feature to your privacy policy page.
  We are also offering a tool that allows you optionally to require consent before any data is tracked. This will be useful if a person should be only tracked after she or he has given explicit consent to be tracked.

  8 – Children

  If your website or app is targeted for children and you are using Matomo, extra measures will need to be taken. For example you will need to write your privacy policy even more clear and moreover getting parents consent if the child is below 13. As it is a very specific case, we strongly recommend you to follow this link for further information.

  9 – Data breaches

  As you may be collecting personal data with Matomo, you should also check your “data breach procedure” to define if a leak may have consequences on the privacy of the data subject. Please consult ICO’s website for further information.

  10 – Data Protection by Design and Data Protection Impact Assessments

  Ask yourself if you really need to process personal data within Matomo. If the data you are processing within Matomo is sensitive, we strongly recommend you to make a Data Protection Impact Assessment. A software is available from the The open source PIA software helps to carry out data protection impact assessment, by French Privacy Commissioner : CNIL.

  11 – Data Protection Officers

  If you are reading this article and you are the Data Protection Officer (DPO), you will not be concerned by this step. If that’s not the case, your duty is to provide to the DPO (if your business has a DPO) our blog post in order for her or him to ask you questions regarding your use of Matomo. Note that your DPO can also be interested in the different data that Matomo can process : “What data does Matomo track ?” (FAQ).

  12 – International

  Matomo data is hosted wherever you want. So according to the location of the data, you will need to show specific safeguard except for EU. For example regarding the USA, you will have to check if your web hosting platform is registered to the Privacy Shield : privacyshield.gov/list
  Note : our Matomo cloud infrastructure is based in France.

  That’s the end of this blog post. As GDPR is a huge topic, we will release many more blog posts in the upcoming weeks. If there are any Matomo GDPR topic related posts you would like us to write, please feel free to contact us.

  The post How to make Matomo GDPR compliant in 12 steps appeared first on Analytics Platform - Matomo.