I've been attempting to set up a performance over the last few hours and the experience has left me more than a little frustrated. Changes I make keep getting lost, the Rig Manager crashed a few times. The Kemper itself even HW-crashed once.
After viewing the tutorial on YouTube my workflow is as follows:
1. Make sure the Kemper is in "perform" mode or the "save performance" button won't show up.
2. Use the GUI to find the rig I want.
3. Edit -> Copy
4. Select the performance slot.
5. Edit -> Paste.
5. Save performance in #8.
6. Make adjustments to the newly added rig until I'm happy.
7. Save performance in #8.
My thoughts along the way goes something like this:
1. Why is this even a thing? Why does the mode of the Kemper affect how the Rig Manager acts?
2. Browsing works for the most time, but I am slightly worried what will happen to my last performance-slot. Does previewing a new one replace it?
3. This is known to me. Familiar ground.
4. Works as expected.
5. What happens if the rig isn't already stored in the Kemper, but in the local library instead?
6. Where exactly is my adjustments stored? Is it in the rig itself, or can I have multiple performance-settings per rig? Do I need to have multiple copies of a rig if I want to use it for multiple performances? Will me screwing up the settings also ruin the rig? Really wish the GUI would give me some pointers here.
7. After saving I usually select the previous performance slot and navigate back to see that my changes were actually saved. More often than not, they aren't. It's even worse if I use the midi-controller to switch between slots. Using the midi-controller to move to a previous slot and back again often seems to "time travel" a few steps back and multiple adjustments are lost. Sometimes using the Kemper directly to navigate back and forth will fix the issue, sometimes not.
The whole experience has caused the Rig Manager to lose my trust, and there is nothing more frustrating working with software you can't trust.
Now I expect a lot you will say: well... bring that screen-recorder, report them issues and live happily ever after. Well I would, except that this software has been out at almost seven years now. Stability issues this serious really shouldn't be a thing at this point. I also suspect that a lot of the problems stems from timing issues and keeping state between two devices in sync. A difficult task at the best of times.
I don't want to spend hours upon hours going back and forth with support.
That does mean however that I'm not ready to make an effort.
I want this software to be open-source!
Give the community an opportunity to give back.