Korg Poly800/EX800 Users group photo

Yahoo Groups archive

Korg Poly800/EX800 Users

Index last updated: 2026-04-05 20:10 UTC

Message

Re: [korgpolyex] best hardware arpeggiator

2009-01-09 by Alex Drinkwater


On 9 Jan 2009, at 13:45, Michael Hawkins wrote:

OK, this is great feedback.

I've been making good progress going back over my code and collapsing certain parts of it into reusable functions so that the memory use is actually dropping right now.

Cool! More room for new stuff, then!

I also have been thinking about the ARP too. It is not on the top of my list that is for sure. I think a simple ARP is a good idea for those of us who don't use computers or a hardware sequencer. But how many of us are in that position?

I use several different computer-based sequencers.

Since I was able to get the sustain pedal working and actually change the EG1/2 sustain in real time according to the pedal, it is now quite possible to change any part of the EG parameters according to velocity.

I believe I can do the same for EG3.

So I can see that altering attack on EG1/2 or EG3 might be things we'd like to change according to velocity.

What other parameters might we want changed according to velocity?

EG3 Decay
Filter Cutoff
Resonance
EG3 Env. Depth

...would be my top picks, with the option of having velocity modulate target values in either direction (ie higher velocity to higher cuttoff, or higher velocity to lower cutoff etc.).

Velocity to LFO depth or rate might be fun, too, actually.

a|x




Mike



From: David Mochen <davidmochen@...>
To: korgpolyex@yahoogroups.com
Sent: Friday, January 9, 2009 9:09:53 AM
Subject: Re: [korgpolyex] best hardware arpeggiator


i'd say the HAWK-800 is well on the way to "killer" without a sequencer or
arpeggiator. somewhat disregarding my own personal wish-list (LCD & sysex
for panel events), i think velocity sensitivity is the *only* thing the
kit is "missing".

--
...atom
100% agree.
Dave


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.