Archive of the former Yahoo!Groups mailing list: Korg Poly800/EX800 Users

previous by date index next by date
previous in topic topic list next in topic

Subject: Re: [korgpolyex] Velocity sensitive

From: Michael Hawkins <korgpolyex800@...>
Date: 2009-01-09

Notice how EG3 has a depth parameter which means that it is written into the code already. And that is because it is ONE EG to handle.

Trying to expand that function to all eight operating DCO's would be 8 times as much code and 8 times as much CPU cycles.

Yes, in retrospect, I should have done the same thing that the team that designed the Europa upgrade for the Jupiter-6 did. They removed the CPU and replaced it.

In the case of the Poly-800, I should have removed the CPU and dropped in one of those nice little ARM LINUX mini computers like the TS7200.

http://www.embeddedarm.com/products/arm-sbc.php#ts-7200-series

I would have written all of the code in C++ (my "native" language) and would never have to worry about CPU cycles ever again.

Oh well.

Mike.



From: Atom Smasher <atom@...>
To: korgpolyex@yahoogroups.com
Sent: Friday, January 9, 2009 5:36:46 PM
Subject: Re: [korgpolyex] Velocity sensitive

On Fri, 9 Jan 2009, Michael Hawkins wrote:

> Group 1 - technically simple and not CPU intensive
> Vel > filter cutoff
> Vel > resonance
> Vel > FM-800
> Vel > EG3 depth
============ =========

EG3 depth is on the simple list? can EG1/2 depth also be on this list, and
used together to implement velocity->volume?

> 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
============ ==

i dunno.... i think i can see vel->detune being useful... but if i can
control detune from a midi knob-box then i guess velocity control isn't
needed.

>
> 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'll agree with you about scrapping the last three.

> 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?
============ ======

for now, i'll sit out any ADBSSR/ADSR debates.

mike: next time you appraoch a project like this, do you think you'd
remove the CPU and put a new one on the expansion board?

--
...atom

____________ _________ ___
http://atom. smasher.org/
762A 3B98 A3C3 96C9 C6B7 582A B88D 52E4 D9F5 7808
------------ --------- --------- --------- --------- -

"The livestock sector emerges as one of the top two or
three most significant contributors to the most serious
environmental problems, at every scale from local to
global. The findings of this report suggest that it
should be a major policy focus when dealing with
problems of land degradation, climate change and air
pollution, water shortage and water pollution and loss
of biodiversity. "
-- Livestock's long shadow, 2006
UN report sponsored by WTO, EU, AS-AID, FAO, et al