Posts by ckemper

  • OS14 / Profiling 2.0 Public Beta Discussion

    Quote from musehead

    Profiling has become incredibly convenient. Among the easiest and fastest methods so far, In 2.0, after profiling with kemper generic... It seems most ideal to transform it into liquid profiling later. Honestly, liquid works almost perfectly identically to block letter 5150. I can now carry my favorite AMP in my backpack.

    That's nice to hear!

    When you do Liquid afterwards, do you set the Gain Pot Ref. in advance at least?

    CK

  • OS14 / Installation and Rig Manager Discussion

    Quote from DamianGreda

    To help clarify the situation regarding the 'unintended' resonance parameters, there is a simple, objective test we can run.

    Using UI to MIDI (courtesy of the KPA Team), we can clearly see that on MK I devices, the parameters correspond to the following:

    • SYSX: F0 00 20 33 00 00 01 00 0C 0B 28 20 F7 (Resonance) 0C 0B
    • SYSX: F0 00 20 33 00 00 01 00 0C 0C 47 5A F7 (Q factor) 0C 0C

    Anyone can do a quick test to check if these exact same NRPN parameters are being modulated with the new FW on MK II devices. If they are, it logically points to the conclusion that these parameters are not just a coincidence, but are fully functional and actively working under the hood in the new firmware.

    My goal here isn't to stir up trouble, but simply to apply objective, critical thinking to the data in front of us.

    Since the DSP and firmware clearly still support and process these parameters, I would like to make a strong request to the development team: please expose them officially in the Editor. > Giving advanced users direct UI access to Resonance and Q factor would be a huge benefit for sound design. Since the underlying code is already handling them, unlocking them in the editor seems like a natural next step and would be greatly appreciated by the community. Could we get this added in a future update?


    It is of course not a coincidence. We have done prototyping back then and these parameter numbers are simply next in line. You were able to test here, that the algorithm prototype behind that does not belong to the cabinet. And actually it does not match the cabinet profile.

    Anyway, there is a good method to control and emphasize a cabinet resonance and it has always been there for everyone. Position a peak equalizer after the cabinet and tune it to somewhere between 75 and 120 Hz to catch the resonance. Set Q factor to 0.7 or 1.0 or more. Tweak Eq gain to your liking.

    This is of course not the authentic way, but very effective. What we have evaluated back in 13.0.5 was somewhat related to this method.

    CK

  • OS14 / Profiling 2.0 Public Beta Discussion

    Quote from Ibot39

    I just wanted to clarify if there is a bug for Mk1 users making 2.0 profiles sound very very thin. This is my first-hand experience (comparing old 1.0 Dill rigs to 2.0 profiles of the same amp)! And there are 2 videos of different users that show the same issue. Mister Kemper responded to one also saying that something sounds clearly wrong.

    The other video is from a beta tester Dee Dammers. Mister Kemper here responded to the wrong video. I post the correct video again here one last time. Maybe someone of the team can have a closer look or contact Dee Dammers. Maybe this helps to find a bug.

    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.

    Hi,

    I responded to your post where you mentioned MK2 Profiles on MK1. "He is a private beta tester as well and has made this video with an older internal beta version, unfortuately."

    And yes, another video was linked in your post. No problem though.

    CK

  • OS14 / Profiling 2.0 Public Beta Discussion

    Quote from tedtan

    You couldn’t tell the difference between sample rates in and of themselves, but sometimes there are other tells, like differences in aliasing when gain is applied or certain converters sound different at different sample rates for some reason. But those are differences i other things, not in the sample rates themselves (44.1k fully captures the range of human hearing (plus a little extra)), and can be worked around via oversampling when adding gain.

    So this is not the topic of this thread, but parts of it.

    Many people were told that a higher sampling rate will tame aliasing, which is true. But on an expert level it is known that taming starts at 4x the sample rate at least. Going from 44 to 48 or 96 kHz has only decent effects on aliasing, depending in the situation. If you have to have your DAW running at 96 kHz (paying a high price) to make your plug-ins better, then you might hear and tame poor coding in your plug-ins.

    Same applies to converters. They run sampling rates in the MHz region at any time for many good reasons, and they simply don't give a * about the incoming sampling rate :)

    Fun aspect: while many believe in null tests as the scientific measurement for everything, the community is kindly forgiving aliasing effects in digital guitar amps.

    CK

  • OS14 / Profiling 2.0 Public Beta Discussion

    Quote from Kellerblues

    There is a long thread about Null Test on TGP that (for once) is very interesting thanks to the contributions of several people that has a deep insight on how things works (including some DSP Engineers from Line 6 and some Psychoacoustics experts). They basically say that Null test is meaningful only for a part of the capturing process and meanigless for another one. And they underline that a null test doesn't reflects how humans perceive sounds.


    And here is another article about null tests:

    “Don’t divide by Zero” 😀 – Why Null Tests Fail for Amp Captures – Modern Guitar Magazine

    Can you post a link to that TGP thread you have mentioned?


    Nulltests are flawed for judgements of authenticity, because they create audible artefacts by aspects that the ear cannot her. For example you could delay two absolutely identical tracks by only a few samples and result in a null test that is louder than each single track, a worst case scenario. The null test community then had to conclude, that the second track is not authentic at all.

    Some of these inaudible phase delays happen in tube amps, too, This often results in the blooming null test sounds, that come out louder than the amp sound alone. The latter happens on every device and video I have seen. There is no science behind it.

    CK

  • OS14 / Profiling 2.0 Public Beta Discussion

    Quote from Ibot39

    External Content youtube.com
    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.

    Here you hear mk1(1.0) profile sounds good and the same on mk1 and mk2.

    Problem appears only 2.0 profile on mk1 unit. Suddenly thin sounding compared to ALL other options. Has to be a bug

    He is a private beta tester as well and has made this video with an older internal beta version, unfortuately.

    This does not explain the differences on that other video, he is not known to us. But the 2.0 Profile was weird there as well.

    CK

  • OS14 / Profiling 2.0 Public Beta Discussion

    I was able to listen to this video now. Seems kind of odd for me.

    Lost most of the mid range going from Classic Profiling to 2.0. That to me is a problem on its own.

    Then lost all bass going from MK2 to MK1. This is not what you experience on the other videos doing kind of the same action. He should give us a note what happened exactly, if he‘s interested. I am sure that no one can reproduce what we see on this video.

    CK

  • OS14 / Profiling 2.0 Public Beta Discussion

    Hi and welcome!

    You are about the first user to have questions about profiling with the player.

    As you know, the final level of the Profile will be set automatically during the Profiling process. But yes, you are told that you should initially set the Return Level in the ballpark of an existing Profile to roughly have the volume set, so that no input distortion occurs, or too much noise on the other hand. This is not easy with the Player for sure.

    Here is my advice for a simple approach, with no recabling.

    Set the Return Level to some level and start profiling. When there is an error message (e.g.) too much volume, reduce the Return Level by 8 dB or so and try again.

    Once the Profile has finished successfully, the Return Level is set automatically, but the level still could have been a bit off the ballpark initially. Simply take the Profile a second time, it will happen now with nearly unchanged Return Level.

    This procedure does not need to be repeated for consecutive Profilings, because the Return Level will roughly stay in the ballpark.

    CK

  • MK 2 - Profiling 2.0

    Hi everyone!

    Greetings from the NAMM Show and thanks for commenting. As mentioned, the clips we have posted are not reamped, but played freely. Thus we have contradicting comments here and among different forums, which we expected.

    A good definition for a dynamic amp sound is the ability to clean out easily when played softly, while maintaining most of its loudness. The Plexi is well known for such high dynamics, caused by a large bright cap.

    For the second clip Thomas opted to turn down „Brightcap Intensity“ because he likes the „jumpered“ sound more, taming the impact of the large bright cap. This way, he did not try to improve the dynamics, but even lowered the dynamics a bit. It brought back some low frequencies however, which he liked for his playing.

    As with the classic Profiling, you hear amp hiss on both the reference amp and the profile. This is because we purposely replicate the hiss for the Profile during the A/B comparison. Once you leave the Profiling Mode the hiss is gone.

    CK

  • using Kemper effects straight into front of tube amp

    Quote from dango123

    Thanks again for weighing in on this point - I will say that the bit shaping pedals that I've worked with, like the EQD Bit Commander, have a more extreme impact on the sound. The test example I provided in my earlier post resulted in an extremely subtle effect which didn't seem like it added much; I did play around with the Drive and Tone settings during my initial experiments but it didn't seem to do much - I will revisit this to see if it makes much of a difference.

    Best,
    Dango

    Hi!

    Another aftermath: The EQD Bit Commander is not a bit shaper at all, but merely a sort of synthesizer/octaver. Different sound.

    CK

  • using Kemper effects straight into front of tube amp

    Quote from dango123

    I had a few moments to try this suggestion out - while it is having an effect, for me it doesn't solve the problem - here's my test case

    1) Load the LMTTRAY - A-Stick profile (as is from Rig Exchange)
    2) Disable all effects
    3) Set monitor output to Master Mono (note that it was already there on my player)
    4) Toggle the amp model on to off, and back on again
    5) Load a Bit Shaper (8Bit Solo) model in front of the amp

    For me, the bit shaper sounds like it is lingering softly in the background (like 5-10% active), while the clean/uneffected sound dominates - the parallel path mixed sound still seems to be happening. To a lesser extent I still heard this effect in some of the drive models (like Green Scream) as well. Some Drives are definitely moving in the right direction, but still have a softish kind of feel to them (at least some that I tried out).

    Wheresthedug and Job Posthuma Can you please see if you can duplicate what I'm hearing (or possibly tell me that I'm crazy...) - I know you had few additional suggested tweaks to the output section, but what I'm hearing is not a slight eq difference, there is still something definitely not right (on my machine at least) in the upfront signal chain. Appreciate your help with this, thanks again!

    The Bit Shaper, as well as any other bit reducing effect, sound like an effect added to the clean signal by nature, when not set to drastical values.

    You can check that there is not parallel signal is added to the Bit Shaper by simply setting Drive and Tone to max value. Then the sound will be cut off, once it decays below the 1 bit barrier.

    CK

  • using Kemper effects straight into front of tube amp


    Hi!

    As some have mentioned here, all overdrive pedals - including our Green Scream and the Kemper Drive - have the clean signal added to the overdriven signal. That is the nature of overdrive pedals.

    The output level of the profiler is not necessarily equal to the output level of an overdrive or distortion pedal.

    Have you tried to change the output level to achieve the desired sound?


    CK

  • Noise Gate Update Request

    Hi!

    Our Expander Noisegates 2:1 and 4:1 are your friends.

    Place it before the amp.

    You can leave the standard noisegate in the input section on. This is a filter noise gate that does not interfere, but work well in combination with an expander noisegate.

    It is a good habit in the analog world to have the sensing of the noise gate before the tube amp, and the gating itself after the amp, e.g. in the fx-loop of the amp, to cut all noise from the guitar and the preamp.

    In a digital guitar amplifier the placement after the amp is not necessary, since the amp section does not produce any additional noise.

    We have made extensive tests that simply placing the expander noisegate before the amp make the best results in terms of the dynamic player interactions. Try it out!

    CK

  • Missing the original vintage chorus in the latest firmware

    Hi Guys,

    I heard you, and thanks for your comments.

    I will bring the old chorus back and add the crossover again.

    However, you will allow me to keep the bugfix that I had applied. The previous model had by far not enough effect level, compared to the reference BOSS CE-1 and a good friend of mine pointed me to this flaw.

    The original CE-1 has a boost of nearly 5 dB, when engaged. I have reduced this boost to less than 2 dB for version 12, the bugfix.

    For the next version I will eliminate the boost completely.


    CK

  • Ahhh What's that? A New Kemper Model? Profiler Player

    Quote from Basti1987

    Does someone successfully get to charge their tablet from the Usb port? My tablet wont charge, only phone gets enough current.

    So that's a story that I wanted to deal with anyway!

    The message "Not Charging" on Apple devices is unfortunately a bit misleading.

    Every Profiler device supplies up to 500 mA of current through the USB A connector. This is what a regular phone charger delivers.

    When you connect an iPad on such a source, it will tell you "Not Charging", because your iPad is switched on, showing that message, and drawing most of the currrent for the device itself, being powered. Not much additional (or no) current is left for charging the battery in parallel.

    Now if you switch off your iPad, it will charge using the full 500 mA! But the display is off and would not inform you about that. That's a paradox :)

    Thus you can charge any device on a Profiler up to 100% if there is enough time. But you should keep it switched off during that time.


    But you can also keep a device powered for an indefinete time, it it does not draw too much current. It would not charge then, but it also would not discharge the battery.

    The rule of thumb is, the larger the screen, and the brighter, the more current the device draws.

    I did a test with my iPad Pro 11' a couple weeks ago to power it with my Profiler. I checked and adjusted the screen brightness so that the battery would not discharge, which took some time. Then I let the iPad run with the Profiler Rigmanager App running for 11 hours. It worked!

    The screen brightness was only at one third, but that was still bright enough for a dim stage. The battery load came up from 76% to 82% in these 11 hours. So merely charging, but not discharging. If it was discharging slowly, the screen brightness would draw a bit more than the 500mA of current, and the battery had to support it, until it was empty.

    The iPad showed "Not Charging" for 11 hours, which is about a true statement.

    If I had a smaller tablet, such as an 8' Kindle Fire, I could have the screen brighter, at the same current.

    So it is possible on stage to have a tablet with editor powered by the Profiler the whole night including sound check.

    CK

  • Ahhh What's that? A New Kemper Model? Profiler Player

    Quote from arkanian

    If I put my wet effects after the player can I still take the last pedal output to Kemper Kone and use imprints?

    Yes, this will work basically.

    The only problem that might arise with this special setting, is that the TS outputs have a very high volume, when the Kemper Power Kabinet is driven to high wattage in "Kone mode". This would potentially overdrive your pedals and create unwanted distortion.

  • Ahhh What's that? A New Kemper Model? Profiler Player

    Quote from texhex

    It's a not an good idea to charge extra for updates to this device if you ask me, IF that is what Kemper actually intends to do in the future. Charging for feature enhancements puts Kemper hardware products into a totally different category IMO.

    We would charge for rising the Player to a different level. And it would be one different level only, lifting it into a different product category. Free of hazzle.

    But this would not cut the Player off from the free feature updates that we have pioneered back in 1998 (Access Virus Synthesizers)

    There is free feature updates in the works where both levels would benefit.