Emu XL-7 & MP-7 User's Group

I think I have something else that may be another, possibly better, way to
achieve what your trying to do. It will also I think point out potential
problems that could arise.

The arpeggiators in the XX-7 are really part of a preset and not a separate
or distinct component in the XX-7.  In other words for there to be any
arpeggiator operating there must also be an active internal synthesizer
channel.

The arpeggiator transmit MIDI setting (in the EDIT-ARP menu) when it is set
to "send MIDI" for the arpeggiation will *always* send the arp MIDI to the
external port and MIDI channel that corresponds to the internal synth
channel.  In other words channels 01A-16A will send on MIDI port A 1-16 and
internal synth channels 01B-16B will send on MIDI port B 1-16. This is
"hard-wired" so to speak.

This interlocking relationship between an arpeggiator and an internal
synthesizer channel can have some interesting implications.  The first is
that *any* arpeggio generated by the XX-7 will always have an internal
synthesizer channel active, and that channel *will make sound* unless it is
assigned a preset that makes no sound.  So if all you want to accomplish is
to have an external MIDI device play the arpeggiator by itself you must set
the corresponding internal synthesizer channel to be a silent preset like
the "default" preset.

An active arpeggiator on *any* internal synthesizer channel will always send
MIDI if the ARP transmit MIDI setting is on.  So it is not possible to have
some channels arpeggiating internally and some externally.  If this is what
you want to do, have two or more arpeggiators working together, say one
external and the other internal, you will need a work around such as
follows.

As mentioned the only way to disable the arpeggiator from sounding an
internal channel is to assign that channel a silent preset like "default".
An external MIDI device can be prevented from responding to the arpeggiator
information by either simply disabling that MIDI channel in it's
multi-timbral setup (most modules have this) or if that does not work assign
it a silent preset.  You will however loose the use of that MIDI channel.

[note that if you have some type of external MIDI router like a MIDI
patchbay or maybe something running in software you can create your own
routing that avoids these issues entirely]

If there is to be a lot of this type of usage, and you are only using a
single external module, or your total external module channels is sixteen or
less, consider hooking all of the external MIDI devices to MIDI output port
B on the XX-7.  Now you will be free to use internal-only arpeggiators on
internal channels 01A-16A without needlessly interfering with your external
MIDI modules.  When you want to use an arpeggiator on one of your external
MIDI devices you would simply assign the track to 01B-16B.

One last point about the use of the XX-7 arpeggiators.  If you want to use
the arpeggiator with a recorded track (for example a track of chords being
played) to play an arpeggiator to an external module you must set that
track's destination assignment to an internal synthesizer channel only, and
the channel must be assigned a silent preset.  The channel used would
correspond to the port and MIDI channel of your external module.  You should
not set the track destination to either EXT or BOTH. If you set it to EXT
you will only get the chords sent to the external device (no arpeggiation),
and when set to BOTH you will get both the chords and the arpeggiation.

All of this admittedly seems a bit convoluted and overly complex.  If you
remember though that the arpeggiator is really a special internal
synthesizer feature that "belongs" to an internal channel you will at least
be able to think through this complex maze.

Hopefully this will help if not now sometime in the future.


drk

www.delora.com/music
www.mp3.com/zdrk
drk.iuma.com


On 12/5/02 7:44 AM, "drK" <drk@...> wrote:

> Hi Sergio,
> 
> I think I have some more information that may help you with your arpeggiator
> playing external MIDI issue.
> 
> First, go into the EDIT-MIDI menu and make sure that the setting:
>  KEYBOARD OUTPUTS MIDI is set to "don't transmit"
> 
> Now find in the EDIT-MIDI menu the screen:
>  RECHANNELIZE INPUT and set it to "off"
> 
> This should solve your problem.
> 
> What I believe was happening was that with the RECHANNELIZE INPUT = ON the
> keyboard pads were always being sent to the active sequencer track.  if this
> track was an external MIDI track with an ARP assigned and on the arp was
> sending it's information and the rechannelization scheme in the XX-7 was
> also sending whatever notes were being held on the pads.  I believe the same
> would have happened from an external keyboard.
> 
> There is a diagram on page 318 of the latest manual that shows MIDI signal
> flow for the pads which should give you an idea what is happening.  Note
> that I believe there is an error in this chart as the pads are always sent
> through the keyboard assign channel regardless of where the MIDI info is
> sent.
> 
> Rechannelization is normally something you need when you want to use an
> external controller and have it automatically control the current active
> track. It makes an external controller behave like the XX-7's panel in that
> whatever current channel you have active will be the destination for the
> external controller.  Without this you have to change MIDI channels on the
> external controller in order to control the internal XX-7 synth.  The
> rechannelizer is also needed to re-rout an external controller to other
> external MIDI devices hooked up to the XX-7.  See page 319 for a diagram
> that should help make this clearer.
> 
> I replicated your symptoms and was able to get things working the way you
> are hoping for by doing the above steps.  let me know if this helps or not.
> 
> 
> drk
> 
> www.delora.com/music
> www.mp3.com/zdrk
> drk.iuma.com
> 
> 
> 
> On 12/4/02 12:37 PM, "Sergio Teixeira Jr." <steixeirajr@...> wrote:
> 
>> 
>> 
>> Just to make sure... The keyboard controller "feeding" the arps is
>> not also
>>> the sound module you are trying to control?  if it is then the
>> problem
>>> requires you to turn "local off" on your keyboard/synthesizer.
>> 
>> 
>> No. I'm playing the MP-7's pads and the arps are sent to a Korg
>> MS2000.
>> 
>> 
>>> What is confusing to me about your description is it is the
>> opposite of how
>>> the arps are supposed to work (and I have verified myself a while
>> back). pre-delay will play the held notes/chord to the synth the arp
>> is controlling
>>> during the duration of the predelay.  After which normal
>> arpeggiation will
>>> begin.
>> 
>> 
>> Let me try again. English is not my first language, but I sure i can
>> get this across. :)
>> 
>> 
>> 1. With pre delay set to off.
>> I play and hold a pad. The arpeggio runs perfectly, BUT the note I am
>> pressing keeps sounding "unarpeggiated" as well. The arpeggio *and*
>> the held note sound at the same time.
>> And this "unarpeggiated" sound is not coming from the MP-7, as the
>> corresponding channel is muted.
>> 
>> 2. With pre delayed turned on.
>> This unarpeggiated sound disappears (that's good) and the arpegiator
>> works fine. But then I am stuck with stuttering arpeggios, as there's
>> always this pre-delay. I don't want this. I want the arpeggios sent
>> to the MS2000 to sound the same as they do when I use the MP7's own
>> sounds.
>> 
>> 
>>> Also if you are using postdelay and recycle=on you will get the
>> notes
>>> playing again during the postdelay period.  At least that is the
>> way it
>>> usually works.
>> 
>> I'v gone through Post-delay and recycle in the manual, and they are
>> not related to my problem. I've tried all the possibilities and it
>> simply does not work.
>> 
>> Hope this clarifies the situation. I am looking forward to some help.
>> 
>> Cheers.
>> 
>> Sergio