I've contacted support about this... but when I load my new soundbank file back into my REV2, all layer B data is scrambled when I look at edit buffer dumps of the programs from the loaded bank... when I look at the same program that was already in my REV2 (have not been dumped out via .syx), then they are all fine.
The reason could be a bug in the exporting of programs, so that the resulting file is damaged itself... it could also be that it's the versioning code that reads from the bank in memory, but I'm beginning to doubt this as my original bank in memory is not scrambled.
I have contacted support about this, but I wanted to make sure everyone is aware of this, becaue IF it is a bug that scrambles all on the way out via SysEx, then you could potentially destroy everything you've made, if you later load that bank back into your REV2 and overwrite your original programs.... luckily I did not do that with my new REV2 soundbank, so anyone who purchased it; DO NOT WORRY! I can create a working file as soon as Sequential has fixed this bug.
I've attached a picture of two instances of my editor showing you the edit buffer content... the top is the working program, the bottom show the same but layer B-destroyed version after .syx import ... yes it's scary!