All, I submitted a ticket for the following but thought it might be useful for others to know about this issue. I will update appropriately as things develop. I have seen this issue at least twice. I am currently on the Kemper 5.0x beta and the latest updated Rig Manager on a MacBook Pro using 10.7.5 software.
Here is a description of the problem:
I create performances and at least one slot of one performance changes randomly on the Kemper and I cannot correct it. Or it gets corrected and another changes.
Picture 1 shows a Performance and in Slot 4 on the Kemper it has replaced the M. Britt 65 AC30 profile with the default Crunch Profile. Picture 2 shows the same Performance, as created, and with Rig Manager currently connected to the Kemper. On the right you can see that Slot 4 should really be '65 Voice ACE30 B 2 7' and not Crunch. The pictures were taken after I tried choosing different performances and then going back using both the Kemper Remote and Rig Manager to see if that would fix the issue. It did not. I also tried re-assigning the correct profile to the slot of the performance in Rig Manager to no avail.
Picture 1:
[Blocked Image: http://i1368.photobucket.com/albums/ag198/flyingheelhook/image1_zpstjgutpws.jpg]
Picture 2:
[Blocked Image: http://i1368.photobucket.com/albums/ag198/flyingheelhook/image2_zpsf3fs3lsz.jpg]
I then attempted to shut both the Kemper and Rig Manager completely down. Waited a bit and then powered back up.
When I did, Slot 4 had corrected itself and was the correct profile. However, now Slot 3 was showing the same profile '65 Voice ACE30 B 2 7' that Slot 4 was supposed to be, instead of '65 Voice ACE30 B 1 5' as it was originally.
Picture 4:
[Blocked Image: http://i1368.photobucket.com/albums/ag198/flyingheelhook/image4_zpsxgpakdl0.jpg]
Picture 5:
[Blocked Image: http://i1368.photobucket.com/albums/ag198/flyingheelhook/image5_zpsnhsqvfgy.jpg]
Pictures 4 and 5 document this and you can see in Picture 5 that nothing has changed with the Performance - it shows exactly what the rigs are supposed to be. At that point, I did a backup, and have submitted a ticket. I will keep you posted.