KTR not tracking keys exactly

    • Topic
    • Voices
    • Posts
    • Last Post

Home Forums Instruments PULSAR-23 KTR not tracking keys exactly

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #18941 Reply

    amjes

      Hey, not sure if this is the intended behaviour or not, but when I use the midi keytracking it isn’t modulating on a note-to-note basis. I’ve tried it on multiple filters and the LFO, but even with the “Amount” knob maxed I’m only getting about 6-7 semitones over an octave at most. Is this the intended behaviour or are there some modules that should be tracking more closely?

      #18942 Reply

      subconscious0
      Participant

        Fair — switching to second person.

        Hey, not sure if this is intended behaviour or not, but when I use the MIDI key tracking it isn’t modulating on a note-to-note basis. I’ve tried it on multiple filters and the LFO, but even with the Amount knob maxed I’m only getting about 6-7 semitones over an octave at most. Is this the intended behaviour, or are there some modules that should be tracking more closely?

        Yes, this is expected — a couple of things stacked together are causing it.
        KTR isn’t 1V/oct. It outputs a CV proportional to MIDI note number, with the 0–10V range spread across a wide note span, so the volts-per-semitone is small by design. It’s a general parameter-follower, not a pitch CV. The only volt/octave logarithmic input on Pulsar is the BASS CV IN pin.
        The MOD inputs are linear, not logarithmic. The BD MOD is explicitly linear volt/hertz in the manual, and the filter and LFO MOD pins are linear scalings of the parameter underneath. So even if KTR were 1V/oct, feeding it into a filter MOD wouldn’t give you one octave of cutoff per octave played — a linear ramp into a linear input produces less and less perceived movement the higher you play, because each successive octave is a smaller fraction of the linear range. That’s the “tracking falls off” thing you’re hearing.
        AMT scales, it doesn’t multiply. Maxing it can’t make KTR swing more than KTR itself produces — it just attenuates down from full. If KTR is putting out ~2V across the notes you’re playing, max AMT gives you 2V of modulation and that’s it.
        If you want filter cutoff to follow pitch musically (one octave of cutoff per played octave), Pulsar doesn’t have a lin→exp converter sitting between KTR and the MOD inputs, so you can’t get it cleanly without something external doing that conversion. What you can do on the box: sum KTR with another mod source (envelope, a second MIDI CC routed through another MIDI→CV channel, SHAOS, LFO) into the same MOD pin to get more total range, or just use the BASS module where the pitch CV path is properly logarithmic.
        TL;DR: KTR + linear MOD = parameter follows note number roughly, not musical pitch. Working as designed.

      Viewing 2 posts - 1 through 2 (of 2 total)
      Reply To: KTR not tracking keys exactly
      Your information:




        Copyright by SOMA Laboratory (This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.) Privacy & Cookies Policy
        Right Menu Icon