Posts by Robrecht

    First thing to check, since you're using the Monitor out: the "Monitor Cab Off" option in the Output settings. It should be unselected, like in the picture:


    just a question, how do you guys cope with the latency, I remarked it takes a while to jump from performance to performance, and it's a little faster from slot to slot... is it something i can anticipate and it'll stay consistent?

    Sorry, I didn't see your question before. I'm not sure if the latency is consistent and predictable... I just keep changes in a song within the same performance, they're fast enough from slot to slot for me not to notice them. I basically have a separate performance for each song, so the switch between performances happens between songs.

    The Main Manual is essential reading as you get to know your Kemper better, but you did nothing wrong going by the Quick Start Guide initially, which should tell you all you need to know when you just want to start playing for the first time! Since you ordered a powered Kemper, it was only natural to assume that's what you'd received, and to link what you read about the Monitor/Speaker Output to the one output you saw on the unit...


    Anyway, I hope the store makes it right as soon as possible.

    Hey Burkhard , you're describing what I called the "footpedal button press" approach in my post above, essentially imitating a short on/off click of a momentary footswitch. You're right, it works fine and is a good option for many people!


    The reason for not resetting a CC to 0 until you switch to another slot is that it allows you to start playback anywhere in the song. MIDI chasing will trace that CC back, find out that it was set to 1-127 at the beginning of the section, and re-send that value to the Kemper, so that the Kemper switches to the appropriate Performance slot, even if you haven't passed the start of the section where the switch is programmed.


    So as long as you make sure no two of CCs 50-54 are set to 1-127 simultaneously, MIDI chasing can be quite useful!


    Of course, even with that method, it isn't necessary to send all five of those CCs for every slot switch: it's enough to only set the previous one to 0 and the new one to 1-127. Sending all five every time (four of them 0, one 1-127) is just a redundancy thing I do: when you're writing a song and moving things around, it's harder to keep track of what CC has been "activated" in the previous section and should be turned off next. Turning all of them off every time (except for the one you're turning on) helps to make sure there are no stray CCs accidentally left on.


    But again, you're right, in many cases a quick "button hit and release" is a better, and certainly more straightforward option!

    BUT HERE IS THE TRICK, which fixes the problem: Every time when I send a ControlChange that lets the Kemper switch to a slot I also send the ControlChanges for the other slots with value 0 - just a short time before.

    I do the exact same thing. I don't think it needs to happen before the actual switch -- I usually just send all five CC's (50-54) simultaneously, all zero except the one I want to switch to. But yes, definitely the right solution!


    (For anyone wondering: alternatively, you could always stick with the basic "footpedal button press" idea and just send the same CC twice in short succession, once with a non-zero value (to activate the slot) and then with value zero (to "take your foot off the pedal"). A short "click", as it were. But then you wouldn't get the benefit of MIDI chasing if you start the song in the middle of a section, since all of the CC's would then be zero most of the time. For that reason, it's best to keep the CC for the desired slot at non-zero for the whole duration of the section where that slot needs to be active (as if constantly keeping your foot on a button) -- as long as you remember to "clean up after yourself", i.e., make sure all of the CC's for the slots you don't want active are reset to zero.)

    "Boot from USB" is just a term.

    I suspect HankLinderman 's original idea was somewhat inspired by the concept of a "portable operating system", where you can have, say, an entire Linux distro on a USB stick, including all of your user settings and files. If you plug it into any computer, even if it's a Windows machine, you'll boot into your own personal environment, which has nothing to do with what is installed or stored on the computer. During the entire session, the operating system, installed apps, settings and user files are all read from and written to the USB stick directly, bypassing the computer's own storage: nothing is installed or overwritten on its hard drive. Unplug the USB and the computer will boot up normally again, totally unaffected.


    As a concept, I thought that was pretty cool, although I suppose it's probably not possible on the Kemper for technical reasons.


    Thank you for the optimization tips though, a special lightweight "concert image" is an excellent idea!

    I don't know how technically feasible it would be, but at least in theory this is a very good idea. Sure, you can take out your laptop on stage and copy some performances over, or wait ten minutes while you flash an entire backup from USB, but those are not fun things to do during a fifteen minute changeover between bands. And then there's the uncertainty of what version of KAOS the local Kemper will be running...


    If the boot image could include everything – profiles, performances, system settings and even the operating system – setting up would be as simple as just plugging one more thing in besides your guitar before turning the Kemper on.

    There's two kinds of latency at play here, no?


    The first one, let's call it "control latency", is the lag between the player's manipulation of the physical whammy bar and whatever the floor unit needs to do in response. I imagine this should be very close to zero, as it only requires a relatively "lean" control signal to be transferred and processed. Wiggle the bar and the floor unit should react virtually instantaneously, even if the connection were wireless, as there's no audio stream passing between the whammy bar and the floor unit.


    The second kind of latency, let's call it "audio pitch shifting latency", happens entirely within the floor unit and is inherent to any pitch shifting algorithm. You would theoretically notice it when picking notes while holding the whammy bar down, for example (like chu says, not something you would traditionally do a lot), or using the "virtual capo" feature.


    It's entirely possible this device has less pitch shifting latency than the Kemper, although I personally think the Kemper's is not bad at all. However, "zero lag" seems like marketing hyperbole when it comes to this kind of latency: real-time pitch shifting simply takes a non-zero amount of processing time. Like Monkey_Man said, the best you can hope for is "not-perceptible" (which is good enough, of course!).


    That said, I would be interested in this without the on-board audio processing in the floor unit, just as a (preferably wireless) control device. Make the floor unit simply output a MIDI cc or expression pedal voltage signal and leave the processing to the Kemper!


    The only challenge would then be that the Kemper expects a traditional expression pedal, which is unipolar, i.e.: it goes from zero in the heel position to 100 in the toe position. To use this as a whammy bar, which goes both up and down, you'd have to be able to define a middle position in the Kemper where the guitar signal is unaffected, which could take a bit of tweaking to make it correspond to the whammy bar's physical middle position. But it would be cool to use it for morphing!


    Edit: I guess the latter issue could be solved if the floor unit acted like two separate expression pedals, one for pressing the bar down and one for pulling it up. Connect it to the Kemper using two TRS cables and you can control two different effects, depending on the direction!

    I don't think that's possible. :/


    You can unlink the headphone out's volume so that it no longer responds to the master volume knob, allowing you to change the main out volume while leaving the headphones out as it is. But that setting doesn't affect the muting behavior of the tuner, and manually turning down the volume every time (and then quickly turning it back exactly to the original volume!) is a lot less convenient.


    Could be a feature request!

    For reference, here's the exact same clip from my first post, but with a notch EQ at 8.7 kHz (and at 17.4, although that one probably doesn't make much of a difference to most of us). If you go back and forth between both, the ringing is very obvious in the first one.


    pasted-from-clipboard.png  pasted-from-clipboard.png


    With this EQ, it sounds great and perfectly usable to me. Like I mentioned, I can use the Kemper's Studio Equalizer to do more or less the same thing, but then I'm using up an additional slot just to correct the Acoustic Sim.


    To be honest, apart from this ringing, I'm not having any issues with the Acoustic Sim (forgot to mention I'm using it with the amp section turned off). It's hyper sensitive, though, with a lot of high-frequency content that makes it sound alive, so I can imagine any single coil hum or electrical noise would be greatly amplified. I'm lucky to have a pretty electromagnetically quiet room, I guess: my Strat generally behaves very nicely.

    I've started to notice a high-pitched tone while using the Acoustic Simulator with a compressor in front. I've tried it with different guitars and different cables. It's especially noticeable with active humbuckers (Seymour Duncan Blackouts in two different guitars) at settings I would otherwise love to use for recording. I can clearly hear it with my Strat as well, but only when I turn up the compressor and the Sparkle parameter in the Acoustic Sim higher than I would normally do.


    Here's an audio example. It's already noticeable during the broken chords at the beginning, but it gets louder as I play more softly. When I mute a note, however, the ringing is also muted. Is this a tone that is already present in the output of my guitars, gets boosted by the compressor and somehow excites the Acoustic Simulator? Or some kind of artifact from the Bronze and Sparkle parameters?


    Compressor in slot A

    Acoustic Simulator in slot X

    Pickup 2.0

    Body <0.0>

    Bronze +2.5

    Sparkle +2.4



    I'm seeing two peaks, around 8.65 and 17.3 kHz. When I use the Studio Equalizer to attenuate precisely those two frequencies (max Q, gain at -18dB), the ringing virtually disappears. Anyone else getting this?


    Edit: On reflection, I suppose "hiss" isn't the right word, as it suggests diffuse, high-frequency white noise. Some of that is present, too, but it isn't as intrusive. The sound I'm referring to here is a focused, sustained, pitched tone.

    Sure, not disputing your choice, I'm just trying to figure out the reasoning behind the absence of a mix parameter.


    A mix parameter is commonly used to make an effect more subtle by combining it with the dry signal, so I assumed that is what you were after. But in this case, turning down the mix from 100% wet to 50% wet, the effect would become less subtle. I think that would confuse a lot of users, even though the result might be interesting.

    The manual says a mix parameter "would contradict the character of the effect". :/ I think this is because the Air Chorus achieves its subtle effect by modulating the pitch of both sides of the stereo signal independently, so that they are mutually detuned but only mix in the room, or "in the air between the speakers", as the manual puts it.


    The moment you would mix this effect with the dry signal, that subtlety would be lost. The detuned signal and the dry signal would be pushed through the same speaker, making the detuning effect much more pronounced, with audible "beating".

    In that video, it seems like Feedback is set to Max, so the delay buffer keeps repeating without decaying. Hence the suggestion by CelticGibson to activate "Infinity", which ups the feedback for as long as it is engaged. But you could also just turn the Feedback parameter to 100%.


    For the pitch shifting effect, however, you have to disable "To Tempo". "To Tempo" sets the delay time in note values, i.e.: it jumps between discrete multiples or divisions of the current tempo in BPM. For pitch shifting, you need to be able to adjust the time continuously in milliseconds.

    Quote from manual

    If “To Tempo” is not engaged, then Delay Time controls the absolute delay time in milliseconds. The maximum delay time is 2000 ms. As you dial through the delay times, you will notice the change in pitch, typical of tape-speed changes in a tape delay.

    I've just given it a try using the Single Delay algorithm (others should work too, for more complicated patterns). I don't know if it sounds exactly like the example in that video, but disabling "To Tempo" does make the delay pitch-shift like a traditional tape delay as you turn the Delay Time knob.

    Ok.

    So the job of the pitch shift in the mentioned rig (Steve Stevens) is to double the guitar (or let it sound "fatter")?

    I don't know about this specific rig, I haven't tried the new collection yet. But the Kemper has other tools for doubling/making "fatter" (like the new Double Tracker effect), so I would assume it's meant to add a harmony line, either a parallel octave or fifth, or thirds or sixths... Kind of like the classic rock thing where two guitarists play in harmonies.


    About the placement of the effect, musicmad summarized what I meant to say quite well: placed before the amp, the result sounds more like a two-string chord (a powerchord in the case of an added fifth) coming from a single guitar. It won't sound as defined and the two voices won't be as discernable as when the effect is placed after the amp.

    And usually you put a pitch shifter at the beginning of the signal chain?

    Usually, yes, because the signal at the beginning of the chain is cleaner, making it easier for the pitch shifter to detect its pitch. However, as far as I can tell, the Kemper always detects the pitch from the clean input signal, regardless of where in the chain the pitch shifter is placed. And if you want to create a "two guitars playing in harmony" effect, for instance, it's better to double the signal after it's been through the amp's overdrive, so it sounds like two independent guitars and amps, than to double up the notes and send them through the same amp together.

    And there was quite a big update. It read that they had a lot of improvements but sadly I actually had more troubles than before. Mainly with not being able to hear random others.

    That's strange. We've been on the latest official/stable update the whole time (7.3.0, which has been out for about two months) and we haven't had any problems like that.


    The reason it took a lot of experimenting in our case was mainly the complexity of my own setup (combining live input and prerecorded tracks in Ableton Live and then routing separate channels to their appropriate clients), and the fact that we wanted to run our own server and had to test different locations for it. Getting the others to install Jamulus, run the client and log onto a server was easy in comparison.


    We've had three full-blown rehearsals now, we've been able to work on new songs and everything, so we'll definitely go on this way. We're still looking forward to actually playing in the same room again, of course, but for now, Jamulus is already giving us something we've been missing a lot. Can't recommend it enough!

    Yes, if it's possible to find a compromise, staying in the same slot will give you a lot more possibilities for the delay!


    I don't know about the length of the spillover trail from one slot to another. Could be that it is limited, regardless of the feedback settings, to limit the processing overhead of adding it on top of an entire other slot.

    You could set up morphing on slot 1 so that ducking is enabled in the unmorphed state, and disabled in the morphed state.


    Then, shortly before switching to slot 2, press the button for slot 1 on the Remote. Pressing the button for a slot that is already active toggles between morphed and unmorphed. That way, you will effectively turn off ducking before switching to slot 2.


    I haven't tried this, but I would expect that the resulting spillover tail would not be ducking, since it was generated while ducking was disabled.


    * You can set the rise and fall time for morphing in the Rig menu. This is the time it takes to fade/switch from unmorphed to morphed and vice versa when using the slot button method. Best to set it short in this case, I think.

    * Try pressing the button for slot 1 (to disable ducking) right before you play the phrase that you want to hear in the spillover delay.