Posts by DamianGreda

Quote from musicmad

Crazy times. Already tripping over my Tonex One pedal. And this one has many more effects?

I agree . Crazy for 79P i will get one too just for fun.

This one is nice and small:

Valeton GP-5 Multi-FX, AMP & IR Loader Mini Pedal

Buy the Valeton GP-5 Multi-FX, AMP & IR Loader Mini Pedal from Andertons Music Co. today!

www.andertons.co.uk

KyleRodriguez I have just checked the AU plugin in Sonoma and it works without the issues. Could you please send me more info via PM ? Are you using mono , stereo track and so on. Maybe you could send me some empty project with plugin inserted on audio track that is crashing for you ? Thanks!

Quote from KyleRodriguez

Thanks everyone!

Not sure whether or not there are optimization issues with RigKeeper (looks like the latest build is a few years old), but left-clicking anywhere in the interface causes Core Audio to crash in Logic Pro 11.1.2 on MacOS Sonoma 14.7.2.

The core functions seems to be working well though so I'll take what I can get Might open up the JUCE project down the line and see if I can figure out what's crashing things.

APPRECIATE Y'ALL IMMENSELY!

Kyle

I will try to see if anything has changed. I don't use Apple hardware so it is a journey for me but I will try to find the problem.

Quote from yorkshireferret

I’m using the acoustic simulator and it sustains too long, not like on records when a strum fades quickly. What are good pre and post amp compression settings to get a good acoustic “feel” on tape, please?

Well it strongly depends on the instrument . My Furch acoustic guitar have very long sustain like a piano. But you could try to use compressor with short attack time and very slow release to try to simulate this. Or you could try to use very clean (end wide rfrequency response) amp profile like matchless without the cab and try to experiment with Pick parameter and compression parameter also.

zabukowski any news about the issue? Have you tried connecting two KPA at once? Maybe there is some bug when one driver is installed for one device after connecting second device. I don't have two KPA devices to test this.

Quote from RosboneMako

SHOULD I PROFILE AMPS AT A LOW TO MID LEVEL GAIN SETTING?

I warned you guys, Kemper better hurry up and make a VST or I will. Well I sort of did.

I had an idea:
1) If you do a frequency sweep of an amp at a very low level, you will get the full freq response of the amp. Pre EQ, Post EQ, and Cab/Mic/etc.
2) Now if you sweep again at a much higher input volume you will go into clipping on the tube. This nulls out the input EQ a bunch.
3) Work out the difference and you now have a guess at the input EQ of the amp. Which is the critical piece.

I now have 30 amps profiled in my VST using this technique. And I have to say, I am pretty amazed with what I got. I would have never guessed it would sound so good. Because I am dumb and there are a lot of places this could go wrong. Probably not very accurate, but sound really good.

But this got me thinking. If the Kemper is doing the same thing, the best results may come when the amp is profiled at a low to mid gain. You need to be able to lower the input signal enough to GET OUT of any tube clipping and then raise it again to get INTO the clipping area.

In my personal experience, profiling at a lower gain on the Kemper almost always sounded better. It will be curious to see if others get the same results.

Now I have made a profile of a few amps. My next step should be to reprofile them on the Kemper with some added VST tweaks because.... you know... why the hell not?

It is very impressive the Kemper can pull this off within itself. I had to use an external program to sweep. Then write code to get the differences. Then make an IR of that data. Generate MIN PHASE for it. Resave the IR for tweaking. Convert the IR into code. The nice part was the resulting IRs were very compact when done. So I have an option to run them as 128,256,512, or 1024 samples in the VST. And most importantly I had FULL control of everything manually. The Kemper has no outside control at all. You set it up and it pulls of some miracles into a totally unkown situation. Very cool!

Happy Profiling!

For giggles here are some pics of the input EQ results I got on my PodHD using a sweep delta of 40dB:

Display More

Congrats! You almost just discovered Wiener-Hammerstein Models https://www.hsu-hh.de/ant/wp-content…h_WH_models.pdf

Quote from zabukowski

One specific scenario that frequently occurs on my system is the use of two profilers (Stage and Player). Sometimes both are connected simultaneously, but most of the time, only one is connected. Out of curiosity, I also tried loading the ASIO driver on the Stage, but the same issue persists.

I wonder if this is the case. Maybe you have two driver instances (for both devices).Or two KPA devices cannot use the same ASIO driver.
What will happen if you connect both devices at once? Is there are more than one KPA driver to select in the Reaper? I guess we will find out next year

Happy New Year!

Quote from zabukowski

Everything is 64-bit. Besides the USB connection, only the main out is connected. A few minutes ago, I tried changing the USB port (I was using a hub), but unfortunately, the issue remains the same. Funny thing is, everything else (Kemper, Rig Manager) is working perfectly, with no issues whatsoever.

Strange issue. Another thing to try is to:

1. Run C:\Program Files\Kemper Amps\ASIO\ASIO Control Panel.exe (also try as admin ) and enter some numbers at input and output latecncy boxes like 1 or so.
2. Run Rig Manager installer as admin and reinstall it.
3. Run RM as admin and try to switch audio drver back and forth.

I'm running out of ideas for now

zabukowski so this leads to the coclusion that driver cannot be initialised. I can reproduce this if my KPA is turned off before i open the reaper. The inputs and outputs are empty.

Another thing to try is to use another USB port(avoiding USB hubs) and try to disconnect any other cables from the device like ethernet or MIDI.
By any chance are you running 32 bit version of the Windows or Reaper?

zabukowski You can try to use ProcessExplorer to check if some software is using ASIO driver. https://learn.microsoft.com/pl-pl/sysinter…rocess-explorer

1. Download it and run procexp64.exe

2. Click on Menu Find-> Find Handle or DLL and paste : KemperProfilerASIO.dll and click Search

As you casn see only reaper is using driver on my PC.

Quote from zabukowski

The ASIO driver is not loading on Windows 10 (Rig Manager 3.8.6, the latest official Kemper drivers, audio mode ASIO, Player LVL II/III, Reaper). All other ASIO drivers are functioning normally.

When this error is displayed? After openning the reaper or after opening some project in the reaper? Make sure that reaper is using 44100 sample rate as this driver only works with 44,1kHz sample rate.

zabukowski There are few tricks to make it running. 1. Go to sound devices in control pannel and make sure Kemper is not set as your default sound device. Use some other device as default.

In case of using XLR there are workaround solution like XLR adapters with ground lifts for example : https://www.gear4music.pl/pl/PA-DJ-and-o…t-XLR-02-m/4VOG
Or one may just cut PIN 1 wire in one XLR end

With Saw Slicer you can get some really interesting effects. Nice update!

Quote from Kim_Olesen

What people don’t realise is that the results wont be great. In order for a tuner to be a functioning utility, the display response time to what is being played needs to be much faster than what rig manager is currently capable of. As it is now the needle on the tuner will be more than a second behind, and you will find yourself frustratet by endlessly overshooting the target tuning.

Rig manager doesn’t seem to be coded with a fast response gui in mind.

Buy a tc polytune clip and forget about having a tuner in RM.

I don't agree with you . The delay is less than a second. Please try manipulate the KPA while the Rig Manager is open. I did the tuner in Toast ME and it was possible and had minimal delay.

Interesting experiment to promote hardware with free NAM based plugin. I wonder how it will go .

Transistor Legacy Virtual

Experience all of our Transistor Legacy preamplifier pedals in your DAW, with the help of neural nets and AI. Explore Our Pedals Have you ever wished you could…

ghostnoteaudio.uk

Quote from Ruefus

In my opinion, CK is an inventor first.

100% agree

Quote from Ruefus

This is the part that doesn’t make sense to me.

Is this suggesting Kemper has ‘fallen behind’ or something and is therefore doomed?

it is only my opinion but i see those products(Virus , now KPA) as a slaves of one processor and its programming language. And what was art to extract what could be achieved from that particular DSP is in my opinion also its limits and cage. But i understand and admire passion and proffesional knowledge behind this .

Quote from dfdfan

I was mostly joking on that one. I'm kind of torn because I would love to see if they find a way to make it happen, yet at the same time when I first started using kemper, I was almost hoping that they would stop adding features and updates because of how smoothly it ran at the time. Didn't even want rig manager. They more features/function they add the more complex the OS gets so I was scared that eventually it would start showing signs of slowdown and bloat. Then they released all those new (at the time) delays and reverbs and I had no choice but to give in to the growth. Being able to incorporate all I need into a single device has been life elevating for me.

No problem brother. I once shot through with a prediction. CK released liquid profiles. Did this have the expected business effect in response to the free solution that is NAM and AI technology? I don't think so. It is a cool feature and a flash and a new invention. But whether it is revolutionary enough to turn the market back from the path already taken - I doubt it. As for NAM and its implementation in the KPA, I believe it could be implemented to some extent for super light profiles. But this would require translating the libraries into the DSP56k assembler. Quite a challenge . I do not dare to say that it is impossible, because ckemper more than once surprised us.