Yahoo Groups archive

MOTM

Index last updated: 2026-04-28 23:35 UTC

Thread

Kenton Pro2000 Modes

Kenton Pro2000 Modes

2000-02-21 by Paul Schreiber

Larry -

I think you need to look at the Kenton manual some more. I'm 99.99% sure you
can
set both A & B to the same channel. There are also 'Note Priority' settings
as Newest, Lowest,
and Highest. The Newest make the most "sense" in playing. If you hold down a
note, keep it down,
that "voice" does NOT get re-assigned as other notes are play (called "note
stealing").

There is a BIG difference between playing *polyphonically* and
*multi-timbrally*.

Paul S.

Re: Kenton Pro2000 Modes

2000-02-22 by Paul Schreiber

> Yes, you are right Paul.  You can set them to the same channel.  However,
> that does not help unless I am missing the obvious.  If both A and B are
> set to the same channel, newest, then any new note played on the keyboard
> on the selected channel will trigger both A and B.  So, A and B will
always
> sounding the same note if placed on the same channel.  One can set A to
> "highest" and B to "lowest" to give a two note poly anytime two notes were
> being played on that channel.  However, if only one note was being played,
> both voices would sound (as highest and lowest would be the same.

I think that's wrong. Playing 1 note at a time is "Lowest", the "Highest"
doesn't
GATE. Have you tried this?

Paul S.

Re: Kenton Pro2000 Modes

2000-02-22 by J. Larry Hendry

> From: "Paul Schreiber" <synth1@...>
> 
> I think you need to look at the Kenton manual some more.
> I'm 99.99% sure you can set both A & B to the same channel.
> There are also 'Note Priority' settings as Newest, Lowest,
> and Highest. The Newest make the most "sense" in playing.
> If you hold down a note, keep it down, that "voice" does
> NOT get re-assigned as other notes are play (called "note
> stealing").

Yes, you are right Paul.  You can set them to the same channel.  However,
that does not help unless I am missing the obvious.  If both A and B are
set to the same channel, newest, then any new note played on the keyboard
on the selected channel will trigger both A and B.  So, A and B will always
sounding the same note if placed on the same channel.  One can set A to
"highest" and B to "lowest" to give a two note poly anytime two notes were
being played on that channel.  However, if only one note was being played,
both voices would sound (as highest and lowest would be the same.

> There is a BIG difference between playing *polyphonically* and

Of course, I am referring to polyphonically.  However, the nature of MOTM
is that any polyphonically is multi-timbrally as each voice is independent
modules.  However, lets say for the sake of discussion, I want a two voice
chord track.  I can get the two separate CVs from the same channel by
setting A and B to the same channel.  However, the GATE out 1 and 2 are
identical.  So, you can have 2 voltages, bit trigger only one envelope. 
And, if you try to do this with triggers out too on the auxes, you will
find that trigger B does nothing when assigned to the same channel as A.

I do know how to get 5 voices of multi-timbrally from the Kenton CV+gate
sending notes on 5 different channels from my keyboard.  However, the
obvious flaw for polyphonic chords is seen there since one would never know
where to split the keyboard for polyphonic operation.  So,  multi-timbrally
is easy, polyphonic however, is a challenge.

Larry H

Re: Kenton Pro2000 Modes

2000-02-22 by J. Larry Hendry

> From: "Paul Schreiber" <synth1@...>
> 
> I think that's wrong. Playing 1 note at a time is "Lowest", the "Highest"
> doesn't
> GATE. Have you tried this?

Yes, I have tried briefly. The note assign does not matter if you play one
note at a time.  However, if you assign "newest" A and B will always output
the same gate and same CV.  If you assign one to lowest and one to highest,
A and B will output two different CVs, but the gates out of A and B will be
the same.

LH

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.