Event Media Creation Guide

LIGHT FORGE — F5 PGS

Content & Pixel Map Guidelines

Westin Seattle Hotel September 13–17, 2026 Prepared by AV Factory v3 · August 2026

About This Guide

Standard 16:9 content, one slightly-wider-than-16:9 wall

This event uses two identical LED walls flanking a printed backdrop, with content delivered as standard 1920 × 1080 video and 16:9 PowerPoint. The walls are slightly wider than 16:9 (2496 × 1344); your frame is scaled to the full wall height, and the live stream crops that same 16:9 region — delivering your file to the broadcast pixel-for-pixel.

This guide shows how that framing works, where to keep your text so nothing gets clipped, and — for anyone who wants their graphics razor-sharp on the wall itself — the native pixel spec. Questions, early and often: cbaldini@avfactory.com

Overview & Quick Reference

Every destination at a glance
2496 × 1344STAGE RIGHT LEDROE GP2.6 · 16:9 CONTENT FIT TO HEIGHTf5PRINTED GRAPHICSCENIC BACKDROP — NO DIGITAL CONTENT2496 × 1344STAGE LEFT LEDROE GP2.6 · 16:9 CONTENT FIT TO HEIGHT12′ × 24′ MAIN STAGE · +24″LIGHT FORGE F5 PGS — SET OVERVIEWPIXEL MAPS BY DESTINATION · ISOMETRIC VIEW · NOT TO SCALE · WESTIN SEATTLE · SEPT 13–17 2026OUTBOARD LED WALL ×2 — 2496 × 1344, mirrored · 16:9 content fit to heightPRINTED CENTER GRAPHIC — scenic only, no content deliverables
The full rig: two outboard LED walls flanking the printed center graphic, with the main stage. Stylized view — not to scale.
DestinationWorking SpecNative ResolutionPhysical SizeContent Sources
Stage Left LED Wall1920 × 1080 (16:9)2496 × 1344 21'-3⅞" × 11'-5¾"PlayBack Pro (video/stills) · PowerPoint (16:9 deck) — mirrored: one file drives both walls
Stage Right LED Wall1920 × 1080 (16:9)2496 × 1344 21'-3⅞" × 11'-5¾"
Live Stream (derived)1920 × 1080 Cropped from the wall feed — your fitted 16:9 frame, returned 1:1
Center Backdrop Printed scenic graphic — no digital content

The System

LED walls are ROE Visual Graphite GP2.6 (2.6 mm pitch), ground-stacked, fed as one mirrored signal. There is no media server on this show — video and stills roll from PlayBack Pro and slides from PowerPoint. Your 16:9 content is scaled to the full wall height by our playback chain, and the live stream crops its 16:9 program from the same feed. You don't need to think about any of that — deliver clean 1080p and we'll do the rest.

Three Rules That Cover 90% of It

  • Deliver 1920 × 1080 at 29.97/30 fps (and ordinary 16:9 decks) — never 23.98/24 fps.
  • Keep text and logos ~40 px inside the edges of your 1080p frame — standard title-safe protects both the physical wall edge and the broadcast.
  • Know the sharpness ceiling: your frame is enlarged 124% on the wall. Video and photography carry it fine; hairlines and small text go a little soft. Hero graphics can be built at native 2496 × 1344 (see Pixel Map) for a pixel-perfect wall.

16:9 on These Walls — Read This First

Two ways to frame it · one clear winner

The wall is 13:7 — just 4% wider than your 16:9 frame. That gap has to go somewhere, and there are exactly two choices: fit the frame to the wall's height (slim gaps at the sides) or to its width (shave the top and bottom). We frame everything fit-height unless you specifically ask otherwise — here's why.

FIT HEIGHT — HOUSE STANDARD ✓what we do unless you ask otherwiseYOUR 1920 × 1080scaled ×1.244 to full wall height → 2389⅓ × 1344complete frame in the room · stream shows it 1:1slim ≈5½″ pillars at the wall edges (53⅓ px) — invisible against the black surroundFIT WIDTH — BY REQUEST ONLY ✕fills the wall edge-to-edge, at a costYOUR 1920 × 1080scaled ×1.30 to full wall width → 2496 × 140430 px shaved off the top AND bottom · stream then crops sides tootitles near the top of a slide are the first thing to go — by request only
Fit height keeps your entire frame and hands the stream a 1:1 copy of your file. Fit width fills the wall but crops 30 px from the top and bottom — and the stream loses side pixels on top of that.
The stream round-trip: fit-height scales your 1080p frame up ×1.244 to wall height; the stream then scales the same region back down ×0.804 to 1080p. The two cancel exactly — the broadcast audience sees your original file, pixel-for-pixel. No crop, no soft generation, no surprises on the recording.
WORKS BEAUTIFULLY
  • Standard 1920 × 1080 renders and 16:9 decks, as-is
  • Text and logos inside normal title-safe (~40 px)
  • Video and photography — the 124% enlargement is invisible at audience distance
  • Darker backgrounds — the side gaps disappear against the black surround
  • Native 2496 × 1344 builds for hero/walk-in looks
ASKS FOR TROUBLE
  • Fit-width framing — crops content, misaligns the stream
  • Hairline rules, 1-px strokes, dense small text — the upscale will soften them
  • Titles parked at the very top of a slide
  • 23.98/24 fps renders (stutter at 30 Hz playback)
  • Letterboxed or pillarboxed sources inside your 16:9 frame — bars inside bars
About that sharpness ceiling: scaled 1080p cannot look as crisp on this wall as native-resolution content, and fine detail is where it shows. For most show content the difference is academic. When it isn't (a hero logo moment, a detailed walk-in graphic), build that one piece at 2496 × 1344 using the pixel map, and it will render 1:1, every pixel yours.

The Canvas & the Stream

One canvas, two audiences — 2,496 × 1,344 px

For the curious (and the broadcast team): the wall is built at LED-native density (1 px = 2.604 mm). A full-height 16:9 window on a 13:7 canvas is 2389⅓ × 1344, centered — which is simultaneously where your fitted 1080p frame lands and what the stream crops. Only 53⅓ px per side of wall lives outside it.

OUTBOARD LED WALLS ×2 2496 × 1344 16:9 ZONE 2389⅓ × 1344 — your fitted 1080p frame = exactly what the stream crops mirrored — one file drives both walls 60 2376 — NATIVE-CONTENT SAFE 60 53⅓ 2389⅓ — 16:9 ZONE · FITTED 1080p · STREAM CROP 53⅓ TOTAL CANVAS: 2496 × 1344 px · 21′-3⅞″ × 11′-5¾″ STREAM PROGRAM: CENTER 16:9 CROP → 1920 × 1080 (your 1080p file, 1:1)
Both dimension chains: orange is the native-content safe area (60 / 2376 / 60, with 50 px top/bottom); red is the 16:9 zone (53⅓ / 2389⅓ / 53⅓) — the fitted 1080p frame and the stream crop, which are the same thing.

Canvas Coordinates

ZoneX StartX EndWidthY RangeContents
Total canvas0249624960 – 1344Native content fills completely
16:9 zone / stream crop53⅓2442⅔2389⅓0 – 1344Fitted 1080p frame · what the stream captures
Native-content safe602436237650 – 1294Text & logos in native 2496×1344 builds
For the stream / broadcast team: extract the center, full-height 16:9 region — in practice x 53 → 2443 (2390 px, nearest even) × 1344 high — and scale to 1920 × 1080 (80.4%). For fit-height 16:9 sources this returns the original file 1:1; for native content it's a clean 16:9 center-cut.

Pixel Map & Templates

For native 2496 × 1344 builds — the sharp way

Actual-Size Templates

Building native? The map is available as a full-resolution PNG (drop into your AE / Photoshop project as an underlay) or as an editable vector SVG, plus the isometric set overview.

  • Outboard LED Walls (SL + SR, mirrored) — 2496 × 1344  PNG · SVG
  • Set Overview (isometric)  PNG · SVG

⬇  Download all maps (PNG + SVG, .zip)

Outboard LED Walls — 2496 × 1344 (mirrored)

OFF the 16:9 FRAMEOFF the 16:9 FRAMENATIVE-CONTENT SAFE — 2376 × 1244 (60 px sides · 50 px top/bottom)2496 × 13441.0 px = 2.604 mm · ROE GP2.6 · Rec.709 · aspect 13:7RED = 16:9 ZONE (2389⅓ × 1344): fit-height 1920 × 1080 lands here — and the stream crops exactly thisOUTBOARD LED WALLS — SL + SR (MIRRORED)F5 PGS · SEPT 13–17 2026 · WESTIN SEATTLE · 13 W × 3.5 H TILES (TOP ROW HALF-HEIGHT)2496 px (21′-3⅞″)1344 px (11′-5¾″)
One file drives both walls. The grid marks physical panel seams (13 columns × 3.5 rows of 500 mm tiles — top row half-height); the red lines bound the 16:9 zone where fitted 1080p content lands and the stream crops; the cyan dashed box is the safe area for native builds.

PowerPoint / Slide Decks

Standard 16:9 — no custom sizes on this show

Build your decks at PowerPoint's default 16:9 widescreen size. They display fitted to the wall height with slim gaps at the sides, and the stream shows them exactly as you designed them. Nothing to configure — this section is mostly about the handful of habits that keep slides clean.

Slide sizeStandard 16:9 (13.333" × 7.5" — PowerPoint's default). No custom sizing needed.
Title-safeKeep text, logos, and charts roughly 0.28" (~40 px) inside every slide edge — PowerPoint's default layouts already do this.
File format.pptx or .key, clearly labeled (e.g. F5PGS_GeneralSession_v3.pptx)
FontsEmbed fonts in the file (File → Options → Save → Embed fonts), and send us any non-standard fonts separately to avoid substitution surprises.
Minimum text size18 pt absolute floor; 24 pt+ recommended — the wall enlarges your slide 124%, but your back row is 100 feet away and small text softens first.
Embedded mediaEmbed all videos/audio in the deck AND provide each media file separately. No linked/streaming media (YouTube, Stream, etc.) — the show network is offline.
Builds & transitionsSimple builds are fine. Avoid exit animations and "random" transitions.
Slide backgrounds: darker backgrounds look intentional — the slim side gaps vanish into the black surround and the wall reads as one seamless picture. A stark white slide will show its edges. Not a rule, just physics worth knowing when you pick a theme.

Full Motion Video

Everything rolls from PlayBack Pro — cued, operator-triggered

Video Export Settings (working spec)

Resolution1920 × 1080 (16:9) — fitted to wall height by us
Preferred codecApple ProRes 422 LT best for PlayBack Pro
Also acceptedProRes 422, DNxHR SQ; high-bitrate H.264 (20–30 Mbps) for non-critical pieces
Container.mov
Frame rate29.97 or 30 progressive — do NOT render 23.98/24 fps
ColorRec.709, video levels; 8- or 10-bit
PlaybackOperator-triggered, plays once — end on a clean frame or fade to black. Seamless loops: put _LOOP in the filename

Going native for a hero piece? Same specs at 2496 × 1344, text inside the 2376 × 1244 safe box — tag the file _Native2496.

Audio in Video

Preferred48 kHz · 24-bit · stereo, embedded
LevelsMix peaking around −6 dBFS; no limiter slam
Silent videosStrip the audio track entirely rather than including silence

Why ProRes instead of H.264?

ProRes decodes with almost no CPU effort — the machine reads it straight to the screen. H.264 needs real-time decompression that can drop frames exactly when it matters. Larger files are expected and fine. If your renderer can't export ProRes, talk to us before inventing an alternative.

Setting Up Your Edit

For the working 1080p spec, any standard HD preset at 29.97/30 fps is correct — nothing custom. Cutting a native 2496 × 1344 piece, use these:

Premiere ProFile → New → Sequence → Settings tab → Editing Mode Custom · Frame Size 2496 h × 1344 v · Timebase 30.00 or 29.97 fps · Square Pixels · Progressive  Adobe: create & change sequences
DaVinci ResolveProject Settings → Master Settings → Timeline Format → Timeline Resolution Custom 2496 × 1344 · Frame Rate 30 / 29.97. 2496 × 1344 fits inside the free version's UHD limit — no Studio license needed.  Blackmagic: Resolve manuals & support
Final Cut ProFile → New → Project → Use Custom settings → Format Custom · 2496 × 1344 · Rate 30p / 29.97p  Apple: create a project

Audio: Stingers, Cues & Music

What to send, and in what format

Cued Audio (stingers, walk-up music, VO, award hits)

Preferred.wav — 48 kHz · 24-bit · stereo
Also fine.mp3 320 kbps (fine for music; use WAV for anything with a hard downbeat)
TrimStart the file at the moment it should be heard — no leading silence; we fire cues on the frame
NamingOne file per cue, named for the moment: F5PGS_AwardSting_Partner_v1.wav
LevelsPeaks around −6 dBFS, consistent loudness across the set

Walk-In / Walk-Out & Break Music

For general ambient music, a Spotify playlist link is all we need — send it with your content delivery and note any tracks that must (or must not) play at specific times. If your organization requires licensed/cleared music only, send us the files instead as .wav or .mp3.

Two quick asks

  • Audio that belongs to a video should stay embedded in that video — separate "sync to picture" audio files are a rehearsal-day time sink.
  • Tell us the vibe and the no-fly list (explicit lyrics? competitor artists?) for anything we might need to fill on the fly.

Still Images & Event Logos

Technical specifications

Full-Screen Stills

Resolution1920 × 1080 (working spec) or native 2496 × 1344 for the sharpest wall
Format.png (preferred) or .tiff — no JPEG for show graphics
ColorsRGB / Rec.709, 8-bit+, no embedded printer profiles
Safe margin~40 px in a 1080p file · 60 px sides / 50 px top-bottom in a native file

Logos & Graphic Elements

Vector (preferred).svg, .ai, or .eps
Raster.png with transparency, 24-bit, largest size available
Brand kitSend your brand guide (colors, clear-space, don'ts) so anything we build on site stays on-brand
Why we push for vectors: a vectorized logo can be re-set at native wall resolution in minutes — it's the one-file answer to the sharpness ceiling. If we have to rebuild a graphic at 2 a.m. before doors, a vector file is the difference between "done in five minutes" and a phone call nobody wants. We never distribute client content outside this event.

File Naming, Versions & Delivery

Small habits, big time savings
Naming pattern F5PGS_[Content]_v[#].[ext]
e.g. F5PGS_WalkIn_v2.mov · F5PGS_GeneralSession_v1.pptx
Optional tags _Native2496 (built at 2496 × 1344) · _LOOP (seamless loop). Untagged files are assumed 1920 × 1080 / 16:9.
VersioningIncrement v1 → v2 → v3 with every change. Please never use "FINAL", "FINAL2", or "FINALfinal" — we've all been there, and it never ends well.
DeadlinesAll show content due Monday, Sept 7, 2026 (one week before load-in). Anything after that lands in the on-site change queue and is handled as time allows.
DeliveryWeTransfer to cbaldini@avfactory.com for day-to-day deliveries and revisions. For the final show package a hard drive hand-off is welcome (exFAT-formatted so it reads on everything; label the drive with the event name). No email attachments over 20 MB, please.

Frequently Asked Questions

You can always ask more — we like questions
Why does my content look slightly soft on the wall?
Your 1080p frame is enlarged 124% to fill the wall height — that's the working trade-off this show chose so existing 16:9 content works as-is. At audience distance it's rarely visible on video or photos; fine text and hairlines show it first. Anything that must be pixel-perfect can be built at native 2496 × 1344 — the pixel map has everything a designer needs.
What are the gaps at the sides of the wall?
The wall is 4% wider than 16:9, so a fitted frame leaves ≈5½ inches of unlit wall per side. Against the black surround they read as set, not as a mistake — especially with darker content. If the gaps bother you on a specific look, that's a candidate for a native build.
Can you just stretch it to fill the wall?
We can fit to width on request, but it crops 30 px off the top and bottom of your frame (goodbye, high-set titles), and the stream then loses side pixels as well. We never distort/stretch — that always looks wrong. Fit-height is the setting that keeps your frame whole in the room and hands the stream a pixel-perfect copy.
Why not 24 fps? It's cinematic!
The playback and switching system runs at 30 Hz. A 23.98/24 fps file forces a 3:2 pulldown at playback, which shows up as stutter on camera moves. Shoot however you like; render at 29.97 or 30.
Do both walls really show the same thing?
Yes — the walls mirror, driven by one file. There is no media server on this show, so independent left/right looks aren't available.
Can I submit other codecs or formats?
Quite possibly yes — but ask first (cbaldini@avfactory.com) so we can confirm smooth playback before you render a show's worth of finished animation.