Yahoo Groups archive

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

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

Thread

Saving stuff, How does this work????

Saving stuff, How does this work????

2003-03-06 by drewaight1

Okay here is a hypothetical situation....

I have a Pattern.........

Channel 1  Sequenced Kit send3 panned slightly left
Channel 2  NylonGtr with preset Arpeggiator panned slightly right
Channel 3  ElectricGtr with preset Arpegiator panned left
Channel 4  Sequenced FretlessBass send2 panned right
Channel 5  70s lead send3 (no sequenced data) 

Trigger 1 --> channel 2 B2
Trigger 2 --> channel 3 B3

Can someone walk me through the steps needed to SAVE all this so that 
if I turn off my MP-7 and turn it back on ALL of these functions will 
be intact

In order to keep the arpeggiator settings and send settings Im 
assuming that I need to save each of these presets to a user preset. 
Then I need to save the pattern. But this does not keep the triggers 
the same. Also for some reason if you dont have data sequenced on a 
channel (channel 5 in this case) but want it to show up as a preset 
when you switch to a certain pattern (so you can solo on it) this is 
not possible. I guess these issues can be addressed using "multi 
setups" but there are only 64 multisetups, does that mean that we can 
only store 64 separate patterns in the XX-7? surely we are going to 
have different send levels for each pattern. Why arent all of these 
parameters saved with the pattern?

Furthermore when I come home and want to compose a new pattern when I 
go to the next empty pattern it still has all the panned and global 
and  preset settings as the last pattern. Doesn't it seem logical 
that when you scroll to a pattern that has not been used it should be 
initialized?

Ive said it before, this is an extremely powerful machine, mabye the 
most powerful sequencer/groovebox ive ever used. I just can't fathom 
why EMU have decided to throw all logic out the window when designing 
the pattern/preset/global sequencer relations.

Thanks in advance.
                                                        Drew

Re: [xl7] Saving stuff, How does this work????

2003-03-06 by erik_magrini@Baxter.com

Channel 1  Sequenced Kit send3 panned slightly left
Channel 2  NylonGtr with preset Arpeggiator panned slightly right
Channel 3  ElectricGtr with preset Arpegiator panned left
Channel 4  Sequenced FretlessBass send2 panned right
Channel 5  70s lead send3 (no sequenced data)

>>Save all of these Presets individually if you want to store the arp on 
and pan status (assuming your using panning in the preset, not the 
pattern).  Then save the Pattern to save all the track assignments and 
send amounts (again asuuming the effects are set to Multimode Control, not 
Preset on Ch.X ).

Trigger 1 --> channel 2 B2
Trigger 2 --> channel 3 B3

>>>Not sure what you mean here.  Guessing B2 and B3 are the notes you 
assigned with the Triggers set to "Plays Notes", and not "Triggers Play 
BTS Riffs" or "Triggers Select Patterns" ?  If so, best bet would be to 
save the MUlti next, that will save the Trigger status and the Note 
numbers assigned too. <<<

In order to keep the arpeggiator settings and send settings Im 
assuming that I need to save each of these presets to a user preset.

>>>Yes. ,<<
 
Then I need to save the pattern. 

>>>Yes again. <<

But this does not keep the triggers the same. 

>>>Those are saved as part of the Multi. <<<

Also for some reason if you dont have data sequenced on a channel (channel 
5 in this case) but want it to show up as a preset when you switch to a 
certain pattern (so you can solo on it) this is not possible. 

>>>You have to have some type of data recorded onto a track for it to 
remember what the Preset assignment is for that Track. This is common 
source of confusion. You could just record some bogus data (pressure = 0 
or something) into Tick 0 on that track.  A few posts from drK awhile 
addressed ways to get around this, might want to search the archives for 
other ideas.<<<

I guess these issues can be addressed using "multi setups" but there are 
only 64 multisetups, does that mean that we can only store 64 separate 
patterns in the XX-7? surely we are going to have different send levels 
for each pattern. Why arent all of these parameters saved with the 
pattern?

>>>Because they're global settings, and not Pattern specific, even though 
YOU are using them for that purpose.  This may have been addressed by OS 
2, I'll have to check and see. <<<

Furthermore when I come home and want to compose a new pattern when I go 
to the next empty pattern it still has all the panned and global and 
preset settings as the last pattern. Doesn't it seem logical that when you 
scroll to a pattern that has not been used it should be initialized?

>>>That's tied in with the issue you're having above where preset 
assignments aren't saved onto empty tracks. You scroll to the next empty 
pattern and technically there's not default Presets saved with it so it 
just uses whatever was assigned since it last received a program change 
message.  I got round this by creating a Multi Setup that has the default 
Preset assigned to all Tracks (the Pattern won't remember this, but the 
Multi does!), and all other paramters int he XX-7 defaulted as well 
(sends, vol, pan, etc).  I just call it "rEalm default" and load that when 
i want to start form scratch on a new Pattern.  Takes half a second to 
load, easy. <<<

Ive said it before, this is an extremely powerful machine, mabye the most 
powerful sequencer/groovebox ive ever used. I just can't fathom why EMU 
have decided to throw all logic out the window when designing the 
pattern/preset/global sequencer relations.

>>>It's only illogical for the way you're trying to use it :) Once you get 
a handle on it, it begins to make mroe sense. Most of the time at least :) 
 <<<

Thanks in advance.

>>>You're welcome in hindsight<<<

rEalm
 

 






[Non-text portions of this message have been removed]

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.