Pixel Artworks Lighthouse – Immersive LED Room At London HQ

Why the immersive theatre used resin‑protected LED (and why that matters)

In Pixel Artworks’ own words, the immersive room was designed with curved corners to reduce breaks in perspective, and they chose a ~1.9 mm DRE Series option over SMD for contrast, colour reproduction, and durability for close‑range audiences.

A short excerpt from their project commentary captures the intent:

“We designed the LED room with curved corners… [and] opted for the 1.9mm DRE series… The resin coating also provides… durability.”

Our technical view (what this means in practice)

When people can stand very close to an LED surface, two things become obvious very quickly:

• Surface finish and contrast matter as much as headline resolution.

• Durability matters because “hands happen” in real spaces — even when it’s not intended to be touch‑interactive.

The DRE Series is one of our resin‑protected product families, which can be appropriate for close‑viewing environments where you want a robust front surface and strong perceived contrast.

Cabinet‑level resolution (example, not project‑specific): a typical ~1.9 mm DRE cabinet is 256 × 256 pixels per cabinet, which is why we always design content to the final cabinet map (cabinet pixels × cabinets across / high), not to “per m²” assumptions.

Interactive LED walls: what makes them feel seamless (and what breaks them)

The Lighthouse AI screen requires users to input prompts via a tablet, and the system uses that input to drive camera‑based visuals on the LED wall.

For interactive installs, we document the full signal chain (input → compute → processing → LED) before build, so responsiveness and stability are engineered in — not patched later.

The practical checklist we run through

• Input devices: What sensors/cameras/tablets are used, and where do they physically live?

• Compute: Where does the real‑time processing happen (local PC, server, or edge device), and what’s the redundancy plan?

• Latency budget: What level of delay is acceptable for the experience to feel responsive?

• Mapping & calibration: How will interactive content be authored and tested to the native LED pixel map?

• Operations: Who starts/stops the experience, updates content, and monitors issues day‑to‑day?

If you want to explore interactive options beyond this case study, see our page on interactive LED screen apps, sensors and software development.

Specification checklist for an immersive LED room (what to decide early)

This is the part that helps projects stay on track. Most delays come from missing decisions rather than technical limitations.

1) Viewing and content

• Closest viewing distance: how close can a person realistically stand to the LED surface?

• Content type: cinematic video, UI‑driven content, generative visuals, camera feed, or mixed?

• Camera capture (if used): will the LED be on camera, and if so, what are the capture requirements?

• Ambient light: daylight, controlled lighting, or mixed conditions?

2) Physical build

• Room geometry: flat corners vs curved corners (and how that affects content design).

• Joinery integration: If a display is integrated into joinery (like the “bar wall”), we agree maintenance access points and cabinet removal routes early, because access decisions affect both uptime and long-term running cost.

• Serviceability: front access vs rear access, and what “maintenance space” exists behind/around the LED.

3) Control system and signal flow

We regularly specify NovaStar and Brompton control ecosystems depending on the performance requirements and the wider workflow (e.g., broadcast‑style pipelines vs corporate signage‑style operation).

If you’re planning a multi‑screen venue, it’s worth deciding early:

• How many independent canvases you need

• What input formats you expect (HDMI, SDI, IP video, etc.)

• Who will operate the system (in‑house, agency, or technical team)

Installation and compliance: the unglamorous bits that protect the programme

Even in a “clean” corporate environment, installation usually involves access equipment, routing power and data, and verifying the wall structure.

• Working at height: any elevated installation work should follow the UK’s Work at Height requirements and HSE guidance. 

• Electrical: your supply and distribution should be designed and installed in line with UK wiring regulations (BS 7671). 

• Ingress Protection (IP) ratings: if an LED surface is exposed to dust, moisture, cleaning regimes, or public touch, the enclosure protection should be assessed against IEC 60529 (IP ratings). 

Common pitfalls we see (and how to avoid them)

• Content arrives late or in the wrong format. Fix this by confirming the native pixel map early, then building content templates to that map.

• Joinery blocks service access. A beautiful finish is still a problem if a cabinet can’t be removed safely for maintenance.

• Interactive systems are “bolted on”. Define your input/compute/processing chain upfront so the experience feels responsive and remains stable.

• No operational owner. Assign a named person/team responsible for day‑to‑day operation, updates, and fault reporting.

• Under‑planned power and data routes. Confirm cable paths, containment, and termination locations before joinery and finishes are locked.

From the field (Daniel Reynolds)

Most immersive LED projects don’t fail because the technology is “too advanced”. They stall because one practical detail is missing — usually service access, content mapping, or a clear plan for who owns the system after handover.

When we scope an immersive room, I always ask two questions early: “How close will people stand to it?” and “Who is responsible for content updates in six months’ time?” Those answers shape the product choice, processing approach, and how we design the system to stay reliable in the real world.