I also have this bug. When I update the rig Name or the comment most of the time is not saved properly. Rig manager "randomly" shows the new and the old one. I have to re-do it 5/6 time before it is correctly saved
Posts by AleFretMaster
-
-
RM 4.1.17 "1727"
-
I am sorry but I have to disagree. Shall we in future expect downgrades only because not many people use a certain feature?
By the way as specified in other threads is not the ASIO driver, but also something related to the generic driver. Some program like Guitar Pro are no longer working correctly with OS14, but works normally with the OS 13. This has also been confirmed when I contacted the support.
-
With my player this happens when the midi device connected is not reading the "active sensing". Practically the Player constantly send an "heart beat" signal that needs to be read, or what described happens. I think this is a common practice and allows to verify the connection between the two devices
-
Ciao gianluca72, per postare in italiano c'é una sezione apposta
Devi prima importarli in una cartella di rig manager. Poi salvarli sul Player.
-
G String I think Radek01 meant what you wrote. That at least you have been transparent about this topic, and it has been communicated.
From my point of view we can also close the thread. As I posted before:
So said.. I know that sooner or later they will patch it, and the only thing I can do is to wait for it (or revert to the previous revision and renounce to 2.0 profiles). But I think is correct to let them know that this cause frustration and a customer can feel disappointed.
-
Yes I am actually running the latest version. On my machine I am running Windows 11, maybe this explains the differences
-
Hi Radek01, thank you for your answer and your tip, I really appreciate it.
Since latest OS (Beta AND release) I receive this error with every audio settings: "Error - Audio device is not available"
(Screenshot above is from Guitar Pro, but the behavior is same as Cubase)
While if I connect the Player after Guitar pro opens, as soon as I press on play the program crash. And unfortunately, I get exactly the same behavior with or without Rig Manager running. What improved a little bit in the released version is Bluetooth, before the Player was always crashing, now it seems more stable.
During the Beta release I did some back and forth between the old OS and the beta, and with the old OS everything was working properly every time. Therefore I think I can exclude that is my cable, the usb, the pc, or whatever.
Furthermore, I contacted Kemper support during the beta and after the release, and..
"... The current version of the driver does not allow using the Profiler as an audio interface while Rig Manager is running at the same time...
...If you need the Profiler in a professional scenario please reinstall the release version since beta versions should only be used for testing purposes."almost one month after official OS release the problem still persist. This is why I feel disappointed.
So said.. I know that sooner or later they will patch it, and the only thing I can do is to wait for it (or revert to the previous revision and renounce to 2.0 profiles). But I think is correct to let them know that this cause frustration and a customer can feel disappointed.
-
Even if you look at the colour.. the player has always been the new dark/black-grey colour, and not the "old" Kemper green. As all the MK2 line 😁
-
Am I the only one disappointed with the new update? I'm not talking about the 2.0 profiles and resonance controls, those are honestly amazing, but about the "overall update" itself.
I am sad to open this thread, but I have been waiting for almost one year while reading comments like "Kemper, take your time and do things right", "we know that when it's out, it will be good", etc. Now, three weeks after the Official Release, I still can't record or use Guitar Pro (part of my daily practice routine) because of ASIO and Generic Driver issues.
I feel this is unprofessional and I think is a bit disrespectful toward people who use the device for professional purposes. Up to now, I feel this has been a downgrade instead of an upgrade.
Furthermore, I’m really frustrated with always having to wait for features that should already work. For example I'll never forget when I bought the Player at release because the manual described the combo buttons, and I was honestly shocked when I later discovered they still weren’t implemented, and that I had to wait eight months for them.
I am sorry, but I had to take out this frustration.
-
Wouldn't be more or less as the possibility to import an IR? Kemper ist profiling the cab, but still is open to import a general IR.
So said, I don't think NAM compatibility would be really nevessary.. in a while we'll have tons of 2.0 profile to chose from
-
Wait.. am I wrong or all this is actually not true? NAM profiles are open source, and do not belong to any specific "company".
-
They talked about improvements for iIR import (to get them with the resonance control if I am not wrong).
But before I would definitely appreciate the fix of the ASIO and Generic driver that are still not working properly in the latest release.
-
By the way, something that I wanted to ask is: are the new resonance parameters intentionally shifted down in rig manager, or it is a bug?
-
The Duncan Tone Stack Calculator on the web can do that really well already. Find a schematic of the Amp and insert the component values in the Calculator shows real time graph of the effect of moving the tone controls. For example it is incredible just how “scooped” the Fender blackface amps really are with all controls at 5.
Correct, and I love that tool. But I assume that a lot of people would have no idea hot to find the tone stack portion of the amp schematic circuit, find the resistor and capacitor values and interpret the output graph.
And even with the Duncan calculator is difficult to remember the complete behaviour of the tone stack.
I think is a lot more beneficial a short description of the various stack behaviour as part of the manual. I never found them documented anywhere.
-
Or maybe really just a description of how every "EQ amp type" is working. I suppose many many people never had direct experience with most of those amplifiers.
To get some knowledge about how they are working would help us to select them based on what we want to achieve and to use them efficiently, instead of only looking for the original of the profiled amp.
-
Try with the "pure cabinet" parameter in the cabinet module. It helped me with some Marshall rigs where I had the same issue
and the BrightCap Int. if is a Liquid profile
-
I think the issue is that some values are "discretised" and not continuous. I remember when I programmed my midi external controller (an Arduino with touch screen) I investigated this. I wanted a button that set me the high cut to 5kHz.
It doesn't metter how much precise did you send the command, after a certain point the Kemper High cut value was just jumping from something slightly smaller than my goal (e.g. 499x.x) to something slightly bigger than it (500x.x). Is like the value in between was not existing.
-
Try with the "pure cabinet" parameter in the cabinet module. It helped me with some Marshall rigs where I had the same issue
-
Yesterday I bought your Recording Essentials 2.0 pack and.. WOW. I should have trust you way before! 🤪
Amazing profiles! Also the rigs tweaked in the sweet spot are amazing and really well described with the name. This plus the well filled tags makes easy to find what are you looking for. That folder is really like a demonstration of the Kemper potential. I would like to be able to tweak the profiles as you are, in order to make good use of the folder with neutral settings.
The only things I fill are missing are some high gain profile with tighter bottom, maybe more mids, and a 2x12 cab*.
Do you already know if something like this is planed for the live package?
I am really looking forward for it!
*EDIT: Or maybe the world does not need anymore 2x12 cab, we just have experiment with the new Resonance Frequency and Intensity
