Yahoo Groups archive

Elektron Musical Instruments

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

Message

Re: [elektron] Re: afraid: monomachine vs. vsynth

2006-12-19 by Niall Munnelly

On Mon, Dec 18, 2006 at 07:43:45PM -0000, robotunes wrote:
> 
> joystick). combind with the "normal" sounds of the sk88 pro and the 
> sample mangling of the esx-1, i will extemporaneously create and 
> improvise over mid-tempo grooves and glitch-hop. this years-long dream 
> will be fulfilled with major helpf from the complex-but-not-
> complicated MnM.

Yup.  Make room for the MDUW, then.  I'm just sayin'.

> 1) what is the polyphony count for the midi sequencer? it's not in the 
> manual or on elektron.se. i've emailed elektron and posted the 
> question on their users forum, but if someone here knows the answer, 
> that would help.

Texmex answered your question on the web forum - cheers,
Texmex.

> 4) does using A LOT of parameter locks (i'll probably hit the max of 
> 62 on most of my patterns) throw off the timing of the sequencer or 
> cause latency with the machines? any affect on the midi sequencer 
> timing?

I did a standard deviation-based test of the Elektron clocks
some time ago that, while not as accurate as recording the
clock pulses as audio, was more than adequate to compare an
empty pattern with a _very_ busy one and their respective
clock output - there was no difference.  If parameter locks
were transmitted as CCs, then there might be a problem, but
I doubt it - further tests on the MIDI machines seem to
indicate that Elektron kit is programmed to give clock
priority over note events, which is as it should be.



-- 
Yours,
Niall.
.. .  .   .    .     .       .           .             .                 .
Aleph-Null.                             A Simple Insinuation Around Silence.
http://aleph-null.net
.. .. gpg public key - http://www.aleph-null.net/niall.gpg .. ..

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.