Posts by slateboy

    Just installed 4.22 and very disappointed to say i notice NO difference whatsoever regarding the calibration procedure.


    Maybe the guys at Kemper can explain what the recent fix to this was? (probably explains why nothing was mentioned in the release notes)
    my biggest question is- why is the KPA always in calibration mode (it defeats the object of having a calibration adjustment) if it constantly works on the min and max values delivered by the expression pedal?


    I'd like to able to set (calibrate?) the KPA to work between point A and point B on my expression device and it "remembers" those two points/values.
    If i temporarily move outside of those points i dont expect it to recalibrate and move my set-points.
    I'll message support on this.

    Agree, I didn't see any comments about it in the release notes, but I guess only the minority were affected and it wasn't a major issue worth mentioning. There's a lot of stuff we don't need to know about 'under the hood' but I see no harm in listing a fix like this. We all know Kemper listen to their users and constantly strive for new and improved features. I wish more companies worked this way.


    Anyhow, hope I haven't spoke too soon, i'll report back when i've checked out this upgrade....
    :/

    Im not convinced nor satisfied with kempers expression pedal calibration procedure.
    the calibration screen shows what is expected but it appears that the KPA is constantly in calibration mode regardless of if the user selects it or not. (connected direct or to the remote unit)
    The full-range (its working range values) is always based on the min and max value received at any time. This is fine for many situations but the following scenario will apply to many and they should be aware of it:


    Here is a typical expression pedal:
    [Blocked Image: http://thelookmusic.co.uk/kemper/expressionpedal.jpg]
    So you've just calibrated your pedal to work between the regular range (red to blue) all is fine. Then you step on the pedal a bit harder (green position shown) to engage the switch but the Kemper now "thinks" this is your full-range, therefore you will mostly using 90% of the full range. This can be acceptable but effects that engage at 100% range wont be achieved. As a result, you can now not achieve 100% range unless you are standing on the button. At rest (blue position) it will lift a little to around 95% of it full movement. You will see clearly on the calibration screen.
    I use the LPF effect and set it to OFF at toe position. In the above scenario the actual toe-position is when the pedal is pushed all the way engaging the button, not just between the red and blue lines the user thought they had calibrated to. Consequently this small deviation means the effect is always on as it is never in "toe-position" unless i hold my weight on it, therefore engaging the button which may not be intended.


    The same is true for pitch dive effects where perhaps a soft spongy stop is at the heel position. the "at rest" position will be on this stopper. a little extra force may compress the sponge material and consequently adjust the low-scale value to the min value received. Noe when the pedal is at rest on this "stopper" the value is above the min value.


    My request is that the calibration screen does what it says and when you exit the calibration screen the settings are stored and locked at those values attained. Otherwise whats the point of this screen?
    I've had this discussion with the Kemper team and they tell me everything works as intended but im not convinced they have allowed for the situation described above
    Maybe i'm missing something here?
    I dont often have a whinge about the KPA as its otherwise awesome!


    my video example shows an extreme case of what i'm trying to say (even though its an older OS its still relevant to v4)

    External Content youtu.be
    Content embedded from external sources will not be displayed without your consent.
    Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.


    I will give this thread an airing for a few days and depending on the response put it forward to the KPA team again.

    in my experience, calibration is in continuous operation always seeking the min and max values without the need to actually push the button. try it- move your pedal over a short/tiny range for your initial calibration, exit the screen and then move the pedal full range. the kpa will detect this and scale its range accordingly.
    however should you wish this to not be the case youre stuffed and there are scenarios where this maybe an unwanted side effect.

    @prsgary , the solution suggested by @paults will mean recalibration is needed so the working range spans across the shortened physical movement, which I'm sure you both know. This probably means you'll encounter the need to recalibrate EVERY time you attach this pedal. See my findings in an earlier thread, explained in this video:

    External Content youtu.be
    Content embedded from external sources will not be displayed without your consent.
    Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.

    I'd be very interested to know how you get on so please report back if you use the suggested alteration thanks.

    Also tuning a guitar played on its back (bench or worktop) may affect setting up and tuning as the weight of the neck will add some strain/movement, as indeed will an extreme temperature environment. Temperature is definitely the biggest enemy of tuning affecting the strings (on a decent set up instrument)imo.

    One thing I have noticed is that if your pot, whether from a recycled wah or something else, does not move through the full sweep range of its mechanical limits you will have to recalibrate EVERY time you connect or disconnect the device. What I perceive as a flaw in the KPA but Kemper tell me is an intentional design is that the KPA does not store the calibrated values for such devices and is constantly in calibrate mode whether it appears so on that page or not. I have requested this from Kemper but they indicate that this is how it will remain.
    3.3 demo here but also applicable on 4.06

    External Content youtu.be
    Content embedded from external sources will not be displayed without your consent.
    Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.

    Let's keep it positive, guys.
    my original post was to see who is not using morph. We've established there's some uses and users making use of this clever feature but I was seeking those who, like me, have yet to find a situation that requires this. Seems there's a spilt down the middle. perhaps a poll would have been better?

    As much as i'd like to, I've yet to find a practical use for the morph feature in my day-to-day playing. Don't get me wrong, i'm not complaining as its a cool feature and i can imagine many players making great use of it.
    In fact, i've not really gained anything by upgrading from 3.3 to 4.06 other than the remote doesnt "time-out" when moving between banks. I was happy with the old delays- not really noticed any audible change there. Not too thrilled with the increase boot-time but thats by the by.
    I love the KPA and use it like a replacement for a traditional amp+fx setup, ie, boost for solos, occasional chorus/delay, etc and v3.3 done everything i wanted reliably.


    So, what I'm asking is, are there other users out there that, perhaps like me, have not benefitted from the latest features/upgrade or maybe hanging on to 3.3 as its suffice to their needs?


    That's not quite right !
    After storing new values, the Name of the Output-Preset is prompted. If you choose this Name, then a synonym will be created.
    A Problem then is, you will find two Output-Presets with the same Name and you won't know which one to choose next time.
    So currently you have to save an overwritten Output-Preset under a different Name, or -if using the same name- to dedicatedly delete the former Version.
    You'll find a post concerning this improvement-potential under Feature requests


    Agree, the save procedure and duplicate names is a problem but wasn't the basis for my comments.
    I only used this as a brief reference whilst discussing which parameters are saved and which are not.
    And you're right, too, this is a separate issue, anyhow

    Went from about 1 min on v3.3 to 77sec on v4.06
    remote adds an extra 25secs on top of that.


    it appears the remote has a timeout if not connected within x-seconds. The remote appears to get power earlier on in the boot cycle than previously but turns off after about 60sec then repowers when boot is near to complete adding 25 secs. I did connect the remote after 40-50 secs of boot and it stayed powered as it continued to search for a connection without going off and increased the start time by several seconds. Anyone else confirm this?

    OK thanks for explaining. I will check this later.
    Do we know what is by-design setup?
    Is this documented in manual, that all of the output parameters are recalled after restoring saved preset?


    Its not something that i've seen explained anywhere. Its one of those articles i find useful to know but is a case of own-discovery.
    I did attempt to add it to the wiki-KPA site (last year) but it think that has deteriorated http://ww1.wikpa.org (having just checked again no site opened whatsoever)


    I guess its a bit like being interested to understand how a car engine works- its not the sort of thing they'd put in the user manual for most users as they just get in and drive it. There's no "service" or haynes manual equivalent for the KPA so the only way to learn the depths of it is, like the car, take it to bits- metaphorically speaking, in a technical sense not physically with a screwdriver and hammer ;)


    When these presets are recalled/ignored? What action should I perform to check this behavior?


    As you might have guessed, you can store output settings for various scenarios.
    If you hit the output button then scroll the browse knob you can find your saved output settings.


    to check:
    If you save some "output-settings" (go to output page then hit "store"->"output section") alter values within the output-section then recall the saved "output setup" certain values will be over-written with the "saved" values, but as i have found, not every output parameter is saved/recalled.

    Following on from this old thread, I've compiled a list of which parameters and settings are stored/recalled in the output presets:
    If anyone would be so kind as to confirm my findings it could prove useful to others, including myself


    OUTPUT PRESETS parameters saved/recalled in presets (FW v4.06)


    page 1/6
    main output config = recalled
    monitor output config = recalled
    direct output config = recalled
    SPDIF output config = recalled


    page 2/6
    main volume dB= ignored
    monitor volume dB= ignored
    direct volume dB= ignored
    headphone volume dB= ignored
    main out link on/off = recalled
    monitor out link on/off = recalled
    direct out link on/off = recalled
    headphone out link on/off= recalled


    page 3/6
    monitor output eq= all values recalled
    monitor cab on/off = recalled (didnt before)


    page 4/6
    main output eq= all values recalled


    page 5/6
    SPDIF volume= ignored
    pure cab amount= recalled
    headphone space amount =recalled
    SPDIF outlink = recalled
    pure cab on/off = recalled
    headphone space on/off= recalled


    page 6/6
    aux in main= recalled
    aux in headphones = recalled
    constant latency = ignored


    the ability to LOCK the output section was removed, i believe. i Guess these parameters are global and not per-preset/rig so pointless locking them.