---
title: "Vision video recording"
slug: "vision-video-recording"
updated: 2025-03-17T13:24:07Z
published: 2025-03-17T13:24:07Z
canonical: "support.tulip.co/vision-video-recording"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.tulip.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Vision video recording

*Learn how to use Video Recording in Tulip Vision*

          Availability

          

Vision Video Recording releases to Tulip Instances with Player 2.6.0/LTS13.

**In this article, you will learn:**

- **How to set up Vision Video Recording in the App Editor**
- **How to use Vision Video Recording to support quality use cases**

---

Handling and recording video is a requirement for many quality use cases. The Vision video recording feature captures video segments of quality events after they’ve taken place (i.e. 5 minutes or less of video).

## Set up Vision video

There are three to four key Triggers to set up to utilize vision video recording.

- **Start Video Buffer**
- **Save Video Buffer**
- **End Video Buffer**
- **Video Save**

The diagram below shows the sequence of these triggers:

![Vision Recording Process Diagram](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Vision%20Recording%20Process%20Diagram.png)

### Start Video Buffer

Establish how long the video buffer records. You can input a value **between 5 and 300 seconds**.

          NOTE

          

If you input a value under 5 or over 300, the value defaults to the minimum or maximum.

This will start an ongoing stream of video that, once ended, retains the last *X* seconds of video (*X* being the number of seconds inputted).

![Screenshot 2024-07-17 at 5.49.14 PM](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Screenshot%202024-07-17%20at%205.49.14%20PM.png)

### Save Video Buffer

This trigger ends the video buffer and stops the recording. It then allows Tulip to prepare the video as a S3 url.

![Screenshot 2024-07-17 at 5.49.23 PM](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Screenshot%202024-07-17%20at%205.49.23%20PM.png)

### Video Save

Create a machine/device trigger that responds to the event **Video Uploaded** (the **Save Video Buffer** trigger). Once this event fires, Tulip provides the video in a S3 url. Users can choose to save the url in a table or show this in the app with an embdedded video widget.

In the example below, the video saves locally, but it can also be written to a table record.

![Screenshot 2024-07-17 at 5.49.35 PM](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Screenshot%202024-07-17%20at%205.49.35%20PM.png)

### End Video Buffer

The **end video buffer** is optional. You can either cancel the video buffer via a button (see example below) or go to another step.

![Screenshot 2024-07-17 at 5.49.28 PM](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Screenshot%202024-07-17%20at%205.49.28%20PM.png)

## Quality Use Case

You want to record a quality use case of a motor assembly process. You need to confirm that every motor packaged has the required motor as well as a neccessary tool. This is to ensure that these are undamaged before shiping them to the customer.

[Video for "Scheduled Automations.mp4"](https://tulip.widen.net/view/video/d5xjutxqlk/Video-Recording-Demo.mp4)

---

Did you find what you were looking for?

You can also head to [community.tulip.co](https://community.tulip.co/?utm_source=intercom&utm_medium=article-link&utm_campaign=all) to post your question or see if others have faced a similar question!

**Tulip Vision**

**Vision**is a simple no-code tool to use cameras for visual inspection, process adherence, equipment, personnel, and material tracking on the shop floor.

**Trigger**

**Triggers** are groups of logic that are tied to an app event, such as step open, timer, widget interaction, etc. App builders can add triggers to **widgets**, **machines**, **devices**, **apps**, and **steps**.

**Triggers** can contain **actions**, **transitions**, and **conditions**.