> For the complete documentation index, see [llms.txt](https://docs.theiamarkerless.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.theiamarkerless.com/theia3d-documentation/theia3d-dropdown-menus/tools-menu/display-video-metadata.md).
# Display Video Metadata
The Display Video Metadata tool.
The Display Video Metadata tool can be used to easily review relevant metadata for the videos currently loaded, including:
### **Camera Id**
Camera ID dropdown, allowing separate cameras to be selected and reviewed.
### **Video Path**
Path to the video file for the currently selected camera.
### **Trial**
Name of the lowest folder level.
### **Size**
Video image resolution, in pixels.
### **Number of Frames**
Video file length, in frames.
### **Frame Rate**
Video file frame rate, in frames per second.
### **Frame Offset**
Number of frames offset between the current video file and other synchronized video files from the current recording. Generally a value of 0 is expected for most camera systems that record frame synchronized videos using on a start/stop trigger signal. Sony RX0 II camera systems may have non-zero values here, as these systems use timecode video synchronization for post-hoc alignment of videos between cameras.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.theiamarkerless.com/theia3d-documentation/theia3d-dropdown-menus/tools-menu/display-video-metadata.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
