Sur d’autres sites (10166)

• Exceeded GA’s 10M hits data limit, now what ?

  21 juin 2019, par Joselyn Khor
  Exceeded GA’s 10M hits data limit, now what ? Matomo has the answers

  “Your data volume (1XXM hits) exceeds the limit of 10M hits per month as outlined in our Terms of Service. If you continue to exceed the limit, we will stop processing new data on XXX 21, 2019. Learn more about possible solutions.”

  Yikes. Alarm bells were ringing when a Google Analytics free user came to us faced with this notice. Let’s call him ‘Mark’. Mark had reached the limits on the data he could collect through Google Analytics and was shocked by the limited options available to fix the problem, without blowing the budget. The thoughts racing through his head were :

  • “What happens to all my data ?”
  • “What if Google starts charging USD150K now ?”

  Then he came across Matomo and decided to get in touch with our support team …

  “Can you fix this issue ?” he asked us.

  “Absolutely !” we said.

  We’ll get back to helping Mark in a minute. For now let’s go over why this was such a dilemma for him.

  In order to resolve this data limits issue, one of the solutions was for him to upgrade to Google Analytics 360, which meant shelling out USD150,000 per year for their 1 billion hits per month option. Going from free to USD150,000 was too much of a stretch for a growing company.

  “Your data volume (1XXM hits) exceeds the limit of 10M hits per month …”, what did this message mean ?

  With the free version, Mark could collect up to 10 million “hits” per month, per account. Going over meant Google Analytics could stop collecting any more data for free as outlined in their Terms.

  Google Analytics’ Terms of Service (2018, sec. 2) states, “Subject to Section 15, the Service is provided without charge to You for up to 10 million Hits per month per account.”[1]

  In general, what’s a "hit" ?

  Data being sent to Google Analytics. It can be a transaction, event, social interaction or pageview - these all produce what Google calls a “hit”.

  

  And their Analytics Help Data Limits (n.d.) support page makes clear that : “If a property sends more hits per month to Analytics than allowed by the Analytics Terms of Service, there is no assurance that the excess hits will be processed. If the property’s hit volume exceeds this limit, a warning may be displayed in the user interface and you may be prevented from accessing reports.”[2]

  

  Possible solutions

  So the possible solutions given by Google Analytics’ Data Limits support page were (also shown in image below) :

  • To pay USD150K to upgrade to Google Analytics 360
  • To send fewer hits by setting up sampling
  • Or choose the slightly less relevant option to upgrade mobile app tracking to Google Analytics for Firebase.

  Without the means to pay, the free version was fast becoming inaccessible for Mark as he was facing a future where he risked no longer having access to up-to-date data used in his business’ reporting.

  Mark was facing a problem that potentially didn’t have a cost-effective solution.

  

  So what can you really do about it ?

  This is where we can help provide some assistance. If you’re reading this article, we’ll assume you can relate to Mark and share with you the advice on options we gave him.

  Options :

  One option posed by Google is for you to send fewer hits by auditing your data collection processes

  If you really don’t have the budget, you’ll need to reassess your data collection priorities and go over your strategies to see what is necessary to track, and what isn’t.

  • Make sure you know what you’re tracking and why. Look at what websites are being tracked by Google and into what properties.
  • Go through what data you’re tracking and decide what is or isn’t of value.
  • Set up data sampling, this however, will lead to inaccurate data.

  From here you can start to course correct. If you’ve found data you’re not using for analysis, get rid of these events/pageviews in your Google Analytics.

  But the limitations here are that eventually, you’re going to run out of irrelevant metrics and everything you’re tracking will be essential. So you’ll hit another brick wall and return to the same situation.

  Option 2 – Ignore and continue using the free version of Google Analytics

  With this option, you’ll have to bear the business risks involved by basing decisions off of analytics reports that may or may not be updated. In this case, you may still get contacted about exceeding the limits. As the free service is provided for only up to 10 million hits, once you’ve gone over them, you’re violating what’s stipulated in the Terms of Service. 

  There’s also the warning that “… you may be prevented from accessing reports” (Data limits, n.d.). So while we may not know for certain what Google Analytics will do, in this case it may be better to be safe rather than sorry by acting quickly to resolve it. 

  Option 3 –The Matomo solution. Upgrade to a web analytics platform that can handle your demanding data requirements

  Save money while continuing to gain valuable insights by moving over to Matomo Analytics (recommended)

  This is where you can save up to USD130,000 a year. As well as that, the transition from Google Analytics to the Matomo Cloud is a seamless experience as setup and maintenance is taken care of by our experts.

  For example, you can get up to 15M pageviews for USD1,612.50/month (or USD19,350/year) on the Essentials plan.

  Or even 25M pageviews for USD2400/month (or USD24000/year) on the Business plan – which offers additional web analytics and conversion optimization resources.

  Matomo Cloud is a great option if you’re looking for a secure, cost-effective and powerful analytics solution. You also get what Google Analytics could never offer you : full control and ownership of your own data and privacy. 

  No need to worry about losing your Google Analytics data because …

  Now you can import your historic Google Analytics data directly into your Matomo with the Google Analytics Importer tool. Simply follow the step-by-step guide to get started for free.

  Along with savings you can get :

  • A solution for the data limits issue forever. You choose the right plan to suit your data needs and adapt as you continue growing
  • 100% accurate data (no data sampling)
  • 100% data ownership of all your information without signing away your data to a third party
  • Powerful web analytics and conversion optimization features
  • Matomo Tag Manager
  • Easy setup
  • Support from Matomo’s specialists

  Learn more about Matomo Cloud pricing.

  

  Or go for Matomo On-Premise

  If you have the in-house infrastructure to support self-hosting Matomo on your own servers then there’s also the option of Matomo On-Premise. Here you’ll get full security knowing the data is on your own servers. 

  Setup will also require technical knowledge. There will also be costs associated with acquiring your own servers, and keeping up with regular maintenance and updates. With On-Premise you get maximum flexibility, with no data limits whatsoever. But if you’re coming over from Google Analytics and don’t have the infrastructure and team to host On-Premise, the Matomo Cloud could be right for you.

  Learn more about Matomo On-Premise.

  Where do you go from here ?

  Getting 10 millions hits per month is no small feat, it’s actually pretty fantastic. But if it means having to shell out USD150,000 just to be able to continue with Google Analytics, we feel your problem could be fixed with Matomo Cloud. You could then put the rest of the money you save to better use.

  If you choose Matomo, you now have the option to : 

  • Raise your data limits for a fraction of Google Analytics 360’s price
  • Get a comprehensive range of analytics features for the most impactful insights to ensure your website continues excelling
  • Get data that’s not sampled – meaning 100% accuracy in your reports
  • Migrate your data easily with the help of Matomo’s support team

  We’ll have you covered. 

  By sharing with you the options and advice we gave to Mark, we hope you’ll be able to find a solution that makes your life easier and solves the issue of data restrictions forever.

  The team at Matomo is here to help you every step of the way to ensure a stress-free transition from Google Analytics if that is what works best for you.

  For next steps, why not check out our pricing page to see what could suit your needs !

  References :

  [1] Terms of Service. (2018, July 24). In Google Analytics Terms of Service. Retrieved June 12, 2019, from https://www.google.com/analytics/terms/us.html

  [2] Data limits. (n.d.). In Analytics Help Data limits. Retrieved June 12, 2019, from https://support.google.com/analytics/answer/1070983?hl=en

• splitting video into shots with ffmpeg from within python

  13 juin 2024, par ludog

  After some searching, the following command works to split my input video into shots, and save the first frame from each shot.

  


  ffmpeg -i input_vid.mp4 -filter:v "select='gt(scene,0.1)',showinfo" -vsync 0 frames/%05d.jpg


  


  When run from the terminal, it prints a line to what I think is stderr for each of the extracted frames, like so

  


  Parsed_showinfo_1 @ 0x7f0198003540] n: 884 pts: 132552 pts_time:2209.2  duration: 2 duration_time:0.0333333 fmt:yuv420p cl:left sar:0/1 s:480x360 i:P iskey:0 type:P checksum:F2D8FCAA plane_checksum:[2D2F32C1 6E0164EC 832064FD] mean:[16 128 128] stdev:[0.0 0.0 0.0]


  


  I want to run this from Python, and also capture the output so I can get the timestamps of the extracted frames (e.g. pts_time:2209.2 in the example above). But when try it in a subprocess.run, I get the following error, and no files are written to frames/.

  


  >> FFMPEG_PATH = imageio_ffmpeg.get_ffmpeg_exe()
>> x = subprocess.run([FFMEPG_PATH, "-i", "input_vid.mp4", '-filter:v ' "select=" "'gt(scene,0.1)'" ",showinfo", "-vsync", "0", r"frames/%05d.jpg"], capture_output=True)
>> print(x.stderr.decode())
  ffmpeg version 4.2.2-static https://johnvansickle.com/ffmpeg/  Copyright (c) 2000-2019 the FFmpeg developers
  built with gcc 8 (Debian 8.3.0-6)
  configuration: --enable-gpl --enable-version3 --enable-static --disable-debug --disable-ffplay --disable-indev=sndio --disable-outdev=sndio --cc=gcc --enable-fontconfig --enable-frei0r --enable-gnutls --enable-gmp --enable-libgme --enable-gray --enable-libaom --enable-libfribidi --enable-libass --enable-libvmaf --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-librubberband --enable-libsoxr --enable-libspeex --enable-libsrt --enable-libvorbis --enable-libopus --enable-libtheora --enable-libvidstab --enable-libvo-amrwbenc --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libdav1d --enable-libxvid --enable-libzvbi --enable-libzimg
  libavutil      56. 31.100 / 56. 31.100
  libavcodec     58. 54.100 / 58. 54.100
  libavformat    58. 29.100 / 58. 29.100
  libavdevice    58.  8.100 / 58.  8.100
  libavfilter     7. 57.100 /  7. 57.100
  libswscale      5.  5.100 /  5.  5.100
  libswresample   3.  5.100 /  3.  5.100
  libpostproc    55.  5.100 / 55.  5.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'input_vid.mp4':
  Metadata:
    major_brand     : mp42
    minor_version   : 0
    compatible_brands: isommp42
    creation_time   : 2013-06-21T09:09:58.000000Z
  Duration: 00:37:10.88, start: 0.000000, bitrate: 394 kb/s
    Stream #0:0(und): Video: h264 (Constrained Baseline) (avc1 / 0x31637661), yuv420p, 480x360, 296 kb/s, 30 fps, 30 tbr, 60 tbn, 60 tbc (default)
    Metadata:
      handler_name    : VideoHandler
    Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 96 kb/s (default)
    Metadata:
      creation_time   : 2013-06-21T09:10:07.000000Z
      handler_name    : IsoMedia File Produced by Google, 5-11-2011
[NULL @ 0x58e6e80] Unable to find a suitable output format for '0'
0: Invalid argument


  


  If I remove the filter argument, it does extract frames, but there are too many, it's important to be able to specify a threshold gt(scene,0.1). It also doesn't capture any output that tells me the timestamps :

  


  >> x = subprocess.run([FFMEPG_PATH, "-i", "input_vid.mp4", "-vsync", "0", "frames2/%05d.jpg"], capture_output=True)
>> print(x.stderr.decode())
ffmpeg version 4.2.2-static https://johnvansickle.com/ffmpeg/  Copyright (c) 2000-2019 the FFmpeg developers
  built with gcc 8 (Debian 8.3.0-6)
  configuration: --enable-gpl --enable-version3 --enable-static --disable-debug --disable-ffplay --disable-indev=sndio --disable-outdev=sndio --cc=gcc --enable-fontconfig --enable-frei0r --enable-gnutls --enable-gmp --enable-libgme --enable-gray --enable-libaom --enable-libfribidi --enable-libass --enable-libvmaf --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-librubberband --enable-libsoxr --enable-libspeex --enable-libsrt --enable-libvorbis --enable-libopus --enable-libtheora --enable-libvidstab --enable-libvo-amrwbenc --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libdav1d --enable-libxvid --enable-libzvbi --enable-libzimg
  libavutil      56. 31.100 / 56. 31.100
  libavcodec     58. 54.100 / 58. 54.100
  libavformat    58. 29.100 / 58. 29.100
  libavdevice    58.  8.100 / 58.  8.100
  libavfilter     7. 57.100 /  7. 57.100
  libswscale      5.  5.100 /  5.  5.100
  libswresample   3.  5.100 /  3.  5.100
  libpostproc    55.  5.100 / 55.  5.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'input_vid.mp4':
  Metadata:
    major_brand     : mp42
    minor_version   : 0
    compatible_brands: isommp42
    creation_time   : 2013-06-21T09:09:58.000000Z
  Duration: 00:37:10.88, start: 0.000000, bitrate: 394 kb/s
    Stream #0:0(und): Video: h264 (Constrained Baseline) (avc1 / 0x31637661), yuv420p, 480x360, 296 kb/s, 30 fps, 30 tbr, 60 tbn, 60 tbc (default)
    Metadata:
      handler_name    : VideoHandler
    Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 96 kb/s (default)
    Metadata:
      creation_time   : 2013-06-21T09:10:07.000000Z
      handler_name    : IsoMedia File Produced by Google, 5-11-2011
Stream mapping:
  Stream #0:0 -> #0:0 (h264 (native) -> mjpeg (native))
Press [q] to stop, [?] for help
[swscaler @ 0x6af2200] deprecated pixel format used, make sure you did set range correctly
Output #0, image2, to 'frames2/%05d.jpg':
  Metadata:
    major_brand     : mp42
    minor_version   : 0
    compatible_brands: isommp42
    encoder         : Lavf58.29.100
    Stream #0:0(und): Video: mjpeg, yuvj420p(pc), 480x360, q=2-31, 200 kb/s, 30 fps, 30 tbn, 30 tbc (default)
    Metadata:
      handler_name    : VideoHandler
      encoder         : Lavc58.54.100 mjpeg
    Side data:
      cpb: bitrate max/min/avg: 0/0/200000 buffer size: 0 vbv_delay: -1
frame=66922 fps=1571 q=24.8 Lsize=N/A time=00:37:10.73 bitrate=N/A speed=52.4x    
video:310586kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown

>> print(x.stdout.decode())


  


  It seems like there are two problems : something to do with the filter argument, and capturing the output that contains the timestamps. I've tried various ways of writing the nested string quotes in the filter argument : triple quotes, escaping, changing the order of double and single quotes, and concatenating separate strings like shown above.

  


• Gracefully closing FFMPEG child processes from node

  10 juin 2019, par Gordon

  I am trying to record numerous audio feeds using ffmpeg. Node downloads a config file with the stream URLS (HLS M3U8 playlists), parses it and starts the appropriate number of ffmpeg instances. When I go to shut them down, nothing happens and I have to kill them with task manager, resulting in corrupt files. When I am debugging and hit control-c within a minute or two of starting the program, it works without issue. When I need to record more than 5-10 minutes that I have problems.

  I found this related question from 2013, and adapted it to fit my multiple stream situation.

  The recorder processes are started with the following code (inside the http request callback) :

  config.audio_config.forEach((channel,i)=>{
  
  self.liveChannels++;
  
  
  
  console.log(`   ${channel.number}`);
  
  self.Channels[i] = spawn('ffmpeg', ['-i', `${channel.base_url + channel.stream_ios}`,  '-c:v', 'none', '-c:a', 'copy', `Output\\${config.folder}\\${channel.number}.m4a`]);
  
  self.Channels[i].stdin.setEncoding('utf8');
  
  self.Channels[i].chNum = channel.number;
  
  
  
  self.Channels[i].on('exit',(code,sig)=>{
  
  console.log(`   Channel ${channel.number} recorder closed.`);
  
  self.liveChannels--;
  
  if(self.liveChannels === 0){
  
      process.exit();
  
  }
  
  });
  
  });
  
  console.log('Press Ctl-C to start Shutdown');

  My shutdown function (triggered by SIGINT to main process) is :

  function shutdown() {
  
      self.Channels.forEach((chan)=>{
  
          chan.stdin.write('q');
  
          chan.stdin.end(); //I have tried both with and without this line and chan.stdin.end('q')
  
      });
  
  
  
  }

  UPDATE :
  Switching to an AAC container file (simply changed the extension on the output) removed the need for a graceful FFMPEG exit. I still would like to know why sending ’q’ to stdin only kills the FFMPEG process for the first 10 minutes.