Recherche avancée

Sur d’autres sites (8190)

• Your introduction to personally identifiable information : What is PII ?

  15 janvier 2020, par Joselyn Khor — Analytics Tips, Privacy, Security
  When it comes to personally identifiable information (PII), people are becoming more concerned with data privacy. Identifiable information can be used for illegal purposes like identity theft and fraud. 

  So how can you protect yourself as an innocent web browser ?

  If you’re a website owner – 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 how you can 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 mainly used 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 misuse of personal data. Websites can compromise your privacy by mishandling or illegally selling/sharing your data. That may lead identity theft, account fraud and account takeovers. 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 ; and anyone working at Facebook can 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)

  If you’re using a web analytics tool like Google Analytics or Matomo, best practise is to not collect PII if possible. This is to better respect your website visitor’s privacy. 

  If you work in an industry which needs people to share personal information (e.g. healthcare, security industries, public sector), then you must collect and handle this data 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. 

  With 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

  You may get confused when considering PII and GDPR (which applies in the EU). The General Data Protection Regulation (GDPR) gives people in the EU more rights over “personal data” – which covers more identifiers than PII (more on PII vs personal data below). GDPR restricts the collection and processing of personal data so businesses need to handle this personal data carefully. 

  According to the GDPR, you can be fined up to 4% of their yearly revenue for data/privacy breaches or non-compliance. 

  

  In the US, there isn’t one overarching data protection law, but there are hundreds of laws on both the federal and state levels to protect PII of US residents. US Congress has enacted industry-specific statutes related to data privacy like HIPAA. Recently state of California also passed the California Consumer Privacy Act (CCPA). 

  To be on the safe side, if you’re using analytics, follow matters relating to “personal data” in the GDPR. It covers more 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” covers more identifiers, including online identifiers. Examples include : IP addresses and URL names. As well as seemingly “innocent” data like height, job position, company etc. 

  What’s seen as 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. So best to be compliant according to GDPR definitions of “personal data” not just what’s considered “PII”.

  How do you keep PII safe ?

  • Try not to give your data away so easily. Read through terms and conditions.
  • Don’t just click ‘agree’ when faced with consent screens, as consent screens are majorly flawed. 
  • Disable third party cookies by default. 
  • Use strong passwords.
  • Be wary of public wifi – hackers can easily access your PII or sensitive data. Use a VPN (virtual private network)
  • Read more on how to keep PII safe. For businesses here’s a checklist on PII compliance.

  How Matomo deals with PII and personal data

  Although Matomo Analytics is a web analytics tool 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/

• On-premise analytics demand grows as Google Analytics GDPR uncertainties continue

  7 janvier 2020, par Jake Thornton — Privacy

  The Google Analytics GDPR relationship is a complicated one. Website owners in states like Berlin in Germany are now required to ask users for consent to collect their data. This doesn’t make for the friendliest user-experience and often the website visitor will simply click “no.”

  The problem Google Analytics now presents website owners in the EU is with more visitors clicking “no”, the less accurate your data will become.

  Why do you need to ask your visitors for consent ?

  At this stage it’s simply because Google Analytics collects data for its own purposes. An example of this is using your visitor’s personal data for retargeting purposes across their advertising platforms like Google Ads and YouTube. 

  Google’s Privacy & Terms states : “when you visit a website that uses advertising services like AdSense, including analytics tools like Google Analytics, or embeds video content from YouTube, your web browser automatically sends certain information to Google. This includes the URL of the page you’re visiting and your IP address. We may also set cookies on your browser or read cookies that are already there. Apps that use Google advertising services also share information with Google, such as the name of the app and a unique identifier for advertising.”

  

  The rise of hosting web analytics on-premise

  Managing Google Analytics and GDPR can quickly become complicated, so there’s been an increase in website owners switching from cloud-hosted web analytics platforms, like Google Analytics, to more GDPR compliant alternatives, where you can host web analytics software on your own servers. This is called hosting web analytics on-premise.

  Hosting web analytics on your own servers means :

  No third-parties are involved

  The visitor data your website collects is stored on your own internal infrastructure. This means no third-parties are involved and there’s no risk of personal data being used in the way Google Analytics uses it e.g. sending personal data to its advertising platforms. 

  When you sign up with Google Analytics you sign away control of your user’s personal data. With on-premise website analytics, you own your data and are in full control.

  NOTE : Though Google Analytics uses personal data for its own purposes, not all cloud hosted web analytics platforms do this. As an example, Matomo Analytics Cloud hosted solution states that all personal data collected is not used for its own purposes and that Matomo has no rights in accessing or using this personal data. 

  

  You control where in the world your personal data is stored

  Google Analytics servers are based out of USA, Europe and Asia, so where your personal data will end up is uncertain and you don’t have the option to choose which location it goes to when using free Google Analytics.

  Different countries have different laws when it comes to accessing personal data. When you choose to host your web analytics on-premise, you can choose the location of your servers and where the personal data is stored.

  More flexibility

  With self-hosted web analytics platforms like Matomo On-Premise, you can extend the platform to do anything you want without the restrictions that cloud hosted platforms impose.

  You can :

  • Get full access to the source code of open-source solutions, like Matomo
  • Extend the platform however you want for your business
  • Get access to APIs
  • Have no data limitations or restrictions
  • Get RAW data access
  • Have control over security

  >> Read more about on-premise flexibility for web analytics here

  

  So what does the future look like for Google Analytics and GDPR ?

  It’s difficult to assess this right now. How exactly GDPR is enforced is still quite unclear. 

  What is clear however, is now website owners in Berlin using Google Analytics are lawfully required to ask their visitors for consent to collect personal data. It has been reported that Google Analytics has already received 200,000 complaints in Germany alone and it appears this trend is likely to continue across much of the EU.

  When using Google Analytics in the EU you must also ensure your privacy policy is updated so website visitors are aware that data is being collected through Google Analytics for its own purposes.

  Moving to a web analytics on-premise platform

  Matomo Analytics is the #1 open-source web analytics platform in the world and has been rated as an exceptional alternative to Google Analytics. Check the reviews on Capterra.

  Choosing Matomo On-Premise means you can control exactly where your data is stored, you have full flexibility to customise the platform to do what you want and it’s FREE.

  Matomo’s mission is to give control back to website owners and the team has designed the platform so that moving away from Google Analytics is seamless. Matomo offers most of your favourite Google Analytics features, a leaner interface to navigate, and the option to add free and paid premium features that Google Analytics can’t even offer you.

  And now you can import your historical Google Analytics data directly into your Matomo with the Google Analytics Importer plugin.

  DOWNLOAD MATOMO (FREE)

  And if you can’t host web analytics on your own servers ...

  Hosting web analytics on-premise is not an option for all businesses as you do need the internal infrastructure and technical knowledge to host your own platform.

  If you can’t self-host, then Matomo has a Cloud hosted solution you can easily install and operate like Google Analytics, which is hosted on Matomo’s servers in the EU. 

  The GDPR advantages of choosing Matomo Cloud over Google Analytics are :

  • Servers are secure and based in the EU (strict laws forbid outside access)
  • 100% data ownership – we never use data for our own purposes
  • You can export your data anytime and switch to Matomo On-Premise whenever you like
  • User-privacy protection
  • Advanced GDPR Manager and data anonymisation features which GA doesn’t offer

  

  Interested to learn more ?

  If you are wanting to learn more about why users are making the move from Google Analytics to Matomo, check out our Matomo Analytics vs Google Analytics comparison page.

  >> Matomo Analytics vs Google Analytics

• Getting green screen in ffplay : Streaming desktop (DirectX surface) as H264 video over RTP stream using Live555

  7 novembre 2019, par Ram

  I’m trying to stream the desktop(DirectX surface in NV12 format) as H264 video over RTP stream using Live555 & Windows media foundation’s hardware encoder on Windows10, and expecting it to be rendered by ffplay (ffmpeg 4.2). But only getting a green screen like below,

  

  

  

  

  I referred MFWebCamToRTP mediafoundation-sample & Encoding DirectX surface using hardware MFT for implementing live555’s FramedSource and changing the input source to DirectX surface instead of webCam.

  Here is an excerpt of my implementation for Live555’s doGetNextFrame callback to feed input samples from directX surface :

  virtual void doGetNextFrame()
  
  {
  
      if (!_isInitialised)
  
      {
  
          if (!initialise()) {
  
              printf("Video device initialisation failed, stopping.");
  
              return;
  
          }
  
          else {
  
              _isInitialised = true;
  
          }
  
      }
  
  
  
      //if (!isCurrentlyAwaitingData()) return;
  
  
  
      DWORD processOutputStatus = 0;
  
      HRESULT mftProcessOutput = S_OK;
  
      MFT_OUTPUT_STREAM_INFO StreamInfo;
  
      IMFMediaBuffer *pBuffer = NULL;
  
      IMFSample *mftOutSample = NULL;
  
      DWORD mftOutFlags;
  
      bool frameSent = false;
  
      bool bTimeout = false;
  
  
  
      // Create sample
  
      CComPtr<imfsample> videoSample = NULL;
  
  
  
      // Create buffer
  
      CComPtr<imfmediabuffer> inputBuffer;
  
      // Get next event
  
      CComPtr<imfmediaevent> event;
  
      HRESULT hr = eventGen->GetEvent(0, &amp;event);
  
      CHECK_HR(hr, "Failed to get next event");
  
  
  
      MediaEventType eventType;
  
      hr = event->GetType(&amp;eventType);
  
      CHECK_HR(hr, "Failed to get event type");
  
  
  
  
  
      switch (eventType)
  
      {
  
      case METransformNeedInput:
  
          {
  
              hr = MFCreateDXGISurfaceBuffer(__uuidof(ID3D11Texture2D), surface, 0, FALSE, &amp;inputBuffer);
  
              CHECK_HR(hr, "Failed to create IMFMediaBuffer");
  
  
  
              hr = MFCreateSample(&amp;videoSample);
  
              CHECK_HR(hr, "Failed to create IMFSample");
  
              hr = videoSample->AddBuffer(inputBuffer);
  
              CHECK_HR(hr, "Failed to add buffer to IMFSample");
  
  
  
              if (videoSample)
  
              {
  
                  _frameCount++;
  
  
  
                  CHECK_HR(videoSample->SetSampleTime(mTimeStamp), "Error setting the video sample time.\n");
  
                  CHECK_HR(videoSample->SetSampleDuration(VIDEO_FRAME_DURATION), "Error getting video sample duration.\n");
  
  
  
                  // Pass the video sample to the H.264 transform.
  
  
  
                  hr = _pTransform->ProcessInput(inputStreamID, videoSample, 0);
  
                  CHECK_HR(hr, "The resampler H264 ProcessInput call failed.\n");
  
  
  
                  mTimeStamp += VIDEO_FRAME_DURATION;
  
              }
  
          }
  
  
  
          break;
  
  
  
      case METransformHaveOutput:
  
  
  
          {
  
              CHECK_HR(_pTransform->GetOutputStatus(&amp;mftOutFlags), "H264 MFT GetOutputStatus failed.\n");
  
  
  
              if (mftOutFlags == MFT_OUTPUT_STATUS_SAMPLE_READY)
  
              {
  
                  MFT_OUTPUT_DATA_BUFFER _outputDataBuffer;
  
                  memset(&amp;_outputDataBuffer, 0, sizeof _outputDataBuffer);
  
                  _outputDataBuffer.dwStreamID = outputStreamID;
  
                  _outputDataBuffer.dwStatus = 0;
  
                  _outputDataBuffer.pEvents = NULL;
  
                  _outputDataBuffer.pSample = nullptr;
  
  
  
                  mftProcessOutput = _pTransform->ProcessOutput(0, 1, &amp;_outputDataBuffer, &amp;processOutputStatus);
  
  
  
                  if (mftProcessOutput != MF_E_TRANSFORM_NEED_MORE_INPUT)
  
                  {
  
                      if (_outputDataBuffer.pSample) {
  
  
  
                          //CHECK_HR(_outputDataBuffer.pSample->SetSampleTime(mTimeStamp), "Error setting MFT sample time.\n");
  
                          //CHECK_HR(_outputDataBuffer.pSample->SetSampleDuration(VIDEO_FRAME_DURATION), "Error setting MFT sample duration.\n");
  
  
  
                          IMFMediaBuffer *buf = NULL;
  
                          DWORD bufLength;
  
                          CHECK_HR(_outputDataBuffer.pSample->ConvertToContiguousBuffer(&amp;buf), "ConvertToContiguousBuffer failed.\n");
  
                          CHECK_HR(buf->GetCurrentLength(&amp;bufLength), "Get buffer length failed.\n");
  
                          BYTE * rawBuffer = NULL;
  
  
  
                          fFrameSize = bufLength;
  
                          fDurationInMicroseconds = 0;
  
                          gettimeofday(&amp;fPresentationTime, NULL);
  
  
  
                          buf->Lock(&amp;rawBuffer, NULL, NULL);
  
                          memmove(fTo, rawBuffer, fFrameSize);
  
  
  
                          FramedSource::afterGetting(this);
  
  
  
                          buf->Unlock();
  
                          SafeRelease(&amp;buf);
  
  
  
                          frameSent = true;
  
                          _lastSendAt = GetTickCount();
  
  
  
                          _outputDataBuffer.pSample->Release();
  
                      }
  
  
  
                      if (_outputDataBuffer.pEvents)
  
                          _outputDataBuffer.pEvents->Release();
  
                  }
  
  
  
                  //SafeRelease(&amp;pBuffer);
  
                  //SafeRelease(&amp;mftOutSample);
  
  
  
                  break;
  
              }
  
          }
  
  
  
          break;
  
      }
  
  
  
      if (!frameSent)
  
      {
  
          envir().taskScheduler().triggerEvent(eventTriggerId, this);
  
      }
  
  
  
      return;
  
  
  
  done:
  
  
  
      printf("MediaFoundationH264LiveSource doGetNextFrame failed.\n");
  
      envir().taskScheduler().triggerEvent(eventTriggerId, this);
  
  }
  
  </imfmediaevent></imfmediabuffer></imfsample>

  Initialise method :

  bool initialise()
  
  {
  
      HRESULT hr;
  
      D3D11_TEXTURE2D_DESC desc = { 0 };
  
  
  
      HDESK CurrentDesktop = nullptr;
  
      CurrentDesktop = OpenInputDesktop(0, FALSE, GENERIC_ALL);
  
      if (!CurrentDesktop)
  
      {
  
          // We do not have access to the desktop so request a retry
  
          return false;
  
      }
  
  
  
      // Attach desktop to this thread
  
      bool DesktopAttached = SetThreadDesktop(CurrentDesktop) != 0;
  
      CloseDesktop(CurrentDesktop);
  
      CurrentDesktop = nullptr;
  
      if (!DesktopAttached)
  
      {
  
          printf("SetThreadDesktop failed\n");
  
      }
  
  
  
      UINT32 activateCount = 0;
  
  
  
      // h264 output
  
      MFT_REGISTER_TYPE_INFO info = { MFMediaType_Video, MFVideoFormat_H264 };
  
  
  
      UINT32 flags =
  
          MFT_ENUM_FLAG_HARDWARE |
  
          MFT_ENUM_FLAG_SORTANDFILTER;
  
  
  
      // ------------------------------------------------------------------------
  
      // Initialize D3D11
  
      // ------------------------------------------------------------------------
  
  
  
      // Driver types supported
  
      D3D_DRIVER_TYPE DriverTypes[] =
  
      {
  
          D3D_DRIVER_TYPE_HARDWARE,
  
          D3D_DRIVER_TYPE_WARP,
  
          D3D_DRIVER_TYPE_REFERENCE,
  
      };
  
      UINT NumDriverTypes = ARRAYSIZE(DriverTypes);
  
  
  
      // Feature levels supported
  
      D3D_FEATURE_LEVEL FeatureLevels[] =
  
      {
  
          D3D_FEATURE_LEVEL_11_0,
  
          D3D_FEATURE_LEVEL_10_1,
  
          D3D_FEATURE_LEVEL_10_0,
  
          D3D_FEATURE_LEVEL_9_1
  
      };
  
      UINT NumFeatureLevels = ARRAYSIZE(FeatureLevels);
  
  
  
      D3D_FEATURE_LEVEL FeatureLevel;
  
  
  
      // Create device
  
      for (UINT DriverTypeIndex = 0; DriverTypeIndex < NumDriverTypes; ++DriverTypeIndex)
  
      {
  
          hr = D3D11CreateDevice(nullptr, DriverTypes[DriverTypeIndex], nullptr,
  
              D3D11_CREATE_DEVICE_VIDEO_SUPPORT,
  
              FeatureLevels, NumFeatureLevels, D3D11_SDK_VERSION, &device, &FeatureLevel, &context);
  
          if (SUCCEEDED(hr))
  
          {
  
              // Device creation success, no need to loop anymore
  
              break;
  
          }
  
      }
  
  
  
      CHECK_HR(hr, "Failed to create device");
  
  
  
      // Create device manager
  
      UINT resetToken;
  
      hr = MFCreateDXGIDeviceManager(&resetToken, &deviceManager);
  
      CHECK_HR(hr, "Failed to create DXGIDeviceManager");
  
  
  
      hr = deviceManager->ResetDevice(device, resetToken);
  
      CHECK_HR(hr, "Failed to assign D3D device to device manager");
  
  
  
  
  
      // ------------------------------------------------------------------------
  
      // Create surface
  
      // ------------------------------------------------------------------------
  
      desc.Format = DXGI_FORMAT_NV12;
  
      desc.Width = surfaceWidth;
  
      desc.Height = surfaceHeight;
  
      desc.MipLevels = 1;
  
      desc.ArraySize = 1;
  
      desc.SampleDesc.Count = 1;
  
  
  
      hr = device->CreateTexture2D(&desc, NULL, &surface);
  
      CHECK_HR(hr, "Could not create surface");
  
  
  
      hr = MFTEnumEx(
  
          MFT_CATEGORY_VIDEO_ENCODER,
  
          flags,
  
          NULL,
  
          &info,
  
          &activateRaw,
  
          &activateCount
  
      );
  
      CHECK_HR(hr, "Failed to enumerate MFTs");
  
  
  
      CHECK(activateCount, "No MFTs found");
  
  
  
      // Choose the first available encoder
  
      activate = activateRaw[0];
  
  
  
      for (UINT32 i = 0; i < activateCount; i++)
  
          activateRaw[i]->Release();
  
  
  
      // Activate
  
      hr = activate->ActivateObject(IID_PPV_ARGS(&_pTransform));
  
      CHECK_HR(hr, "Failed to activate MFT");
  
  
  
      // Get attributes
  
      hr = _pTransform->GetAttributes(&attributes);
  
      CHECK_HR(hr, "Failed to get MFT attributes");
  
  
  
      // Unlock the transform for async use and get event generator
  
      hr = attributes->SetUINT32(MF_TRANSFORM_ASYNC_UNLOCK, TRUE);
  
      CHECK_HR(hr, "Failed to unlock MFT");
  
  
  
      eventGen = _pTransform;
  
      CHECK(eventGen, "Failed to QI for event generator");
  
  
  
      // Get stream IDs (expect 1 input and 1 output stream)
  
      hr = _pTransform->GetStreamIDs(1, &inputStreamID, 1, &outputStreamID);
  
      if (hr == E_NOTIMPL)
  
      {
  
          inputStreamID = 0;
  
          outputStreamID = 0;
  
          hr = S_OK;
  
      }
  
      CHECK_HR(hr, "Failed to get stream IDs");
  
  
  
       // ------------------------------------------------------------------------
  
      // Configure hardware encoder MFT
  
     // ------------------------------------------------------------------------
  
      CHECK_HR(_pTransform->ProcessMessage(MFT_MESSAGE_SET_D3D_MANAGER, reinterpret_cast(deviceManager.p)), "Failed to set device manager.\n");
  
  
  
      // Set low latency hint
  
      hr = attributes->SetUINT32(MF_LOW_LATENCY, TRUE);
  
      CHECK_HR(hr, "Failed to set MF_LOW_LATENCY");
  
  
  
      hr = MFCreateMediaType(&outputType);
  
      CHECK_HR(hr, "Failed to create media type");
  
  
  
      hr = outputType->SetGUID(MF_MT_MAJOR_TYPE, MFMediaType_Video);
  
      CHECK_HR(hr, "Failed to set MF_MT_MAJOR_TYPE on H264 output media type");
  
  
  
      hr = outputType->SetGUID(MF_MT_SUBTYPE, MFVideoFormat_H264);
  
      CHECK_HR(hr, "Failed to set MF_MT_SUBTYPE on H264 output media type");
  
  
  
      hr = outputType->SetUINT32(MF_MT_AVG_BITRATE, TARGET_AVERAGE_BIT_RATE);
  
      CHECK_HR(hr, "Failed to set average bit rate on H264 output media type");
  
  
  
      hr = MFSetAttributeSize(outputType, MF_MT_FRAME_SIZE, desc.Width, desc.Height);
  
      CHECK_HR(hr, "Failed to set frame size on H264 MFT out type");
  
  
  
      hr = MFSetAttributeRatio(outputType, MF_MT_FRAME_RATE, TARGET_FRAME_RATE, 1);
  
      CHECK_HR(hr, "Failed to set frame rate on H264 MFT out type");
  
  
  
      hr = outputType->SetUINT32(MF_MT_INTERLACE_MODE, 2);
  
      CHECK_HR(hr, "Failed to set MF_MT_INTERLACE_MODE on H.264 encoder MFT");
  
  
  
      hr = outputType->SetUINT32(MF_MT_ALL_SAMPLES_INDEPENDENT, TRUE);
  
      CHECK_HR(hr, "Failed to set MF_MT_ALL_SAMPLES_INDEPENDENT on H.264 encoder MFT");
  
  
  
      hr = _pTransform->SetOutputType(outputStreamID, outputType, 0);
  
      CHECK_HR(hr, "Failed to set output media type on H.264 encoder MFT");
  
  
  
      hr = MFCreateMediaType(&inputType);
  
      CHECK_HR(hr, "Failed to create media type");
  
  
  
      for (DWORD i = 0;; i++)
  
      {
  
          inputType = nullptr;
  
          hr = _pTransform->GetInputAvailableType(inputStreamID, i, &inputType);
  
          CHECK_HR(hr, "Failed to get input type");
  
  
  
          hr = inputType->SetGUID(MF_MT_MAJOR_TYPE, MFMediaType_Video);
  
          CHECK_HR(hr, "Failed to set MF_MT_MAJOR_TYPE on H264 MFT input type");
  
  
  
          hr = inputType->SetGUID(MF_MT_SUBTYPE, MFVideoFormat_NV12);
  
          CHECK_HR(hr, "Failed to set MF_MT_SUBTYPE on H264 MFT input type");
  
  
  
          hr = MFSetAttributeSize(inputType, MF_MT_FRAME_SIZE, desc.Width, desc.Height);
  
          CHECK_HR(hr, "Failed to set MF_MT_FRAME_SIZE on H264 MFT input type");
  
  
  
          hr = MFSetAttributeRatio(inputType, MF_MT_FRAME_RATE, TARGET_FRAME_RATE, 1);
  
          CHECK_HR(hr, "Failed to set MF_MT_FRAME_RATE on H264 MFT input type");
  
  
  
          hr = _pTransform->SetInputType(inputStreamID, inputType, 0);
  
          CHECK_HR(hr, "Failed to set input type");
  
  
  
          break;
  
      }
  
  
  
      CheckHardwareSupport();
  
  
  
      CHECK_HR(_pTransform->ProcessMessage(MFT_MESSAGE_COMMAND_FLUSH, NULL), "Failed to process FLUSH command on H.264 MFT.\n");
  
      CHECK_HR(_pTransform->ProcessMessage(MFT_MESSAGE_NOTIFY_BEGIN_STREAMING, NULL), "Failed to process BEGIN_STREAMING command on H.264 MFT.\n");
  
      CHECK_HR(_pTransform->ProcessMessage(MFT_MESSAGE_NOTIFY_START_OF_STREAM, NULL), "Failed to process START_OF_STREAM command on H.264 MFT.\n");
  
  
  
      return true;
  
  
  
  done:
  
  
  
      printf("MediaFoundationH264LiveSource initialisation failed.\n");
  
      return false;
  
  }
  
  
  
  
  
      HRESULT CheckHardwareSupport()
  
      {
  
          IMFAttributes *attributes;
  
          HRESULT hr = _pTransform->GetAttributes(&attributes);
  
          UINT32 dxva = 0;
  
  
  
          if (SUCCEEDED(hr))
  
          {
  
              hr = attributes->GetUINT32(MF_SA_D3D11_AWARE, &dxva);
  
          }
  
  
  
          if (SUCCEEDED(hr))
  
          {
  
              hr = attributes->SetUINT32(CODECAPI_AVDecVideoAcceleration_H264, TRUE);
  
          }
  
  
  
  #if defined(CODECAPI_AVLowLatencyMode) // Win8 only
  
  
  
          hr = _pTransform->QueryInterface(IID_PPV_ARGS(&mpCodecAPI));
  
  
  
          if (SUCCEEDED(hr))
  
          {
  
              VARIANT var = { 0 };
  
  
  
              // FIXME: encoder only
  
              var.vt = VT_UI4;
  
              var.ulVal = 0;
  
  
  
              hr = mpCodecAPI->SetValue(&CODECAPI_AVEncMPVDefaultBPictureCount, &var);
  
  
  
              var.vt = VT_BOOL;
  
              var.boolVal = VARIANT_TRUE;
  
              hr = mpCodecAPI->SetValue(&CODECAPI_AVEncCommonLowLatency, &var);
  
              hr = mpCodecAPI->SetValue(&CODECAPI_AVEncCommonRealTime, &var);
  
  
  
              hr = attributes->SetUINT32(CODECAPI_AVLowLatencyMode, TRUE);
  
  
  
              if (SUCCEEDED(hr))
  
              {
  
                  var.vt = VT_UI4;
  
                  var.ulVal = eAVEncCommonRateControlMode_Quality;
  
                  hr = mpCodecAPI->SetValue(&CODECAPI_AVEncCommonRateControlMode, &var);
  
  
  
                  // This property controls the quality level when the encoder is not using a constrained bit rate. The AVEncCommonRateControlMode property determines whether the bit rate is constrained.
  
                  VARIANT quality;
  
                  InitVariantFromUInt32(50, &quality);
  
                  hr = mpCodecAPI->SetValue(&CODECAPI_AVEncCommonQuality, &quality);
  
              }
  
          }
  
  #endif
  
  
  
          return hr;
  
      }

  ffplay command :

  ffplay -protocol_whitelist file,udp,rtp -i test.sdp -x 800 -y 600 -profile:v baseline

  SDP :

  v=0
  
  o=- 0 0 IN IP4 127.0.0.1
  
  s=No Name
  
  t=0 0
  
  c=IN IP4 127.0.0.1
  
  m=video 1234 RTP/AVP 96
  
  a=rtpmap:96 H264/90000
  
  a=fmtp:96 packetization-mode=1

  I don’t know what am I missing, I have been trying to fix this for almost a week without any progress, and tried almost everything I could. Also, the online resources for encoding a DirectX surface as video are very limited.

  Any help would be appreciated.