Yahoo Groups archive

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

Index last updated: 2026-04-29 00:09 UTC

Thread

Arp bug here too?

Arp bug here too?

2002-09-24 by erik_magrini@Baxter.com

Ok, I think I may have run across that Arp bug that Nick was mentioning, 
though I'm not sure if it's the same thing he's talking about.  Here's the 
situation.

I sat down last night to try again at making my own Custom arps and 
Presets to help me with getting around the lack of "RPS" features.  After 
waiting to see if we'd get a simlar feature in new OS update, I realized I 
can't keep waiting on that (since it might never happen), I need to find a 
workaround, or I'm just gonna have to get something else that will suit my 
live needs. 

I wanted to make 16 new Presets, each of which would be assigned a 
seperate Trigger Button (1-16) and Midi Channel (1-16B).  The goal was to 
create 4 different "kits' that I could interchange live as I saw fit, and 
to add some variety while switching patterns.  It was set up like this:

Trigger/MIDI 'B' channel 
1 - BD
2- Snare
3- HH
4- Perc
5- BD2
6- Snare2
7- HH2
8- Perc2
9- BD3
10- Snare3
11- HH3
12- Perc3
13- BD4
14- Snare4
15- HH4
16- Perc4

Everything was going great at first, I created 16 different Presets, saved 
them with the above names, assigned each to the appropriate B-MIDI 
channel, then saved the Multi.  I next went and copied a blank User Arp 16 
times making sure to make the name them the same as their associated 
Preset. 

The first trouble began when no matter what Global, COntroller or MIDI 
settings I changed, I couldn't use the key pads to play back the B channel 
Presets, until I played a previous recorded Pattern first.  Weird, and it 
made me wonder what I was really hearing, even though the Preset was still 
the same according to the Preset Display.  Editing the arps and saving 
them seemed to go ok, I made each arp play back the associated Presets (or 
rather I should say I assigned the arp to correct Preset), and programmed 
each step to be offset by 0, so that I could assign the actual drum sound 
(Note Number) via the Controllers Trigger menu.

And that was where I ran into my problems, changing the Note Number in the 
Controller menu didn't actually reflect the right sound in the Drum 
Preset.  I could even use the keypads to assign the correct note in the 
Controller Triggers screen, and it would sound fine as I played it that 
way.  However, as soon as I actually used the Triggers, the sound being 
played back wasn't the same at all.  To make sure I even fired up the PC 
and used SX (as well as E-Loader 1.0's MIDI monitor) to double check I had 
the right note numbers assigned.  I'd play the keypads until I heard the 
sound I wanted, then assigned that Note to be triggered by the Trigger 
button in the Controllers menu.  It sounded like it was playing the right 
Preset (hard to tell really, so many are similar sounding), just not the 
right note numbers.  I'd back out of the controller menu, try again, still 
no luck.  I'd press C2, hear the sound I wanted, then assign that Trigger 
to play that note.  Yet the Trigger wasn't playing back that note at all!

Ideas? Did I explain that cleary enough?  Is this what you were seeing 
Nick?

This really sucks, even a feasible work around isn't umm....working!
rEalm

Re: [xl7] Arp bug here too?

2002-09-24 by Aaron Eppolito

--- erik_magrini@... wrote:
> Ok, I think I may have run across that Arp bug

Well, you already know that it's not Nick's bug (which I should
probably confirm as a bug by the way - I checked and it is most
certainly the case that Extension Interval gets picked up from the
*prviously* selected preset - good catch Nick).

I just did a quick test to try your thing rEalm, and I think you may be
running into problems with rechannelization.  Make sure you set the
channel explicitly in the Triggers menu instead of setting it to Basic
(you probably already did that).  Also, you might want to turn
rechannelization off because if no sequencer track is set to use the
"B" channel you're working on, you can switch to that B channel on the
preset screen, but the keyboard will still be on some other channel
(specificly, the last channel selected that actually had a track
assigned to it).

So, I think what's happening is that your keypads are playing one
channel, and the triggers are playing a different one.  Oh, note also
that the selection or channel for the keypads in the controllers menu
is overriden by rechannelize, so if you're using that to set channel
with rechannelize on, it won't do anything.

-Aaron

__________________________________________________
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
http://sbc.yahoo.com

Re: [xl7] Arp bug here too?

2002-09-24 by erik_magrini@Baxter.com

I just did a quick test to try your thing rEalm, and I think you may be 
running into problems with rechannelization.  Make sure you set the 
channel explicitly in the Triggers menu instead of setting it to Basic 
(you probably already did that). 

>>>Yep, did that already. <<<

Also, you might want to turn rechannelization off because if no sequencer 
track is set to use the "B" channel you're working on, you can switch to 
that B channel on the preset screen, but the keyboard will still be on 
some other channel (specificly, the last channel selected that actually 
had a track assigned to it).

>>>Ah, that makes sense. I set up my XL-7 so that Pattern 000:0 is a 
default one with all A channels set to the Default Preset (the very last 
one in the Preset menu). So I can see why nothing would sound in this case 
upon first powering up.  I'll turn off rechannelize tonight and try that. 
<<<

So, I think what's happening is that your keypads are playing one channel, 
and the triggers are playing a different one. 

>>>That's what I suspected too, but it was hard to confirm as I'm mashing 
up so many things (Triggers, B channels, arps, ect) into one solution to 
get this to work. <<<

Oh, note also that the selection or channel for the keypads in the 
controllers menu is overriden by rechannelize, so if you're using that to 
set channel with rechannelize on, it won't do anything.

>>>OK, I'll have another go at it with Rechannelize off.  BTW is this 
stuff in the manual and I just missed it?  I poured over the manual and 
addendums last night to make sure I wasn't missing something, but didn't 
see a referrence to this anywhere. 

Also, on the subject of addedums, can Emu please post the previous 
addendums on the website, or combine them into one?  I get a lot of emails 
from people with questions about new features that are pretty well covered 
in manual addendum 1.18 (like Event and Note list edit), but they can only 
get addendum 1.31.  The addendums aren't cumalative, though the OS updates 
are, so a lot of added features aren't covered right now.  Just a 
suggestion. Thanx for your help too! It was all going so well until that 
last step! <<<

rEalm

Re: [xl7] Arp bug here too?

2002-09-24 by erik_magrini@Baxter.com

Gotcha!  I tried that last night too, but I think the rechannelize bug was 
still affecting me.  I always forget about that aspect (channel selection) 
of the LED display.

rEalm





"Sean Wilhelmsen" <seanw@...>
09/24/02 11:31 AM
Please respond to xl7

 
        To:     xl7@yahoogroups.com
        cc: 
Show quoted textHide quoted text
        Subject:        Re: [xl7] Arp bug here too?


rEalm,
One more thing. Try using the 7 segment display (press edit, select
Track/channel), it's really helpful when choosing B channels for the key 
pad
when assigning B channels to triggers.

sean at e-mu
----- Original Message -----
From: "Aaron Eppolito" <synthesis77@...>
To: <xl7@yahoogroups.com>
Sent: Tuesday, September 24, 2002 9:03 AM
Subject: Re: [xl7] Arp bug here too?


> --- erik_magrini@... wrote:
> > Ok, I think I may have run across that Arp bug
>
> Well, you already know that it's not Nick's bug (which I should
> probably confirm as a bug by the way - I checked and it is most
> certainly the case that Extension Interval gets picked up from the
> *prviously* selected preset - good catch Nick).
>
> I just did a quick test to try your thing rEalm, and I think you may be
> running into problems with rechannelization.  Make sure you set the
> channel explicitly in the Triggers menu instead of setting it to Basic
> (you probably already did that).  Also, you might want to turn
> rechannelization off because if no sequencer track is set to use the
> "B" channel you're working on, you can switch to that B channel on the
> preset screen, but the keyboard will still be on some other channel
> (specificly, the last channel selected that actually had a track
> assigned to it).
>
> So, I think what's happening is that your keypads are playing one
> channel, and the triggers are playing a different one.  Oh, note also
> that the selection or channel for the keypads in the controllers menu
> is overriden by rechannelize, so if you're using that to set channel
> with rechannelize on, it won't do anything.
>
> -Aaron
>
> __________________________________________________
> Do you Yahoo!?
> New DSL Internet Access from SBC & Yahoo!
> http://sbc.yahoo.com
>
>
> To unsubscribe from this group, send an email to:
> xl7-unsubscribe@yahoogroups.com
>
>
>
> Your use of Yahoo! Groups is subject to 
http://docs.yahoo.com/info/terms/
>
>
>



To unsubscribe from this group, send an email to:
xl7-unsubscribe@yahoogroups.com

 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/

Re: [xl7] Arp bug here too?

2002-09-24 by Sean Wilhelmsen

rEalm,
One more thing. Try using the 7 segment display (press edit, select
Track/channel), it's really helpful when choosing B channels for the key pad
when assigning B channels to triggers.

sean at e-mu
----- Original Message -----
Show quoted textHide quoted text
From: "Aaron Eppolito" <synthesis77@...>
To: <xl7@yahoogroups.com>
Sent: Tuesday, September 24, 2002 9:03 AM
Subject: Re: [xl7] Arp bug here too?


> --- erik_magrini@... wrote:
> > Ok, I think I may have run across that Arp bug
>
> Well, you already know that it's not Nick's bug (which I should
> probably confirm as a bug by the way - I checked and it is most
> certainly the case that Extension Interval gets picked up from the
> *prviously* selected preset - good catch Nick).
>
> I just did a quick test to try your thing rEalm, and I think you may be
> running into problems with rechannelization.  Make sure you set the
> channel explicitly in the Triggers menu instead of setting it to Basic
> (you probably already did that).  Also, you might want to turn
> rechannelization off because if no sequencer track is set to use the
> "B" channel you're working on, you can switch to that B channel on the
> preset screen, but the keyboard will still be on some other channel
> (specificly, the last channel selected that actually had a track
> assigned to it).
>
> So, I think what's happening is that your keypads are playing one
> channel, and the triggers are playing a different one.  Oh, note also
> that the selection or channel for the keypads in the controllers menu
> is overriden by rechannelize, so if you're using that to set channel
> with rechannelize on, it won't do anything.
>
> -Aaron
>
> __________________________________________________
> Do you Yahoo!?
> New DSL Internet Access from SBC & Yahoo!
> http://sbc.yahoo.com
>
>
> To unsubscribe from this group, send an email to:
> xl7-unsubscribe@yahoogroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>

Re: [xl7] Arp bug here too?

2002-09-24 by Aaron Eppolito

--- erik_magrini@... wrote:
> I think the rechannelize bug was still affecting me.

It's meant to be that way.  The whole idea of rechannelization was to
ensure that what you record sounded like what got played back.  If you
were able to play a channel for which no track uses, when you went to
record that, you'd be recording one channel, and it'd play back on a
different one.

Note that you don't have to leave rechannelize off once you've set up
the triggers - it will just make the setup easier.  Once you're done,
you can turn it back on.

-Aaron

__________________________________________________
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
http://sbc.yahoo.com

Re: [xl7] Arp bug here too?

2002-09-25 by erik_magrini@Baxter.com

Right, got my head around it now, doh!   BTW, did this last night and it 
worked beautifully!  Now I have some very cool sounding 'rps' parts I can 
mix and match and use while transitioning between patterns, they even get 
effects.  This helps alot, and aside from the lot of time it takes to plan 
out and program rhythm arps, it actually wasn't too hard to do, just time 
consuming.  Thanx again Aaron!

rEalm





"Aaron Eppolito" <synthesis77@...>
09/24/02 01:21 PM
Please respond to xl7

 
        To:     xl7@yahoogroups.com
        cc: 
Show quoted textHide quoted text
        Subject:        Re: [xl7] Arp bug here too?


--- erik_magrini@... wrote:
> I think the rechannelize bug was still affecting me.

It's meant to be that way.  The whole idea of rechannelization was to
ensure that what you record sounded like what got played back.  If you
were able to play a channel for which no track uses, when you went to
record that, you'd be recording one channel, and it'd play back on a
different one.

Note that you don't have to leave rechannelize off once you've set up
the triggers - it will just make the setup easier.  Once you're done,
you can turn it back on.

-Aaron

__________________________________________________
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
http://sbc.yahoo.com


To unsubscribe from this group, send an email to:
xl7-unsubscribe@yahoogroups.com

 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.