Unfortunately this was a bug that seems to have crept in to MixEmergency during the transition of some of my development tools. It'll be fixed for the next version, but until then, the only work-around is to record using an older version of MixEmergency. Apologies for the inconvenience - it was a frustrating bug to find.