iHeart Fiesta 2025 Artist Video Specifications
Last updated: Oct 19, 2025
These content delivery guidelines are meant to help us achieve a smooth and successful show. If you have any questions please contact Sean Green at [email protected]
LED Screens
- 1x center Hero LED wall
- 1x center Turntable LED wall (also called Guillotine wall)
- 2x IMAG sidescreens
- Screens 1-6
Content Pixel Map
- 1x 3840x2160 output
Safe areas for scaling 1920x1080 content
If you have 1920x1080 content intended for the IMAG and/or HERO LED wall please ensure that no critical content is in the red areas below. These pixels will be cropped off when 1920x1080 content is scaled to fit the width of the LED. You can use the images below as a reference for the safe areas.
IMAG screen safe area:
HERO screen safe area:
d3 Template Project
Here is a template project for d3 with all the pixel maps and feed maps ready to go.
File Delivery
Encoding Specs
| Video Content | |
|---|---|
| Codec | NotchLC |
| Container | Quicktime MOV |
| Frame Rate | 30 |
Rendering to NotchLC:
Download the NotchLC codec: https://notchlc.notch.one
File Naming Conventions
Please name all content according to the following parameters:
[look###] _ [lookDescription] _ [versionTag] .mov
| Example: | |
|---|---|
| filename | 023_KashmirPart1_v7502240941.mov |
| alt. version scheme | 001_FourSticks_v1.mov |
Further Clarification of the Naming Convention
Look### and Look Description:
A “look” is a discrete moment on stage that can incorporate as many screens as necessary to achieve the creative goal. The look number should be three digits (i.e. “001”, not “1”). The look description helps to describe the look number. Do not use spaces in the look description, but do capitalize the first letter of each word.
| Examples: | |
|---|---|
| look 1 | 001_KashmirPart1_v2205311430.mov |
| look 2 | 002_KashmirPart2_v2205311430.mov |
| look 3 | 003_ImmigrantSong_v2205311430.mov |
Version Tag:
Versioning allows the server to automatically update video files and can save programming time. This can be used anytime a new file is a direct replacement for an existing asset. For versioning to work, the base filename must be exactly the same with an updated version tag.
All content, including the initial delivery, must have a version number. You can use a version tag with date and 24-hour time-based tag appended to the filename using the format “_vYYMMDDHHMM”. Alternatively, you can use an incremented version tag using the format “_v#”.
| Examples: | |
|---|---|
| video created | January 15th, 2022 at 2:30pm |
| version tag | “_v2201151430.mov” |
| alt. version scheme | “_v1.mov”, “_v2.mov” |
POC: Sean W. Green
[email protected]