Your original post (and the linked video) has single abilities macroed. This is not appropriate because it increases the time commitment for each action. Because macroed actions do not participate in the ability queue, they cannot be activated until they are clear of animation lock or cooldowns. This is intentional. Therefore, you should not macro single actions except in the case of (1) alternate targeting of heals or buffs via the tags <mo> (mouseover), <tt> (target of target), <f> (focus target), or <2>-<8> (party slots), which decreases the cognitive load of using an action on a party member or (2) automatically centering ground target abilities on a target entity, which is the unusual case of a macro actually saving time. Outside of these two scenarios, there is no good reason to have a macro that just executes one action.
Your second post shows a gross misunderstanding of the macro system, and this is fine for a new adventurer; we are explaining it to you so you understand. /macrolock does not take any arguments; you can verify this by typing "/? macrolock". The macrolock is not why your second macro refuses to fire. Your second macro refuses to fire because (a) you're firing it during the global cooldown and (b) its purpose is to execute an action that shares the global cooldown. Because of B, it will not execute the intended action until the global cooldown is complete. Raw ability buttons are not affected by this restriction because there is an action queue of max size 1, to which you can push new actions up to 0.5s before the action would actually be available. So during the last 0.5s of the GCD, you can press the button for another GCD action to queue it, and it will execute immediately upon completion of the global cooldown. These points are also intentional, and as Legion has tried to explain, it is to prevent automating optimal play.
So again, nothing is broken, and there is nothing to fix, gamewise.