Recherche avancée

Sur d’autres sites (14136)

• Memory Leak in c++/cli application

  10 décembre 2013, par Ankush

  I am passing bitmap from my c# app to c++/cli dll that add it to video.
  The problem is program slowly leaking memory. I tried _CrtDumpMemoryLeaks() shows me leak of bitmap & another 40 byte leak but i am disposing bitmap.
  Can anyone see memory leak, Here is code..

  Flow :

  1) Capture screenshot by takescreenshot()

  2) pass it to c++/cli function

  3) dispose bitmap

  lines from my c# app

  Bitmap snap = takescreeshot();
  
  vencoder.AddBitmap(snap);
  
  snap.Dispose();
  
  vencoder.printleak();
  
  
  
  private static Bitmap takescreeshot()
  
      {
  
          System.Drawing.Bitmap bitmap = null;
  
          System.Drawing.Graphics graphics = null;
  
  
  
          bitmap = new Bitmap
  
          (
  
              System.Windows.Forms.Screen.PrimaryScreen.Bounds.Width,
  
              System.Windows.Forms.Screen.PrimaryScreen.Bounds.Height,
  
              System.Drawing.Imaging.PixelFormat.Format24bppRgb
  
          );
  
  
  
          graphics = System.Drawing.Graphics.FromImage(bitmap);
  
  
  
          graphics.CopyFromScreen(Screen.PrimaryScreen.Bounds.X, Screen.PrimaryScreen.Bounds.Y, 0, 0, Screen.PrimaryScreen.Bounds.Size);
  
  
  
          //Write TimeSpamp
  
          Rectangle rect = new Rectangle(1166, 738, 200, 20);
  
          String datetime= System.String.Format("{0:dd:MM:yy  hh:mm:ss}",DateTime.Now);
  
          System.Drawing.Font sysfont = new System.Drawing.Font("Times New Roman", 14, FontStyle.Bold);
  
          graphics.DrawString(datetime, sysfont, Brushes.Red,rect);
  
          //
  
  
  
          Grayscale filter = new Grayscale(0.2125, 0.7154, 0.0721);
  
          Bitmap grayImage = filter.Apply(bitmap);
  
  
  
          //Dispose
  
          bitmap.Dispose();
  
          graphics.Dispose();
  
  
  
          return grayImage;
  
      }

  now in c++/cli dll

  bool VideoEncoder::AddBitmap(Bitmap^ bitmap)
  
      {
  
          BitmapData^ bitmapData = bitmap->LockBits( System::Drawing::Rectangle( 0, 0,bitmap->Width, bitmap->Height ),ImageLockMode::ReadOnly,PixelFormat::Format8bppIndexed);
  
          uint8_t* ptr = reinterpret_cast( static_cast( bitmapData->Scan0 ) );
  
          uint8_t* srcData[4] = { ptr, NULL, NULL, NULL };
  
          int srcLinesize[4] = { bitmapData->Stride, 0, 0, 0 };
  
  
  
          pCurrentPicture = CreateFFmpegPicture(pVideoStream->codec->pix_fmt, pVideoStream->codec->width, pVideoStream->codec->height);
  
  
  
          sws_scale(pImgConvertCtx, srcData, srcLinesize, 0, bitmap->Height, pCurrentPicture->data, pCurrentPicture->linesize );
  
  
  
          bitmap->UnlockBits( bitmapData );
  
  
  
          write_video_frame();
  
  
  
          bitmapData=nullptr;
  
          ptr=NULL;
  
  
  
          return true;
  
      }
  
  
  
  AVFrame * VideoEncoder::CreateFFmpegPicture(int pix_fmt, int nWidth, int nHeight)
  
      {
  
  
  
        AVFrame *picture     = NULL;
  
        uint8_t *picture_buf = NULL;
  
        int size;
  
  
  
        picture = avcodec_alloc_frame();
  
        if ( !picture)
  
        {
  
          printf("Cannot create frame\n");
  
          return NULL;
  
        }
  
  
  
        size = avpicture_get_size((AVPixelFormat)pix_fmt, nWidth, nHeight);
  
  
  
        picture_buf = (uint8_t *) av_malloc(size);
  
  
  
        if (!picture_buf) 
  
        {
  
          av_free(picture);
  
          printf("Cannot allocate buffer\n");
  
          return NULL;
  
        }
  
  
  
        avpicture_fill((AVPicture *)picture, picture_buf,
  
          (AVPixelFormat)pix_fmt, nWidth, nHeight);
  
  
  
        return picture;
  
      }
  
  
  
      void VideoEncoder::write_video_frame()
  
      {
  
          AVCodecContext* codecContext = pVideoStream->codec;
  
  
  
          int out_size, ret = 0;
  
  
  
          if ( pFormatContext->oformat->flags & AVFMT_RAWPICTURE )
  
          {
  
              printf( "raw picture must be written" );
  
          }
  
          else
  
          {
  
              out_size = avcodec_encode_video( codecContext, pVideoEncodeBuffer,nSizeVideoEncodeBuffer, pCurrentPicture );
  
  
  
              if ( out_size > 0 )
  
              {
  
                  AVPacket packet;
  
                  av_init_packet( &packet );
  
  
  
                  if ( codecContext->coded_frame->pts != AV_NOPTS_VALUE )
  
                  {
  
                      packet.pts = av_rescale_q( packet.pts, codecContext->time_base, pVideoStream->time_base );
  
                  }
  
  
  
                  if ( codecContext->coded_frame->pkt_dts != AV_NOPTS_VALUE )
  
                  {
  
                      packet.dts = av_rescale_q( packet.dts, codecContext->time_base, pVideoStream->time_base );
  
                  }
  
  
  
                  if ( codecContext->coded_frame->key_frame )
  
                  {
  
                      packet.flags |= AV_PKT_FLAG_KEY;
  
                  }
  
  
  
                  packet.stream_index = pVideoStream->index;
  
                  packet.data = pVideoEncodeBuffer;
  
                  packet.size = out_size;
  
  
  
                  ret = av_interleaved_write_frame( pFormatContext, &packet );
  
  
  
                  av_free_packet(&packet);
  
                  av_freep(pCurrentPicture);
  
              }
  
              else
  
              {
  
                  // image was buffered
  
              }
  
          }
  
  
  
          if ( ret != 0 )
  
          {
  
              throw gcnew Exception( "Error while writing video frame." );
  
          }
  
      }
  
  
  
  
  
      void VideoEncoder::printleak()
  
      {
  
          printf("No of leaks: %d",_CrtDumpMemoryLeaks());
  
          printf("\n");
  
      }

• 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.

• Redux : how to add subtitles to mp4 using ffmpeg ?

  25 novembre 2015, par stachyra

  I have a tiny little example mp4 video (which unfortunately stack overflow won’t allow me to embed directly inside my question). Following the advice previously offered in this answer, I’d like to add a subtitle to the video, which will flash on the screen for 2 seconds, using an .srt file that looks like this :

  1
  
  00:00:02,000 --> 00:00:04,000
  
  Test subtitle

  As provided in the link above, I issue a command that looks like this :

  ffmpeg -i small.mp4 -f srt -i small.srt -c:v copy -c:a copy -c:s mov_text small_subtitles.mp4 >& err.log

  And the err.log file looks like this :

  ffmpeg version N-76950-g401c93d-tessus Copyright (c) 2000-2015 the FFmpeg developers
  
  built with Apple LLVM version 6.0 (clang-600.0.57) (based on LLVM 3.5svn)
  
  configuration: --cc=/usr/bin/clang --prefix=/opt/ffmpeg --as=yasm --extra-version=tessus --enable-avisynth --enable-fontconfig --enable-gpl --enable-libass --enable-libbluray --enable-libfreetype --enable-libgsm --enable-libmodplug --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopus --enable-libschroedinger --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libvidstab --enable-libvo-aacenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libx264 --enable-libx265 --enable-libxavs --enable-libxvid --enable-libzmq --enable-version3 --disable-ffplay --disable-indev=qtkit --disable-indev=x11grab_xcb
  
    libavutil      55.  7.100 / 55.  7.100
  
    libavcodec     57. 15.100 / 57. 15.100
  
    libavformat    57. 17.100 / 57. 17.100
  
    libavdevice    57.  0.100 / 57.  0.100
  
    libavfilter     6. 15.100 /  6. 15.100
  
    libswscale      4.  0.100 /  4.  0.100
  
    libswresample   2.  0.101 /  2.  0.101
  
    libpostproc    54.  0.100 / 54.  0.100
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'small.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf56.40.101
  
    Duration: 00:00:10.02, start: 0.000000, bitrate: 23 kb/s
  
      Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 188x112 [SAR 1:1 DAR 47:28], 17 kb/s, 60 fps, 60 tbr, 15360 tbn, 120 tbc (default)
  
  Metadata:
  
    handler_name    : VideoHandler
  
  Input #1, srt, from 'small.srt':
  
    Duration: N/A, bitrate: N/A
  
  Stream #1:0: Subtitle: subrip
  
  [mp4 @ 0x7f8492848000] Codec for stream 0 does not use global headers but container format requires global headers
  
  Output #0, mp4, to 'small_subtitles.mp4':
  
    Metadata:
  
  major_brand     : isom
  
  minor_version   : 512
  
  compatible_brands: isomiso2avc1mp41
  
  encoder         : Lavf57.17.100
  
  Stream #0:0(und): Video: h264 ([33][0][0][0] / 0x0021), yuv420p, 188x112 [SAR 1:1 DAR 47:28], q=2-31, 17 kb/s, 60 fps, 60 tbr, 15360 tbn, 15360 tbc (default)
  
  Metadata:
  
    handler_name    : VideoHandler
  
  Stream #0:1: Subtitle: mov_text ([8][0][0][0] / 0x0008) (default)
  
  Metadata:
  
    encoder         : Lavc57.15.100 mov_text
  
  Stream mapping:
  
    Stream #0:0 -> #0:0 (copy)
  
    Stream #1:0 -> #0:1 (subrip (srt) -> mov_text (native))
  
  Press [q] to stop, [?] for help
  
  frame=  601 fps=0.0 q=-1.0 Lsize=      29kB time=00:00:09.96 bitrate=  24.0kbits/s    
  
  video:21kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 39.561928%

  The resulting output, small_subtitles.mp4, does not seem to have the expected subtitle present.

  Furthermore, the error message,

  [mp4 @ 0x7f8492848000] Codec for stream 0 does not use global headers but container format requires global headers

  is highlighted in bold colors when I run this at the command line without capturing the err.log file (which makes me think it must be a significant message), although I am unable to reproduce that special print formatting easily here.

  I’ve also tried this method, but with the .avi replaced by .mp4, and it seems to just fail silently—no obvious error message, but also no subtitle in the resulting video either.

  Anybody have an idea how to fix this ? In particular, what does the business about global headers mean ?

  I’m working on OS X and am open to hearing answers that would use other open source tools as well.