Posts by Yoda Guitar

Quote from 6Stringbender

Do you mean create another different account for Rig Manager? Would it be better to delete rm and reinstall?

Thanks for your suggestion.

No, create a new MAC user account and reinstall RM to test if there is any interference from other software.

This is what my Kemper Brain AI says about the Greg Koch sound setup. You can try it out and see if it works for you.

How to dial in the Greg Koch "Gristle" Tone on Kemper

To get Greg’s signature snappy, dynamic tone, you need a high-headroom, clean amp foundation driven by a hot boost and a mandatory slapback delay. Greg controls almost all his gain via his guitar's volume knob.

1. The Amp Foundation (Profiles)

• Amp Type: Look for '65 Vibrolux, '65 Deluxe Reverb, or Tone King Imperial profiles.
• Gain: Pick a Clean or Edge-of-Breakup profile. It should be punchy and clear.
• Cab: Choose a 2x10" configuration if possible. It keeps the low-end tight for fast chicken-picking.

2. Stomp Section (Pre-Amp)

• Slot A (Green Scream / Tube Screamer):
  • Settings: Drive at 1.0 - 2.0 / Volume at 7.0 - 8.5.
  • Purpose: Pushes the front end and adds mid-range cut without heavy distortion.
• Slot B (Pure Boost):
  • Settings: Mild volume boost with a slight treble bump for extra "spank."
• Slot C (The Crucial Slapback Delay):
  • Settings: Time: 100ms - 140ms / Feedback: 0% (exactly one repeat) / Mix: 15% - 20%.
  • Purpose: Adds his signature 3D depth. Keep it on all the time.

3. Rig Menu Fine-Tuning

• Definition: Crank to 6.5 - 7.0 to mimic the bite of his active Fishman Gristle-Tone pickups.
• Pick: Set to +1.0 or +2.0 to accentuate the hard pick attack and finger snaps.

4. Effects Section (Post-Amp)

• Reverb Slot: Select Spring Reverb (medium mix, short decay) for that vintage surf/blues vibe.
• Mod Slot: Use a Harmonic Tremolo (slow rate, medium depth) to copy his signature Koch Amps "The Greg" vibrato.

Golden Rule: Set your guitar's volume to 10 for solos (singing overdrive), and roll it back to 6 or 7 for funky, crisp cleans.

I use Rig Manager on a very old Intel-based Mac and also on a Mac Mini M1, without any performance issues. Your Mac is significantly more powerful than what's needed for Rig Manager. I would check if your USB connection is working correctly.

Perhaps something is running in the background that's slowing down the app.

Try this: Create a new Mac user from scratch, log in with that user, and install Rig Manager there. This will allow you to quickly test whether it's a software or hardware problem.

Quote from ReneLangenhan

1. so far EVERY device of hardware I bought has a PDF or printed manual.

...You can use CTRL-F to find faster what you're looking for and if you are really too lazy to read a little more

2. This is the European Union, EVERY (Electronic) device has to have a manual by law.

You can continue wasting your time endlessly searching and reading manuals.

In the new world, you ask your AI:
"Send me a MIDI sequence to set up my Kemper to sound like the rhythm guitar in 'Hold the Line' by Toto."
Or you ask:
"Create a PDF document with all the information I need to set up reamping on my Kemper Stage MK2."
Or even:
"How do I change the system settings for Live IEM if I only have a mono return from the mixer but want to hear my guitar in stereo?"

All you need is a self-learning system like HERMES, the analysis of all documents in a Karpathy's Second Brain and a Graphify Knowledge Graph, and of course any LLM.

I've already scanned the manuals, the master manual and the MIDI manual. That took me half a day. And it's astonishing how surprisingly accurate the system's responses already are.

However, I'll run through the master manual again, this time focusing on a different aspect, to delve a little deeper. I'll also provide the AI with some additional sound examples with corresponding settings so it can learn how to interpret the Kemper parameters. In other words, you make a WAV or MP3 recording and instruct the AI to extract the MIDI data. It saves the MIDI settings and the WAV file, then performs a frequency analysis, and that's it.

IMHO best is using a midi guitar software like midi guitar 2 or 3.
Use a Oberheim 8 or Yamaha CS 80 was used on what a fool believes.

All I can say is: anyone still working with multilingual PDFs is completely out of touch. Nobody reads hundreds of pages these days without knowing if they'll find the answer they're looking for. These days, you work with AI-powered Second Brain or RAG architectures. You publish these on the company website (Quartz (v4), Docsify, Docmost, or Outline) and supplement them with a small LLM system. This can be a rented AI or, for example, a custom-developed LLM system, such as OLAMA. The documentation is then searchable online at any time. And the LLM can answer system-related questions directly, without having to wade through pages of useless information. Kemper, I would have had my source code checked by AI long ago, just to find the most glaring errors that have accumulated over the years.

I created a Second Brain from the existing Kemper documentation, which I can search directly using Obsidiano and the AI. I simply followed Andrej Karpathy's instructions. The entire process took no more than two hours; then the brain was ready to go.

Here's an example:

Quote from Wheresthedug

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.

Quote from JoePVblue

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.

I'm using a Rack MK1 and a Stage MK2, both connected via USB to the same Apple Mac (I've also tried it with a Windows PC (Windows 11)).

When I select one of the devices as active in RM and choose a profile or performance on the passive device button or selector wheel,
the active device loads the selection from the passive device.

This happens when both devices are in the same mode (e.g., Browse or Performance).
Does anyone have any suggestions on how to fix this behavior?

Is there anyone here who runs two Kemper devices simultaneously on one PC or Mac?

For studio or hobby purposes?

If so, how do you do it? Do you only plug one device into the PC at a time?
Running two devices simultaneously on a Mac is practically impossible.

Thx a lot

Unfortunately, the Kemper Stage MKII still has the problem of a loud popping sound when starting up.

The problem seems to be solved when shutting down, but there's still a loud popping sound when starting up, even in version 14.0.3.

Sorry, but this should be clearly audible during testing.

Is there any news on this Issue ?
I have this too Kemper Stage MK2 release 14.0.3 extrem loud pop on startup.

In my case it was the PSU (Aug-2025) and cost over all 180 EUR inc VAT without shipping.
So if you Send it for repair from outside Europe to Germany take care about customs process.

Inward Processing (Repair in Germany)

To ensure the sender (customer) and the repair center in Germany do not pay unnecessary duties, follow these steps:

1. Shipping to Germany (Import)

The sender in the USA, UK, or Switzerland must declare the shipment as a temporary export for repair.

• Commercial/Pro-forma Invoice: Must clearly state: "Goods for repair and return. To be placed under Inward Processing in Germany."
• Value: State the realistic value of the device (for insurance and customs calculation).
• HS Code: Use the correct tariff code for the device to avoid delays.

2. Customs Procedure in Germany

The German repair center or the courier (e.g., DHL, FedEx) must apply for Inward Processing.

• Authorization: For occasional repairs, a "Simplified Authorization" can be granted directly by the customs declaration (the act of declaring the goods for inward processing).
• Security (Kaution): Customs might require a security deposit (duty/tax amount) which is refunded once the device is exported back.

3. Return Shipping (Re-Export)

After repair, the device must be officially re-exported to prove it left the EU.

• Proof of Export: The repair center must provide an export declaration.
• INF 1 Form: For commercial cases, this form tracks the process and ensures duties are only paid (if at all) in the destination country based on the repair value.

Important Advice

• DDP vs. DAP: Clarify with the courier if they handle the "Inward Processing" declaration. Many couriers default to "Standard Import," which results in duties that are hard to get back.
• Switzerland & UK: Use the specific Trade and Cooperation Agreement (UK) or Free Trade Agreement (CH) to further simplify origin-based duty relief if applicable.

Wenn du live In Ear spielst wirst du never ever das Spielgefühl einer Röhre haben.
IMHO du must dich entscheiden was dir wichtiger ist Guter Sound für das Publikum oder flatternde Hosenbeine.
Jedem sollte klar sein das was du als AMP Sound hörst, wird auch nie das sein was im Mix landet.

Use the simplest 12 " wedge cab you can get and replace the speaker ...
e.g.

the box PA M 12 ECO MKII

the box PA M 12 ECO MKII, Passiver Monitor, 12" und 3" Hochtöner, 65Hz - 15kHz, 113 dB SPL Max, 8Ohm, 140/560W RMS/PEAK, 90 x 90°, 6,3mm Klinken/Speaker Twist…

www.thomann.de

📢 the box MA120 MKII

the box MA120 MKII, aktiver 2-Wege Monitor mit 12" Woofer und Hochtöner, 120W (RMS @ 4 Ohm), Grenzschalldruck: 120dB, 1 Line- und 1 Mikrofoneingang (beide…

www.thomann.de

Behringer F1220D Eurolive

Behringer F 1220 D Eurolive-Serie, Aktiver Monitor, 12" Basslautsprecher + 3" Tweeter, Leistung (max.): 250W, XLR In/Out, Abmessungen 238 x 500 x354, Gewicht…

www.thomann.de

Kann ich gut nachvollziehen, der Aha-Moment mit dem Röhrenamp ist real 😉

Meine 5 Cent dazu:

Ich glaube nicht, dass es primär an der Latenz liegt – die ist beim Kemper extrem gering. aber Constant Latency kann sich minimal anders anfühlen, ist aber einen Test wert.

Das „schnell-komprimierte“ Gefühl vom Röhrenamp kommt eher von Endstufensag und Transientenverhalten, nicht von klassischer Kompression. IMHO der Amp Compressor im Kemper ist da deutlich näher dran als ein Stomp-Compressor. Ich würde:

• Amp Compressor nur leicht (1–2)
• Pick Attack etwas runter
• Power Sagging moderat hochziehen

High-Output-Humbuckern auch wichtig:

• Clean Sense nicht zu hoch
• Distortion Sense evtl. leicht ins Minus

Bei DI oder Liquid Profiles:

• Definition eher etwas runter
• Clarity sparsam oder aus
  Zu viel davon killt genau dieses „klebt am Finger“-Gefühl.

Pure Cab ruhig mal leicht antesten (1–2), fühlt sich oft direkter und weniger harsch an.

Und Röhrenendstufe (Return vom Crate oder externe Poweramp) macht spielgefühlmäßig mehr aus als jede einzelne Einstellung im Kemper.

Highcut bei 4,8 kHz ist live okay, zum Testen aber ruhig mal höher (6–7 kHz) und stattdessen Presence zähmen.

Kurz: Weniger klassische Kompression, mehr Sag + Endstufenfeeling – dann kommt man deutlich näher an das Röhren-Spielgefühl ran.

Quote from DonPetersen

a short and concise feature request is IMO preferrable to overly long essays (possibly generated with an AI assistent).

The post is friendly and correctly worded.
These days, you practically need an AI agent to find the right wording;
even Kemper support does this when you call their hotline, for example.

The goal was to describe the behavior as precisely as possible so that other users could reproduce, understand, and track it.
I agree that some users generally prefer a short, concise feature request,
but a short post is also prone to misinterpretations and unnecessary follow-up questions.

Anyway the core problem remains:
Two profilers in browse mode cannot be used independently when connected to the Rig Manager.

Feature Request: Prevent Connected Profilers from Influencing Each Other in Rig Manager (Browse Mode)

I would like to propose a feature that addresses a significant workflow issue I recently discussed with Kemper Support.

Problem Description

When two Profilers (in my case a Stage and a Rack) are connected simultaneously via USB to Rig Manager and both units are in Browse Mode, any local Rig change on the inactive device is immediately pushed into the edit buffer of the active Profiler.

This happens when the Rig change is performed directly on the hardware (browse knob, footswitch, etc.).
As a result, both Profilers cannot be used independently while connected to Rig Manager.

Kemper Support confirmed that this is intended behavior.
According to their explanation, Rig Manager treats any connected but inactive Profiler as a kind of “library,” similar to an opened Rig Pack. Therefore, any Rig selected on the inactive unit is automatically fed into the editor of the active Profiler.

However:

1. this behavior is not documented anywhere,
2. it does not align with real-world usage of two hardware units,
3. and it creates significant workflow problems, especially in studio environments.

Why This Is a Problem

A connected Profiler is not a passive data source.
It is a fully functional hardware device that may be operated simultaneously by different people (engineer vs. musician, FOH vs. guitarist, etc.).

In my case, local Rig changes on the second device have repeatedly overwritten the edit buffer on the active one.
From a practical perspective, this does not feel like a feature — rather like a bug that is now being interpreted as intended behavior.

Feature Request:

Please add an option that allows users to:

Disable any influence from the inactive Profiler on the active Profiler when both are connected to Rig Manager.

A simple toggle such as:

• “Ignore local operations from other connected Profilers”

would completely resolve the issue.

Call for User Feedback

If anyone else is using two Profilers in Browse Mode connected to Rig Manager, please test this behavior and share your findings.

It would be extremely helpful to confirm whether other users experience the same limitations in their workflow.

Von Schaltnetzteilen sollte man die Finger lassen, wenn man keine Fachkenntnis hat. Sie arbeiten direkt mit 230 V, was bei unsachgemäßer Handhabung lebensgefährlich ist. Das betroffene Bauteil ist ein AC/DC-Wandler vom Typ TNY280GN-TL. Da das Gerät jedoch älter ist, ist es naheliegend, dass einige Elkos gealtert oder defekt sind und dadurch den Schaden ausgelöst haben. Sinnvoll wäre es, das gesamte Schaltnetzteil austauschen zu lassen.

Schaltnetzteile und Wechselrichter haben in der Regel eine Lebensdauer von unter zehn Jahren. Ursache sind vor allem die Elektrolytkondensatoren, die mit hohen Spannungen und Strömen mehrere tausend Male pro Sekunde geladen und entladen werden. Ein Austausch des Netzteils ist meist kostengünstig und schafft langfristig Ruhe.

Thanks for checking this. I’m also not using any MIDI at all. I only mentioned the MIDI channels because I wondered if MIDI-over-USB might somehow play a role and cause both Profilers to react when they are set to the same channel.

However, after testing and discussing this further, it seems that MIDI is not involved. The strange “ghost control” effect you see in my video appears even when no MIDI is used or connected. So it looks like the behavior is coming entirely from Rig Manager, not from any MIDI channel settings.

I’ll keep testing, but right now it seems that USB-MIDI has nothing to do with it.