I had the same thing happen that the keys stayed on. Found it was a corrupt registration bank that had a voice in that had become corrupt. Deleted that Reg and all has been OK ever since.
I hope this issue gets clarified. I will rely on my future Genos for live performances. Never heard of such a thing or experienced anything remotely close to a registration file becoming corrupted and the arranger freezes up.
I hope the issue is referring to a registration bank being transferred from another arranger model, like the Tyros. All my registration banks from my Tyros 5 are going to be transferred to my Genos and reworked to suit. I can understand that there might be a slight possibility that a conflict might occur or a compatibility issue could happen when the Genos reads the registration, but for keys and notes freezing is completely unacceptable.
So is the issue, incompatibility with something within the Tyros registration or the actual registration bank got corrupt in the transfer process. If an incompatibility issue, Yamaha needs to correct and update the Genos firmware, where instead of just freezing on the user, at least a warning or pop up window notifies the user of the problem (warning that a certain voice doesn't exist) instead of just freezing.
Sometimes when I transfer folders and files from a USB stick to my Tyros, a warning pop up tell me if perhaps you might have too many files within certain folders to allow the transfer as a protection. This same protection must exist for these so- called registration transfer problems. An arranger should not just freeze up.
It would be inconceivable to me that if the registration was created on the Genos first, it could in anyway possibly corrupt. Since this occurred on both your Genoses, Yamaha needs to look into this and correct it. Obviously Yamaha knows most Genos users are going to transfer previously created registrations and files.
If anyone still saved a copy the actual corrupt registration bank file, please contact Yamaha and sent it to them for examination and hopefully a correction in an updated firmware updated. Thanks for informing us of this issue.
Regards, Marcus