Recherche avancée

Sur d’autres sites (9964)

• UWP run ffmpeg process to capture

  16 février 2018, par InspiracvionV

  I’m developing a UWP app with C# and I need to start FFmpeg in a process.

  I use this ffmpeg command which works good in CMD :

  D :\ffmpeg.exe -f dshow -crossbar_video_input_pin_number 1 -i
  video="AVerMedia BDA Analog Capture" -vcodec rawvideo -pix_fmt yuv420p
  -s 864x768 -r 10 "D :\capture\output.yuv" -loglevel 16

  But when I start the process with the same command and arguments in my UWP app I get this error from ffmpeg :

  [dshow @ 000001bd43907e80] Unable to BindToObject for AVerMedia BDA
  Analog Capture [dshow @ 000001bd43907e80] Could not find video device
  with name [AVerMedia BDA Analog Capture] among source devices of type
  video. video=AVerMedia BDA Analog Capture : I/O error

  This is my code :

          string filename = @"D:\ffmpeg.exe";
  
          string arg = " -f dshow -crossbar_video_input_pin_number [VIDEOPIN] -i video=\"AVerMedia BDA Analog Capture\" -vcodec rawvideo -pix_fmt [PIXELCONF] -s [SIZE] -r [FPS] \"[FOLDER]\\[VIDEONAME]\" -loglevel 16";
  
          arg = path.Text;
  
          if (!File.Exists(filename))
  
              System.Diagnostics.Debug.WriteLine("Not exist ffmpeg");
  
  
  
  
  
  
  
          arg = arg.Replace("[VIDEOPIN]", "1");
  
          arg = arg.Replace("[VIDEODEVICE]", "AVerMedia BDA Analog Capture");
  
          arg = arg.Replace("[PIXELCONF]", "yuv420p");
  
          arg = arg.Replace("[SIZE]", "864x768");
  
          arg = arg.Replace("[FPS]", "10");
  
          arg = arg.Replace("[FOLDER]", "D:\\capture");
  
          arg = arg.Replace("[VIDEONAME]", "output.yuv");
  
  
  
          ProcessStartInfo pi = new ProcessStartInfo(filename, arg);
  
          System.Diagnostics.Debug.WriteLine(pi.FileName + " " + pi.Arguments.ToString());
  
          pi.RedirectStandardInput = true;
  
          pi.RedirectStandardOutput = true;
  
          pi.RedirectStandardError = true;
  
          pi.UseShellExecute = false;
  
  
  
          pi.CreateNoWindow = true;
  
          process = new Process();
  
          process.StartInfo = pi;
  
          process.EnableRaisingEvents = true;
  
          process.OutputDataReceived += new DataReceivedEventHandler(MyProcOutputHandler);
  
          process.ErrorDataReceived += new DataReceivedEventHandler(MyProcErrorHandler);
  
          process.Exited += new EventHandler(ExitedProcess);
  
  
  
  
  
  
  
          process.Start();
  
          process.BeginErrorReadLine();
  
          process.BeginOutputReadLine();

  EDIT : This is what i have with :

  ffmpeg -list_devices true -f dshow -i dummy

  ffmpeg version N-90054-g474194a8d0 Copyright (c) 2000-2018 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-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-libmfx —enable-amf —enable-cuda —enable-cuvid —enable-d3d11va —enable-nvenc —enable-dxva2 —enable-avisynth libavutil 56. 7.101 / 56. 7.101 libavcodec 58. 11.101 / 58. 11.101 libavformat 58. 9.100 / 58. 9.100 libavdevice 58. 1.100 / 58. 1.100 libavfilter 7. 12.100 / 7. 12.100 libswscale 5. 0.101 / 5. 0.101 libswresample 3. 0.101 / 3. 0.101 libpostproc 55. 0.100 / 55. 0.100 [dshow @ 0000029065b07940] DirectShow video devices (some may be both video and audio devices) [dshow @ 0000029065b07940]
  "AVerMedia BDA Analog Capture" [dshow @ 0000029065b07940] Alternative
  name
  "@device_pnp_~?\pci#ven_1a0a&dev_6202&subsys_620f1461&rev_01#4&3632f028&0&00e6#65e8773d-8f56-11d0-a3b9-00a0c9223196ca465100-deb0-4d59-818f-8c477184adf6"
  [dshow @ 0000029065b07940] "AVerMedia BDA Analog Capture Secondary"
  [dshow @ 0000029065b07940] Alternative name
  "@device_pnp_~?\pci#ven_1a0a&dev_6202&subsys_620f1461&rev_01#4&3632f028&0&00e6#65e8773d-8f56-11d0-a3b9-00a0c9223196ede957b0-eaa5-4bf4-acf3-6e10cb4836c3"
  [dshow @ 0000029065b07940] DirectShow audio devices [dshow @
  0000029065b07940] Could not enumerate audio only devices (or none
  found). dummy : Immediate exit requested

• 12 ways Matomo Analytics helps you to protect your visitor’s privacy

  5 mai 2020, par InnoCraft — Analytics Tips, Privacy, Security

  This post was originally published on January 11, 2017, and updated on May, 2020.

  At Matomo we think privacy matters. From the beginning, Matomo has had a strong focus on privacy and ensuring the privacy of your visitors and analytics data. 

  Here are some ways how you can ensure your users and visitors privacy by using Matomo (Piwik).

  1. Owning the data gives you power to protect user privacy

  Whether you host Matomo on-premises yourself, or whether you use Matomo’s cloud, YOU keep control of your data and nobody else. By knowing exactly where your data is stored and having full control over what happens to it, you have the power to protect your user’s privacy. No-one else can claim ownership. 

  2. GDPR compliance

  GDPR is one of the most important privacy laws to have come out in the last few years. As such, Matomo takes GDPR compliance very seriously. There’s even a 12-step checklist for you to follow to ensure your Matomo is GDPR compliant. Not only that Matomo is HIPAA, CCPA, LGPD, and PECR compliant.

  3. Data anonymization

  For better privacy by default, Matomo implements a range of data anonymization techniques. One of the main techniques is not recording the full IP address of your visitors. Some countries even require you to anonymize additional info considered Personally Identifiable Information (PII).

  To change the IP anonymization settings go to “Administration > Privacy”. 

  

  4. Configuring Matomo to not process personal data or personally identifiable information (PII)

  To further protect the privacy of your visitors, you can learn how to not process any personal information or PII. 

  5. Deleting old visitor logs

  The is important because visitor logs contain information all the collected raw data about every visitor and every action. You can configure Matomo to automatically delete logs from the database. When you delete old logs, only the real time and visitor log reports will no longer work for this old time period, all other aggregated reports will still work.

  For privacy reasons, we highly recommend that you keep the detailed Matomo logs for only 3 to 6 months and delete older log data. This has one other nice side effect : it will free significant database space, which will, in turn, slightly increase performance !

  

  6. Supporting the Do Not Track preference

  Do Not Track enables users to opt out of any tracking by websites they do not visit, including analytics services, advertising networks, and social platforms. By default, Matomo respects users preference and will not track visitors which have specified “I do not want to be tracked” in their web browsers. Get more information about DoNotTrack.

  To make sure Do Not Track is respected, go to “Administration => Privacy”.

  7. Including an Opt-Out Feature on your website or app

  By embedding the Opt-Out feature in your website, you give your visitors the possibility to opt-out of the tracking. When you go to “Administration > Privacy”, you will be able to copy and paste an HTML Iframe code to embed the opt-out feature for example into your privacy policy page or in your ‘Legal’ page. Your users can then click on a link to opt-out.

  On the Matomo Marketplace there are also some plugins available to customize the Opt-Out experience. For example AjaxOptOut and CustomOptOut.

  

  8. Disabling Live features

  The Real-Time, Visitor Log and Visitor Profile features give you insights into the tracked raw data by showing you details about every visitor and every action they performed. To protect the privacy of your visitors you may decide to prevent access to such features by disabling the “Live” plugin in “Administration => Plugins”. This way only aggregated reports will be shown in your Matomo.

  9. Disabling fingerprinting across websites

  By default, when one of your visitors visits several of your websites, Matomo will create a fingerprint for this user that will be different across the websites to increase the visitors’ privacy. You can make sure that this feature is disabled by going to “Administration => Config file” and verifying that the value of “enable_fingerprinting_across_websites” is set to zero.

  10. Disabling tracking cookies

  Matomo uses first-party cookies to store some information about visitors between visits. In some countries, the legislation requires websites to provide a way for users to opt-out of all tracking, in particular tracking cookies. You can disable cookies by adding one line in the Matomo Javascript code.

  11. Creating the tool of your dreams by developing your own plugins and getting access to the API

  Matomo is an open platform that lets you extend and customise the tracking ; reporting ; and user interface to your needs and to protect your visitors’ privacy the way you want or need it. Learn more in the Matomo Developer Zone. You may also have a look at our Matomo Marketplace where you can find several free and premium features to extend your Matomo.

  12. Transparency

  By default, all information and all collected data in your Matomo server are protected and nobody can access it. However, Matomo allows you to optionally make your collected data public and you can export any Matomo report including the whole dashboard to embed it into your website. This way you can show your users exactly which information you track. When you decide to make reports public, we do our best to protect privacy and automatically hide any Personally Identifiable Information such as the Visitor Profile and we make sure to not show any Visitor IP address and the Visitor ID.

  Bonus tip – A privacy policy template for you

  When you use Matomo to track your visitors, we recommend you update your Privacy Policy to explain how Matomo is used and what data it gathers. Here’s a Privacy Policy template for you to copy on your site.

  Continuous privacy improvements

  We are always interested in improving the privacy. If you miss any feature or have an idea on how to improve the privacy, please let us know.

  More information about all the Matomo features

  If you want to learn more about all the features in Matomo, have a look at our User Guides and FAQ entries.

• FFMPEG Concat DNxHD-Files : wrong duration of output-file

  4 mai 2020, par Thomas

  I have AVID-DNxHD-files created by Ikegami EditCamHD and FFMPEG-coded DNxHD-Files.

  



  Ikegami-Files are 1080/25psF at 185MBit/sec (10Bit). FFMPEG-Files are crated with this command :

  



  ffmpeg -loop 1 -i c:\pics\VideoNichtVorhanden.jpg -s 1920x1080 -r 25 -t 92.8 -c:v dnxhd -b:v 185M -pix_fmt yuv422p10le d:\MissingFiles\missing_0001.mov


  



  ffprobe from Ikegami-file :

  



  {
  "streams": [
    {
      "index": 0,
      "codec_name": "dnxhd",
      "codec_long_name": "VC3\/DNxHD",
      "profile": "DNXHD",
      "codec_type": "video",
      "codec_time_base": "1\/25",
      "codec_tag_string": "[0][0][0][0]",
      "codec_tag": "0x0000",
      "width": 1920,
      "height": 1080,
      "coded_width": 1920,
      "coded_height": 1088,
      "has_b_frames": 0,
      "sample_aspect_ratio": "1:1",
      "display_aspect_ratio": "16:9",
      "pix_fmt": "yuv422p10le",
      "level": -99,
      "color_space": "bt709",
      "field_order": "tt",
      "refs": 1,
      "r_frame_rate": "25\/1",
      "avg_frame_rate": "25\/1",
      "time_base": "1\/25",
      "start_pts": 0,
      "start_time": "0.000000",
      "duration_ts": 827,
      "duration": "33.080000",
      "bits_per_raw_sample": "10",
      "disposition": {
        "default": 0,
        "dub": 0,
        "original": 0,
        "comment": 0,
        "lyrics": 0,
        "karaoke": 0,
        "forced": 0,
        "hearing_impaired": 0,
        "visual_impaired": 0,
        "clean_effects": 0,
        "attached_pic": 0,
        "timed_thumbnails": 0
      },
      "tags": {
        "file_package_umid": "0x060A2B340101010101010F0013000000D6F21F070302074C060E2B347F7F2A80",
        "file_package_name": "File Package",
        "track_name": "V1"
      }
    },
    {
      "index": 1,
      "codec_type": "data",
      "codec_tag_string": "[0][0][0][0]",
      "codec_tag": "0x0000",
      "r_frame_rate": "0\/0",
      "avg_frame_rate": "0\/0",
      "time_base": "1\/90000",
      "start_pts": 0,
      "start_time": "0.000000",
      "duration_ts": 2977200,
      "duration": "33.080000",
      "disposition": {
        "default": 0,
        "dub": 0,
        "original": 0,
        "comment": 0,
        "lyrics": 0,
        "karaoke": 0,
        "forced": 0,
        "hearing_impaired": 0,
        "visual_impaired": 0,
        "clean_effects": 0,
        "attached_pic": 0,
        "timed_thumbnails": 0
      },
      "tags": {
        "file_package_umid": "0x060A2B34010101010101080013000000D6F21F070276074C060E2B347F7F2A80",
        "track_name": "A1",
        "data_type": "audio"
      }
    },
    {
      "index": 2,
      "codec_type": "data",
      "codec_tag_string": "[0][0][0][0]",
      "codec_tag": "0x0000",
      "r_frame_rate": "0\/0",
      "avg_frame_rate": "0\/0",
      "time_base": "1\/90000",
      "start_pts": 0,
      "start_time": "0.000000",
      "duration_ts": 2977200,
      "duration": "33.080000",
      "disposition": {
        "default": 0,
        "dub": 0,
        "original": 0,
        "comment": 0,
        "lyrics": 0,
        "karaoke": 0,
        "forced": 0,
        "hearing_impaired": 0,
        "visual_impaired": 0,
        "clean_effects": 0,
        "attached_pic": 0,
        "timed_thumbnails": 0
      },
      "tags": {
        "file_package_umid": "0x060A2B34010101010101080013000000D6F21F07028A074C060E2B347F7F2A80",
        "track_name": "A2",
        "data_type": "audio"
      }
    }
  ],
  "format": {
    "filename": "G:\\MXF-sortiert\\Ikegami\\2018-04-10\\V\\MULTI_NN17GN0V\\NN17GN0V.0001.MXF",
    "nb_streams": 3,
    "nb_programs": 0,
    "format_name": "mxf",
    "format_long_name": "MXF (Material eXchange Format)",
    "start_time": "0.000000",
    "duration": "33.080000",
    "size": "761004264",
    "bit_rate": "184039725",
    "probe_score": 100,
    "tags": {
      "operational_pattern_ul": "060e2b34.04010102.0d010201.10030000",
      "uid": "caf0bf8e-ff07-b34d-9616-bc3e7bd32d54",
      "generation_uid": "fb90769f-a46d-d546-983d-dda63339a8fd",
      "company_name": "Ikegami",
      "product_name": "HDN-X10",
      "product_version": "1.30d",
      "product_uid": "3e2189d7-294b-4612-8243-1b1990e14055",
      "modification_date": "2018-04-10T05:57:59.788000Z",
      "material_package_umid": "0x060A2B340101010101010F0013000000D6F21F070262074C060E2B347F7F2A80",
      "material_package_name": "01047",
      "timecode": "01:23:17:03"
    }
  }
}


  



  ffprobe from ffmpeg-coded-file :

  



  {
  "streams": [
    {
      "index": 0,
      "codec_name": "dnxhd",
      "codec_long_name": "VC3\/DNxHD",
      "profile": "DNXHD",
      "codec_type": "video",
      "codec_time_base": "1\/25",
      "codec_tag_string": "AVdn",
      "codec_tag": "0x6e645641",
      "width": 1920,
      "height": 1080,
      "coded_width": 1920,
      "coded_height": 1088,
      "has_b_frames": 0,
      "sample_aspect_ratio": "1:1",
      "display_aspect_ratio": "16:9",
      "pix_fmt": "yuv422p10le",
      "level": -99,
      "color_range": "tv",
      "color_space": "bt709",
      "refs": 1,
      "r_frame_rate": "25\/1",
      "avg_frame_rate": "25\/1",
      "time_base": "1\/12800",
      "start_pts": 0,
      "start_time": "0.000000",
      "duration_ts": 1187840,
      "duration": "92.800000",
      "bit_rate": "183500800",
      "bits_per_raw_sample": "10",
      "nb_frames": "2320",
      "disposition": {
        "default": 1,
        "dub": 0,
        "original": 0,
        "comment": 0,
        "lyrics": 0,
        "karaoke": 0,
        "forced": 0,
        "hearing_impaired": 0,
        "visual_impaired": 0,
        "clean_effects": 0,
        "attached_pic": 0,
        "timed_thumbnails": 0
      },
      "tags": {
        "handler_name": "VideoHandler",
        "encoder": "Lavc58.54.100 dnxhd"
      }
    }
  ],
  "format": {
    "filename": "G:\\MXF-sortiert\\Ikegami\\2018-04-10\\V\\MULTI_NN1EUS0V\\MXF\\NN1EUS0V.0001.mov",
    "nb_streams": 1,
    "nb_programs": 0,
    "format_name": "mov,mp4,m4a,3gp,3g2,mj2",
    "format_long_name": "QuickTime \/ MOV",
    "start_time": "0.000000",
    "duration": "92.800000",
    "size": "2128619444",
    "bit_rate": "183501676",
    "probe_score": 100,
    "tags": {
      "major_brand": "qt  ",
      "minor_version": "512",
      "compatible_brands": "qt  ",
      "encoder": "Lavf58.29.100"
    }
  }
}


  



  When I concat for example one .mxf with one .mov and another .mxf at the end, the duration is frong (about 26 Miuntes when it should be some 4 Minutes or so) and VLC-Player gives a Framerate of a very slow framerate and the video does not play the ffmpeg coded part.

  



  ffprobe from concat-output :

  



  {
  "streams": [
    {
      "index": 0,
      "codec_name": "dnxhd",
      "codec_long_name": "VC3\/DNxHD",
      "profile": "DNXHD",
      "codec_type": "video",
      "codec_time_base": "20268137\/1351040",
      "codec_tag_string": "AVdn",
      "codec_tag": "0x6e645641",
      "width": 1920,
      "height": 1080,
      "coded_width": 1920,
      "coded_height": 1088,
      "has_b_frames": 0,
      "sample_aspect_ratio": "1:1",
      "display_aspect_ratio": "16:9",
      "pix_fmt": "yuv422p10le",
      "level": -99,
      "color_range": "tv",
      "color_space": "bt709",
      "refs": 1,
      "r_frame_rate": "25\/1",
      "avg_frame_rate": "1351040\/20268137",
      "time_base": "1\/12800",
      "start_pts": 0,
      "start_time": "0.000000",
      "duration_ts": 1216088220,
      "duration": "95006.892188",
      "bit_rate": "489252",
      "bits_per_raw_sample": "10",
      "nb_frames": "6333",
      "disposition": {
        "default": 1,
        "dub": 0,
        "original": 0,
        "comment": 0,
        "lyrics": 0,
        "karaoke": 0,
        "forced": 0,
        "hearing_impaired": 0,
        "visual_impaired": 0,
        "clean_effects": 0,
        "attached_pic": 0,
        "timed_thumbnails": 0
      },
      "tags": {
        "handler_name": "VideoHandler"
      }
    }
  ],
  "format": {
    "filename": "G:\\MXF-sortiert\\Ikegami\\2018-04-10\\V\\NN1EUS0V_MIES.mov",
    "nb_streams": 1,
    "nb_programs": 0,
    "format_name": "mov,mp4,m4a,3gp,3g2,mj2",
    "format_long_name": "QuickTime \/ MOV",
    "start_time": "0.000000",
    "duration": "95006.893000",
    "size": "5810367616",
    "bit_rate": "489258",
    "probe_score": 100,
    "tags": {
      "major_brand": "qt  ",
      "minor_version": "512",
      "compatible_brands": "qt  ",
      "encoder": "Lavf58.29.100"
    }
  }
}


  



  The Ikegami and ffmpeg-coded files for themselves are playing great and do show the correct fps in VLC.

  



  I can see in the probe-logs the

  



    "codec_time_base": "20268137\/1351040"


  



  and

  



    "avg_frame_rate": "1351040\/20268137"


  



  What is going wrong here ? How can I improve the coding-part and / or the concat to get a good result ? Is it only possible with re-encode instead of c:v copy ?

  



  Any help welcome, thanks in advance,

  



  tom