Question about the kit
2008-02-04 by honod3k
Yahoo Groups archive
Index last updated: 2026-04-28 23:27 UTC
Thread
2008-02-04 by honod3k
If I hold off on doing the moogslayer mod, will those functions be controllable via MIDI CC's with the kit, or is doing the mod a necessity to get that capability?
2008-02-04 by korgpolyex800
This is the million dollar question. The answer is - probably. That is, I do intend to control the moogslayer via the kit. However, I've not done this yet but I plan to test it within a month or two. So if you can wait a month or two I'll have a better answer then. Mike. --- In korgpolyex@yahoogroups.com, "honod3k" <cbluff@...> wrote:
> > If I hold off on doing the moogslayer mod, will those functions be > controllable via MIDI CC's with the kit, or is doing the mod a > necessity to get that capability? >
2008-02-05 by Russ
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.
2008-02-05 by korgpolyex800
Hi Russ, Yes, I have added a prototyping area onto the board that I designed so that I could add additional control chips. So the idea is to add a digital potentiometer chip or two or more along with the latching logic needed to make the moogslayer mod a part of the kit. So it has a hardware and software element to it. That's why I haven't got to it yet. Mike. --- In korgpolyex@yahoogroups.com, Russ <russdaren@...> wrote: > > The moogslayer routs additional voltage to the filter so its not something that can really be implemented in software as far as I understand. you can already of course vary the amount of filter and cutoff in the preset which DOES affect the amount of moogslayerishness that happens. I am tempted to dig in there myslef and figure if there is a way to make a mix knob. So I could bring down the amount of filter relative to the DCO's > . > > --------------------------------- > Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. >
2008-02-06 by Russ
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.
2008-02-07 by korgpolyex800
I'm no rocket scientist but I did stay at a Holiday Inn once. LOL But seriously, your suggestion of a third oscillator is a good one. The problem in the end is going to be two fold. First, how much time do I/we intend to spend programming this thing and second, how many CPU cycles can you squeeze out of an 8 bit microprocessor running at 3Mhz. That's right - 3 megahertz. Although we can add quite a few digital pot's, the real time operations required to control them requires a certain amount of CPU cycles - cycles that are running out fast. As it is right now, I've discovered that some of my code is already big enough that it causes the envelope generators to slow down. I don't think that's something that I'm worried about too much because you can always speed things up again with a little tweak of the EG's but I now know that there are distinct limitations as to what we're going to be able to do. The more we add, the more likely we run out of CPU. The good news is that I got two Super LFO's working yesterday with triangle, sawtooth, sine and stepped triangle (based on a waveform lookup table). Plus, all of them can be inverted so that they first sweep down instead of up. The frequency is adjustable from about 4hz thru to a 20 second cycle. The plan is to apply these waveforms to the LFO1 and or LFO2 frequency, depth and baseline. And also make them available to the VCF cutoff and resonance levels. This is going to take quite a bit of time to do though because the mathematics is a little tricky and the CPU is pretty busy already. I have to write the code as efficiently as I possibly can. And it's no easy task for this amateur. So at this point, I am probably going to try to get the SLFO's working and later work on send the LFO's or EG3 to the moog slayer. But that may be the last thing we can squeeze out of the real time code. That's not to say that there are not a lot of other things to do. For starters, I have got to get to work on the arpeggiator. Since the arpeggiator is not nearly so CPU intensive as the real time sound generation it should be no problem to make it quite sophisticated. And then there are the many MIDI CC's that need to be added for all of the parameters. That's also something that won't take many CPU cycles. So there's still a lot to do and much fun to be had. PS: I have seriously contemplated replacing the LED display with a backlit LCD but I refuse to do it since it just wouldn't be the Poly 800 of the 1980's anymore. Mike. --- In korgpolyex@yahoogroups.com, Russ <russdaren@...> wrote: > > wow thats pretty impressive! What are you doing for a living? Rocket Scientist? I mean really, you seem to have thought of everything! > I am really interested in this digital pot/latching function > especially if we can just wire it up as we see fit. Might make for some interesting hybridized 800s. Maybe add a 3rd osc? I am sure there is a way to bridge it in there electronically. And if your gizmo provides the means to make it controlable. Wow. > Gosh you are going to add so many functions to the beasty it may need a 4th LED display! > > > --------------------------------- > Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. >
2008-02-07 by Alan Currall
Hi there, MikeThe LFO thing sounds damn good to me. And yes, we shouldn't expect the Poly 800 to sound/behave like a Matrix 12. You're already doing a lot to improve it, but the temptation to ask more and more from you is difficult to fight... good thing you know where you stand.thanksDave----- Original Message -----From: korgpolyex800Sent: Thursday, February 07, 2008 10:31 AMSubject: [korgpolyex] Re:Moogslayer and the kit...I'm no rocket scientist but I did stay at a Holiday Inn once. LOL
But seriously, your suggestion of a third oscillator is a good one.
The problem in the end is going to be two fold. First, how much time
do I/we intend to spend programming this thing and second, how many
CPU cycles can you squeeze out of an 8 bit microprocessor running at
3Mhz. That's right - 3 megahertz. Although we can add quite a few
digital pot's, the real time operations required to control them
requires a certain amount of CPU cycles - cycles that are running out
fast.
As it is right now, I've discovered that some of my code is already
big enough that it causes the envelope generators to slow down. I
don't think that's something that I'm worried about too much because
you can always speed things up again with a little tweak of the EG's
but I now know that there are distinct limitations as to what we're
going to be able to do. The more we add, the more likely we run out of
CPU.
The good news is that I got two Super LFO's working yesterday with
triangle, sawtooth, sine and stepped triangle (based on a waveform
lookup table). Plus, all of them can be inverted so that they first
sweep down instead of up. The frequency is adjustable from about 4hz
thru to a 20 second cycle. The plan is to apply these waveforms to the
LFO1 and or LFO2 frequency, depth and baseline. And also make them
available to the VCF cutoff and resonance levels. This is going to
take quite a bit of time to do though because the mathematics is a
little tricky and the CPU is pretty busy already. I have to write the
code as efficiently as I possibly can. And it's no easy task for this
amateur.
So at this point, I am probably going to try to get the SLFO's working
and later work on send the LFO's or EG3 to the moog slayer. But that
may be the last thing we can squeeze out of the real time code.
That's not to say that there are not a lot of other things to do. For
starters, I have got to get to work on the arpeggiator. Since the
arpeggiator is not nearly so CPU intensive as the real time sound
generation it should be no problem to make it quite sophisticated.
And then there are the many MIDI CC's that need to be added for all of
the parameters. That's also something that won't take many CPU cycles.
So there's still a lot to do and much fun to be had.
PS: I have seriously contemplated replacing the LED display with a
backlit LCD but I refuse to do it since it just wouldn't be the Poly
800 of the 1980's anymore.
Mike.
--- In korgpolyex@yahoogroups.com, Russ <russdaren@...> wrote:
>
> wow thats pretty impressive! What are you doing for a living? Rocket
Scientist? I mean really, you seem to have thought of everything!
> I am really interested in this digital pot/latching function
> especially if we can just wire it up as we see fit. Might make for
some interesting hybridized 800s. Maybe add a 3rd osc? I am sure
there is a way to bridge it in there electronically. And if your gizmo
provides the means to make it controlable. Wow.
> Gosh you are going to add so many functions to the beasty it may
need a 4th LED display!
>
>
> ---------------------------------
> Be a better friend, newshound, and know-it-all with Yahoo! Mobile.
Try it now.
>
2008-02-07 by David Mochen
----- Original Message -----From: korgpolyex800Sent: Thursday, February 07, 2008 10:31 AMSubject: [korgpolyex] Re:Moogslayer and the kit...I'm no rocket scientist but I did stay at a Holiday Inn once. LOL
But seriously, your suggestion of a third oscillator is a good one.
The problem in the end is going to be two fold. First, how much time
do I/we intend to spend programming this thing and second, how many
CPU cycles can you squeeze out of an 8 bit microprocessor running at
3Mhz. That's right - 3 megahertz. Although we can add quite a few
digital pot's, the real time operations required to control them
requires a certain amount of CPU cycles - cycles that are running out
fast.
As it is right now, I've discovered that some of my code is already
big enough that it causes the envelope generators to slow down. I
don't think that's something that I'm worried about too much because
you can always speed things up again with a little tweak of the EG's
but I now know that there are distinct limitations as to what we're
going to be able to do. The more we add, the more likely we run out of
CPU.
The good news is that I got two Super LFO's working yesterday with
triangle, sawtooth, sine and stepped triangle (based on a waveform
lookup table). Plus, all of them can be inverted so that they first
sweep down instead of up. The frequency is adjustable from about 4hz
thru to a 20 second cycle. The plan is to apply these waveforms to the
LFO1 and or LFO2 frequency, depth and baseline. And also make them
available to the VCF cutoff and resonance levels. This is going to
take quite a bit of time to do though because the mathematics is a
little tricky and the CPU is pretty busy already. I have to write the
code as efficiently as I possibly can. And it's no easy task for this
amateur.
So at this point, I am probably going to try to get the SLFO's working
and later work on send the LFO's or EG3 to the moog slayer. But that
may be the last thing we can squeeze out of the real time code.
That's not to say that there are not a lot of other things to do. For
starters, I have got to get to work on the arpeggiator. Since the
arpeggiator is not nearly so CPU intensive as the real time sound
generation it should be no problem to make it quite sophisticated.
And then there are the many MIDI CC's that need to be added for all of
the parameters. That's also something that won't take many CPU cycles.
So there's still a lot to do and much fun to be had.
PS: I have seriously contemplated replacing the LED display with a
backlit LCD but I refuse to do it since it just wouldn't be the Poly
800 of the 1980's anymore.
Mike.
--- In korgpolyex@yahoogroups.com, Russ ..> wrote:
>
> wow thats pretty impressive! What are you doing for a living? Rocket
Scientist? I mean really, you seem to have thought of everything!
> I am really interested in this digital pot/latching function
> especially if we can just wire it up as we see fit. Might make for
some interesting hybridized 800s. Maybe add a 3rd osc? I am sure
there is a way to bridge it in there electronically. And if your gizmo
provides the means to make it controlable. Wow.
> Gosh you are going to add so many functions to the beasty it may
need a 4th LED display!
>
>
> ---------------------------------
> Be a better friend, newshound, and know-it-all with Yahoo! Mobile.
Try it now.
>