Yahoo Groups archive

Doepfer

Index last updated: 2026-04-29 00:15 UTC

Message

Re: AW: [Doepfer_a100] RE: AW: a1065 SEM filter

2007-03-21 by Axel Jungkunst

I prefer also the mono version, looking at the AKS or similar solutions.
I never thought of a polyphonic TKB.
best regards
Axel

John schrieb:
>
> RELEASE THE MONO ONE!!!!!
>
> Regards,
> John
>
> On 3/21/07 12:24 PM, "hardware@doepfer.de 
> <mailto:hardware%40doepfer.de>" <hardware@doepfer.de 
> <mailto:hardware%40doepfer.de>> wrote:
>
> >
> >
> >
> >
> >> > And what about the Doepfer (Touch) Keyboard?
> >> >
> >> > David Westling
> >
> > I have been waiting already for this question :-)
> >
> > This is the current state: the TBK is working in principle (e.g. the 
> Sonic
> > State NAMM video 2006) but we we are not really pleased with the
> > functionality as the working principle we use (hum noise detection) 
> allows
> > only monophonic applications. It is not possible to touch a second 
> or third
> > key for polphonic application. Actually we wanted to built a polyphonic
> > device but we could not realize that with the hum noise principle. So we
> > have two alternatives: publish the TKB as it is or start the design 
> from the
> > beginning with another basic principle. In the first case the TKB 
> could be
> > publishes within 2-3 months as only the case has to be made. The 
> electronics
> > is working. If we have to start again I don't know how long it will take
> > until the polyphonic version will work as it should. Another 
> principle would
> > be the measurement of the skin resistance of the fingers. But for this
> > solution one has to touch an area of each "key" that has a copper 
> structure
> > like two nested combs very exactly.
> >
> > I think we will decide after the Frankfurt show how we continue.
> >
> > Best wishes
> > Dieter Doepfer
> >
> >
> >
>
> [Non-text portions of this message have been removed]
>
>

Attachments

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.