Posts by Burkhard

    Thanks for your feedback so far! Needs don't seem to be that congruent.


    I'd like to dig deeper into this Delay Mix Morphing approach. Our today's Morphing works like this - let's assume you have set up Slots in Performance Mode this way:


    Base Sound Morph Sound

    Slot 1 Delay Mix 0% 60%

    Slot 2 Delay Mix 10% 50%

    Slot 3 Delay Mix 20% 40%

    Slot 4 Delay Mix 30% 80%

    Slot 5 Delay Mix 40% 10%


    Each Slot gets loaded with the Base Sound values regardess of the current pedal position. As soon as the pedal gets moved it is soft catching the Delay Mix starting from these Base Sound values. Do you expect the same logical approach for a second Morphing layer or something else, and what would that be? From what I read before I got the impression, that people are looking for a way to adjust Delay Mix and Reverb Mix more permanently, than what Morphing does.

    We are considering a potential enhancement ideally adressing a whole family of feature requests and asking for your educated feedback.


    Features:


    - another pedal controller primarily for Delay Mix and Reverb Mix leaving Morphing for other tasks by Rig,

    - another pedal controller for Looper Volume,

    - potentially integrating the existing pedal controller for Monitor Output Volume into a broader concept.

    - ...


    Considerations:


    - Looper Volume and Monitor Output Volume are global parameters and don't fit with the concept of Morphing as it is today.

    - What is really the exact purpose, when people are requesting additional pedal controllers for Delay Mix and Reverb Mix? Morphing allows to control the Delay Mixes and Reverb Mixes within any delay and reverb effect within any effect module individually or combined. Ranges can vary by parameter. Each Rig change resets Morphing to its base sound. Is this, what's also needed for a second Morphing?

    - Otherwise - if the pedal level would be maintained during Rig changes and overwrite the stored Delay and Reverb Mixes in the Rigs, should this affect all delay/reverb effects in all modules? So, for example all delays would run at n% Mix? Or how should the fixed pedal level be applied as stored effect locations, types and settings could vary by Rig?

    - Perhaps it might be more useful to establish two global offsets for Delay Mix and Reverb Mix, which would allow to reduce or increase all delay and reverb mixes across all Rigs and effect modules by a specified amount? Imagine you had a global controller for example to increase Delay Mix by +10% and to lower Reverb Mix by -5% across all Rigs and effect modules. Would this help and is a pedal then even needed or is this an adjustment you do once per gig/event manually?


    Idea


    Imagine such global offsets would exist and we would introduce another Morphing limited to global parameters. Today's Morphing is restricted to Rig parameters. So there would be no overlap between both Morphings. There would be a new Global Morphing Pedal. And you could configure global continuous parameters like Looper Volume, Monitor Output Volume, any other output volume, output EQ settings,.... and the Delay Mix and Reverb offsets mentioned above individually or combined with individual ranges to that new pedal controller the same way as you practice it with Rig-specific parameters to the existing Morph Pedal today. These assignments of global parameters to the Global Morphing Pedal would also be global and not be stored by Rig. Would that cover the needs?


    Please think through the consequences and let us know!

    According to the technical specs you are safe if you allow the unit to warm up to 10° C before switching it on - except if you cycle across the Mount Everest:

    ¨   Environmental Requirements

    Operating temperature: 10° to 35° C (50° to 95° F)

    Non-operating temperature: −20° to 47° C (−4° to 116° F)

    Relative humidity: 5% to 95% non-condensing

    Maximum altitude: 3000 m (10,000 feet)

    If you intend to use your expression pedal exclusively as Wah Pedal, never as Volume and never as Pitch Pedal, it is most logical and straight forward to deselect "WahPedal to Volume" and "WahPedal to Pitch". These are global settings. Within the wah effect select Pedal Mode "Bypass @ Toe".

    Effects don't appear nor disappear accidentally. There are multiple ways to select other effect types in the PROFILER user interface as well as in Rig Manager. You could have locked the module here or there. You could have stored the Rig with locked modules ....

    The behavior is only strange until you understand basic concepts described on the first few pages of the Main Manual.


    Things like verifying what kind of effect is actually in a module or what a Rig change does ("But hang on. I just pressed some Rig buttons on the right hand side of my profiler. So now reverb is back & reverb mix & time controls are working.") shouldn't be mysteries.


    The liberalization of the REV module - freeing it up for other effect types - happened in OS 5.7 about two years ago.

    We have just elevated OS 8.0.3 to release level! In includes the following improvements versus OS 8.0.2.


    Audio


    changed: automatic amp volume compensation in combination with distortion effects, which have volume set below zero


    User Interface


    fixed: sometimes replacing wrong Rig after editing via Rig Manager and changing Rig before store

    changed: Tuner and Harmonic Pitch display keys in B instead of #


    Rig Manager 3.0.145 required!

    If you place a wah effect in the REV module, then there is no reverb sound, but a wah sound from that module. If you empty the REV module then there is no effect from that module at all. When you load another Rig, the whole signale chain including modules from A to REV get replaced.


    To avoid such "mysteries" you need to read the manual and familiarize yourself with basic concepts like Rigs, signal chain, modules, and effects within those modules. All this is covered right at the beggining of the Main Manual.

    Because it is not easy to see it from the outside, speaker cables are normally clearly offered and marked as such. If the description doesn't mention "spealer cable" in any language e.g. "Lautsprecherkabel", it's none.

    Use a speaker cable to connect the red SPEAKER OUTPUT of your PowerHead or PowerRack with the input of your KEMPER Kabinet.


    If you own a second KEMPER Kabinet, use a second speaker cable to connect the output of the first KEMPER Kabinet with the input of the second KEMPER Kabinet.


    Speaker cables have TS jacks (1/4 inch mono) and are normally thicker than instrument cables and not shielded. Speaker cables are marked and named as such. Check the description on the packaging.


    Don't use instrument cables (like guitar cables) nor insert cables with two mono jacks on one side and one stereo jack on the other side for this puspose! Just had one client trying that ....

    I thought the subject here is volume pedal positions!?


    Even if you select "Post Stack" or "Output" as your Volume Pedal Location, it is still in the signal chain for Output Source = Stack. And that is intentional. It is not the purpose of the Volume Pedal to control Delay Mix nor Reverb Mix.

    Ok, you seem to be using "Sorted by Author". Which of the Views are you using? Or could the View vary? If you for example select Views "Favorite" or "Just Bass", there are less Rigs and consequently less authors. And are you absolutely sure not to press twice accidentally?


    I doubt, that this has anything to do with Performance skipping and nobody else has reported such behavior ever. Are you really always completely aware of the above scenarios?


    If you are able to reproduce, please open a support ticket, attach a current backup of your PROFILER and instructions how to reproduce.

    By the way, those of you experiencing this Performance skipping issue, have you really installed our current OS release, which is 8.0.2?


    I can easily reproduce the issue - with customer backup - under 7.5.4, but not under 8.0.2!


    And ... is Rig Manager connected, while you are experiencing the issue. And if so, which revision?