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

So I've been working on a track, and having this maddening glitch pop 
up on one of my other pieces of gear - Every time I reset playback 
(ie, press STOP 3 times) the patch I'm using on my AN200 goes all 
nutty on me and I have to reset it.  So I change to a different patch 
& change back, and all is well - but it started to get on my nerves, 
so I decided to try and track it down.

I fired up MIDIOx and did some testing.  Turns out the XL7 is causing 
the problem!  If you have Channel Assign for a track set to EXT or 
BOTH, a series of CCs are sent out on that channel when you reset the 
sequence:

 07    7F    4  ---  CC: Volume     
 0A    40    4  ---  CC: PAN        
 4F    00    4  ---  Control Change 
 50    02    4  ---  Control Change 

I understand the first 2.  Set CC#7 (Volume) to 127, and set CC#10 
(Pan) to 64. But the next 2 correspond to CC#s 79 and 80 - and CC#80 
controls LFO->VCA on the AN200! Unfortunately, there is no way to 
disable that on the AN200, other than disable ALL CCs, which I really 
don't want to do. 

So, my questions:

Why does the XL send CC 79&80 on reset?  What's the significance of 
those 2 CC #s?

Is there any way to *not* send them? Or for that matter, is there a 
way to not send *any* CCs to outboard gear on reset?  It seems to do 
more harm than good, at least for me... 

I checked the manual, browsed the menus on the XL, and checked the 
archives here, but I couldn't seem to find anything helpful.  Sorry if 
this is old hat, but any help you can provide would be greatly 
appreciated!

Thanks!

DTK

BTW, I know the easy answer to this is "Only press STOP *2* times!" -
 That's not really what I'm looking for. :)

--- In xl7@yahoogroups.com, "soundcrafter" <aurastar@...> wrote:
>
> So I've been working on a track, and having this maddening glitch 
pop 
> up on one of my other pieces of gear - Every time I reset playback 
> (ie, press STOP 3 times) the patch I'm using on my AN200 goes all 
> nutty on me and I have to reset it.  So I change to a different 
patch 
> & change back, and all is well - but it started to get on my 
nerves, 
> so I decided to try and track it down.
> 
> I fired up MIDIOx and did some testing.  Turns out the XL7 is 
causing 
> the problem!  If you have Channel Assign for a track set to EXT or 
> BOTH, a series of CCs are sent out on that channel when you reset 
the 
> sequence:
> 
>  07    7F    4  ---  CC: Volume     
>  0A    40    4  ---  CC: PAN        
>  4F    00    4  ---  Control Change 
>  50    02    4  ---  Control Change 
> 
> I understand the first 2.  Set CC#7 (Volume) to 127, and set CC#10 
> (Pan) to 64. But the next 2 correspond to CC#s 79 and 80 - and 
CC#80 
> controls LFO->VCA on the AN200! Unfortunately, there is no way to 
> disable that on the AN200, other than disable ALL CCs, which I 
really 
> don't want to do. 
> 
> So, my questions:
> 
> Why does the XL send CC 79&80 on reset?  What's the significance 
of 
> those 2 CC #s?
> 
> Is there any way to *not* send them? Or for that matter, is there 
a 
> way to not send *any* CCs to outboard gear on reset?  It seems to 
do 
> more harm than good, at least for me... 
> 
> I checked the manual, browsed the menus on the XL, and checked the 
> archives here, but I couldn't seem to find anything helpful.  
Sorry if 

> this is old hat, but any help you can provide would be greatly 
> appreciated!
> 
> Thanks!
> 
> DTK
>

Hitting stop three times resends all data at tick 0.  This info is
typically only played the first time through the sequence, not at ecery
loop.  (this is why the event editor doesn't let you get to the first
tick).

More background: cc79 and cc80 are arp status and send bus select if I
recall correctly.  The XL-7 stores this per track so that it sets those
settings up for each pattern.

And finally, the solution.  Either don't save the sequence with data on
a track assigned internally that will eventually go external, or, if
you have already, remove the offending cc data on your external tracks.
 It's easiest to do this with the erase events menu (where you could
target cc79).

-Aaron

--- soundcrafter <aurastar@...> wrote:

> So I've been working on a track, and having this maddening glitch pop
> 
> up on one of my other pieces of gear - Every time I reset playback 
> (ie, press STOP 3 times) the patch I'm using on my AN200 goes all 
> nutty on me and I have to reset it.  So I change to a different patch
> 
> & change back, and all is well - but it started to get on my nerves, 
> so I decided to try and track it down.
> 
> I fired up MIDIOx and did some testing.  Turns out the XL7 is causing
> 
> the problem!  If you have Channel Assign for a track set to EXT or 
> BOTH, a series of CCs are sent out on that channel when you reset the
> 
> sequence:
> 
>  07    7F    4  ---  CC: Volume     
>  0A    40    4  ---  CC: PAN        
>  4F    00    4  ---  Control Change 
>  50    02    4  ---  Control Change 
> 
> I understand the first 2.  Set CC#7 (Volume) to 127, and set CC#10 
> (Pan) to 64. But the next 2 correspond to CC#s 79 and 80 - and CC#80 
> controls LFO->VCA on the AN200! Unfortunately, there is no way to 
> disable that on the AN200, other than disable ALL CCs, which I really
> 
> don't want to do. 
> 
> So, my questions:
> 
> Why does the XL send CC 79&80 on reset?  What's the significance of 
> those 2 CC #s?
> 
> Is there any way to *not* send them? Or for that matter, is there a 
> way to not send *any* CCs to outboard gear on reset?  It seems to do 
> more harm than good, at least for me... 
> 
> I checked the manual, browsed the menus on the XL, and checked the 
> archives here, but I couldn't seem to find anything helpful.  Sorry
> if 
> this is old hat, but any help you can provide would be greatly 
> appreciated!
> 
> Thanks!
> 
> DTK
> 
> 
> 
> 
> 
>  
> Yahoo! Groups Links
> 
> 
> 
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com

> And finally, the solution.  Either don't save the sequence with data 
on
> a track assigned internally that will eventually go external, or, if
> you have already, remove the offending cc data on your external 
tracks.
>  It's easiest to do this with the erase events menu (where you could
> target cc79).
> 
> -Aaron

Thanks Aaron!  So if I go in and do an Erase Events -> All CC (or 79, 
etc), that will also remove the data from tick 0?

Is there any way to access & change the data at tick 0?  That could be 
handy in some situations...  

DTK

--- soundcrafter <aurastar@...> wrote:
> Thanks Aaron!  So if I go in and do an Erase Events -> All CC (or 79,
> etc), that will also remove the data from tick 0?
> 
> Is there any way to access & change the data at tick 0?  That could
> be handy in some situations...  
> 
> DTK

Yes, erase events should remove things at tick 0 too, be it all
controllers, or just a specific one like 79 or 80.  As for accessing
the tick 0 events, you should be able to edit or erase events at tick 0
on external tracks, but not add them.  Internal tracks don't let you at
tick 0 at all (to disuade you from messing up the sequencer's events
that it adds).  Also, I believe the first 3 ticks (maybe four) of
controllers (i.e. not notes) only play the first time through the loop,
giving you a place to put stuff that you only want the first time (like
program changes, initial volume, etc).

-Aaron

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com

Excellent points raised on this thread (both Qs and As).

Suggestion, if you haven't done so already, create pattern templates. 
For example, I have one pattern that assigns all tracks to external 
with benign data on each track (Vol = 127, I think; but any CC data 
should do it). The placeholder data is important, otherwise (if there 
are no notes or events in a track) the OS will reset the track when you 
save it.

--Steve