Yahoo Groups archive

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

Index last updated: 2026-04-05 20:33 UTC

Message

Re: [xl7] Erasing tracks AND their LED's

2002-06-20 by erik_magrini@Baxter.com

Weird!  I'll try that one tonight, funny that revert fixes it!

rEalm





"S V G" <vsyevolod@...>
06/18/02 06:28 PM
Please respond to xl7

 
        To:     xl7@yahoogroups.com
        cc: 
        Subject:        [xl7] Erasing tracks AND their LED's



     A few months ago, there was several postings on getting rid of the 
LED on a track once
everything has been erased from it.  Several people had some workarounds 
including exporting the
whole pattern into Reason and fugging with it then sending it back.

     Today, I came across a simple way to do this.

     1)  Select the pattern you want to erase your track(s) from.

     2)  Go into Pattern Edit.

     3)  Scroll across to <Erase Events>

     4)  Set the parameter to <all track events>, press Enter.

     5)  Select which track(s) you wish to erase, press Enter.

     6)  Save your pattern to the same location.

     7)  Go back into Pattern Edit and scroll across to <Revert to Saved 
Pattern>, press Enter.

     Voila!  Your pesky little LED's are now outta the way.  It seems that 
the last step is the
one that wasn't being done by those who wanted to get rid of the LED. 

     I don't know if this counts as an OS bug, though if Scott or Aaron 
are reading this, they
would probably know.  If it's not a bug, then perhaps it can make it into 
future manual updates,
or even rEalm's excellent FAQ.

     Cheers,

          SVG

__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.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/

Attachments

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.