Need Help ASAP with Clearing Parameters

Your macros are setting manual values.  Then you hit go, they are still captured.  When you hit back, it is like running an out of sequence cue, as if you have said "Go to Cue Last Enter' and the forces the manual values out.

Adding a clear at the end of the Macro should clear the channel selection from the command line and allow the cue to progress and take over the levels. 

You mention this is not working- do you still have text on the command line when you hit go?

and I DO NOT have any text on command line

That is certainly odd.

Any chance you can share the show file?
What software version are you running? 

What mode is the macro in?

Also, apologies ahead of time but I'm not going to be able to respond as quickly very soon, but I think this data may help others to help you as well.

Mode is Background mode. 

I wonder if that's part of it.  Background mode runs as user 0- so the command was set by a different user than the one hitting go...

tried both foreground and default. Neither result in it clearing for the next cue. I also added Clear_CmdLine at end of macro. No luck. I imagine it's something stupid that I'm doing. 

can't upload file. email?

2.8.2 build 8

Your values are not being overridden because there isn’t a move instruction in the next cue. If you assert the cue, it will fade the values back to where they are in the cue. You can also assert the entire cue list, if you would like this to be the behavior for every cue.

This definitely sounds like a bug, because you are doing things correctly. try creating a new macro, default mode, same syntax. but don't put an enter after the clear command line

This is not a bug - this is how the console works. In the Eos only the values that have changed get played back. By adding an “assert” to the cue you are telling the console to treat all values as if they’re move instructions.

If running in CueOnly mode instead of tracking, this is not how having manual data up and playing a cue work together, correct?. Which is where our confusion with each other is coming from.

Cue Only is an editing tool, and has nothing to do with how things are played back, just how they are stored and modified.

This is strange because I work with manual data that isn't in my cues a lot, and when clearing the command line to make sure nothing is selected and advancing to the next cue, It has always restored to its background state, for as long as I could remember.

This is strange because I work with manual data that isn't in my cues a lot, and when clearing the command line to make sure nothing is selected and advancing to the next cue, It has always restored to its background state, for as long as I could remember.

The rules are (and have always been):

A selected channel with manual data will not move by playback

A captured channel with manual data will not move by playback (selection status doesn't matter)

A de-selected channel with manual data will only move parameters by playback if the incoming cue has move instructions for that parameter. Unless the incoming cue is asserted.