Xpantastic!

Hi,

In the modulation pages of the Xpander, it's possible to set a
quantize option to themodulation. The manual of the Xpander says,
"Quantizing cause semitone steps instead of a smooth change of an
Enveloppe, LFO, Lever or other modulation".

I did set quantize for some modulations of some patches, but I really
can not hear a difference in my sound.
I understand what a "semitone step" is if the modulation destination
is the VCO freq or detune, but what is the meaning for an enveloppe
attack or LFO speed ?

In the MIDI implementation, it's possible to enable/disable the
quantize thru a "Modulation edit follows" SysEx message (with
action=05h which is "set quantize on/off"). The same message with
action=06h is "toggle quantize N/A".
Does anybody knows what the difference is between this two messages ?
As far as I know, it's only possible to enable/disable the quantize
from the XPander panel.

Is a patch with a modulation quantize demo available somewhere ?

Thanks,
/Greg.

Hmm, that's an interesting question.
 
My guess is that applying quantize to ANY mod produces identical quantization as compared to a mod routing with the keyboard as the mod source with a mod amount of +63?
 
Randy

--- On Thu, 10/16/08, baumont987 <geebeex@...> wrote:

From: baumont987 <geebeex@...>
Subject: [xpantastic] demystifying the quantized modulation...
To: xpantastic@yahoogroups.com
Date: Thursday, October 16, 2008, 6:28 PM






Hi,

In the modulation pages of the Xpander, it's possible to set a
quantize option to themodulation. The manual of the Xpander says,
"Quantizing cause semitone steps instead of a smooth change of an
Enveloppe, LFO, Lever or other modulation".

I did set quantize for some modulations of some patches, but I really
can not hear a difference in my sound.
I understand what a "semitone step" is if the modulation destination
is the VCO freq or detune, but what is the meaning for an enveloppe
attack or LFO speed ?

In the MIDI implementation, it's possible to enable/disable the
quantize thru a "Modulation edit follows" SysEx message (with
action=05h which is "set quantize on/off"). The same message with
action=06h is "toggle quantize N/A".
Does anybody knows what the difference is between this two messages ?
As far as I know, it's only possible to enable/disable the quantize
from the XPander panel.

Is a patch with a modulation quantize demo available somewhere ?

Thanks,
/Greg.

> In the MIDI implementation, it's possible to enable/disable the
> quantize thru a "Modulation edit follows" SysEx message (with
> action=05h which is "set quantize on/off"). The same message with
> action=06h is "toggle quantize N/A".
> Does anybody knows what the difference is between this two messages ?
> As far as I know, it's only possible to enable/disable the quantize
> from the XPander panel.
>

How about sending one of those messages via midi, save the patches
(before/after the messages), to see which bit(s) are set or cleared
(if any).
Repeat with the other message.

I found the differences between these messages. It's only about how to
activate/desactivate the quantize:

- action=06h "toggle" simply toggles the actual quantize. If it's ON,
it will go OFF and vice-versa.
- action=05h is set quantize ON or set OFF. Is that simple :)

My question was more about what it does to the *sound*. I tried many
settings (just a VC0, and set quantize to a mod source for VC0 freq,
VCF freq and so on). I do not hear any difference between quantize ON
or OFF).

This was my question because I'm currently developping a real-time
control/programming software for the XPander. My program do send the
right SysEx message, but I wondered there where no differences in the
sound itself.

I looked into my SysEx presets and I did not found any preset with a
quantize modulation. strange.

Looks like this option is never used or does nothing at all (?)

/Greg

--- In xpantastic@yahoogroups.com, "Tony Cappellini" <cappy2112@...>
wrote:

>
> > In the MIDI implementation, it's possible to enable/disable the
> > quantize thru a "Modulation edit follows" SysEx message (with
> > action=05h which is "set quantize on/off"). The same message with
> > action=06h is "toggle quantize N/A".
> > Does anybody knows what the difference is between this two messages ?
> > As far as I know, it's only possible to enable/disable the quantize
> > from the XPander panel.
> >
> 
> How about sending one of those messages via midi, save the patches
> (before/after the messages), to see which bit(s) are set or cleared
> (if any).
> Repeat with the other message.
>

Hi,

I had to go through my patches to find some patchs using quatize.
It seems AFAIK the quantize function is most useful when modulating 
the frequency of a VCO. As you point out it is hardly noticable on 
other modulations.
You can quantize the lag modulations going to the VCOs  repete many 
times to get a large range. This gives a glisando sound Tomita used 
on Planets. " Turn the regular lag off in the main VCO page"
I have also found it useful to quatize square or tri wave LFOs 
modulating the VCO frequency. You can get a stepped series of notes 
in halfsteps.
If you feel ambitious try several LFOs all set to the same frequency.
Then adjust the re-trigger different for each LFO. This creates a 
programmable arpeggio.    
I remember using it once on a modulation of an LFO rate to sync 
things together. But I can't find this patch.  

Hope this helps

Karl









--- In xpantastic@yahoogroups.com, "baumont987" <geebeex@...> wrote:
>
> I found the differences between these messages. It's only about how 
to
> activate/desactivate the quantize:
> 
> - action=06h "toggle" simply toggles the actual quantize. If it's 
ON,
> it will go OFF and vice-versa.
> - action=05h is set quantize ON or set OFF. Is that simple :)
> 
> My question was more about what it does to the *sound*. I tried many
> settings (just a VC0, and set quantize to a mod source for VC0 freq,
> VCF freq and so on). I do not hear any difference between quantize 
ON
> or OFF).
> 
> This was my question because I'm currently developping a real-time
> control/programming software for the XPander. My program do send the
> right SysEx message, but I wondered there where no differences in 
the
> sound itself.
> 
> I looked into my SysEx presets and I did not found any preset with a
> quantize modulation. strange.
> 
> Looks like this option is never used or does nothing at all (?)
> 
> /Greg
> 
> --- In xpantastic@yahoogroups.com, "Tony Cappellini" <cappy2112@>
> wrote:
> >
> > > In the MIDI implementation, it's possible to enable/disable the
> > > quantize thru a "Modulation edit follows" SysEx message (with
> > > action=05h which is "set quantize on/off"). The same message 
with
> > > action=06h is "toggle quantize N/A".
> > > Does anybody knows what the difference is between this two 
messages ?
> > > As far as I know, it's only possible to enable/disable the 
quantize
> > > from the XPander panel.
> > >
> > 
> > How about sending one of those messages via midi, save the patches
> > (before/after the messages), to see which bit(s) are set or 
cleared

> > (if any).
> > Repeat with the other message.
> >
>

Karl,

Thank you for the tips, at least I can hear the quantize effect. I
reached my geek quest ;)


--- In xpantastic@yahoogroups.com, "Karl" <shire03@...> wrote:

>
> Hi,
> 
> I had to go through my patches to find some patchs using quatize.
> It seems AFAIK the quantize function is most useful when modulating 
> the frequency of a VCO. As you point out it is hardly noticable on 
> other modulations.
> You can quantize the lag modulations going to the VCOs  repete many 
> times to get a large range. This gives a glisando sound Tomita used 
> on Planets. " Turn the regular lag off in the main VCO page"
> I have also found it useful to quatize square or tri wave LFOs 
> modulating the VCO frequency. You can get a stepped series of notes 
> in halfsteps.
> If you feel ambitious try several LFOs all set to the same frequency.
> Then adjust the re-trigger different for each LFO. This creates a 
> programmable arpeggio.    
> I remember using it once on a modulation of an LFO rate to sync 
> things together. But I can't find this patch.  
> 
> Hope this helps
> 
> Karl
> 
> 
> 
> 
> 
> 
> 
> 
> 
> --- In xpantastic@yahoogroups.com, "baumont987" <geebeex@> wrote:
> >
> > I found the differences between these messages. It's only about how 
> to
> > activate/desactivate the quantize:
> > 
> > - action=06h "toggle" simply toggles the actual quantize. If it's 
> ON,
> > it will go OFF and vice-versa.
> > - action=05h is set quantize ON or set OFF. Is that simple :)
> > 
> > My question was more about what it does to the *sound*. I tried many
> > settings (just a VC0, and set quantize to a mod source for VC0 freq,
> > VCF freq and so on). I do not hear any difference between quantize 
> ON
> > or OFF).
> > 
> > This was my question because I'm currently developping a real-time
> > control/programming software for the XPander. My program do send the
> > right SysEx message, but I wondered there where no differences in 
> the
> > sound itself.
> > 
> > I looked into my SysEx presets and I did not found any preset with a
> > quantize modulation. strange.
> > 
> > Looks like this option is never used or does nothing at all (?)
> > 
> > /Greg
> > 
> > --- In xpantastic@yahoogroups.com, "Tony Cappellini" <cappy2112@>
> > wrote:
> > >
> > > > In the MIDI implementation, it's possible to enable/disable the
> > > > quantize thru a "Modulation edit follows" SysEx message (with
> > > > action=05h which is "set quantize on/off"). The same message 
> with
> > > > action=06h is "toggle quantize N/A".
> > > > Does anybody knows what the difference is between this two 
> messages ?
> > > > As far as I know, it's only possible to enable/disable the 
> quantize
> > > > from the XPander panel.
> > > >
> > > 
> > > How about sending one of those messages via midi, save the patches
> > > (before/after the messages), to see which bit(s) are set or 
> cleared
> > > (if any).
> > > Repeat with the other message.
> > >
> >
>