Hm, you store it via Rig Manager, there is probably a bug, I‘ll check. In the meantime, just store it with the Profiler‘s STORE key.
Posts by timo
-
-
Is that a bug or am I missing something?
This is a feature. Author for Profiles is the owner of the device on which the profiles were made. They get automatically set during profiling.
-
So I did, didn´t help. I made dozends of restarts of KPA, RM, PC.
I really do NOT like this disappointing situation. If someone wants me to betatest his software,
I expect at least a working system.
I will try to go back to last official, and will do more betatests.I need a working system.
Please contact support so we can investigate on that. It is okay to go to the latest stable release, this does not restrict the Investigation.
-
With the cable connected, when I bring up the latest version of Rig Manager, RM states that it needs to be upgraded. Also, it displays a messages in its status bar about not being able to find
You need to update Rig Manager to the current Beta. Do this by enabling „beta versions“ in the preferences dialog and then „check for updates“.
-
I'm afraid we've been terminated

Anyway I keep my KPA in OS 13 and RM 3 to benefit from these tweaks, No need to upgrade all

Or you just read what Burkhard wrote. 🤷♂️
-
Post
RE: OS14 / Profiling 2.0 Public Beta Discussion
MK1 units play back 2.0 PROFILEs in standard quality, independent of the firmware version. You could verify this via A/B tests.
The Cabinet Resonance that you found in these older software versions dates back from our first prototyping and research to create a faithful adjustable resonance. These parameters definitely sound attractive, but they do not belong to the cabinet and thus don’t match the PROFILE plus have technical limitations. For example: they impact the MONITOR OUT even while…
BurkhardMarch 7, 2026 at 4:31 PM -
Switching the type enables initial calibration. You can acchieve the same thing by pressing the Calibrate button.
I would try to swap the cable. -
Die Remote ist kompatibel mit MK1 und MK2.
-
Mine updated a couple of days ago, before the beta dropped. No additional update since then. Still on 1.9.36. Strange...
The Android version (1.9.36) came earlier, iOS (1.9.19) took longer since Apple needed a more few days than usual for App Review.
Note that those have different version numbers due technical reasons. -
You can’t use the ASIO driver whilst running Rig Manager. This is a known issue on the current beta, but will be fixed.
-
Have you switched Audio Mode to "Native"?
-
This is a known issue with the current public beta, it does not work sametime with a DAW using the Profiler as aufio interface. this will be fixed in a future version. Sorry for the inconvenience.
-
For the player: in the editor under the system page: „Set device name“.
On the Profiler in System Page 1, „Edit Owner“ -> „Device Name“
HTH -
The slots are adressed in program change 1 to 625. so Performance 3 Slot 2 is Bank Select MSB 0, LSB 0, PC 11 (2*5+1).
If the selected program flips over 128 you need to increase Bank Select LSB by 1.
It was designed that way to accommodate simpler MIDI foot controllers.
-
If you send more than one program change, it is possible that the mod controller is being processed before the rig switch. Since rig switches are "expensive", they might be deferred. Probably a delay to allow the Profiler to switch before setting this helps.
-
We haven‘t replicated that behavior yet. Also, the network code didn‘t change. Has anybody experienced this on Android devices?
-
You have to send a „multiple request“ for the base NRPN of each effect, so 8 requests, one for each „block“.
-
Tools -> Export Tags to CSV
HTH
-
The Profiler itself.
-
I switch off Kemper, turn it on. Often the delay is then on again. It happens also sometimes that is is initially off, but after switching between different rigs - it is on again. Without ever touching on of the effect switches.
Do you turn it off with the chickenhead/the standby function?