Korg Poly800/EX800 Users group photo

Yahoo Groups archive

Korg Poly800/EX800 Users

Index last updated: 2026-04-13 23:51 UTC

Message

Re: [korgpolyex] Velocity sensitive

2009-01-09 by Alex Drinkwater

And I'd add (again)
EG3 decay (though I'm aware that would only be useful with certain  
Breakpoint/Slope setting, I still think it would be nice to get a  
'twangier', tighter envelope on bass sounds with higher velocity, for  
example).
Otherwise the list looks good to me.

a|x



On 9 Jan 2009, at 20:16, Michael Hawkins wrote:

> Which MG depth? DCO or VCF, resonance MG or FM-800 MG?
>
> The list could get so long that there's no way the Poly has the  
> cycles to handle it.
>
> In fact, I really think the Poly is probably only capable of  
> handling one at a time. Otherwise, Poly notes will sound half an  
> hour after they were hit.
>
> So I have split the velocity features into two groups.
>
> Group 1 - technically simple and not CPU intensive
> Vel > filter cutoff
> Vel > resonance
> Vel > FM-800
> Vel > EG3 depth
> Vel > VCF MG depth
> Vel > DCO MG depth
> Vel > harmonics mapping
> Vel > oscillator detune - *** I doubt I would ever use this  - vote  
> to remove from list
>
> Group2  - technically complex and CPU intensive
> Vel > EG1/2 attack
> Vel > EG1/2 decay
> Vel > EG1/2 release
> Vel > LFO speed - *** I doubt I would ever use this - vote to remove  
> from list
> Vel > LFO waveform change - *** I doubt I would ever use this - vote  
> to remove from list
> Vel > oscillator interval - *** I doubt I would ever use this - vote  
> to remove from list
>
> I am working on other features at the moment so there is no rush to  
> get this all agreed upon in a day or two but I would like to see  
> everyone put their two cents in and work on this list.
>
> Another thing that is out floating right now is getting EG4 created  
> and working. I am beginning to think that there simply won't be  
> enough CPU cycles to do it at all. One way to get CPU cycles back  
> would be to change the EG's into ADSR instead of the ADBSSR Korg  
> type. Who would be disappointed if we just made them into ADSR?
>
> Mike.
>
> From: "electrohead2000@..." <electrohead2000@...>
> To: "korgpolyex@yahoogroups.com" <korgpolyex@yahoogroups.com>
> Sent: Friday, January 9, 2009 1:52:54 PM
> Subject: Re: [korgpolyex] Velocity sensitive
>
>
> Your priority list looks good. Has anyone mentioned Velocity > MG  
> depth?
> Also, I might have missed something earlier, does the Hawk kit  
> disable the sequencer?
>
>
> On Jan 9, 2009, at 1:37 PM, Michael Hawkins <korgpolyex800@  
> yahoo.com> wrote:
>
>>
>> The only part of this list that is not doable given the CPU cycle  
>> constraints is probably the one most ppl might want the most which  
>> is...
>>
>> Velocity to Amplitude. I can't do this because it would require a  
>> massive rewrite of the code and a massive increase in CPU cycles  
>> (of which there none to be had). I don't think it's worth doing  
>> break point, sustain level etc and the math is so complex, I don't  
>> think I want to take it on anyway.
>>
>> The rest I will parse through and think about, although most of  
>> them look doable on immediate examination.
>>
>> What's more important though, is that everyone that has a HAWK kit  
>> now should try to put all of these into some sort of priority.
>>
>> So here I post the list again (with my suggested priority) but now  
>> can people reorder them and see if we can come up with a consensus  
>> on what should be done first.
>>
>> Vel > filter cutoff
>> Vel > resonance
>> Vel > FM-800
>> Vel > EG1/2 attack
>> Vel > EG1/2 decay
>> Vel > harmonics mapping
>> Vel > oscillator interval
>> Vel > oscillator detune
>> Vel > LFO speed
>> Vel > LFO wave change
>> Vel > EG1/2 release
>>
>> Mike.
>>
>> From: David Mochen <davidmochen@ hotmail.com>
>> To: korgpolyex@yahoogro ups.com
>> Sent: Friday, January 9, 2009 1:06:51 PM
>> Subject: Re: [korgpolyex] best hardware arpeggiator
>>
>>
>> Hi,
>>
>> *Vel > Eg 1, 2, 3, and 4 Amplitude (not sure if this is the best  
>> techie way to describe it but, basically, the harder you hit, the  
>> louder it sounds/the more the VCF opens up/the more EG4 affects  
>> global pitch/noise)
>>
>> *Vel > all EG steps (att, dec, brk p, slope, sus, rel) or at least  
>> some of them
>>
>> *Vel > filter cutoff and reso
>>
>> *Vel > FM-800
>>
>> *Vel > oscillator interval
>>
>> *Vel > oscillator detune
>>
>> *Vel > LFO speed
>>
>> *Vel > LFO wave change
>>
>> *Vel > "muting/unmuting" the different harmonics? Say, play  
>> lightly, only first harmonic is heard... play harder, a more  
>> sawtooth-like sound
>> is heard as the remaninig 3 harmonics are engaged. Dunno if it is  
>> feasible, though.
>>
>> (if any other ideas come to me, i'll let you know)
>>
>> BTW, all the above should be possible to be assigned both positive  
>> and negative modulation on the targets. Also, some sort of keyboard  
>> tracking would be cool.
>>
>> Who knows? maybe the Atomahawk 800 will end up as a poor-man  
>> Oberheim Matrix 12? Ha, it feels so nice just asking The Man for  
>> more... like a kid in a candy store...
>>
>> dave
>>
>> ----- Original Message -----
>> From: Michael Hawkins
>> To: korgpolyex@yahoogro ups.com
>> Sent: Friday, January 09, 2009 10:45 AM
>> Subject: Re: [korgpolyex] best hardware arpeggiator
>>
>>
>> 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.
>>
>> 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?
>>
>> 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?
>>
>> Mike
>>
>>
>>
>> From: David Mochen <davidmochen@ hotmail.com>
>> To: korgpolyex@yahoogro ups.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
>>
>>
>>
>>
>> Messages in this topic (1) Reply (via web post) | Start a new topic
>> MARKETPLACE
>> From kitchen basics to easy recipes - join the Group from Kraft Foods
>> Recent Activity
>>  3
>> New Members
>> Visit Your Group
>> Yahoo! News
>> Get it all here
>>
>> Breaking news to
>>
>> entertainment news
>>
>> Group Charity
>>
>
>
>

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.