I'm running into a workflow bottleneck when sending MVRs to grandMA3, and I'd love to see a workaround or fix for it in a future update.

The issue is how Capture translates high fixture numbers. In a standard MA3 showfile, it's pretty normal to patch infrastructure stuff (like floor hazers, relays, or work lights) into the 90,000+ range to keep them out of the main rig. For example, my hazers are usually numbered 93001, 93002, etc. MA3 handles these FIDs well.

Since Capture caps the Channel field at 65,535 (due to the 16-bit limit), I can't put my 90k numbers there. I can put them in Capture's Fixture ID field, which allows huge numbers. The problem happens during the MVR export: Capture automatically maps the 16-bit Channel field to the primary MVR  tag, and relegates the Capture Fixture to a secondary string.

When MA3 imports that MVR, it only looks at the official  tag. It completely ignores my 65k+ IDs. This breaks my patch every time I merge an updated MVR, forcing me to manually update numbers for those fixtures.

It would be awesome if you guys could consider one of two solutions:

1. Add a toggle for MVR Export mapping: Just a simple dropdown in the export window that lets us choose whether the Capture Channel OR the Capture Fixture gets written to the main MVR  tag.

2. Upgrade Channel IDs to 32-bit: Moving the Channel property away from a 16-bit limit would future-proof the software and let it natively match the numbering capabilities of modern desks like MA3.

Implementing either of these would save MA3 programmers a ton of tedious patch management.