The range on that parameter was changed in between 2.9 and 3.x
It went from being a range of 1% to 100% to being the "User Range" of 10 - 50. The software is incorrectly reading the values of your cues/etc from 2.9 and giving the "wrong" values back as it maps some DMX value back to a User value.
The workaround for this is to enable "Preserve Native" in patch on those channels prior to merging. In my quick test, that seems to give the "right" values after merging.
The range on that parameter was changed in between 2.9 and 3.x
It went from being a range of 1% to 100% to being the "User Range" of 10 - 50. The software is incorrectly reading the values of your cues/etc from 2.9 and giving the "wrong" values back as it maps some DMX value back to a User value.
The workaround for this is to enable "Preserve Native" in patch on those channels prior to merging. In my quick test, that seems to give the "right" values after merging.
Yes! I knew I was missing something obvious.
www.etcconnect.com