Hi,
The KeyFol knob on Zebra's vcf filter does not seem behave as described in the manual - can anyone explain it better, or point out what I'm missing? (or does my zebra have a bug??)
As I understand, this knob (2nd knob from the right on the vcf) controls the ammount of cutoff modulation applied as you go higher up the keyboard. So, if I've got the filter's cutoff routed to env2, if I increase the keyfol knob, the modulation depth of this routing to env2 will steadily increase higher up they keyboard from E2 (and decrease below E2).
However, even if I don't have the filter's cutoff routed to any modulation source whatsoever, increasing the vcf's KeyFol knob seemingly affects the actual cutoff point of the filter (ie not just any modulation applied to it, which is what I understood it did), and uniformly across the entire keyboard; apparently E2 is the pivot key where nothing changes, but it certainly is affected by increasing KeyFol, as are the notes beneath it - the whole range of the keyboard gets brighter as you increase KeyFol. Also, what if you wanted negative values?
Contrast this with a use of KeyFol that I do understand: modulating the vcf's cutoff with KeyFol (ie right clicking on one of the vcf's "..." knobs and selecting KeyFol). Now here KeyFol makes perfect sense, behaves as the manual (and any synth tutorial on key tracking) says - the cutoff point of E2 is clearly not affected, and positive values gradually increase cutoff above this, reduce them below - negative values vice versa.
The vcf's KeyFol knob however behaves differently, is not bipolar, and doesn't seem to regard E2 as a "pivot" note? In fact, it really does seem to behave more like another "Cutoff" knob than a KeyTracking function.
So, bearing in mind that I do understand KeyFol in principle - and how to use KeyFol as a modulation source - can anyone explain what exactly the inbuilt KeyFol knob on the vcf does, and how it's meant to behave?
Thanks!
Zebra's vcf KeyFol knob (behaves very differently to KeyFol as modulation source)
-
alligatorlizard alligatorlizard https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=276868
- KVRist
- 133 posts since 14 Mar, 2012
-
alligatorlizard alligatorlizard https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=276868
- KVRist
- Topic Starter
- 133 posts since 14 Mar, 2012
Just bumping this old post, as it's still the one thing about Zebra that doesn't make sense, and is NOT explained in the manual.
Since originally posting this, I've got a lot more comfortable with programming synths (learning Diva and it's more limited options inside out helped) but am still still not sure what's going on with Zebra's VCF's KeyFol knob!!
To quickly re-iterate - using key follow as one of the modulation sources (r-click on one of the mod knobs on the VCF) makes perfect sense, and behaves as keytracking does on Diva etc. It uses E2 as pivot key, so is easy to work with.
BUT - the keyfol knob that's built into the VCF does not use E2 as pivot key (contrary to manual) - it raises cutoff over whole keyboard range.
So, I can just ignore this knob, and use keyfol as a modulation parameter instead - but I'm sure there is a reason for this knob, and a reason why it's different? Could anyone explain??
Since originally posting this, I've got a lot more comfortable with programming synths (learning Diva and it's more limited options inside out helped) but am still still not sure what's going on with Zebra's VCF's KeyFol knob!!
To quickly re-iterate - using key follow as one of the modulation sources (r-click on one of the mod knobs on the VCF) makes perfect sense, and behaves as keytracking does on Diva etc. It uses E2 as pivot key, so is easy to work with.
BUT - the keyfol knob that's built into the VCF does not use E2 as pivot key (contrary to manual) - it raises cutoff over whole keyboard range.
So, I can just ignore this knob, and use keyfol as a modulation parameter instead - but I'm sure there is a reason for this knob, and a reason why it's different? Could anyone explain??
-
- KVRAF
- 24448 posts since 7 Jan, 2009 from Croatia
VCF Keyfollow does NOT apply to the cutoff modulation amount - it applies to cutoff knob directly. That's how it's meant to work.
-
- u-he
- 30222 posts since 8 Aug, 2002 from Berlin
I think the breakpoint in Zebra is generally at MIDI Note 0, such that Cutoff at 0 (or 12, or 24, don't recall) with Keyfollow at 100% gives you full tracking.
I think the easter egg filters (MS20/TyrellN6) have their breakpoint at middle E (Note 64), but we left it that way after we left them in.
I think the easter egg filters (MS20/TyrellN6) have their breakpoint at middle E (Note 64), but we left it that way after we left them in.
-
- KVRAF
- 4197 posts since 23 May, 2004 from Bad Vilbel, Germany
Ah yes, you misunderstood, and I can see why (at a pinch). Here's the original sentence in the manual:alligatorlizard wrote:The KeyFol knob on Zebra's vcf filter does not seem behave as described in the manual - can anyone explain it better, or point out what I'm missing? (or does my zebra have a bug??)
As I understand, this knob (2nd knob from the right on the vcf) controls the ammount of cutoff modulation applied as you go higher up the keyboard.
"The ‘key follow’ parameter controls the amount of cutoff modulation from MIDI note / keyboard – the higher the note, the higher the cutoff."
How about this? It is simpler:
"The ‘key follow’ parameter adjusts how strongly the cutoff follows MIDI notes (the higher the note, the higher the cutoff)."
Also: "Note that the breakpoint (the key that doesn’t change) in KeyF is E2." doesn't apply to the dedicated KeyF parameter. Will fix that in the manual.