When enabled, an event video will only be requested for the first event when there is a succession of event triggers. No further videos will be requested for any subsequent events that are triggered during the set duration. Use this to reduce data usage.
You have to enable this setting. Then specify the duration, which is the window in seconds where only the first event will trigger a video in the sequence of events. This is configured independently per event and each event can have a different duration while some events do not need to be enabled at all.
Please note that you can only set this for MiX Vision AI event types and not the OBC events that have video capability.
Set this on either library or template level, but not on asset-level:
- Click Manage.
- Under Config Admin, click Templates / Libraries.
- Make sure you are on the Event library/ Event templates tab.
- Look for the relevant template name or event in the library and click on the downwards action arrow and select Edit:
- If you are making changes to the event template, you have to click on the name of the relevant event in the template. Remember that this only applies to MiX Vision AI events.
Click on the image to view it in full screen if the article is open in your browser
:
- Scroll to Limit video requests and check the box next to it. You can now specify the duration where only a single video will be sent in a sequence of events.
- Enter the duration. You can enter a value between 30 seconds and 600 seconds.
- Click Save.
Please note that the event cap setting will take priority over the set video limits. Say for example you have the seatbelt event configured with a video limit and you exceed the *event cap threshold while also limiting the video requests, the system will switch to the event cap (which is a 24-hour lock on requests) for that event instead of using the duration of the video limit request.
*Event cap is if an excessive number of events are triggered for an asset, the video requests for that event are temporarily stopped for 24 hours, after which they will resume as normal. This helps limit high data usage. The threshold determines how many events must occur within 1 hour before the cap is enabled. It is applied per asset and per event.