Recherche avancée

Sur d’autres sites (9360)

• 5 Key Benefits of Using a Tag Manager

  12 décembre 2021, par erin — Analytics Tips, Marketing

  Websites today have become very complex to manage, and as you continue to look for ways to optimise your website, you’ll want to consider using a Tag Manager. 

  A Tag Manager will help your marketing team seamlessly track how your visitors are engaging with your website’s elements. Without a Tag Manager, you are missing out on business-altering insights.

  In this blog, we’ll cover :

  Tag Manager overview 

  A Tag Manager (AKA Tag Management System or TMS) is a centralised system for implementing, managing and tracking events. A tag is just another word for a piece of code on a website that tracks a specific event. 

  An example of a tag tracking code might be Facebook pixels, ad conversions and other website activities such as signing up to a newsletter or PDF download. 

  Triggers are the actual actions that website visitors take that activate the tag. Examples of triggers are things like : 

  • A thank you page view to show that a visitor has completed a conversion action
  • Clicking a download or sign up button 
  • Scroll depth or how far down users are scrolling on your webpage 

  Each of these will give you insights into how your website is performing and how your users are engaging with your content. Going back to the scroll depth trigger example, this would be particularly helpful for validating bounce rate and finding out where users are dropping off on a page. Discover other ways to take advantage of tags and event tracking. 

  

  5 key benefits of a Tag Manager

  1. Removes the risks of website downtime 

  Tags are powerful for in-depth web analytics. However, tagging opens up the potential for non-technical team members to break the front-end of your website in a couple of clicks. 

  A Tag Manager reduces that risk. For example, Matomo Tag Manager lets you preview tags to see if they are firing before pushing them live. You can also give specific users restricted access so you can approve any tagging before it goes live. 

  Tag Managers protect the functionality of your website and ensure that there is no downtime.

  2. Your website will load faster 

  When it comes to the success of your website, page speed is one of the most important factors. 

  Each time you add a tag to your site, you run the risk of slowing down the page speed. This can quickly build up to a poor performing site and frustrate your visitors.

  You can’t track tags if visitors won’t even stay long enough for your site to load. In fact, 1 in 4 visitors would abandon a website that takes more than 4 seconds to load. According to Deloitte, just a 0.1 second difference in loading speed can affect every step of your customer journey. 

  A Tag Manager, on the other hand, is a lightweight option only requiring one single tag. Using a Tag Manager to track events can make all the difference to your website’s performance and user experience.

  3. Greater efficiency for marketing

  Time is critical in marketing. The longer it takes for a campaign to launch, the greater the chances are that you’re missing out on sales opportunities.

  Waiting for the IT team to tag a thank you page before setting an ad live is inefficient and impacts your bottom line.

  Equipping marketing with a Tag Manager means that they’ll be able to launch campaigns faster and more effectively.

  Check out our Marketer’s Guide to Successful Website Event Tracking for more.

  4. Control all of your tracking and marketing tags in one place 

  Keeping track of what tags are on your site and where they’re located is a complicated task if you aren’t using a Tag Manager. Unmanaged tags can quickly pile up and result in errors with your analytics, like counting conversions twice. 

  Using a Tag Manager to centralise your tags in one easy to manage place reduces the chances of human errors. Instead, your team will be able to quickly see what tags are already in place so they aren’t doubling up on tracking.

  5. Reduce work for the IT team 

  Let’s face it, the IT team has more critical tasks at hand than adding tags to the website. Freeing up your IT team to focus on higher priority tasks should always be a goal.

  Tagging, while crucial for marketing, has the potential to create a lot of extra work for your website developers. Inserting code for each individual tag is time-consuming and means you aren’t collecting data in the meantime.

  Rather than overloading your IT team, empower your marketing team with the ability to add tags with a few clicks. 

  How to choose a Tag Management System

  There are many tools to choose from and the default option tends to be Google Tag Manager (GTM). But before you implement GTM or any other Tag Management Solution, we highly recommend asking these questions :

  1. What are my goals for a Tag Manager ? Before purchasing a Tag Manager, or any tool for that matter, understanding your goals upfront is best practice.
  2. Does the solution offer Tag Manager training resources ? If online Tag Manager training and educational resources are available for the tool, then you’ll be able to hit the ground running and start to see an ROI instantly.
  3. Can I get online support ? In case you need any help with the tool, having access to online support is a big bonus. 
  4. Is it compliant with privacy regulations ? If your business is already compliant, in the process of becoming compliant or future-proofing your tech stack for looming privacy regulations, then researching this is crucial. 
  5. How much does it cost ? If it’s “free”, find out how and why. In most cases, free solutions are just vehicles for collecting data to advertise to your users. 
  6. What do others think about the Tag Manager ? Check out reviews on sites like Capterra or G2 to find out how other businesses rate the tool. 

  Google Tag Manager alternative

  As privacy becomes a greater concern globally for end-users and governments, many businesses are looking for alternatives to the world’s largest advertising company – Google.

  Matomo Tag Manager is more than a Google Tag Manager alternative. With Matomo Tag Manager, you get a GDPR, HIPAA, CCPA and PECR compliant, open source Tag Manager and your data is 100% yours to own.

  Plus, with Matomo Tag Manager you only need one single tracking code for all of your website and tag analytics. No matter what you are tracking (scrolls, clicks, downloads, Heatmaps, visits, etc.), you will only ever need one piece of code on your website and one tool to manage it all. 

  The takeaway 

  Tagging is powerful but can quickly become complicated, risky and time-consuming. Tag Managers reduce these obstacles allowing you to set tags and triggers effortlessly. It empowers marketing teams, streamlines processes and removes the reliance on IT.

  Ready to try Matomo Tag Manager ? Start your 21-day free trial now – no credit card required. 

• how to change the frame rate and capturing image size from IP camera

  6 décembre 2015, par rockycai

  Now I have a IP camera and I want to capture image from it through RTSP.I use below code and it works well.But the camera’s frame rate is 25/s.So I got a lot of images per second.I don’t want it.And per image is 6.2MB.I also don’t want need to get high quality image.What can I do to slower the frame rate and smaller the size of image ?

  #ifndef INT64_C
  
  #define INT64_C(c) (c ## LL)
  
  #define UINT64_C(c) (c ## ULL)
  
  #endif
  
  
  
  #ifdef __cplusplus
  
  extern "C" {
  
  #endif
  
      /*Include ffmpeg header file*/
  
  #include <libavformat></libavformat>avformat.h>
  
  #include <libavcodec></libavcodec>avcodec.h>
  
  #include <libswscale></libswscale>swscale.h>
  
  #include 
  
  #ifdef __cplusplus
  
  }
  
  #endif
  
  
  
  #include 
  
  
  
  
  
  static void SaveFrame(AVFrame *pFrame, int width, int height, int iFrame);
  
  
  
  int main (int argc, const char * argv[])
  
  {
  
      AVFormatContext *pFormatCtx;
  
      int             i, videoStream;
  
      AVCodecContext  *pCodecCtx;
  
      AVCodec         *pCodec;
  
      AVFrame         *pFrame; 
  
      AVFrame         *pFrameRGB;
  
      AVPacket        packet;
  
      int             frameFinished;
  
      int             numBytes;
  
      uint8_t         *buffer;
  
  
  
      // Register all formats and codecs
  
      av_register_all();
  
  //  const char *filename="C:\libraries\gfjyp.avi";
  
      // Open video file
  
      //AVDictionary *options = NULL;
  
      //av_dict_set(&amp;options,"rtsp_transport","tcp",0);
  
      if(av_open_input_file(&amp;pFormatCtx, argv[1], NULL, 0, NULL)!=0)
  
          return -1; // Couldn't open file
  
  
  
      // Retrieve stream information
  
      if(av_find_stream_info(pFormatCtx)&lt;0)
  
          return -1; // Couldn't find stream information
  
  
  
      // Dump information about file onto standard error
  
      dump_format(pFormatCtx, 0, argv[1], false);
  
  
  
      // Find the first video stream
  
      videoStream=-1;
  
      for(i=0; inb_streams; i++)
  
          if(pFormatCtx->streams[i]->codec->codec_type==AVMEDIA_TYPE_VIDEO)
  
          {
  
              videoStream=i;
  
              break;
  
          }
  
          if(videoStream==-1)
  
              return -1; // Didn't find a video stream
  
  
  
          // Get a pointer to the codec context for the video stream
  
          pCodecCtx=pFormatCtx->streams[videoStream]->codec;
  
  
  
          // Find the decoder for the video stream
  
          pCodec=avcodec_find_decoder(pCodecCtx->codec_id);
  
          if(pCodec==NULL)
  
              return -1; // Codec not found
  
  
  
          // Open codec
  
          if(avcodec_open(pCodecCtx, pCodec)&lt;0)
  
              return -1; // Could not open codec
  
  
  
          // Hack to correct wrong frame rates that seem to be generated by some codecs
  
  
  
          if(pCodecCtx->time_base.num>1000 &amp;&amp; pCodecCtx->time_base.den==1)
  
              pCodecCtx->time_base.den=1000;
  
  
  
          //pCodecCtx->time_base.den=1;
  
          //pCodecCtx->time_base.num=1;
  
          // Allocate video frame
  
          pFrame=avcodec_alloc_frame();
  
  
  
          // Allocate an AVFrame structure
  
          pFrameRGB=avcodec_alloc_frame();
  
          if(pFrameRGB==NULL)
  
              return -1;
  
  
  
          // Determine required buffer size and allocate buffer
  
          numBytes=avpicture_get_size(PIX_FMT_RGB24, pCodecCtx->width,
  
              pCodecCtx->height);
  
  
  
          //buffer=malloc(numBytes);
  
          buffer=(uint8_t *)av_malloc(numBytes*sizeof(uint8_t));
  
  
  
          // Assign appropriate parts of buffer to image planes in pFrameRGB
  
          avpicture_fill((AVPicture *)pFrameRGB, buffer, PIX_FMT_RGB24,
  
              pCodecCtx->width, pCodecCtx->height);
  
  
  
          // Read frames and save first five frames to disk
  
          i=0;
  
          while(av_read_frame(pFormatCtx, &amp;packet)>=0)
  
          {
  
              // Is this a packet from the video stream?
  
              if(packet.stream_index==videoStream)
  
              {
  
                  // Decode video frame
  
                  avcodec_decode_video2(pCodecCtx, pFrame, &amp;frameFinished, 
  
                      &amp;packet);
  
  
  
                  // Did we get a video frame?
  
                  if(frameFinished)
  
                  {
  
  
  
                      static struct SwsContext *img_convert_ctx;
  
  
  
  #if 0
  
                      // Older removed code
  
                      // Convert the image from its native format to RGB swscale
  
                      img_convert((AVPicture *)pFrameRGB, PIX_FMT_RGB24, 
  
                          (AVPicture*)pFrame, pCodecCtx->pix_fmt, pCodecCtx->width, 
  
                          pCodecCtx->height);
  
  
  
                      // function template, for reference
  
                      int sws_scale(struct SwsContext *context, uint8_t* src[], int srcStride[], int srcSliceY,
  
                          int srcSliceH, uint8_t* dst[], int dstStride[]);
  
  #endif
  
                      // Convert the image into YUV format that SDL uses
  
                      if(img_convert_ctx == NULL) {
  
                          int w = pCodecCtx->width;
  
                          int h = pCodecCtx->height;
  
  
  
                          img_convert_ctx = sws_getContext(w, h, 
  
                              pCodecCtx->pix_fmt, 
  
                              w, h, PIX_FMT_RGB24, SWS_BICUBIC,
  
                              NULL, NULL, NULL);
  
                          if(img_convert_ctx == NULL) {
  
                              fprintf(stderr, "Cannot initialize the conversion context!\n");
  
                              exit(1);
  
                          }
  
                      }
  
                      int ret = sws_scale(img_convert_ctx, pFrame->data, pFrame->linesize, 0, 
  
                          pCodecCtx->height, pFrameRGB->data, pFrameRGB->linesize);
  
  #if 0 
  
                      // this use to be true, as of 1/2009, but apparently it is no longer true in 3/2009
  
                      if(ret) {
  
                          fprintf(stderr, "SWS_Scale failed [%d]!\n", ret);
  
                          exit(-1);
  
                      }
  
  #endif
  
  
  
                      // Save the frame to disk
  
                      if(i++&lt;=1000)
  
                          SaveFrame(pFrameRGB, pCodecCtx->width, pCodecCtx->height, i);
  
                  }
  
              }
  
  
  
              // Free the packet that was allocated by av_read_frame
  
              av_free_packet(&amp;packet);
  
              //sleep(1);
  
          }
  
  
  
          // Free the RGB image
  
          //free(buffer);
  
          av_free(buffer);
  
          av_free(pFrameRGB);
  
  
  
          // Free the YUV frame
  
          av_free(pFrame);
  
  
  
          // Close the codec
  
          avcodec_close(pCodecCtx);
  
  
  
          // Close the video file
  
          av_close_input_file(pFormatCtx);
  
  
  
          return 0;
  
  }
  
  
  
  static void SaveFrame(AVFrame *pFrame, int width, int height, int iFrame)
  
  {
  
      FILE *pFile;
  
      char szFilename[32];
  
      int  y;
  
  
  
      // Open file
  
      sprintf(szFilename, "frame%d.ppm", iFrame);
  
      pFile=fopen(szFilename, "wb");
  
      if(pFile==NULL)
  
          return;
  
  
  
      // Write header
  
      fprintf(pFile, "P6\n%d %d\n255\n", width, height);
  
  
  
      // Write pixel data
  
      for(y=0; ydata[0]+y*pFrame->linesize[0], 1, width*3, pFile);
  
  
  
      // Close file
  
      fclose(pFile);
  
  }

• aacenc : remove the experimental flag

  5 décembre 2015, par Rostislav Pehlivanov

  aacenc : remove the experimental flag
  Thiss commit removes the experimental flag from the native AAC Encoder
  
  and thus makes it the default.
  After a lot of work, done by myself and Claudio Freire, the quality of
  
  this encoder rivals and surpasses libfdk_aac in some situations. The
  
  encoder had instability issues earlier which prevented it from having
  
  its experimental flag removed, however the last commits done by Claudio
  
  removed the last known source of instability and solved a lot of
  
  problems which were previously observed. The issues were caused by the
  
  various coding tools interfering with the scalefactor indices. Thus,
  
  with these problems solved, it should now be possible to declare this
  
  encoder as the default and recommend that the users should use it
  
  instead of others provided by external libraries, as it is both faster
  
  and has a subjectively higher quality with selected tracks.
  
  The encoder has still yet to be fine tuned for every possible audio file
  
  type like music or voice, so it is hoped that with the experimental flag
  
  removed the users should be able to provide feedback and make the
  
  encoder better than the alternatives for every type of audio and at
  
  every bitrate.
  Signed-off-by : Rostislav Pehlivanov <atomnuker@gmail.com>
  

  • [DH] libavcodec/aacenc.c