I did it a couple of times with a Lucille 'cause it has a Stereo Output (one for Each Humbucker)
(I was basically tring to Double-Doubletrack in one take, L& R from eack KPA)
I don't remeber I had any issue with the DAW nor Rig Manager.. it works on Win 10
I have two USB controllers running in Windows with no problem. One for left hand and one for right hand. I even have a USB keyboard for center channel (both hands). 
I don't see why it won't work. Try it. But I don't think you can run two instances of Rig Manager at the same time.
Make sure they are not both named "My Profiler" on the two Kempers.
I use MK1 and MK2 same time with. same PC. Naming is essential. There is a menu item to choose the active Profiler in Rig Manager. No problems. Win 11.
When you “run two Kemper devices simultaneously”, do you mean just connected to the computer and Rig Manager or as interfaces for recording? If interfaces, you can do that on a Mac by creating what’s called an aggregate device. If just connecting them, they probably need different names, but I’m not certain on that last one.
Using rig manager, not using as interfaces. Easier to use when having different names.
i had the same problem - no idea to avoid this! I thought it´s a bug in the last RM - but may be it´s a feature?
i had the same problem - no idea to avoid this! I thought it´s a bug in the last RM - but may be it´s a feature?
For me, it's defenitly a flaw; there's no sensible use for this behavior, and it's not documented anywhere. The fact that the second "passive" device simply overwrites the active one is a no-go. Especially in the studio, when a second person wants to try something out on the stage device and I'm trying to reamping on the rack at the same time, it's been incredibly frustrating, as it took me quite a while to figure out what was happening.
Lucky me alone controlling the racked devices only with RM. I would never catch these anomalies.
For me, it's defenitly a flaw; there's no sensible use for this behavior, and it's not documented anywhere. The fact that the second "passive" device simply overwrites the active one is a no-go. Especially in the studio, when a second person wants to try something out on the stage device and I'm trying to reamping on the rack at the same time, it's been incredibly frustrating, as it took me quite a while to figure out what was happening.
It doesn’t seem logical to me either but I’m sure I remember Kemper saying in another thread that this is intended behaviour. I can’t remember the reason but it definitely isn’t a bug.
It doesn’t seem logical to me either but I’m sure I remember Kemper saying in another thread that this is intended behaviour. I can’t remember the reason but it definitely isn’t a bug.
I'll probably be branded a traitor after this post. But here's my opinion on the matter.
If Kemper says it's not a bug, do we just accept it ?
Well, then Kemper should explain and document what purpose this is supposed to serve. To me, it's a bug, and it increasingly seems that, especially with the Rig Manager, errors and shortcomings in the software's behavior and operation are declared "intentional" instead of being fixed.
I'm just reminded of the disaster with copying and editing performances; they simply imposed restrictions, for example, you can only orchestrate performances if the KPA is connected and in Performance Mode.
I'm reluctant to use the Kemper anymore; the device is outdated in terms of operation and usability. And its stability is nowhere near what it used to be.
To me, it looks like parts of the Rig Manager, especially the drivers and rig management, were programmed by people who haven't been with the company for a long time, and they're trying to program something without touching the "legacy code."
That's why it took so long to even develop an editor. They should have completely reprogrammed the Rig Manager when they introduced the editor.
Sometimes you have to cut ties with the past and look to the future, and in my opinion, Kemper isn't doing that.
Gui to midi enabled might explain something ? Nope. It goes somehow through RM and only changes the performance, not the slot. Using new betas 24.4.
