Recherche avancée

Sur d’autres sites (12930)

• Revision 32596 : minuscules et fin pour aujourd’hui

  1er novembre 2009, par fil@… — Log

  minuscules et fin pour aujourd’hui

• FFMPEG not enough data (x y), trying to decode anyway

  7 juin 2016, par Forest J. Handford

  I’m trying to make videos of Direct3D games using a C# app. For non-Direct3D games I stream images from Graphics.CopyFromScreen which works. When I copy the screen from Direct3D and stream it to FFMPEG I get :

  [bmp @ 00000276b0b9c280] not enough data (5070 < 129654), trying to
  decode anyway

  An MP4 file is created, but it is always 0 bytes.

  To get screenshots from Direct3D, I am using Justin Stenning’s Direct3DHook. This produces images MUCH bigger than when I get images from Graphics.CopyFromScreen (8 MB vs 136 KB). I’ve tried increasing the buffer (-bufsize) but the number on the left of the error is not impacted.

  I’ve tried resizing the image to 1/6th the original. That reduces the number on the right, but does not eliminate it. Even when the number on the right is close to what I have for Graphics.CopyFromScreen I get an error. Here is a sample of the current code :

  using System;
  
  using System.Diagnostics;
  
  using System.Threading;
  
  using System.Drawing;
  
  using Capture.Hook;
  
  using Capture.Interface;
  
  using Capture;
  
  using System.IO;
  
  
  
  namespace GameRecord
  
  {
  
      public class Video
  
      {
  
          private const int VID_FRAME_FPS = 8;
  
          private const int SIZE_MODIFIER = 6;
  
          private const double FRAMES_PER_MS = VID_FRAME_FPS * 0.001;
  
          private const int SLEEP_INTERVAL = 2;
  
          private const int CONSTANT_RATE_FACTOR = 18; // Lower crf = Higher Quality https://trac.ffmpeg.org/wiki/Encode/H.264
  
          private Image image;
  
          private Capture captureScreen;
  
          private int processId = 0;
  
          private Process process;
  
          private CaptureProcess captureProcess;
  
          private Process launchingFFMPEG;
  
          private string arg;
  
          private int frame = 0;
  
          private Size? resize = null;
  
  
  
  
  
          /// <summary>
  
          /// Generates the Videos by gathering frames and processing via FFMPEG.
  
          /// </summary>
  
          public void RecordScreenTillGameEnd(string exe, OutputDirectory outputDirectory, CustomMessageBox alertBox, Thread workerThread)
  
          {
  
              AttachProcess(exe);
  
              RequestD3DScreenShot();
  
              while (image == null) ;
  
              Logger.log.Info("Launching FFMPEG ....");
  
              resize = new Size(image.Width / SIZE_MODIFIER, image.Height / SIZE_MODIFIER);
  
              // H.264 can let us do 8 FPS in high res . . . but must be licensed for commercial use.
  
              arg = "-f image2pipe -framerate " + VID_FRAME_FPS + " -i pipe:.bmp -pix_fmt yuv420p -crf " +
  
                  CONSTANT_RATE_FACTOR + " -preset ultrafast -s " + resize.Value.Width + "x" +
  
                  resize.Value.Height + " -vcodec libx264 -bufsize 30000k -y \"" +
  
                  outputDirectory.pathToVideo + "\"";
  
  
  
              launchingFFMPEG = new Process
  
              {
  
                  StartInfo = new ProcessStartInfo
  
                  {
  
                      FileName = "ffmpeg",
  
                      Arguments = arg,
  
                      UseShellExecute = false,
  
                      CreateNoWindow = true,
  
                      RedirectStandardInput = true,
  
                      RedirectStandardError = true
  
                  }
  
              };
  
              launchingFFMPEG.Start();
  
  
  
              Stopwatch stopWatch = Stopwatch.StartNew(); //creates and start the instance of Stopwatch
  
  
  
              do
  
              {
  
                  Thread.Sleep(SLEEP_INTERVAL);
  
              } while (workerThread.IsAlive);
  
  
  
              Logger.log.Info("Total frames: " + frame + " Expected frames: " + (ExpectedFrames(stopWatch.ElapsedMilliseconds) - 1));
  
  
  
              launchingFFMPEG.StandardInput.Close();
  
  
  
  #if DEBUG
  
              string line;
  
              while ((line = launchingFFMPEG.StandardError.ReadLine()) != null)
  
              {
  
                  Logger.log.Debug(line);
  
              }
  
  #endif
  
              launchingFFMPEG.Close();
  
              alertBox.Show();
  
          }
  
  
  
          void RequestD3DScreenShot()
  
          {
  
              captureProcess.CaptureInterface.BeginGetScreenshot(new Rectangle(0, 0, 0, 0), new TimeSpan(0, 0, 2), Callback, resize, (ImageFormat)Enum.Parse(typeof(ImageFormat), "Bitmap"));
  
          }
  
  
  
          private void AttachProcess(string exe)
  
          {
  
              Thread.Sleep(300);
  
              Process[] processes = Process.GetProcessesByName(Path.GetFileNameWithoutExtension(exe));
  
              foreach (Process currProcess in processes)
  
              {
  
                  // Simply attach to the first one found.
  
  
  
                  // If the process doesn't have a mainwindowhandle yet, skip it (we need to be able to get the hwnd to set foreground etc)
  
                  if (currProcess.MainWindowHandle == IntPtr.Zero)
  
                  {
  
                      continue;
  
                  }
  
  
  
                  // Skip if the process is already hooked (and we want to hook multiple applications)
  
                  if (HookManager.IsHooked(currProcess.Id))
  
                  {
  
                      continue;
  
                  }
  
  
  
                  Direct3DVersion direct3DVersion = Direct3DVersion.AutoDetect;
  
  
  
                  CaptureConfig cc = new CaptureConfig()
  
                  {
  
                      Direct3DVersion = direct3DVersion,
  
                      ShowOverlay = false
  
                  };
  
  
  
                  processId = currProcess.Id;
  
                  process = currProcess;
  
  
  
                  var captureInterface = new CaptureInterface();
  
                  captureInterface.RemoteMessage += new MessageReceivedEvent(CaptureInterface_RemoteMessage);
  
                  captureProcess = new CaptureProcess(process, cc, captureInterface);
  
  
  
                  break;
  
              }
  
              Thread.Sleep(10);
  
  
  
              if (captureProcess == null)
  
              {
  
                  ShowUser.Exception("No executable found matching: '" + exe + "'");
  
              }
  
          }
  
  
  
          /// <summary>
  
          /// The callback for when the screenshot has been taken
  
          /// </summary>
  
          /// 
  
          /// 
  
          /// 
  
          void Callback(IAsyncResult result)
  
          {
  
              using (Screenshot screenshot = captureProcess.CaptureInterface.EndGetScreenshot(result))
  
              if (screenshot != null &amp;&amp; screenshot.Data != null &amp;&amp; arg != null)
  
              {
  
                  if (image != null)
  
                  {
  
                      image.Dispose();
  
                  }
  
  
  
                  image = screenshot.ToBitmap();
  
                  // image.Save("D3DImageTest.bmp");
  
                  image.Save(launchingFFMPEG.StandardInput.BaseStream, System.Drawing.Imaging.ImageFormat.Bmp);
  
                  launchingFFMPEG.StandardInput.Flush();
  
                  frame++;
  
              }
  
  
  
              if (frame &lt; 5)
  
              {
  
                  Thread t = new Thread(new ThreadStart(RequestD3DScreenShot));
  
                  t.Start();
  
              }
  
              else
  
              {
  
                  Logger.log.Info("Done getting shots from D3D.");
  
              }
  
          }
  
  
  
          /// <summary>
  
          /// Display messages from the target process
  
          /// </summary>
  
          /// 
  
          private void CaptureInterface_RemoteMessage(MessageReceivedEventArgs message)
  
          {
  
              Logger.log.Info(message);
  
          }
  
      }
  
  }

  When I search the internet for the error all I get is the FFMPEG source code, which has not proven to be illuminating. I have been able to save the image directly to disk, which makes me feel like it is not an issue with disposing the data. I have also tried only grabbing one frame, but that produces the same error, which suggests to me it is not a threading issue.

  Here is the full sample of stderr :

  2016-06-02 18:29:38,046 === ffmpeg version N-79143-g8ff0f6a Copyright (c) 2000-2016 the FFmpeg developers
  
  
  
  2016-06-02 18:29:38,047 ===   built with gcc 5.3.0 (GCC)
  
  
  
  2016-06-02 18:29:38,048 ===   configuration: --enable-gpl
  
  --enable-version3 --disable-w32threads --enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libdcadec --enable-libfreetype --enable-libgme --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmfx --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-librtmp --enable-libschroedinger --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxavs --enable-libxvid --enable-libzimg --enable-lzma --enable-decklink --enable-zlib
  
  
  
  2016-06-02 18:29:38,062 ===   libavutil      55. 19.100 / 55. 19.100
  
  
  
  2016-06-02 18:29:38,063 ===   libavcodec     57. 30.100 / 57. 30.100
  
  
  
  2016-06-02 18:29:38,064 ===   libavformat    57. 29.101 / 57. 29.101
  
  
  
  2016-06-02 18:29:38,064 ===   libavdevice    57.  0.101 / 57.  0.101
  
  
  
  2016-06-02 18:29:38,065 ===   libavfilter     6. 40.102 /  6. 40.102
  
  
  
  2016-06-02 18:29:38,066 ===   libswscale      4.  0.100 /  4.  0.100
  
  
  
  2016-06-02 18:29:38,067 ===   libswresample   2.  0.101 /  2.  0.101
  
  
  
  2016-06-02 18:29:38,068 ===   libpostproc    54.  0.100 / 54.  0.100
  
  
  
  2016-06-02 18:29:38,068 === [bmp @ 000002cd7e5cc280] not enough data (13070 < 8294454), trying to decode anyway
  
  
  
  2016-06-02 18:29:38,069 === [bmp @ 000002cd7e5cc280] not enough data (13016 < 8294400)
  
  
  
  2016-06-02 18:29:38,069 === Input #0, image2pipe, from 'pipe:.bmp':
  
  
  
  2016-06-02 18:29:38,262 ===   Duration: N/A, bitrate: N/A
  
  
  
  2016-06-02 18:29:38,262 ===     Stream #0:0: Video: bmp, bgra, 1920x1080, 8 tbr, 8 tbn, 8 tbc
  
  
  
  2016-06-02 18:29:38,263 === [libx264 @ 000002cd7e5d59a0] VBV bufsize set but maxrate unspecified, ignored
  
  
  
  2016-06-02 18:29:38,264 === [libx264 @ 000002cd7e5d59a0] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 AVX2 LZCNT BMI2
  
  
  
  2016-06-02 18:29:38,265 === [libx264 @ 000002cd7e5d59a0] profile Constrained Baseline, level 1.1
  
  
  
  2016-06-02 18:29:38,266 === [libx264 @ 000002cd7e5d59a0] 264 - core 148 r2665 a01e339 - H.264/MPEG-4 AVC codec - Copyleft 2003-2016 - http://www.videolan.org/x264.html - options: cabac=0 ref=1 deblock=0:0:0 analyse=0:0 me=dia subme=0 psy=1 psy_rd=1.00:0.00 mixed_ref=0 me_range=16 chroma_me=1 trellis=0 8x8dct=0 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=0 threads=6 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=0 weightp=0 keyint=250 keyint_min=8 scenecut=0 intra_refresh=0 rc=crf mbtree=0 crf=18.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=0
  
  
  
  2016-06-02 18:29:38,463 === Output #0, mp4, to 'C:\Users\fores\AppData\Roaming\Affectiva\n_Artifacts_20160602_182857\GameplayVidOut.mp4':
  
  
  
  2016-06-02 18:29:38,464 ===   Metadata:
  
  
  
  2016-06-02 18:29:38,465 ===     encoder         : Lavf57.29.101
  
  
  
  2016-06-02 18:29:38,469 ===     Stream #0:0: Video: h264 (libx264) ([33][0][0][0] / 0x0021), yuv420p, 320x180, q=-1--1, 8 fps, 16384 tbn, 8 tbc
  
  
  
  2016-06-02 18:29:38,470 ===     Metadata:
  
  
  
  2016-06-02 18:29:38,472 ===       encoder         : Lavc57.30.100 libx264
  
  
  
  2016-06-02 18:29:38,474 ===     Side data:
  
  
  
  2016-06-02 18:29:38,475 ===       cpb: bitrate max/min/avg: 0/0/0 buffer size: 30000000 vbv_delay: -1
  
  
  
  2016-06-02 18:29:38,476 === Stream mapping:
  
  
  
  2016-06-02 18:29:38,477 ===   Stream #0:0 -> #0:0 (bmp (native) -> h264 (libx264))
  
  
  
  2016-06-02 18:29:38,480 === [bmp @ 000002cd7e5cc9a0] not enough data (13070 < 8294454), trying to decode anyway
  
  
  
  2016-06-02 18:29:38,662 === [bmp @ 000002cd7e5cc9a0] not enough data (13016 < 8294400)
  
  
  
  2016-06-02 18:29:38,662 === Error while decoding stream #0:0: Invalid data found when processing input
  
  
  
  2016-06-02 18:29:38,663 === frame=    0 fps=0.0 q=0.0 Lsize=       0kB time=00:00:00.00 bitrate=N/A speed=   0x    
  
  
  
  2016-06-02 18:29:38,663 === video:0kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown
  
  
  
  2016-06-02 18:29:38,664 === Conversion failed!

  In memory, the current image is 320 pixels wide and 180 pixels long. The pixel format is Format32bppRgb. The horizontal and vertical resolutions seem odd, they are both 96.01199. When filed to disk here is ffprobe output for the file :

  ffprobe version N-79143-g8ff0f6a Copyright (c) 2007-2016 the FFmpeg developers
  
    built with gcc 5.3.0 (GCC)
  
    configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libdcadec --enable-libfreetype --enable-libgme --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmfx --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-librtmp --enable-libschroedinger --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxavs --enable-libxvid --enable-libzimg --enable-lzma --enable-decklink --enable-zlib
  
    libavutil      55. 19.100 / 55. 19.100
  
    libavcodec     57. 30.100 / 57. 30.100
  
    libavformat    57. 29.101 / 57. 29.101
  
    libavdevice    57.  0.101 / 57.  0.101
  
    libavfilter     6. 40.102 /  6. 40.102
  
    libswscale      4.  0.100 /  4.  0.100
  
    libswresample   2.  0.101 /  2.  0.101
  
    libpostproc    54.  0.100 / 54.  0.100
  
  Input #0, png_pipe, from 'C:\Users\fores\git\game-playtest-tool\GamePlayTest\bin\x64\Debug\D3DFromCapture.bmp':
  
    Duration: N/A, bitrate: N/A
  
      Stream #0:0: Video: png, rgba(pc), 1920x1080 [SAR 3779:3779 DAR 16:9], 25 tbr, 25 tbn, 25 tbc

  Here is a PNG version of an example screenshot from the current code (playing Portal 2) :
  

  Any ideas would be greatly appreciated. My current workaround is to save the files to the HDD and compile the video after gameplay, but it’s a far less performant option. Thank you !

• What is PII ? Your introduction to personally identifiable information

  15 janvier 2020, par Joselyn Khor — Analytics Tips, Privacy, Security
  Most websites you visit collect information about you via tools like Google Analytics and Matomo – sometimes collecting personally identifiable information (PII).

  When it comes to PII, people are becoming more concerned about data privacy. Identifiable information can be used for illegal purposes like identity theft and fraud. 

  So how can you protect yourself as an innocent internet browser ? In the case of website owners – how do you protect users and your company from falling prey to privacy breaches ?

  

  As one of the most trusted analytics companies, we feel our readers would benefit from being as informed as possible about data privacy issues and PII. Learn what it means, and what you can do to keep yours or others’ information safe.

  Table of Contents

  What does PII stand for ?

  PII acronym

  PII is an acronym for personally identifiable information.

  PII definition

  Personally identifiable information (PII) is a term used predominantly in the United States.

  The appendix of OMB M-10-23 (Guidance for Agency Use of Third-Party Website and Applications) gives this definition for PII :

  “The term ‘personally identifiable information’ refers to information which can be used to distinguish or trace an individual’s identity, such as their name, social security number, biometric records, etc. alone, or when combined with other personal or identifying information which is linked or linkable to a specific individual, such as date and place of birth, mother’s maiden name, etc.”

  What can be considered personally identifiable information (PII) ? Some PII examples :

  • Full name/usernames
  • Home address/mailing address
  • Email address
  • Credit card numbers
  • Date of birth
  • Phone numbers
  • Login details

  • Precise locations
  • Account numbers
  • Passwords
  • Security codes (including biometric records)
  • Personal identification numbers
  • Driver license number
  • Get a more comprehensive list here

  What’s non-PII ?

  Anonymous information, or information that can’t be traced back to an individual, can be considered non-PII.

  Who is affected by the exploitation of PII ?

  Anyone can be affected by the exploitation of personal data, where you have identity theft, account fraud and account takeovers. When websites resort to illegally selling or sharing your data and compromising your privacy, the fear is falling victim to such fraudulent activity. 

  PII can also be an issue when employees have access to the database and the data is not encrypted. For example, anyone working in a bank can access your accounts ; anyone working at Facebook may be able to read your messages. This shows how privacy breaches can easily happen when employees have access to PII.

  Website owner’s responsibility for data privacy (PII and analytics)

  To respect your website visitor’s privacy, best practice is to avoid collecting PII whenever possible. If you work in an industry which requires people to disclose personal information (e.g. healthcare, security industries, public sector), then you must ensure this data is collected and handled securely. 

  

  The US National Institute of Standards and Technology states : “The likelihood of harm caused by a breach involving PII is greatly reduced if an organisation minimises the amount of PII it uses, collects, and stores. For example, an organisation should only request PII in a new form if the PII is absolutely necessary.” 

  How you’re held accountable remains up to the privacy laws of the country you’re doing business in. Make sure you are fully aware of the privacy and data protection laws that relate specifically to you. 

  To reduce the risk of privacy breaches, try collecting as little PII as you can ; purging it as soon as you can ; and making sure your IT security is updated and protected against security threats. 

  If you’re using data collection tools like web analytics, data may be tracked through features like User ID, custom variables, and custom dimensions. Sometimes they are also harder to identify when they are present, for example, in page URLs, page titles, or referrers URLs. So make sure you’re optimising your web analytics tools’ settings to ensure you’re asking your users for consent and respecting users’ privacy.

  If you’re using a GDPR compliant tool like Matomo, learn how you can stop processing such personal data

  PII, GDPR and businesses in the US/EU

  Because PII is broad, you may run into confusion when considering PII and GDPR (which applies in the EU). The General Data Protection Regulation (GDPR) provides more safeguards for user privacy.

  GDPR grants people in the EU more rights concerning their “personal data” (more on PII vs personal data below). In the EU the GDPR restricts the collection and processing of personal data. The repercussions are severe penalties and fines for privacy infringements. Businesses are required to handle this personal data carefully. You can be fined up to 4% of their yearly revenue for data breaches or non-compliance. 

  

  Although there isn’t an overarching data protection law in the US, there are hundreds of laws on both the federal and state levels to protect the personal data of US residents. US Congress has also enacted industry-specific statutes related to data privacy, and the state of California passed the California Consumer Privacy Act. 

  To be on the safe side, if you are using analytics, follow matters relating to “personal data” in the GDPR. It’s all-encompassing when it comes to protecting user privacy. GDPR rules still apply whenever an EU citizen visits any non EU site (that processes personal data).

  Personally identifiable information (PII) vs personal data

  PII and “personal data” aren’t used interchangeably. All personal data can be PII, but not all PII can be defined as personal data.

  The definition of “personal data” according to the GDPR :

  

  This means “personal data” encompasses a greater number of identifiers which include the online sphere. Examples include : IP addresses and URL names. As well as seemingly “innocent” data like height, job position, company etc. 

  What’s considered personal data depends on the context. If a piece of information can be combined with others to establish someone’s identity then that can be considered personal data. 

  Under GDPR, when processing personal data, you need explicit consent. You need to ensure you’re compliant according to GDPR definitions of “personal data” not just what’s considered “PII”.

  How Matomo deals with PII and personal data

  Although Matomo Analytics is a web analytics software that tracks user activity on your website, we take privacy and PII very seriously – on both our Cloud and On-Premise offerings. 

  If you’re using Matomo and would like to know how you can be fully GDPR compliant and protect user privacy, read more :
  

  • Learn how to not process any personally identifiable information – Anonymise IP addresses, user IDs, and order IDs
  • Matomo protects user privacy by talking the talk and walking the walk
  • Stay ahead of the GDPR with a privacy-respecting analytics platform
  • 11 ways Matomo helps you protect your visitor’s privacy

  Disclaimer

  We are not lawyers and don’t claim to be. The information provided here is to help give an introduction to issues you may encounter when dealing with PII. We encourage every business and website to take data privacy seriously and discuss these issues with your lawyer if you have any concerns. 

  Additional resources :

  • https://www.consumeraffairs.com/finance/identity-theft-statistics.html#identity-theft-trends-in-2019
  • https://ec.europa.eu/info/law/law-topic/data-protection_en
  • https://iclg.com/practice-areas/data-protection-laws-and-regulations/usa
  • https://www.csoonline.com/article/3215864/how-to-protect-personally-identifiable-information-pii-under-gdpr.html
  • https://ico.org.uk/for-organisations/guide-to-data-protection/guide-to-the-general-data-protection-regulation-gdpr/key-definitions/what-is-personal-data/