Posts by nejo_hh

  • Web Midi Controller

    Quote from schoko

    Do you have also found out how to e.g.: calc the "studio eq low frequency" from

    a value from 0 - 16383 to

    20hz - 33 488hz (as displayed on the kemper)

    i just stored it in an array, but that is quite clumsy: https://github.com/schoko11/KEKO-…rc/FxObj.ts#L32

    (similiar for graphic eq : "low cut" and "high cut" and rigvol "-inf" to "+12db", which i didn't find on your page )

    You can ask the Profiler for the human readable interpretation (shown in display and RM) of any encoded value. Refer to the MIDI Parameter Documentation, chapter Request Parameter Value as Rendered String.

    Example: What is the meaning of the encoded value of 1000 (msb = 0x07, lsb = 0x68) for the Rig Volume (address page 4, number 1)?
    Using the excellent tools ReceiveMIDI and SendMIDI we find (comments in last line)

    Code
    receivemidi dev Profiler
system-exclusive hex 00 20 33 02 7F 3C 00 04 01 07 68 2D 31 38 2E 38 64 42 00 dec
                                          p# n# ms ls -  1  8  .  8  d  B  \0

    i.e. "-18.8dB" when sending (comments in last line)

    Code
    sendmidi dev Profiler syx hex 00 20 33 02 7F 7C 00 04   01     07       68
                                                   page number valueMsb valueLsb

    Be aware that SendMIDI requires the delimiters (F0/F7) to be omitted for SYSEX messages.

  • Web Midi Controller

    First: Thank you all for your excellent work! Highly appreciated.

    Quote from slateboy

    that i dont know- But i agree, there must be some kind of log scale. Anyone up for some logarithmic formulation? ||

    Although not perfect the following formulas come quite close:

    Code
    frequency_Hz = exp(3.025291 + 0.0004513004 * value_14bit)
value_14bit = (log(frequency_Hz) - 3.025291) / 0.0004513004

    They have been derived from the simple approach:

    Code
    fMin = 20.6
fMax = 33488.1
exp(log(fMin) + (log(fMax) - log(fMin)) * value_14bit / 16383)

  • On the implicit Low-Cut Filter of the CABINET Slot

    There is even more to learn from the above analysis:

    1. There is also an implicit high-cut present at about 21.83kHz; see attached plot frequencyResponse-KPA_CABINET-flat-highCut.png.
    2. The ripples seem to be evenly spaced with a raster of slightly over 86/172Hz. Dividing 22.05kHz by this results in approx. 256/128 support points of the CABINET filter.

    Another humble suggestion to the Kemper team: If it is possible to individually define the center frequencies (like for a cascade of IIRs), how about a log(f) spacing? See attached plot filterSupportPoints.png.

  • Whose Profiles does Michael Britt use?

    Quote from lonestargtr

    I've thought about putting out my live rig performances but people would probably be taken aback by how much fx I have on them. Out of context, there is a lot of delay and such. But in context and since I program everything to the exact tempo of each song, the delays kinda disappear and I have to run the mix higher to hear/feel them where I want. But listening to them in isolation they sound pretty effected. If you play those rigs on a different tempo song it would sound cluttered I would think.

    Please! I think many of us would love to learn from one of the greats.

  • Whose Profiles does Michael Britt use?

    Quote from lonestargtr

    Also, I usually use the profiled cabs on most of the clean tones, but as the gain goes up, if I hear too much tonal difference or feel like the bottom or low mid drops out I will try a couple of my favorite cabs on the gain rigs. There is one in particular that I use a lot for many of my live performance rigs. I use the same cab most of the time when profiling but the Kemper algorithm that decides what is the cab and what is the amp creates slightly different sounding cabs with every profile. One of those I just find particularly pleasing and it works well sonically with the band. I would say that most of my mid to high gain tones use that cab unless I'm really just going for a "different" sound like on our cover of "In The Air Tonight" where I want that mesa grind.

    Thank you very much for chiming in and providing such valuable insights! Would you mind sharing the actual name of the profile containing that magical cab?

  • On the implicit Low-Cut Filter of the CABINET Slot

    Short version

    If you plan to profile (bass) amps or want to use (bass) cab IRs: Be aware of the implicit low-cut filter at 70Hz of the cabinet slot.

    Humble suggestion to the Kemper team: How about having frequency and slope of the low-cut filter as (internal) free parameters?

    Long version

    I've tried to profile a bass amp through the DI out but completely failed at first. I've then tracked down the cause and was really surprised by the findings. So why not share them?

    Already a coarse comparison of the frequency responses of the amp and the profile using white noise showed major differences: There was a steep low-cut at about 70Hz present in the profile and a ripple of alternating bumps and dips up to about 2kHz.

    But I've seen many bass amp profiles with deep lows. So how do they differ? It turned out that all such profiles were direct profiles, i.e. without a cab. In contrast, I naively hadn't engage the No Cabinet option for profiling the amp because the highcut filter of the amp was engaged which provides a gentle high-end roll-off like cabs do.

    Now having a clear suspect I imported an IR with a totally flat frequency response and analysed the resulting CABINET preset: A steep low-cut at about 70Hz, a light bump at about 100Hz, flat above; see attached plot frequencyResponse-KPA_CABINET-flat.png.

    Out of curiosity I've then tried to get a truly flat response by inverting the "flat" CABINET response to compensate for the unwanted "add-ons". The resulting frequency response was then transformed to an IR and imported via RM: Still a steep low-cut, above prominent ripples with decreasing intensity; see attached plot frequencyResponse-KPA_CABINET-compensated.png. Apparently, the algorithm is trying hard to match the desired (low-end) response but needs to introduce over- and undershoots in order to minimise the overall deviation. Actually, this is a common problem for filters with a limited number of uniform filter stages/taps: Large gradients in the low-end response are just hard to reproduce.

    Possibly said effects (low-cut, ripples) are the reason for some people finding it hard to get the low-end/low-mids right when profiling?

    KAOS version used: 8.5.8. Infos on the methods used to do the analysis: here.

  • EQ Question

    Hi cbecker999, welcome to the Kemperverse! There is an easy way to get a clue of what all the EQs are doing in sum: Send white noise through just the stack of EQs and analyse the result with a (Match) EQ in your DAW. And if you're after the tone of the cab plus the stack of EQs: You can make an IR of the whole thing by following the instructions here and here (sections Craft... & Finalise...). The final IR can then be imported to the Profiler via RigManager. But as already pointed out by others: If you want the whole rig in your Profiler: try profiling it. Hope that helps.

  • Studio EQ in Cab section / render button

    Quote from Bommel

    If the space or computing power is too limited it would be great to add a render button to the studio eq. What i mean by that is, you choose the studio eq make the changes you like press a render button and these settings will then be baked into the cab, creating a duplicate of this cab with the eq already applied. That would make things ultra useful

    Hey Bommel, how about doing it yourself? Extract the cab IR with the desired EQ engaged and import the result via RM. Just make sure the EQ doesn't clip the output. Hope that helps...

    Oh, and many thanks for all the good stuff you share!

  • Profiling the profiler through DAW...

    Another possibility would be to extract the cab IR from said profile and then bounce it through the match EQ to form a new cab with the desired frequency response: irSampling.wav -> DAW -> Profiler (well prepared) -> DAW -> MatchEQ (zero latency) -> WAV -> Edit -> Rig Manager -> Replace original Cab

    Edit: A more elaborate way would be: ((cab IR -> frequency response) * (match EQ -> IR -> frequency response)) -> minimum phase FIR filter [i.e. the final cab IR]. But that would require quite a bit of DSP math...

  • The Perfect cab IR ? Part 2 ... you are looking to get the sound of band XY? Check this out:

    Hey Matt BS, there is no need to perform the deconvolving step: Just directly sample the filter taps of the Match EQ (make sure to set it to zero latency) following the instructions here and here:

    1. Bounce the sampling pulse from here (section Craft the magical sampling DI signal) through the Match EQ (set to zero latency). Use Wave with 44.1kHz/24bit.
    2. Finalise the recorded IR following the instructions here (section Finalise the recorded IR).

    Edit: Also make sure that the Match EQ does not increase gain (check the peak level of the output before bouncing).

    Edit2: Disable normalisation, dithering and other fancy options for the export (you need it to be raw/unaltered).

  • [FIXED] RM3.1.62/OS8.0.6 Bugs

    First: Many thanks to the Kemper Team for constantly improving the KPA OS and RM, and providing everything for free to their customers!

    In order to help to improve things, here my current bug list for RM 3.1.62 (macOS 10.14.6), KPA OS 8.0.6, non-powered Head & Remote:

    1. Double-clicking a cab preset also engages effect in selected slot.
      To reproduce: Load a rig with a disengaged effect in slot C, select slot C in editor, and then double-click on any cab preset.
    2. Weird assignments to remote buttons when switching rigs while effects are locked (see attached photo).
      To reproduce: Load factory rig BM - Acoustic Fingerpick, lock all slots except for amp and cab, and then double-click on factory rig BM - B&H Filmo crunch.

    EDIT: Changed title to [FIXED]...

    • Bug 1: Fixed with OS8.2.2/RM3.2.30 (Thanks, Kemper Team!)
    • Bug 2: It's a feature! Whenever you lock a module with an assignment to a Remote button the lower right LED is lit. However, this doesn't hold true if there is more than one slot assigned to the button in question.