Anamorphic 3.9/7.8 support
3.9/7.8 is a common pitch for transparent LED walls. A real pixel lands every 3.9mm across, but only every 7.8mm down, because the cabinet skips every other row of LEDs. The gaps let light through, which is the whole point of a transparent wall.
Side effect: a normal image stretches vertically on the wall, because each pixel covers 3.9mm across but 7.8mm down. HappyMaps handles the squish for you. You design on a normal canvas, the render pre-squishes, and the physical wall shows the right shape on load-in.
Where you'll see this
Transparent 3.9/7.8 walls turn up on scenic stages, theatre sets, retail storefronts, and anywhere you want LED content without blocking the view behind it. In the cabinet picker, look for:
- Vanish 3.9/7.8 (3.9mm horizontal, 7.8mm vertical)
- Vanish 7.8/3.9 (the rotated variant: 7.8mm horizontal, 3.9mm vertical)
Both are detected automatically. There's no "anamorphic mode" to switch on.
What the app shows
When you pick one of these cabinets, an amber notice appears under the panel picker:
- Input is the source dimensions for content, before the squish.
- Output is the LED grid the cabinet actually has, after the squish.
In the Render options there's an Anamorphic notice toggle. Turn it on and the exported PNG gets a small footer flagging that the map is pre-squished, so whoever picks it up on load-in knows what they're looking at.
Gotchas
The preview looks stretched
Correct. The signal plays back at the right shape on the physical wall. Trust the output, not the preview.
Slicing still works
Splits on a 3.9/7.8 object keep the squish on each slice. Nothing extra to configure. See Slicing and Advanced mode for how the flow works.
Native dimensions on the input side
On the canvas, a Pitch 3.9/7.8 screen is shown post-squished so its proportions read weirdly. When you export Resolume XML, the screen appears at native dimensions on the input side, twice as tall (or twice as wide, for the rotated variant) as the canvas view suggests. Resolume applies the squish itself during playback.
A 1920x1080 screen on the canvas becomes 1920x2160 on the input composition. The same logic applies to per-object input PNG exports: those use native dimensions too.
If the native footprint of one screen would overlap another screen's input slice, later screens shift down or right to make room. The composition size HappyMaps reports is the bounding box of every input slice after that shifting. Resolume Arena treats it as a hint and may keep its own. See Exports for the full export reference.