Running 1.3.1, 1 RPU as Master, 1 Eos as Client. I have two macros that wont fire via either a cuelist execute link or via a timecode event. They will fire fine if manually executed.
The macro statements are;
Live Sub 127 @ Full Enter
and
Live Sub 127 @ 0 Enter
I don;t know if this is the problem, but when you link a macro to a cue, the macro will always fire on the master RPU. If you are on a client, but have the same user Id as the master RPU, you will see the commands on your command line. If you are a different user, the sub should still go to that level, but you won't see it on your command line.
We are still discussing how to improve this, but currently Eos doesn't know which user shoudl run the macro when it is stored in a cue.
I don;t know if this is the problem, but when you link a macro to a cue, the macro will always fire on the master RPU. If you are on a client, but have the same user Id as the master RPU, you will see the commands on your command line. If you are a different user, the sub should still go to that level, but you won't see it on your command line.
We are still discussing how to improve this, but currently Eos doesn't know which user shoudl run the macro when it is stored in a cue.
Just to take this a little further.... this is because cue lists and playback faders are global.... We could trigger the macro on whatever desk hits the go button. Or... there are other options. Any thoughts on this Jason (and others?)
