Some More thoughts on Effects

So I been I've flailing about with a lot of Effects run live this week.

Besides my issue with Randomized Steps (which I am pretty sure is an undesirable glitch,) I have had on several occasions, found entire channel lists of all steps of an effect dissapear.  I would start a Step Effect from Direct Selects ([Group} effect X) then I would go to the Effects editing page, mess with the attributes to mix it up a bit.  Sometimes, I would select the effect, only to get an error saying no channels were modified.  When I would go back to that effect blind, the channel fields were all empty.  I was unable to pinpoint the sequence of events exactly, but none of my actions were anywhere near the channel fields.  I'll let you know when I figure that out, but that leads me to another issue.

To solve the problem of the missing effect, I decided to just import it from an earlier save. That worked fine, but I soon discovered that Importing a single effect results in the first cue of the list being loaded into the main fader.  The first time was quite a surprise, but the next time my effect dissappeared, I was able to replicate that.  It seems like undesirable behavior to me.

Also, I would like an easier way to Stop individual effects.  With, say six effects running, and music blaring, it dificult to pick the correct effect number to stop.  I tried making Stop Effect Macros but was unsuccessful getting it to recognize the Stop Effect Key.  What if there were a Direct Select section that correspond to the Effect DS's and initiated the stops for them?

Thanks

Parents
  • A thought on your stop effect macro... if the macro editor is not recognising the [stop effect] button, could you instead use [@ enter]?  I quite often find with the ion this this is the quickest way to stop an effect, as the ion doen't have a stop effect button.

    for example: [effect 901 @ enter].  On the command line, this appears as "effect 901 stop effect"

    Hope that helps

    Cheers 

Reply
  • A thought on your stop effect macro... if the macro editor is not recognising the [stop effect] button, could you instead use [@ enter]?  I quite often find with the ion this this is the quickest way to stop an effect, as the ion doen't have a stop effect button.

    for example: [effect 901 @ enter].  On the command line, this appears as "effect 901 stop effect"

    Hope that helps

    Cheers 

Children
  • Brent.

    That may be just the kind of tip I was looking for.  Especially if I can enter the effect from the Direct Selects.

    It could lower my stress level quite a bit today.

    As I said above, I was thinking that Stop Effects in the DSs would be a good idea, as well as with Fader Pages.  But being able to do those things with DS Macros would be just as good.

    Thanks,

    B

Related