MM6 export missing Fixture-Line-16 (15 fixtures vs 16 in MM5)

[JoshuaBatty]

What's happening

When we parse SJ02-JOSH_COHEN-MM5-01.mad we get 16 fixtures (Fixture-Line-1 through Fixture-Line-16), but when we parse SJ02-JOSH_COHEN-MM6-01.mad we only get 15 fixtures — Fixture-Line-16 is completely absent from the file.

These two files should be the same project, just saved in MadMapper 5 vs MadMapper 6 format.

The details

MM5 file (correct — 16 fixtures)

• Fixtures: Fixture-Line-1 through Fixture-Line-16
• Universes: 0, 1, 4, 7, 10, 13, 16, 19, 22, 25, 28, 31, 34, 37, 40, 43
• Total pixels: 6,400 (400 per fixture)

MM6 file (missing one — 15 fixtures)

• Fixtures: Fixture-Line-1 through Fixture-Line-15 only
• Universes: 0, 3, 6, 9, 12, 15, 18, 21, 24, 27, 30, 33, 36, 39, 42
• Total pixels: 6,000 (400 per fixture)
• File is ~1.2 KB smaller than MM5 — roughly the size of one fixture's data

The universe numbering is also different between the two files (MM5 has irregular spacing, MM6 has clean 3-apart spacing), which suggests the project may have been modified between saves rather than just re-exported.

What to check in MadMapper

1. Open the MM6 project in MadMapper 6
2. Check if Fixture-Line-16 is present in the fixture list
3. If it's there, it might not be getting saved properly — try re-saving
4. If it's missing, the project was likely modified after the MM5 save and the fixture was removed or renamed
5. Also worth checking: is Fixture-Line-16 maybe inside a Fixture Group that doesn't export its children the same way?

Why this matters

Our software reads these .mad files to automatically set up the LED layout and DMX addressing. If a fixture is missing from the file, that strip of 400 LEDs won't get any signal.

Not a parser bug

We've confirmed by searching the raw binary data that Fixture-Line-16's data (name, universe, pixel mapping, etc.) simply doesn't exist anywhere in the MM6 file. Our parser correctly extracts everything that's there.

[JoshuaBatty]

Update

The position issue is resolved — MM6 stores fixture positions under the position key instead of positionUv (which MM6 fills with a default 0.5, 0.5). The parser now handles both formats correctly.

The missing Fixture-Line-16 in the MM6 file is still real — the fixture data genuinely isn't in the binary. This is likely a project-level difference between the two saves rather than a format issue. Still worth checking with Jobe if Fixture-Line-16 should be present.