Another issue with running macros from the remote and the MSC 400 is that the MSC is unaware of what the remote is doing and vice versa. The MSC only has a single IR engine and if it is executing a long macro via a hot trigger a macro that is being executed by the remote will be ignored. The problem will be magnified if you are using sensors to check state and the macros in the MSC are delayed until the state is confirmed.

The whole point of the MSC is to offload all of your macros to a standalone "macro player" which can be fired off with 4, 5, 6-bit or whatever RF triggers.

I try to force the MSC to do everything it possibly can and massage all the macro delays, IR repeats, etc. to work in the tightest tolerances for snappiest system performance.