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

ok .i am back with the same prb  
here is what i am doing 
write a pattern 
set the knobs to different controls 
save the pattern first..
the play the pattern and then save the muti ( to save the controller 
set up )
save it then name it 

i do this for two patterns ..
the controller vaules being different for both patterns 

pattern A   multi A
pattern B   multi B

when i go from pattern A to B   the controller vaules remian the same 
in order for me to get the right pattern with the right multisetup is 
to stop play change 
multi then do a revert to pattern .. but how are you supposed to do 
that live ?

i am truly sorry that i do not understand this concept.


-- In xl7@yahoogroups.com, erik_magrini@B... wrote:
> hmm ..i found out that it was the multisetup that was causing this 
whole 
> prb .. but i still do not know why ???
> 
> >>>Well, if you load a multisetups, it loads the presets that were 
on each 
> Track when you saved the Multi.  So if you save the pattern after 
loading 
> a Multi, it will save the Presets assigned in the Multi, not the 
ones you 
> saved as part of the Pattern.   Best bet, is to Revert to Saved 
Pattern 
> before you save the Pattern! <<<
> 
> i went to the emu site to check out the prb last night and found my 
prb 
> ..but i cant understandy why emu would do this or if it just a way 
of 
> thinking that i am not used to ..
> 
> >>>99% sure it's the later, no offense. :) <<
> 
> "the Multisetups channel settings will be saved to Pattern, instead 
of the 
> correct values you wanted"
> 
> i do not get this at all .. why would a multiset up save a preset 
> assigment ..there is already a way to save the preset to 
pattern ..and it 
> is simple and logical ..save it to pattern ...in my head the 
multisetup 
> should contain information about the channel assigment ...like what 
sub 
> groups the tracks are assigned to and the 
> effects percentage such that if a person wanted to have one pattern 
start 
> out with one effect setting and change to another all they would 
have to 
> do is switch the mutisetup ..
> 
> >>>You can do what you suggest too, but Multisetups are more 
flexible than 
> that.  Say you were sequencing from an external sequencer, like 
Cubase, 
> then you wouldn't need to create a pattern (since the notes would 
be 
> stored in Cubase).  However, you'd still want the right sounds on 
each 
> track, so you could save a Multisetup to store this data.  There's 
lots 
> more uses for Multi's, they're not JUST to save Preset assignments, 
though 
> that is a nice benefit. <<<
> 
> in my case say .i am on one of the orginal xl patterns ..and i 
switch the 
> multisetup the pattern goes all wacky ..it changes all the presets 
in that 
> pattern...  how do i fix this ?? 
> 
> >>>Easy, just perform a "Revert To Saved Pattern" (Pattern Edit 
menu). 
> This will relaod the Presets that were saved with the Pattern.  Now 
resave 
> the Multi.  Whenever you load the Multi, it will recall the Presets 
from 
> the Pattern now.  You will need to do this for each of Multi's you 
want to 
> load durring a Pattern, and you will nee to do it for all 
Patterns.  Think 
> of Multi's as a snapshot of every setting within the XX-7 at the 
moment 
> you save it. Everytime you load a Multi, EVERYTHING will revert to 
how the 
> XX-7 was when you saved the multi. <<<
> 
> "and if you save your Pattern before playing it, the Multisetups 
channel 
> settings will be saved to Pattern"  err why why why ??
> 
> >>>Because when you load the multisetup, it will assign the Presets 
to 
> each track that were there when you saved the multi.  As far as the 
> Pattern is concerned, it has no idea the Presets aren't what you 
want, 
> it's like you manually changed them one at a time as far as it's 
> concerned.  So when you save the Pattern, it will now store the new 
> Presets, instead of the ones you had orginally saved. <<<
> 
> how is this undone ?????
> 
> >>>If you load a multi and it doesn't have the Presets you want, 
perform a 
> Revert to Saved. <<<
> 
> thanks again to all
> 
> >>>Let me know if I didn't explain it well enough.  Believe it or 
not, 
> it's a really, really flexible feature, you just need to get your 
head 
> around and it'll make more sense. <<<
> 
> rEalm
> 
> 
> 
> [Non-text portions of this message have been removed]