Posts by Grooguit

    Just a thought but have you checked the input settings. These are independent between Browser and Performance mode. Even if they are locked the two modes could be different. If your Noise gate or clean sens settings are different it might account for different triggering.

    good suggestion. I’ll double check that, however I did play around with the noise gate a bunch from totally off, to most of the way up and couldn’t get it to work. I should see about clean sens, but that’s set about where it ought to be.

    There's also a glitch in 7.5 performance mode that renames your slots. Using the performance mode, I was in performance 5. In performance 5, I had selected the rig with Browse "living hope" saved the performance and even left that performance and returned and it still showed "living hope" in the slot and on the remote. But when I went to a different performance and decided to move that performance to another location (not even the one where my "living hope" rig resided, but further away) when I returned to permanence 5, the slots were not just renamed but actually replaced to rigs that had previously resided there, weeks ago, before I placed the "living hope" rig in its place. I know 100% the issue isn't me forgetting to hit save before leaving the performance. Sometimes it won't rename the slot to the rig name when I browse for a new rig. Sometimes it will. Since all of my "rigs" have been renamed to song titles, but were created by first going to go a few "template" rigs I use on a regular basis in browse mode, editing and Save-As-ing them with the song title, I don't know what is goin on.


    What is frustrating is that I have been experiencing similar glitchy behavior in the most currently available OS release, not just this beta

    The Auto Swell doesn't really work (in performance mode). (I'm using todays latest beta release) I've used auto swell effects a lot, and even got a setting on one of the kemper's delays for years that does a pretty good autoswell, so I'm familiar with the innate limitations of this type of effect.

    In any case, sometimes it swells notes, sometimes it doesn't. And yes, I'm aware that the gate doesn't close and allow a new swell, unless I first mute my strings before hitting the next note or chord. Even waiting in complete silence for minute while I type this and the first note I strike isn't swelled. If I keep playing it kicks in for a few seconds and then stops functioning again. I tried picking harder, softer, single notes, chords, plucked chords, etc. Nothing seems to be more or less effective.


    For several years, I had created presets for producing a very effective autoswell in the kemper by playing with the swell control and setting the mix at 100% in one of the delay models, always worked, never an issue. After one of the updates in the past year or so, I noticed a similar glitchiness to these rigs in the autoswell I had created with the delay type, in that the autoswell wasn't reliable anymore, but not as bad as what I'm getting with this new autoswell effect. I tried placing it in the D and X slots and with and without the normal compressor I use active in the A slot. The profile I'm using is the same one I used with my "historic" swell rigs and is at a relatively low gain setting. I also tried playing with the input noise gate settings just in case something was up there. I'm also trying this effect out without using Rig Manager. I also have only 100 profiles in my KPA.


    *Edit: I tried it in browse mode and it seemed to work reliably and effectively, even in the same exact rig that I couldn't get to work in performance mode. Thus the issue is something with performance mode. ( I've also had an issue using 7.3 where it moves profiles around in performance mode, after powering off, and yes I saved the rig/performance before changing performances and shutting the unit down) Finally I went back to peformance mode after my success in browser mode, and dialing in the autoswell effect in the exact same rig I did before and this time it worked a bit better, though still not as reliably as I could get in Browse mode.

    The helix drives are great. However development of drives has already been floated as in the future for the KPA. I you’re already using the KpA without external overdrives, you might just want to wait it out. Though if I had to guess, it would be a full year before a release with drives would be available, given that it’s typically taken six months for even betas to be released of the demoed new features at Namm.

    To me adding such an additional pedal has its pluses and minuses. An extra power supply and patch cables. Increased latency. An additional potential for noise. More set up time. More programing in the KpA if you want it to trigger midi patches in the external unit. On the positive side, you have more options and the drive independence to where you can adjust your external drives on the fly without thinking about your Kempers organization of rigs.


    Since there’s an endless number of profiles of every sort of amp, cab at various settings and with various drive pedals baked in, it all comes down to whether it makes more sense to get a variety of gain stages using different profiles and the current limit of internal drive and boost options vs picking a cleanish go to profile and hitting it with a variety of drive pedals, or something like the helix.

    Keep in mind the huge audio gap between presets in all the helix products and be sure that you’ll be content organizing using their snap shot feature, as you can’t musically switch presets in the middle of a song. I personally hated this limitation of the helix. Yes, I loved the ability to create mammoth presets with loads of options. The issue was that I always have a handful of go to sounds I want instant access to. These are best organized by having them on their own preset, vs copying and pasting each of the components that I used for a go to sound into each and every new preset I create. This requires going back and and forth copying/pasting/saving multiple times. repeat for each new preset I want to have access to that go to sound. Would be much easier to simply change presets, but you can’t mid song because of the audio gap. Also keep in mind that you can’t as conveniently change midi patches on the Kemper as you can toggle on and off internal effects. You can send a midi message to the helix in a change of rig, but you can’t send messages with a toggle switch, though you can open and close the effects loop.

    I'm in the process of looking for a new audio interface and the majority do not have spdif ins and outs. I heard somewhere that you can get an adaptor to connect the spdifs to an adat optical ins and outs. I've looked into it a bit, and couldn't find a straight answer on whether this works. Has anyone here used the kemper spdifs with adat optical ins and outs? And if so, any concerns or glitchiness, or disadvantage beyond needing extra adaptors? I already own two pricey spdif cables.

    If I remember correctly from last year, the kone algorithm will work ok with a frfr speaker. If I understand correctly, the kpa cab/speaker is relatively flat, but of course idealized to pair well with the kone settings. Maybe this gives the ability to get a more amp in the room sound when using an frfr?

    If the kone speaker and software mimic specific speakers, it doesn’t act as a frfr, where you would send the cabinet sim to the frfr as you would direct to FOH? You would still have to treat it as a regular guitar cab and turn the cab sim off going to the kone and use the kone software to to mimic the speaker you use as the cab sim in the rig that goes to FOH? Or am I missing someth

    I'm thinking that however they lay it out, you'll continue to be able to send the cab portion of a profile or cab IR to any output, but with the additional ability to send a Kone filtered signal to any output as well. And I'd imagine that you'd be able to change the cab and what Kone per Rig. So that, for example, you send a regular studio profile with cab actived to the FOH using the main outputs, while sending the Kone affected signal (minus the cab sound going to the just the mains) through the monitor or speaker output, where you plug your kone cabinet.

    When I first heard the marketing about the KPA 7 years ago or so, I was skeptical because I assumed it would probably profile a 2-dimensional, digitally harsh, and less responsive version of the amp/cab it was capturing. Or some some sort of "something's not right" when you try to put it in the mix. The difference is, at least to my ears and virtually everyone here, is that the KPA has lived up to the hype. It's just as dimensional, no harshness, and just as responsive to the original, with all the benefits of a digital solution.

    To that end, I don't see how anyone could improve the core sound of the original KPA. How do you improve on virtually indistinguishable? Whatever the process of this new product uses to "capture the sound" the relevant question is not how much processing power is included or utilized in the capture, but if it actually sounds, feels, responds, sits in the mix, like the original and/or a real amp and cab does.

    At the same time, should this product function similar to the Helix, regardless of accuracy of the "profiles" I want no part. Organizing sounds for live use on the Helix is an endless mess because of the lack of spillover and even a large audible gap between presets. The fact that you can do so much within a single preset means nothing. If I have a couple specialty combos of effects/amps saved to a preset, say a ideal autoswell for ambient stuff, I can't just plop that preset next to a song specific preset and toggle between them in the song, because of the gap. I have to make sure I have enough left over DSP in the song specific preset and copy and paste all of my individual effects from the autoswell preset into the song specific preset, and then set up a "snapshot" to use it. Nor do I want to go back to volume matching hell between presets, when I decide to increase or decrease the gain in the amp section of one rig. The KPA is still the only digital unit that solves this problem as well.

    There is a swell preset in one of new delays as a good starting point, I'm pretty sure it has swell in the name. But if starting from scratch, I believe the mix of the delay has to be all the way up, and just because the parameter says 100% keep turning it up to the right as some of those keep going up till is says 100/100 or something like that to where you are not hearing the original signal at all, put only the repeats. The swell effect is applied to the repeats only, thus you want the mix up to the point where you are only hearing the repeats, and zero of the original signal. In this case if the delay time is set too long you will notice a long delay between when you strum the strings and you hear the swelled sound begin. If so, shorten the delay time to taste and lengthen the repeats.

    And just a pointer to make any autoswell from any company sound convincing and like using a volume pedal. If you let notes or chords sustain on your guitar and don't lift up slightly or mute before hitting the next note or chord, the next note or chord may not be swelled in, because the volume of the incoming signal hasn't dropped enough to cross the threshold and the autoswell just keeps the gate open allowing your percussive attack come through. If you stop the sound coming from your guitar itself between notes and chords, this of course could lead to audible gaps between those notes and chords depending on the settings of your swell effect. But this is why it's best to place a swell effect BEFORE dedicated delay and/or reverb effects. This way, the swell effect handles the swell, and the delay/reverb effect continues to ring out even though you've muted the sound with your hands for half a second.

    You can also set it to be instantaneous and have it toggle with the bottom row of buttons on the remote. This way you could, for example back off gain a certain amount while increasing delay. And go back and forth instantly between those two settings. Quite often I find this useful where I don’t need a certain effect to turn completely on and off in a song, but perhaps more or less subtle from one section to another. Rather than having a second almost duplicate rig with one setting different than the original.

    lol. What a cluster* that was! It took years and never worked.

    TC Electronic really drove off a cliff. when the G-system came out it was cutting edge and FINALLY was a product that allowed you to set your real overdrives up the way you like them in four loops, control your amp with a 5th, and use them independently within an-all in one high end digital effects system without tap-dancing. And high end effects from a company that was at the time considered top shelf in the post effects department. And the thing was serious tour grade, not a 2000's line6/boss multi-effects modeling toy. Then when all the ambient/shimmering delay/reverb stuff started coming out, (and is now made by everyone) and TC is still partying like it's 2005. They still sell that silly Nova System which has a huge audio gap when you change presets with the built in overdrive and which doesn't switch presets until you release the switches.

    To me, the Remote is the simplest plug and play option for the head IF you don't need other effects than what you place in the loop or loops or midi functionality beyond what you can do with the slot settings, AND if the ability to *only have four dedicated switches to turn things on an off with in a rig is sufficienct, on top of seeing with an led the morph status and the convenient possibilities of toggling that with the 1-5 switches. With midi controllers, you always have to make sure the led status matches up properly. Add in having a built in tuner at your feet and one less thing to plug into an AC outlet.


    I'd seriously doubt a 2.0 at Namm what with all the never-ending work they've done to get a working editor and enhancements for the firmware of the current generation. And for that matter, if rolling out a 2.0 head/rack in 2020, why go through all the trouble of developing a 1.0 floor model in 2019, when you could just role out all three products in the same upcoming generation? Like I said years ago, they could have made a floor version very quickly once the development of the Remote was finished, the hard work for a Stage was done. All they really needed to develop was a floor-shaped metal container that held the hardware of the head and remote, and perhaps streamlining a few knobs and controls.. Going forward with 1.0, Stage, head w/remote and rack w/remote, they have three products: that have virtually the same hardware/firmware/software/editor to roll out new features for. This ensure that future rigs will be cross compatible with the three.

    I went with the stage for two reasons, first off is the form factor. I like the all in one design of the foot controller for its compact design and easy transport. Second was the cost compared to buying a toaster and controller. I liked the form factor of the Helix and if it was not for their editor I would have left that product a lot sooner then this past August. At this point if I could trade the stage for a toaster and controller, I would but no one would make that trade.

    I'd consider making that trade! And you could probably easily find someone willing to do so straight up. The falling resale of a used unpowered head+remote is partially due to the fact that one can buy a brand new Stage (which is feature wise the same thing as the head and remote in a single floor-shaped box) for $1700. I don't think I'd get close to $1700 if I tried to sell my head and remote, unless I found someone locally who wanted one without losing money on shipping costs and seller fees. (Even if the buyer pays shipping, this just reduces the total cost he's willing to pay for the product.)

    Do you think this is more or less dangerous than announcing "a couple of days" when the product is months from being ready ?

    No youre right, it's not less dangerous. But if "maybe days" is the actual case, and they said such, isn't it then a bit extraneous to bother mention such beta testing? If it's days away from a public beta release, you'd expect private beta testing to precede it. My suspicion (knowing nothing about programing) is that the delay has had more to do with getting the firmware straightened out, and perhaps even that kemper cone thing, as they need the editor they roll out to function with the kemper cone thing vs. rolling out the editor, then having to roll out new enhancements for the editor as soon as they release the kemper cone thing when it's ready. The Kemper cone thing would also be tied in with the whole preset/library/ organizational side of things for which the editor would need to accommodate. And for that matter, depending on what their workers specialize in, at the moment fixing the glitchy firmware and issues with the roll out of the Stage as the holiday sales season is upon them needs to take priority; that's how they'll afford to keep the development department churning out new things.

    Tone junkies being well known or “Obscure” or not is besides the point. Either way It’s info coming out from a third party, not an announcement from kemper and perhaps not an announcement they were pleased the third party shared. In any case the fact that there are some beta testers perhaps tasked with looking for specific issues doesn’t tell us that there aren’t other issues kemper told the beta guys they are still working on. There could have been beta testers back in January who tested the seemingly perfectly functional and demoed Namm version of the editor. However the moment Kemper officially announces beta testers, this inevitably ramps up the “any day now” assumptions and rumors leading to more disappointment if it takes longer. Last quote I saw from the company first hand was perhaps weeks it might be ready, barring unforeseen issues. Apparently a half dozen pages back on this thread there was an indication of possibly even days? So if they’re at one of those two stages, baring potential and unpredictable setbacks, is there really a compelling reason they need to make an official announcement about beta testing?

    By the way, we should care, at least indirectly, about Stage sales and the overall success of the KpA line of products if we like new features for our kpas or hope for new products from the kemper company in the future. Bills have to be paid, teams of paid employees that develop editors, roll out new effects and firmware improvements, as well as ongoing customer and product support and continued compatibility with Mac and Windows over time isn’t cheap. New sales provide the means.

    So to summarize 115 pages of comments and many other editor threads over the years. What we know for sure:


    When the editor arrives, the net
    time it will save us and the convenience it will provide in our lives will be vastly exceeded by the hours we spent thinking, hoping, discussing, and arguing about it before it is actually released.