I've recent;y stumbled onto a fabulous new way to crash my Receptor: just send a series of patch change mesages in succession without giving it time to fully load the multi being called up. Sometimes, but not always, the Receptor will freeze and then must be rebooted before it will respond to anything. Once, I couldn't even shut it down and had to pull out the power cord to get it to reboot. I think this happens most often when the multi contains a sampler like Kontakt or Kompakt, and it has not finished loading the samples when I call up another multi.
There is an obvious work-around here: Just like the old joke about the guy who goes to the doctor and says "it hurts when I do this" and the doctor says "so, don't do that." So, don't send patch change messages while a multi is loading.
However, the reality is this: Bandleader calls a tune, I hit a patch on my controller. Maybe I accidentally hit the wrong patch. Or, maybe he changes his mind and calls out something else. Whatever, the drummer's already started the count. Don't have time to wait for the patch to load, or even to look and see if it is still loading. Gotta hit a new patch . . . Now, my Receptor is frozen. Miss the big dramatic keyboard entrance. Have to walk over to my rack and push the Receptor's button 2X and wait for it to reboot. Everybody is staring at me and they don't look happy.
Has anyone else encountered this? Are our good friends at Muse aware of it? Is it caused by the source VST and out of Muse's hands or is it something that could be fixed in an OS update?
K.
