Recherche avancée

Sur d’autres sites (12424)

• 10 Key Google Analytics Limitations You Should Be Aware Of

  9 mai 2022, par Erin

  Google Analytics (GA) is the biggest player in the web analytics space. But is it as “universal” as its brand name suggests ?
  

  Over the years users have pointed out a number of major Google Analytics limitations. Many of these are even more visible in Google Analytics 4. 

  Introduced in 2020, Google Analytics 4 (GA4) has been sceptically received. As the sunset date of 1st, July 2023 for the current version, Google Universal Analytics (UA), approaches, the dismay grows stronger.

  To the point where people are pleading with others to intervene : 

  

  Main limitations of Google Analytics

  Google Analytics 4 is advertised as a more privacy-centred, comprehensive and “intelligent” web analytics platform. 

  According to Google, the newest version touts : 

  • Machine learning at its core provides better segmentation and fast-track access to granular insights 
  • Privacy-by-design controls, addressing restrictions on cookies and new regulatory demands 
  • More complete understanding of customer journeys across channels and devices 

  Some of these claims hold true. Others crumble upon a deeper investigation. Newly advertised Google Analytics capabilities such as ‘custom events’, ‘predictive insights’ and ‘privacy consent mode’ only have marginal improvements. 

  Complex setup, poor UI and lack of support with migration also leave many other users frustrated with GA4. 

  

  Let’s unpack all the current (and legacy) limitations of Google Analytics you should account for. 

  1. No Historical Data Imports 

  Google rushed users to migrate from Universal Analytics to Google Analytics 4. But they overlooked one important precondition — backwards compatibility. 

  You have no way to import data from Google Universal Analytics to Google Analytics 4. 

  Historical records are essential for analysing growth trends and creating benchmarks for new marketing campaigns. Effectively, you are cut short from past insights — and forced to start strategising from scratch. 

  At present, Google offers two feeble solutions : 

  • Run data collection in parallel and have separate reporting for GA4 and UA until the latter is shut down. Then your UA records are gone. 
  • For Ecommerce data, manually duplicate events from UA at a new GA4 property while trying to figure out the new event names and parameters. 

  Google’s new data collection model is the reason for migration difficulties. 

  In Google Analytics 4, all analytics hits types — page hits, social hits, app/screen view, etc. — are recorded as events. Respectively, the “‘event’ parameter in GA4 is different from one in Google Universal Analytics as the company explains : 

  

  This change makes migration tedious — and Google offers little assistance with proper events and custom dimensions set up. 

  2. Data Collection Limits 

  If you’ve wrapped your head around new GA4 events, congrats ! You did a great job, but the hassle isn’t over. 

  You still need to pay attention to new Google Analytics limits on data collection for event parameters and user properties. 

  

  These apply to :

  • Automatically collected events
  • Enhanced measurement events
  • Recommended events 
  • Custom events 

  When it comes to custom events, GA4 also has a limit of 25 custom parameters per event. Even though it seems a lot, it may not be enough for bigger websites. 

  You can get higher limits by upgrading to Google Analytics 360, but the costs are steep. 

  3. Limited GDPR Compliance 

  Google Analytics has a complex history with European GDPR compliance. 

  A 2020 ruling by the Court of Justice of the European Union (CJEU) invalidated the Privacy Shield framework Google leaned upon. This framework allowed the company to regulate EU-US data transfers of sensitive user data. 

  But after this loophole was closed, Google faced a heavy series of privacy-related fines :

  • French data protection authority, CNIL, ruled that  “the transfers to the US of personal data collected through Google Analytics are illegal” — and proceeded to fine Google for a record-setting €150 million at the beginning of 2022. 
  • Austrian regulators also deemed Google in breach of GDPR requirements and also branded the analytics as illegal. 

  Other EU-member states might soon proceed with similar rulings. These, in turn, can directly affect Google Analytics users, whose businesses could face brand damage and regulatory fines for non-compliance. In fact, companies cannot select where the collected analytics data will be stored — on European servers or abroad — nor can they obtain this information from Google.

  Getting a web analytics platform that allows you to keep data on your own servers or select specific Cloud locations is a great alternative. 

  Google also has been lax with its cookie consent policy and doesn’t properly inform consumers about data collection, storage or subsequent usage. Google Analytics 4 addresses this issue to an extent. 

  By default, GA4 relies on first-party cookies, instead of third-party ones — which is a step forward. But the user privacy controls are hard to configure without losing most of the GA4 functionality. Implementing user consent mode to different types of data collection also requires a heavy setup. 

  4. Strong Reliance on Sampled Data 

  To compensate for ditching third-party cookies, GA4 more heavily leans on sampled data and machine learning to fill the gaps in reporting. 

  In GA4 sampling automatically applies when you :

  • Perform advanced analysis such as cohort analysis, exploration, segment overlap or funnel analysis with not enough data 
  • Have over 10,000,000 data rows and generate any type of non-default report 

  Google also notes that data sampling can occur at lower thresholds when you are trying to get granular insights. If there’s not enough data or because Google thinks it’s too complex to retrieve. 

  In their words :

  

  Data sampling adds “guesswork” to your reports, meaning you can’t be 100% sure of data accuracy. The divergence from actual data depends on the size and quality of sampled data. Again, this isn’t something you can control. 

  Unlike Google Analytics 4, Matomo applies no data sampling. Your reports are always accurate and fully representative of actual user behaviours. 

  5. No Proper Data Anonymization 

  Data anonymization allows you to collect basic analytics about users — visits, clicks, page views — but without personally identifiable information (or PII) such as geo-location, assigns tracking ID or other cookie-based data. 

  This reduced your ability to :

  • Remarket 
  • Identify repeating visitors
  • Do advanced conversion attribution 

  But you still get basic data from users who ignored or declined consent to data collection. 

  By default, Google Analytics 4 anonymizes all user IP addresses — an upgrade from UA. However, it still assigned a unique user ID to each user. These count as personal data under GDPR. 

  For comparison, Matomo provides more advanced privacy controls. You can anonymize :

  • Previously tracked raw data 
  • Visitor IP addresses
  • Geo-location information
  • User IDs 

  This can ensure compliance, especially if you operate in a sensitive industry — and delight privacy-mindful users ! 

  6. No Roll-Up Reporting

  Getting a bird’s-eye view of all your data is helpful when you need hotkey access to main sites — global traffic volume, user count or percentage of returning visitors.

  With Roll-Up Reporting, you can see global-performance metrics for multiple localised properties (.co.nz, .co.uk, .com, etc,) in one screen. Then zoom in on specific localised sites when you need to. 

  

  7. Report Processing Latency 

  The average data processing latency is 24-48 hours with Google Analytics. 

  Accounts with over 200,000 daily sessions get data refreshes only once a day. So you won’t be seeing the latest data on core metrics. This can be a bummer during one-day promo events like Black Friday or Cyber Monday when real-time information can prove to be game-changing ! 

  Matomo processes data with lower latency even for high-traffic websites. Currently, we have 6-24 hour latency for cloud deployments. On-premises web analytics can be refreshed even faster — within an hour or instantly, depending on the traffic volumes. 

  8. No Native Conversion Optimisation Features

  Google Analytics users have to use third-party tools to get deeper insights like how people are interacting with your webpage or call-to-action.

  You can use the free Google Optimize tool, but it comes with limits : 

  • No segmentation is available 
  • Only 10 simultaneous running experiments allowed 

  There isn’t a native integration between Google Optimize and Google Analytics 4. Instead, you have to manually link an Optimize Container to an analytics account. Also, you can’t select experiment dimensions in Google Analytics reports.

  What’s more, Google Optimize is a basic CRO tool, best suited for split testing (A/B testing) of copy, visuals, URLs and page layouts. If you want to get more advanced data, you need to pay for extra tools. 

  Matomo comes with a native set of built-in conversion optimization features : 

  • Heatmaps 
  • User session recording 
  • Sales funnel analysis 
  • A/B testing 
  • Form submission analytics 

  

  9. Deprecated Annotations

  Annotations come in handy when you need to provide extra context to other team members. For example, point out unusual traffic spikes or highlight a leak in the sales funnel. 

  This feature was available in Universal Analytics but is now gone in Google Analytics 4. But you can still quickly capture, comment and share knowledge with your team in Matomo. 

  You can add annotations to any graph that shows statistics over time including visitor reports, funnel analysis charts or running A/B tests. 

  10. No White Label Option 

  This might be a minor limitation of Google Analytics, but a tangible one for agency owners. 

  Offering an on-brand, embedded web analytics platform can elevate your customer experience. But white label analytics were never a thing with Google Analytics, unlike Matomo. 

  Wrap Up 

  Google set a high bar for web analytics. But Google Analytics inherent limitations around privacy, reporting and deployment options prompt more users to consider Google Analytics alternatives, like Matomo. 

  With Matomo, you can easily migrate your historical data records and store customer data locally or in a designated cloud location. We operate by a 100% unsampled data principle and provide an array of privacy controls for advanced compliance. 

  Start your 21-day free trial (no credit card required) to see how Matomo compares to Google Analytics ! 

  21 day free trial. No credit card required.

  Your email address
  

  Your website address
  

  Your Analytics subdomain will be .matomo.cloud (change)

  Choose your analytics subdomain
  

  .matomo.cloud

  I hereby accept the terms and conditions and the data processing agreeement (DPA).

  
  Your information will be used to create an account on our cloud service. For more information please consult our privacy policy.
  
  

  » Start improving your websites now

  

• Google Analytics 4 (GA4) vs Universal Analytics (UA)

  24 janvier 2022, par Erin — Analytics Tips

  March 2022 Update : It’s official ! Google announced that Universal Analytics will no longer process any new data as of 1 July 2023. Google is now pushing Universal Analytics users to switch to the latest version of GA – Google Analytics 4. 

  Currently, Google Analytics 4 is unable to accept historical data from Universal Analytics. Users need to take action before July 2022, to ensure they have 12 months of data built up before the sunset of Universal Analytics

  So how do Universal Analytics and Google Analytics 4 compare ? And what alternative options do you have ? Let’s dive in. 

  In this blog, we’ll cover :

  What is Google Analytics 4 ? 

  In October 2020, Google launched Google Analytics 4, a completely redesigned analytics platform. This follows on from the previous version known as Universal Analytics (or UA).

  Amongst its touted benefits, GA4 promises a completely new way to model data and even the ability to predict future revenue. 

  However, the reception of GA4 has been largely negative. In fact, some users from the digital marketing community have said that GA4 is awful, unusable and so bad it can bring you to tears.

  

  

  Google Analytics 4 vs Universal Analytics

  There are some pretty big differences between Google Analytics 4 and Universal Analytics but for this blog, we’ll cover the top three.

  1. Redesigned user interface (UI)

  GA4 features a completely redesigned UI to Universal Analytics’ popular interface. This dramatic change has left many users in confusion and fuelled some users to declare that “most of the time you are going round in circles to find what you’re looking for.”

  

  2. Event-based tracking

  Google Analytics 4 also brings with it a new data model which is purely event-based. This event-based model moves away from the typical “pageview” metric that underpins Universal Analytics.

  3. Machine learning insights

  Google Analytics 4 promises to “predict the future behavior of your users” with their machine-learning-powered predictive metrics. This feature can “use shared aggregated and anonymous data to improve model quality”. Sounds powerful, right ?

  Unfortunately, it only works if at least 1,000 returning users triggered the relevant predictive condition over a seven-day period. Also, if the model isn’t sustained over a “period of time” then it won’t work. And according to Google, if “the model quality for your property falls below the minimum threshold, then Analytics will stop updating the corresponding predictions”.

  This means GA4’s machine learning insights probably won’t work for the majority of analytics users.

  Ultimately, GA4 is just not ready to replace Google’s Universal Analytics for most users. There are too many missing features.

  What’s missing in Google Analytics 4 ?

  Quite a lot. Even though it offers a completely new approach to analytics, there are a lot of key features and functions missing in GA4.

  Behavior Flow

  The Behavior Flow report in Universal Analytics helps to visualise the path users take from one page or Event to the next. It’s extremely useful when you’re looking for quick and clear insight. But it no longer exists in Google Analytics 4, and instead, two new overcomplicated reports have been introduced to replace it – funnel exploration report and path exploration report.

  The decision to remove this critical report will leave many users feeling disappointed and frustrated. 

  Limitations on custom dimensions

  You can create custom dimensions in Google Analytics 4 to capture advanced information. For example, if a user reads a blog post you can supplement that data with custom dimensions like author name or blog post length. But, you can only use up to 50, and for some that will make functionality like this almost pointless.

  Machine learning (ML) limitations

  Google Analytics 4 promises powerful ML insights to predict the likelihood of users converting based on their behaviors. The problem ? You need 1,000 returning users in one week. For most small-medium businesses this just isn’t possible.

  And if you do get this level of traffic in a week, there’s another hurdle. According to Google, if “the model quality for your property falls below the minimum threshold, then GA will stop updating the corresponding predictions.” To add insult to injury Google suggests that this might make all ML insights unavailable. But they can’t say for certain… 

  Views

  One cornerstone of Universal Analytics is the ability to configure views. Views allow you to set certain analytics environments for testing or cleaning up data by filtering out internal traffic, for example. 

  Views are great for quickly and easily filtering data. Preset views that contain just the information you want to see are the ideal analytics setup for smaller businesses, casual users, and do-it-yourself marketing departments.

  

  There are a few workarounds but they’re “messy [,] annoying and clunky,” says a disenfranchised Redditor.

  Another helpful Reddit user stumbled upon an unhelpful statement from Google. Google says that they “do not offer [the views] feature in Google Analytics 4 but are planning similar functionality in the future.” There’s no specific date yet though.

  Bounce rate

  Those that rely on bounce rate to understand their site’s performance will be disappointed to find out that bounce rate is also not available in GA4. Instead, Google is pushing a new metric known as “Engagement Rate”. With this metric, Google now uses their own formula to establish if a visitor is engaged with a site.

  Lack of integration

  Currently, GA4 isn’t ready to integrate with many core digital marketing tools and doesn’t accept non-Google data imports. This makes it difficult for users to analyse ROI and ROAS for campaigns measured in other tools. 

  Content Grouping

  Yet another key feature that Google has done away with is Content Grouping. However, as with some of the other missing features in GA4, there is a workaround, but it’s not simple for casual users to implement. In order to keep using Content Grouping, you’ll need to create event-scoped custom dimensions.

  Annotations 

  A key feature of Universal Analytics is the ability to add custom Annotations in views. Annotations are useful for marking dates that site changes were made for analysis in the future. However, Google has removed the Annotations feature and offered no alternative or workaround.

  Historical data imports are not available

  The new approach to data modelling in GA4 adds new functionality that UA can’t match. However, it also means that you can’t import historical UA data into GA4. 

  Google’s suggestion for this one ? Keep running UA with GA4 and duplicate events for your GA4 property. Now you will have two different implementations running alongside each other and doing slightly different things. Which doesn’t sound like a particularly streamlined solution, and adds another level of complexity.

  Should you switch to Google Analytics 4 ?

  So the burning question is, should you switch from Universal Analytics to Google Analytics 4 ? It really depends on whether you have the available resources and if you believe this tool is still right for your organisation. At the time of writing, GA4 is not ready for day-to-day use in most organisations.

  If you’re a casual user or someone looking for quick, clear insights then you will likely struggle with the switch to GA4. It appears that the new Google Analytics 4 has been designed for enterprise-scale businesses with large internal teams of analysts.

  

  Unfortunately, for most casual users, business owners and do-it-yourself marketers there are complex workarounds and time-consuming implementations to handle. Ultimately, it’s up to you to decide if the effort to migrate and relearn GA is worth it.

  Right now is the best time to draw the line and make a decision to either switch to GA4 or look for a better alternative to Google Analytics.

  Google Analytics alternative

  Matomo is one of the best Google Analytics alternatives offering an easy to use design with enhanced insights on our Cloud, On-Premise and on Matomo for WordPress solutions. 

  

  Matomo is an open-source analytics solution that provides a comprehensive, user-friendly and compliance-focused alternative to both Google Analytics 4 and Universal Analytics.

  The key benefits of using Matomo include :

  • Easy to use – Matomo provides a simpler interface and understandable KPIs. See for yourself with our live demo. 
  • Compliance – Future-proof your tech stack for looming privacy regulations. Matomo covers all of your ePrivacy, GDPR, HIPAA, CCPA, and PECR data compliance requirements. 
  • Data privacy and ownership – Your analytics data is 100% yours to own, with no external parties looking in.
  • Flexible, all-in-one solution – Get features like A/B Testing, Heatmaps, Session Recordings, SEO Web Vitals, Tag Manager, Media Analytics, Search Engine Keyword Performance, custom reports and much more. 
  • Integrations galore – Expand your Matomo capabilities by adding integrations from over 100 leading technologies.

  Plus, unlike GA4, Matomo will accept your historical data from UA so you don’t have to start all over again. Check out our 7 step guide to migrating from Google Analytics to find out how.

  Getting started with Matomo is easy. Check out our live demo and start your free 21-day trial. No credit card required.

  In addition to the limitations and complexities of GA4, there are many other significant drawbacks to using Google Analytics.

  Google’s data ethics are a growing concern of many and it is often discussed in the mainstream media. In addition, GA is not GDPR compliant by default and has resulted in 200k+ data protection cases against websites using GA.

  What’s more, the data that Google Analytics actually provides its end-users is extrapolated from samples. GA’s data sampling model means that once you’ve collected a certain amount of data Google Analytics will make educated guesses rather than use up its server space collecting your actual data. 

  The reasons to switch from Google Analytics are rising each day. 

  Wrap up

  The now required update to GA4 will add new layers of complexity, which will leave many casual web analytics users and marketers wondering if there’s a better way. Luckily there is. Get clear insights quickly and easily with Matomo – start your 21-day free trial now.

• How to get .mp4 videos from motion on a Raspberry Pi ?

  9 octobre 2016, par Maarti

  I use motion on my laptop and it works perfectly in any format. But when I use it on my Raspberry Pi 3 (Raspbian Jessie) with the Raspberry Camera V2, the only formats that work are : .avi and .swf.

  When I choose any other format, the output video is a "0 sec video" that is played and closed instantly.

  I would like to have .mp4 or .ogg output so I can read it easily with HTML5.

  Here is the motion codec documentation.

  Here is my config file :

  ############################################################
  
  # Daemon
  
  ############################################################
  
  
  
  # Start in daemon (background) mode and release terminal (default: off)
  
  daemon on
  
  
  
  # File to store the process ID, also called pid file. (default: not defined)
  
  process_id_file /var/run/motion/motion.pid
  
  
  
  ############################################################
  
  # Basic Setup Mode
  
  ############################################################
  
  
  
  # Start in Setup-Mode, daemon disabled. (default: off)
  
  setup_mode off
  
  
  
  
  
  # Use a file to save logs messages, if not defined stderr and syslog is used. (default: not defined)
  
  #logfile /mnt/camshare/Cam1/motion.log
  
  logfile /tmp/motion.log
  
  
  
  # Level of log messages [1..9] (EMR, ALR, CRT, ERR, WRN, NTC, INF, DBG, ALL). (default: 6 / NTC)
  
  log_level 2
  
  
  
  # Filter to log messages by type (COR, STR, ENC, NET, DBL, EVT, TRK, VID, ALL). (default: ALL)
  
  log_type all
  
  
  
  ###########################################################
  
  # Capture device options
  
  ############################################################
  
  
  
  # Videodevice to be used for capturing  (default /dev/video0)
  
  # for FreeBSD default is /dev/bktr0
  
  #videodevice /dev/video0
  
  
  
  # v4l2_palette allows to choose preferable palette to be use by motion
  
  # to capture from those supported by your videodevice. (default: 17)
  
  # E.g. if your videodevice supports both V4L2_PIX_FMT_SBGGR8 and
  
  # V4L2_PIX_FMT_MJPEG then motion will by default use V4L2_PIX_FMT_MJPEG.
  
  # Setting v4l2_palette to 2 forces motion to use V4L2_PIX_FMT_SBGGR8
  
  # instead.
  
  #
  
  # Values :
  
  # V4L2_PIX_FMT_SN9C10X : 0  'S910'
  
  # V4L2_PIX_FMT_SBGGR16 : 1  'BYR2'
  
  # V4L2_PIX_FMT_SBGGR8  : 2  'BA81'
  
  # V4L2_PIX_FMT_SPCA561 : 3  'S561'
  
  # V4L2_PIX_FMT_SGBRG8  : 4  'GBRG'
  
  # V4L2_PIX_FMT_SGRBG8  : 5  'GRBG'
  
  # V4L2_PIX_FMT_PAC207  : 6  'P207'
  
  # V4L2_PIX_FMT_PJPG    : 7  'PJPG'
  
  # V4L2_PIX_FMT_MJPEG   : 8  'MJPEG'
  
  # V4L2_PIX_FMT_JPEG    : 9  'JPEG'
  
  # V4L2_PIX_FMT_RGB24   : 10 'RGB3'
  
  # V4L2_PIX_FMT_SPCA501 : 11 'S501'
  
  # V4L2_PIX_FMT_SPCA505 : 12 'S505'
  
  # V4L2_PIX_FMT_SPCA508 : 13 'S508'
  
  # V4L2_PIX_FMT_UYVY    : 14 'UYVY'
  
  # V4L2_PIX_FMT_YUYV    : 15 'YUYV'
  
  # V4L2_PIX_FMT_YUV422P : 16 '422P'
  
  # V4L2_PIX_FMT_YUV420  : 17 'YU12'
  
  #
  
  v4l2_palette 7
  
  
  
  # Tuner device to be used for capturing using tuner as source (default /dev/tuner0)
  
  # This is ONLY used for FreeBSD. Leave it commented out for Linux
  
  ; tunerdevice /dev/tuner0
  
  
  
  # The video input to be used (default: -1)
  
  # Should normally be set to 0 or 1 for video/TV cards, and -1 for USB cameras
  
  input -1
  
  
  
  # The video norm to use (only for video capture and TV tuner cards)
  
  # Values: 0 (PAL), 1 (NTSC), 2 (SECAM), 3 (PAL NC no colour). Default: 0 (PAL)
  
  norm 0
  
  
  
  # The frequency to set the tuner to (kHz) (only for TV tuner cards) (default: 0)
  
  frequency 0
  
  
  
  # Rotate image this number of degrees. The rotation affects all saved images as
  
  # well as movies. Valid values: 0 (default = no rotation), 90, 180 and 270.
  
  rotate 0
  
  
  
  # Image width (pixels). Valid range: Camera dependent, default: 352
  
  #width 1024
  
  width 640
  
  
  
  # Image height (pixels). Valid range: Camera dependent, default: 288
  
  #height 576
  
  height 480
  
  
  
  # Maximum number of frames to be captured per second.
  
  # Valid range: 2-100. Default: 100 (almost no limit).
  
  framerate 15
  
  
  
  # Minimum time in seconds between capturing picture frames from the camera.
  
  # Default: 0 = disabled - the capture rate is given by the camera framerate.
  
  # This option is used when you want to capture images at a rate lower than 2 per second.
  
  minimum_frame_time 0
  
  
  
  # URL to use if you are using a network camera, size will be autodetected (incl http:// ftp:// mjpg:// or file:///)
  
  # Must be a URL that returns single jpeg pictures or a raw mjpeg stream. Default: Not defined
  
  ;netcam_url http://127.0.0.1/cgi-bin/raspicam.sh
  
  
  
  # Username and password for network camera (only if required). Default: not defined
  
  # Syntax is user:password
  
  ; netcam_userpass value
  
  
  
  # The setting for keep-alive of network socket, should improve performance on compatible net cameras.
  
  # off:   The historical implementation using HTTP/1.0, closing the socket after each http request.
  
  # force: Use HTTP/1.0 requests with keep alive header to reuse the same connection.
  
  # on:    Use HTTP/1.1 requests that support keep alive as default.
  
  # Default: off
  
  netcam_keepalive off
  
  
  
  # URL to use for a netcam proxy server, if required, e.g. "http://myproxy".
  
  # If a port number other than 80 is needed, use "http://myproxy:1234".
  
  # Default: not defined
  
  ; netcam_proxy value
  
  
  
  # Set less strict jpeg checks for network cameras with a poor/buggy firmware.
  
  # Default: off
  
  netcam_tolerant_check off
  
  
  
  # Let motion regulate the brightness of a video device (default: off).
  
  # The auto_brightness feature uses the brightness option as its target value.
  
  # If brightness is zero auto_brightness will adjust to average brightness value 128.
  
  # Only recommended for cameras without auto brightness
  
  auto_brightness off
  
  
  
  # Set the initial brightness of a video device.
  
  # If auto_brightness is enabled, this value defines the average brightness level
  
  # which Motion will try and adjust to.
  
  # Valid range 0-255, default 0 = disabled
  
  brightness 0
  
  
  
  # Set the contrast of a video device.
  
  # Valid range 0-255, default 0 = disabled
  
  contrast 0
  
  
  
  # Set the saturation of a video device.
  
  # Valid range 0-255, default 0 = disabled
  
  saturation 0
  
  
  
  # Set the hue of a video device (NTSC feature).
  
  # Valid range 0-255, default 0 = disabled
  
  hue 0
  
  
  
  ############################################################
  
  # File "camera" support - read raw YUV data from a file
  
  ############################################################
  
  #filecam_path /home/pi/test-cap/motion-mmal.capture
  
  
  
  ############################################################
  
  # OpenMax/MMAL camera support for Raspberry Pi
  
  ############################################################
  
  mmalcam_name vc.ril.camera
  
  #mmalcam_control_params
  
  #mmalcam_raw_capture_file /home/pi/motion-mmal.capture
  
  
  
  # Switch this setting to "on" to use the still image mode of the Pi's camera
  
  # instead of video. This gives a wider field of view, but requires
  
  # a much slower frame-rate to achieve exposure stability
  
  # (e.g. 0.25 fps or slower). You can use the minimum_frame_time
  
  # parameter above to achieve this
  
  
  
  mmalcam_use_still off
  
  
  
  
  
  ############################################################
  
  # Round Robin (multiple inputs on same video device name)
  
  ############################################################
  
  
  
  # Number of frames to capture in each roundrobin step (default: 1)
  
  roundrobin_frames 1
  
  
  
  # Number of frames to skip before each roundrobin step (default: 1)
  
  roundrobin_skip 1
  
  
  
  # Try to filter out noise generated by roundrobin (default: off)
  
  switchfilter off
  
  
  
  
  
  ############################################################
  
  # Motion Detection Settings:
  
  ############################################################
  
  
  
  # Threshold for number of changed pixels in an image that
  
  # triggers motion detection (default: 1500)
  
  threshold 1500
  
  
  
  # Automatically tune the threshold down if possible (default: off)
  
  threshold_tune off
  
  
  
  # Noise threshold for the motion detection (default: 32)
  
  noise_level 32
  
  
  
  # Automatically tune the noise threshold (default: on)
  
  noise_tune on
  
  
  
  # Despeckle motion image using (e)rode or (d)ilate or (l)abel (Default: not defined)
  
  # Recommended value is EedDl. Any combination (and number of) of E, e, d, and D is valid.
  
  # (l)abeling must only be used once and the 'l' must be the last letter.
  
  # Comment out to disable
  
  despeckle_filter EedDl
  
  
  
  # Detect motion in predefined areas (1 - 9). Areas are numbered like that:  1 2 3
  
  # A script (on_area_detected) is started immediately when motion is         4 5 6
  
  # detected in one of the given areas, but only once during an event.        7 8 9
  
  # One or more areas can be specified with this option. Take care: This option
  
  # does NOT restrict detection to these areas! (Default: not defined)
  
  ; area_detect value
  
  
  
  # PGM file to use as a sensitivity mask.
  
  # Full path name to. (Default: not defined)
  
  ; mask_file value
  
  
  
  # Dynamically create a mask file during operation (default: 0)
  
  # Adjust speed of mask changes from 0 (off) to 10 (fast)
  
  smart_mask_speed 0
  
  
  
  # Ignore sudden massive light intensity changes given as a percentage of the picture
  
  # area that changed intensity. Valid range: 0 - 100 , default: 0 = disabled
  
  lightswitch 0
  
  
  
  # Picture frames must contain motion at least the specified number of frames
  
  # in a row before they are detected as true motion. At the default of 1, all
  
  # motion is detected. Valid range: 1 to thousands, recommended 1-5
  
  minimum_motion_frames 1
  
  
  
  # Specifies the number of pre-captured (buffered) pictures from before motion
  
  # was detected that will be output at motion detection.
  
  # Recommended range: 0 to 5 (default: 0)
  
  # Do not use large values! Large values will cause Motion to skip video frames and
  
  # cause unsmooth movies. To smooth movies use larger values of post_capture instead.
  
  pre_capture 2
  
  
  
  # Number of frames to capture after motion is no longer detected (default: 0)
  
  post_capture 2
  
  
  
  # Event Gap is the seconds of no motion detection that triggers the end of an event.
  
  # An event is defined as a series of motion images taken within a short timeframe.
  
  # Recommended value is 60 seconds (Default). The value -1 is allowed and disables
  
  # events causing all Motion to be written to one single movie file and no pre_capture.
  
  # If set to 0, motion is running in gapless mode. Movies don't have gaps anymore. An
  
  # event ends right after no more motion is detected and post_capture is over.
  
  event_gap 60
  
  
  
  # Maximum length in seconds of an mpeg movie
  
  # When value is exceeded a new movie file is created. (Default: 0 = infinite)
  
  # ATTENTION: when you're not using the motion build from the tutorial, it might fail with error 'Unknown config option "max_mpeg_time"'
  
  # the use this line instead:
  
  # max_movie_time 60
  
  max_movie_time 60
  
  
  
  # Always save images even if there was no motion (default: off)
  
  emulate_motion off
  
  
  
  
  
  ############################################################
  
  # Image File Output
  
  ############################################################
  
  
  
  # Output 'normal' pictures when motion is detected (default: on)
  
  # Valid values: on, off, first, best, center
  
  # When set to 'first', only the first picture of an event is saved.
  
  # Picture with most motion of an event is saved when set to 'best'.
  
  # Picture with motion nearest center of picture is saved when set to 'center'.
  
  # Can be used as preview shot for the corresponding movie.
  
  output_pictures best
  
  
  
  # Output pictures with only the pixels moving object (ghost images) (default: off)
  
  output_debug_pictures off
  
  
  
  # The quality (in percent) to be used by the jpeg compression (default: 75)
  
  quality 75
  
  
  
  # Type of output images
  
  # Valid values: jpeg, ppm (default: jpeg)
  
  picture_type jpeg
  
  
  
  ############################################################
  
  # FFMPEG related options
  
  # Film (movies) file output, and deinterlacing of the video input
  
  # The options movie_filename and timelapse_filename are also used
  
  # by the ffmpeg feature
  
  ############################################################
  
  
  
  # Use ffmpeg to encode movies in realtime (default: off)
  
  ffmpeg_output_movies on
  
  
  
  # Use ffmpeg to make movies with only the pixels moving
  
  # object (ghost images) (default: off)
  
  ffmpeg_output_debug_movies off
  
  
  
  # Use ffmpeg to encode a timelapse movie
  
  # Default value 0 = off - else save frame every Nth second
  
  ffmpeg_timelapse 0
  
  
  
  # The file rollover mode of the timelapse video
  
  # Valid values: hourly, daily (default), weekly-sunday, weekly-monday, monthly, manual
  
  ffmpeg_timelapse_mode daily
  
  
  
  # Bitrate to be used by the ffmpeg encoder (default: 400000)
  
  # This option is ignored if ffmpeg_variable_bitrate is not 0 (disabled)
  
  ffmpeg_bps 500000
  
  
  
  # Enables and defines variable bitrate for the ffmpeg encoder.
  
  # ffmpeg_bps is ignored if variable bitrate is enabled.
  
  # Valid values: 0 (default) = fixed bitrate defined by ffmpeg_bps,
  
  # or the range 2 - 31 where 2 means best quality and 31 is worst.
  
  ffmpeg_variable_bitrate 5
  
  
  
  # Codec to used by ffmpeg for the video compression.
  
  # Timelapse mpegs are always made in mpeg1 format independent from this option.
  
  # Supported formats are: mpeg1 (ffmpeg-0.4.8 only), mpeg4 (default), and msmpeg4.
  
  # mpeg1 - gives you files with extension .mpg
  
  # mpeg4 or msmpeg4 - gives you files with extension .avi
  
  # msmpeg4 is recommended for use with Windows Media Player because
  
  # it requires no installation of codec on the Windows client.
  
  # swf - gives you a flash film with extension .swf
  
  # flv - gives you a flash video with extension .flv
  
  # ffv1 - FF video codec 1 for Lossless Encoding ( experimental )
  
  # mov - QuickTime ( testing )
  
  # ogg - Ogg/Theora ( testing )
  
  #ffmpeg_video_codec msmpeg4
  
  ffmpeg_video_codec mp4
  
  
  
  # Use ffmpeg to deinterlace video. Necessary if you use an analog camera
  
  # and see horizontal combing on moving objects in video or pictures.
  
  # (default: off)
  
  ffmpeg_deinterlace off
  
  
  
  ############################################################
  
  # SDL Window
  
  ############################################################
  
  
  
  # Number of motion thread to show in SDL Window (default: 0 = disabled)
  
  #sdl_threadnr 0
  
  
  
  ############################################################
  
  # External pipe to video encoder
  
  # Replacement for FFMPEG builtin encoder for ffmpeg_output_movies only.
  
  # The options movie_filename and timelapse_filename are also used
  
  # by the ffmpeg feature
  
  #############################################################
  
  
  
  # Bool to enable or disable extpipe (default: off)
  
  use_extpipe off
  
  
  
  # External program (full path and opts) to pipe raw video to
  
  # Generally, use '-' for STDIN...
  
  ;extpipe mencoder -demuxer rawvideo -rawvideo w=320:h=240:i420 -ovc x264 -x264encopts bframes=4:frameref=1:subq=1:scenecut=-1:nob_adapt:threads=1:keyint=1000:8x8dct:vbv_bufsize=4000:crf=24:partitions=i8x8,i4x4:vbv_maxrate=800:no-chroma-me -vf denoise3d=16:12:48:4,pp=lb -of   avi -o %f.avi - -fps %fps
  
  
  
  
  
  
  
  ############################################################
  
  # Snapshots (Traditional Periodic Webcam File Output)
  
  ############################################################
  
  
  
  # Make automated snapshot every N seconds (default: 0 = disabled)
  
  snapshot_interval 0
  
  
  
  
  
  ############################################################
  
  # Text Display
  
  # %Y = year, %m = month, %d = date,
  
  # %H = hour, %M = minute, %S = second, %T = HH:MM:SS,
  
  # %v = event, %q = frame number, %t = thread (camera) number,
  
  # %D = changed pixels, %N = noise level, \n = new line,
  
  # %i and %J = width and height of motion area,
  
  # %K and %L = X and Y coordinates of motion center
  
  # %C = value defined by text_event - do not use with text_event!
  
  # You can put quotation marks around the text to allow
  
  # leading spaces
  
  ############################################################
  
  
  
  # Locate and draw a box around the moving object.
  
  # Valid values: on, off, preview (default: off)
  
  # Set to 'preview' will only draw a box in preview_shot pictures.
  
  locate_motion_mode off
  
  
  
  # Set the look and style of the locate box if enabled.
  
  # Valid values: box, redbox, cross, redcross (default: box)
  
  # Set to 'box' will draw the traditional box.
  
  # Set to 'redbox' will draw a red box.
  
  # Set to 'cross' will draw a little cross to mark center.
  
  # Set to 'redcross' will draw a little red cross to mark center.
  
  locate_motion_style box
  
  
  
  # Draws the timestamp using same options as C function strftime(3)
  
  # Default: %Y-%m-%d\n%T = date in ISO format and time in 24 hour clock
  
  # Text is placed in lower right corner
  
  text_right %d.%m.%Y\n%T
  
  
  
  # Draw a user defined text on the images using same options as C function strftime(3)
  
  # Default: Not defined = no text
  
  # Text is placed in lower left corner
  
  ; text_left CAMERA %t
  
  text_left HofCam
  
  
  
  # Draw the number of changed pixed on the images (default: off)
  
  # Will normally be set to off except when you setup and adjust the motion settings
  
  # Text is placed in upper right corner
  
  text_changes off
  
  
  
  # This option defines the value of the special event conversion specifier %C
  
  # You can use any conversion specifier in this option except %C. Date and time
  
  # values are from the timestamp of the first image in the current event.
  
  # Default: %Y%m%d%H%M%S
  
  # The idea is that %C can be used filenames and text_left/right for creating
  
  # a unique identifier for each event.
  
  text_event %Y%m%d%H%M%S
  
  
  
  # Draw characters at twice normal size on images. (default: off)
  
  text_double on
  
  
  
  
  
  # Text to include in a JPEG EXIF comment
  
  # May be any text, including conversion specifiers.
  
  # The EXIF timestamp is included independent of this text.
  
  ;exif_text %i%J/%K%L
  
  
  
  ############################################################
  
  # Target Directories and filenames For Images And Films
  
  # For the options snapshot_, picture_, movie_ and timelapse_filename
  
  # you can use conversion specifiers
  
  # %Y = year, %m = month, %d = date,
  
  # %H = hour, %M = minute, %S = second,
  
  # %v = event, %q = frame number, %t = thread (camera) number,
  
  # %D = changed pixels, %N = noise level,
  
  # %i and %J = width and height of motion area,
  
  # %K and %L = X and Y coordinates of motion center
  
  # %C = value defined by text_event
  
  # Quotation marks round string are allowed.
  
  ############################################################
  
  
  
  # Target base directory for pictures and films
  
  # Recommended to use absolute path. (Default: current working directory)
  
  target_dir /home/pi
  
  
  
  # File path for snapshots (jpeg or ppm) relative to target_dir
  
  # Default: %v-%Y%m%d%H%M%S-snapshot
  
  # Default value is equivalent to legacy oldlayout option
  
  # For Motion 3.0 compatible mode choose: %Y/%m/%d/%H/%M/%S-snapshot
  
  # File extension .jpg or .ppm is automatically added so do not include this.
  
  # Note: A symbolic link called lastsnap.jpg created in the target_dir will always
  
  # point to the latest snapshot, unless snapshot_filename is exactly 'lastsnap'
  
  snapshot_filename %v-%Y%m%d%H%M%S-snapshot
  
  
  
  # File path for motion triggered images (jpeg or ppm) relative to target_dir
  
  # Default: %v-%Y%m%d%H%M%S-%q
  
  # Default value is equivalent to legacy oldlayout option
  
  # For Motion 3.0 compatible mode choose: %Y/%m/%d/%H/%M/%S-%q
  
  # File extension .jpg or .ppm is automatically added so do not include this
  
  # Set to 'preview' together with best-preview feature enables special naming
  
  # convention for preview shots. See motion guide for details
  
  picture_filename %v-%Y%m%d%H%M%S-%q
  
  
  
  # File path for motion triggered ffmpeg films (movies) relative to target_dir
  
  # Default: %v-%Y%m%d%H%M%S
  
  # Default value is equivalent to legacy oldlayout option
  
  # For Motion 3.0 compatible mode choose: %Y/%m/%d/%H%M%S
  
  # File extension .mpg or .avi is automatically added so do not include this
  
  # This option was previously called ffmpeg_filename
  
  movie_filename %v-%Y%m%d%H%M%S
  
  
  
  # File path for timelapse movies relative to target_dir
  
  # Default: %Y%m%d-timelapse
  
  # Default value is near equivalent to legacy oldlayout option
  
  # For Motion 3.0 compatible mode choose: %Y/%m/%d-timelapse
  
  # File extension .mpg is automatically added so do not include this
  
  timelapse_filename %Y%m%d-timelapse
  
  
  
  ############################################################
  
  # Global Network Options
  
  ############################################################
  
  # Enable or disable IPV6 for http control and stream (default: off )
  
  ipv6_enabled off
  
  
  
  ############################################################
  
  # Live Stream Server
  
  ############################################################
  
  
  
  # The mini-http server listens to this port for requests (default: 0 = disabled)
  
  stream_port 8080
  
  
  
  # Quality of the jpeg (in percent) images produced (default: 50)
  
  stream_quality 50
  
  
  
  # Output frames at 1 fps when no motion is detected and increase to the
  
  # rate given by stream_maxrate when motion is detected (default: off)
  
  stream_motion on
  
  
  
  # Maximum framerate for stream streams (default: 1)
  
  stream_maxrate 4
  
  
  
  # Restrict stream connections to localhost only (default: on)
  
  stream_localhost off
  
  
  
  # Limits the number of images per connection (default: 0 = unlimited)
  
  # Number can be defined by multiplying actual stream rate by desired number of seconds
  
  # Actual stream rate is the smallest of the numbers framerate and stream_maxrate
  
  stream_limit 0
  
  
  
  # Set the authentication method (default: 0)
  
  # 0 = disabled
  
  # 1 = Basic authentication
  
  # 2 = MD5 digest (the safer authentication)
  
  stream_auth_method 0
  
  
  
  # Authentication for the stream. Syntax username:password
  
  # Default: not defined (Disabled)
  
  ; stream_authentication username:password
  
  
  
  
  
  ############################################################
  
  # HTTP Based Control
  
  ############################################################
  
  
  
  # TCP/IP port for the http server to listen on (default: 0 = disabled)
  
  webcontrol_port 8081
  
  
  
  # Restrict control connections to localhost only (default: on)
  
  webcontrol_localhost off
  
  
  
  # Output for http server, select off to choose raw text plain (default: on)
  
  webcontrol_html_output on
  
  
  
  # Authentication for the http based control. Syntax username:password
  
  # Default: not defined (Disabled)
  
  ; webcontrol_authentication username:password
  
  
  
  
  
  ############################################################
  
  # Tracking (Pan/Tilt)
  
  #############################################################
  
  
  
  # Type of tracker (0=none (default), 1=stepper, 2=iomojo, 3=pwc, 4=generic, 5=uvcvideo, 6=servo)
  
  # The generic type enables the definition of motion center and motion size to
  
  # be used with the conversion specifiers for options like on_motion_detected
  
  track_type 0
  
  
  
  # Enable auto tracking (default: off)
  
  track_auto off
  
  
  
  # Serial port of motor (default: none)
  
  ;track_port /dev/ttyS0
  
  
  
  # Motor number for x-axis (default: 0)
  
  ;track_motorx 0
  
  
  
  # Set motorx reverse (default: 0)
  
  ;track_motorx_reverse 0
  
  
  
  # Motor number for y-axis (default: 0)
  
  ;track_motory 1
  
  
  
  # Set motory reverse (default: 0)
  
  ;track_motory_reverse 0
  
  
  
  # Maximum value on x-axis (default: 0)
  
  ;track_maxx 200
  
  
  
  # Minimum value on x-axis (default: 0)
  
  ;track_minx 50
  
  
  
  # Maximum value on y-axis (default: 0)
  
  ;track_maxy 200
  
  
  
  # Minimum value on y-axis (default: 0)
  
  ;track_miny 50
  
  
  
  # Center value on x-axis (default: 0)
  
  ;track_homex 128
  
  
  
  # Center value on y-axis (default: 0)
  
  ;track_homey 128
  
  
  
  # ID of an iomojo camera if used (default: 0)
  
  track_iomojo_id 0
  
  
  
  # Angle in degrees the camera moves per step on the X-axis
  
  # with auto-track (default: 10)
  
  # Currently only used with pwc type cameras
  
  track_step_angle_x 10
  
  
  
  [...]