Korg Poly800/EX800 Users

Hi Poly fans,

It's very quiet around here lately so here is a little update to let you all know how the HAWK-800 software development is coming along.

At this point most of the features that have been promised have been delivered.

Some of the important sysex features added recently include the ability to send a sysex patch dump to the operating patch scratch memory (allowing real time editing of sounds without changing any actual saved patch).

Sequencer data sysex dump send and receive. Now you can send and receive sequences completely independent of patch dumps.

There are three global parameters that display counts of MIDI bytes sent and received as well as over run errors. This is very useful for checking that your MIDI rig is working.

Also, in parameter edit mode you can step back and forth between P1 and P2 editing using the step key (go from P2 to P1) and the prog/para key (go from P1 to P2). This makes editing patch parameters less tedious.

The two most important features that have not been delivered as yet are the arpeggiator and velocity sensitivity.

The good news is that a new version of the software is almost ready that will include velocity sensitive features.

You will be able to map VCF cutoff to velocity. This feature is already tested and working (and sounds sweet even if I do say so myself).

There will be two velocity "operators" that can be mapped to any two (different) EG parameters. This means you will be able to change EG1 attack or EG3 release or (almost) any other two EG parameters in between based upon incoming MIDI note velocity.

For both VCF and EG velocity, you can invert the behavior (less cut off with greater velocity or more cut off with greater velocity) and there are depth parameters that determine the velocity influence too.

The EG velocity sensitivity is in the closing stages of testing. Assuming that the testing shows no serious performance degradation then the software should be available within a week or so.

The arpeggiator is quite a complex task. First, the sequencer code has to be rewritten to handle different "modes". Second, the arpeggiator functions have to be decided and designed. And third, the arp code itself has to be written and tested. So the arp is going to take a while longer.

But, I think the velocity sensitivity should keep a lot of you happy for a while.

Cheers,

Mike.

Hi!

Sounds very cool! Looking forward to the update!

//JOJA

--- In korgpolyex@yahoogroups.com, "korgpolyex800" <korgpolyex800@...> wrote:
>
> Hi Poly fans,
>
> It's very quiet around here lately so here is a little update to let you all know how the HAWK-800 software development is coming along.
>
> At this point most of the features that have been promised have been delivered.
>
> Some of the important sysex features added recently include the ability to send a sysex patch dump to the operating patch scratch memory (allowing real time editing of sounds without changing any actual saved patch).
>
> Sequencer data sysex dump send and receive. Now you can send and receive sequences completely independent of patch dumps.
>
> There are three global parameters that display counts of MIDI bytes sent and received as well as over run errors. This is very useful for checking that your MIDI rig is working.
>
> Also, in parameter edit mode you can step back and forth between P1 and P2 editing using the step key (go from P2 to P1) and the prog/para key (go from P1 to P2). This makes editing patch parameters less tedious.
>
> The two most important features that have not been delivered as yet are the arpeggiator and velocity sensitivity.
>
> The good news is that a new version of the software is almost ready that will include velocity sensitive features.
>
> You will be able to map VCF cutoff to velocity. This feature is already tested and working (and sounds sweet even if I do say so myself).
>
> There will be two velocity "operators" that can be mapped to any two (different) EG parameters. This means you will be able to change EG1 attack or EG3 release or (almost) any other two EG parameters in between based upon incoming MIDI note velocity.
>
> For both VCF and EG velocity, you can invert the behavior (less cut off with greater velocity or more cut off with greater velocity) and there are depth parameters that determine the velocity influence too.
>
> The EG velocity sensitivity is in the closing stages of testing. Assuming that the testing shows no serious performance degradation then the software should be available within a week or so.
>
> The arpeggiator is quite a complex task. First, the sequencer code has to be rewritten to handle different "modes". Second, the arpeggiator functions have to be decided and designed. And third, the arp code itself has to be written and tested. So the arp is going to take a while longer.
>
> But, I think the velocity sensitivity should keep a lot of you happy for a while.
>
> Cheers,
>
> Mike.
>

That all sounds great, Michael! Unfortunately I haven't got around to installing my FM800 mod yet. Hoping to do that next week, and (fingers crossed) not wreck my EX-800 in the process.

Looking forward to all the new features once I've got that out of the way...

a|x

--- On Tue, 11/8/09, korgpolyex800 <korgpolyex800@...> wrote:

> From: korgpolyex800 <korgpolyex800@...>
> Subject: [korgpolyex] HAWK-800 - update
> To: korgpolyex@yahoogroups.com
> Date: Tuesday, 11 August, 2009, 4:25 PM
> Hi Poly fans,
>
> It's very quiet around here lately so here is a little
> update to let you all know how the HAWK-800 software
> development is coming along.
>
> At this point most of the features that have been promised
> have been delivered.
>
> Some of the important sysex features added recently include
> the ability to send a sysex patch dump to the operating
> patch scratch memory (allowing real time editing of sounds
> without changing any actual saved patch).
>
> Sequencer data sysex dump send and receive. Now you can
> send and receive sequences completely independent of patch
> dumps.
>
> There are three global parameters that display counts of
> MIDI bytes sent and received as well as over run errors.
> This is very useful for checking that your MIDI rig is
> working.
>
> Also, in parameter edit mode you can step back and forth
> between P1 and P2 editing using the step key (go from P2 to
> P1) and the prog/para key (go from P1 to P2). This makes
> editing patch parameters less tedious.
>
> The two most important features that have not been
> delivered as yet are the arpeggiator and velocity
> sensitivity.
>
> The good news is that a new version of the software is
> almost ready that will include velocity sensitive features.
>
> You will be able to map VCF cutoff to velocity. This
> feature is already tested and working (and sounds sweet even
> if I do say so myself).
>
> There will be two velocity "operators" that can be mapped
> to any two (different) EG parameters. This means you will be
> able to change EG1 attack or EG3 release or (almost) any
> other two EG parameters in between based upon incoming MIDI
> note velocity.
>
> For both VCF and EG velocity, you can invert the behavior
> (less cut off with greater velocity or more cut off with
> greater velocity) and there are depth parameters that
> determine the velocity influence too.
>
> The EG velocity sensitivity is in the closing stages of
> testing. Assuming that the testing shows no serious
> performance degradation then the software should be
> available within a week or so.
>
> The arpeggiator is quite a complex task. First, the
> sequencer code has to be rewritten to handle different
> "modes". Second, the arpeggiator functions have to be
> decided and designed. And third, the arp code itself has to
> be written and tested. So the arp is going to take a while
> longer.
>
> But, I think the velocity sensitivity should keep a lot of
> you happy for a while.
>
> Cheers,
>
> Mike.
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>     mailto:korgpolyex-fullfeatured@yahoogroups.com
>
>
>

Hi Mike,

Great news on the velocity and patch dump work!!!! I'm still working on getting my head around all these new features after installing the Hawk-800 and AtomaHawk kits in my Mark II. Not to fear circuit benders the AtomaHawk interfaced very nicely with all the front panel mods I already had installed! Mike, you thought out the wiring locations so well I only have one location that has 2 wires on it. Wow!

I sent you a review of the Hawk-800 kit installation and I still owe you the AtomaHawk install review. Hopefully they're not in the spam bucket...

Keep up all the awesome work. Meanwhile I need to get some patches written for the AtomaHawk Mark II to show off all these neat features.

Fran

Fran,

thanks for the props. I really appreciate it. Yes, I got your review/write up and am deciding how soon I can get a new web page put together to include it. If anyone is a web designer out there that would like to give me a bit of help to put a basic web page together please let me know.

I have another favor to ask of people. If any of you have a frequency counter I would like to know what the frequency of the RES7.5 clock is on your Poly. You can measure the signal at IC36 pin 7. This is the clock that determines the rate of the envelope generators.

The circuit description documentation says that this clock can be anywhere from 2,400 to 3,600 hz. Now that is a huge variation. If the variation is that big then alot of Poly 800 envelope generators are going to have faster or slower envelopes. Since I'm trying to implement velocity sensitivity, I really need to know what the clock is more likely to be. I know most of you don't have frequency counters but even a reading from a CRO would be enough.

Any and all help is much appreciated.

Mike.

--- In korgpolyex@yahoogroups.com, "narfman96" <narfman96@...> wrote:
>
> Hi Mike,
>
> Great news on the velocity and patch dump work!!!! I'm still working on getting my head around all these new features after installing the Hawk-800 and AtomaHawk kits in my Mark II. Not to fear circuit benders the AtomaHawk interfaced very nicely with all the front panel mods I already had installed! Mike, you thought out the wiring locations so well I only have one location that has 2 wires on it. Wow!
>
> I sent you a review of the Hawk-800 kit installation and I still owe you the AtomaHawk install review. Hopefully they're not in the spam bucket...
>
> Keep up all the awesome work. Meanwhile I need to get some patches written for the AtomaHawk Mark II to show off all these neat features.
>
> Fran
>

Hi Mike!

>I have another favor to ask of people. If any of you have a frequency counter I would like to know
>what the frequency of the RES7.5 clock is on your Poly. You can measure the signal at IC36 pin 7.
>This is the clock that determines the rate of the envelope generators.
>The circuit description documentation says that this clock can be anywhere from 2,400 to 3,600 hz.
>Now that is a huge variation. If the variation is that big then alot of Poly 800 envelope generators are
>going to have faster or slower envelopes. Since I'm trying to implement velocity sensitivity, I really
>need to know what the clock is more likely to be. I know most of you don't have frequency counters
>but even a reading from a CRO would be enough.
>Any and all help is much appreciated.

I opened my Poly800 Mk I and measured the frequency on Pin 7 of IC36 (TL072).

As both of my frequency counter are defect at the moment I had to measure the frequency with my DSOs built in
measurement routines: It is 2,94kHz
I crosschecked with the period time and its OK.

Ciao
Peter

http://come.to/synpro

Thanks for that. I really appreciate it.

2.9Khz is within the spec noted in the Poly documentation. But I wonder what everybody else has for a EG clock rate?

Mike.

--- In korgpolyex@yahoogroups.com, Ullrich Peter <peter.ullrich@...> wrote:
>
> Hi Mike!
>
> >I have another favor to ask of people. If any of you have a frequency counter I would like to know
> >what the frequency of the RES7.5 clock is on your Poly. You can measure the signal at IC36 pin 7.
> >This is the clock that determines the rate of the envelope generators.
> >The circuit description documentation says that this clock can be anywhere from 2,400 to 3,600 hz.
> >Now that is a huge variation. If the variation is that big then alot of Poly 800 envelope generators are
> >going to have faster or slower envelopes. Since I'm trying to implement velocity sensitivity, I really
> >need to know what the clock is more likely to be. I know most of you don't have frequency counters
> >but even a reading from a CRO would be enough.
> >Any and all help is much appreciated.
>
> I opened my Poly800 Mk I and measured the frequency on Pin 7 of IC36 (TL072).
>
> As both of my frequency counter are defect at the moment I had to measure the frequency with my DSOs built in
> measurement routines: It is 2,94kHz
> I crosschecked with the period time and its OK.
>
> Ciao
> Peter
>
> http://come.to/synpro
>

Hi Mike!

One of my frequency counter is working again: The exact frequency is 2878 Hz.

Ciao
Peter

http://come.to/synpro

________________________________________
Von: korgpolyex@yahoogroups.com [korgpolyex@yahoogroups.com] im Auftrag von korgpolyex800 [korgpolyex800@...]
Gesendet: Donnerstag, 13. August 2009 18:35
An: korgpolyex@yahoogroups.com
Betreff: [korgpolyex] Re: HAWK-800 - update

Thanks for that. I really appreciate it.

2.9Khz is within the spec noted in the Poly documentation. But I wonder what everybody else has for a EG clock rate?

Mike.

--- In korgpolyex@yahoogroups.com, Ullrich Peter <peter.ullrich@...> wrote:
>
> Hi Mike!
>
> >I have another favor to ask of people. If any of you have a frequency counter I would like to know
> >what the frequency of the RES7.5 clock is on your Poly. You can measure the signal at IC36 pin 7.
> >This is the clock that determines the rate of the envelope generators.
> >The circuit description documentation says that this clock can be anywhere from 2,400 to 3,600 hz.
> >Now that is a huge variation. If the variation is that big then alot of Poly 800 envelope generators are
> >going to have faster or slower envelopes. Since I'm trying to implement velocity sensitivity, I really
> >need to know what the clock is more likely to be. I know most of you don't have frequency counters
> >but even a reading from a CRO would be enough.
> >Any and all help is much appreciated.
>
> I opened my Poly800 Mk I and measured the frequency on Pin 7 of IC36 (TL072).
>
> As both of my frequency counter are defect at the moment I had to measure the frequency with my DSOs built in
> measurement routines: It is 2,94kHz
> I crosschecked with the period time and its OK.
>
> Ciao
> Peter
>
> http://come.to/synpro
>




------------------------------------

Yahoo! Groups Links



http://docs.yahoo.com/info/terms/