Recherche avancée

Sur d’autres sites (13586)

• It’s January 28th : Let’s celebrate Data Privacy !

  29 janvier 2018, par Matomo Core Team

  It is a special Sunday here for us at Matomo, as today is international Data Privacy Day. The day was created in 2007 to raise awareness of the importance of data privacy for people and businesses worldwide.

  

  What is data privacy about ?

  Personal data refers to any data which is collected and can be linked to an individual human being such as phone records, credit card transactions, GPS position, IP addresses, browsing history… So basically, personal data refers to your identity online. That is why you should be highly concerned about sending your personal data (or your customers’ personal data) away. It is important to be aware of who is collecting the information and how it is being used.

  What big changes are happening in 2018 ?

  New privacy regulations GDPR comes into play next May 2018 : GDPR will bring about some changes (in the right direction) by making people and businesses aware of what data privacy means, and what they should be doing to protect their customers’ privacy. With these new regulations, data privacy awareness is reaching a critical milestone this year.

  How can I protect my privacy ?

  Here are a few tips to protect your privacy :

  • Educate yourself on the importance of privacy : the more informed you are the better.
  • Use open source solutions where you can keep full control of your own data (such as NextCloud instead of Dropbox and of course Matomo instead of Google Analytics),
  • Experiment with different online services to protect your data privacy, for example using an alternative search engine (such as DuckDuckGo instead of Google) or an alternative email provider (such as ProtonMail).

  What’s coming next for Matomo and Privacy ?

  Here at Matomo, we are building the leading decentralised open web analytics platform. We’re currently working on new sets of privacy features to make compliance with GDPR a breeze. Stay tuned here to be notified when we launch the new privacy compliance tools !

  And in case you’ve missed this important info, you may be interested in :

  • Configure Privacy Settings in Matomo
  • 11 ways Matomo Analytics helps you to protect your visitors privacy

   

  The post It’s January 28th : Let’s celebrate Data Privacy ! appeared first on Analytics Platform - Matomo.

• Encoding raw YUV420P to h264 with AVCodec on iOS

  4 janvier 2013, par Wade

  I am trying to encode a single YUV420P image gathered from a CMSampleBuffer to an AVPacket so that I can send h264 video over the network with RTMP.

  The posted code example seems to work as avcodec_encode_video2 returns 0 (Success) however got_output is also 0 (AVPacket is empty).

  Does anyone have any experience with encoding video on iOS devices that might know what I am doing wrong ?

  - (void) captureOutput:(AVCaptureOutput *)captureOutput
  
   didOutputSampleBuffer:(CMSampleBufferRef)sampleBuffer
  
          fromConnection:(AVCaptureConnection *)connection {
  
  
  
    // sampleBuffer now contains an individual frame of raw video frames
  
    CVPixelBufferRef pixelBuffer = CMSampleBufferGetImageBuffer(sampleBuffer);
  
  
  
    CVPixelBufferLockBaseAddress(pixelBuffer, 0);
  
  
  
    // access the data
  
    int width = CVPixelBufferGetWidth(pixelBuffer);
  
    int height = CVPixelBufferGetHeight(pixelBuffer);
  
    int bytesPerRow = CVPixelBufferGetBytesPerRowOfPlane(pixelBuffer, 0);
  
    unsigned char *rawPixelBase = (unsigned char *)CVPixelBufferGetBaseAddressOfPlane(pixelBuffer, 0);
  
  
  
  
  
    // Convert the raw pixel base to h.264 format
  
    AVCodec *codec = 0;
  
    AVCodecContext *context = 0;
  
    AVFrame *frame = 0;
  
    AVPacket packet;
  
  
  
    //avcodec_init();
  
    avcodec_register_all();
  
    codec = avcodec_find_encoder(AV_CODEC_ID_H264);
  
  
  
    if (codec == 0) {
  
      NSLog(@"Codec not found!!");
  
      return;
  
    }
  
  
  
    context = avcodec_alloc_context3(codec);
  
  
  
    if (!context) {
  
      NSLog(@"Context no bueno.");
  
      return;
  
    }
  
  
  
    // Bit rate
  
    context->bit_rate = 400000; // HARD CODE
  
    context->bit_rate_tolerance = 10;
  
    // Resolution
  
    context->width = width;
  
    context->height = height;
  
    // Frames Per Second
  
    context->time_base = (AVRational) {1,25};
  
    context->gop_size = 1;
  
    //context->max_b_frames = 1;
  
    context->pix_fmt = PIX_FMT_YUV420P;
  
  
  
    // Open the codec
  
    if (avcodec_open2(context, codec, 0) < 0) {
  
      NSLog(@"Unable to open codec");
  
      return;
  
    }
  
  
  
  
  
    // Create the frame
  
    frame = avcodec_alloc_frame();
  
    if (!frame) {
  
      NSLog(@"Unable to alloc frame");
  
      return;
  
    }
  
    frame->format = context->pix_fmt;
  
    frame->width = context->width;
  
    frame->height = context->height;
  
  
  
  
  
    avpicture_fill((AVPicture *) frame, rawPixelBase, context->pix_fmt, frame->width, frame->height);
  
  
  
    int got_output = 0;
  
    av_init_packet(&packet);
  
    avcodec_encode_video2(context, &packet, frame, &got_output)
  
  
  
    // Unlock the pixel data
  
    CVPixelBufferUnlockBaseAddress(pixelBuffer, 0);
  
    // Send the data over the network
  
    [self uploadData:[NSData dataWithBytes:packet.data length:packet.size] toRTMP:self.rtmp_OutVideoStream];
  
  }

  Note : It is known that this code has memory leaks because I am not freeing the memory that is dynamically allocated.

  UPDATE

  I updated my code to use @pogorskiy method. I only try to upload the frame if got output returns 1 and clear the buffer once I am done encoding video frames.

• rtpdec : Don’t pass non-const pointers to fmtp attribute parsing functions

  24 février 2015, par Martin Storsjö

  rtpdec : Don’t pass non-const pointers to fmtp attribute parsing functions
  This makes it clear that the individual parsing functions can’t
  
  touch the parsed out value.
  Signed-off-by : Martin Storsjö <martin@martin.st>
  

  • [DH] libavformat/rtpdec.c
  • [DH] libavformat/rtpdec.h
  • [DH] libavformat/rtpdec_amr.c
  • [DH] libavformat/rtpdec_dv.c
  • [DH] libavformat/rtpdec_h264.c
  • [DH] libavformat/rtpdec_hevc.c
  • [DH] libavformat/rtpdec_ilbc.c
  • [DH] libavformat/rtpdec_latm.c
  • [DH] libavformat/rtpdec_mpeg4.c
  • [DH] libavformat/rtpdec_xiph.c