BadWolf probably wasn't online for a long time, so I'm afraid he isn't able to check and correct his code.
Ok, now I see the problem.
Per default, ZapRecorder2 writes his messages to ChatFrame1, which is /say after WoW started.
This makes no problems as far as you are not in a crowded area and haven't declared another Channel for ChatFrame1, like /1 or /2.
This is really a bad fault in the plugin code!
May BadWolf excuse me for altering his code here.

I hope, he will read this post and implement the changes into the next update.
To fix that ChatFrame thing, search for a file named "ZapForm.cs" in the Plugins/ZapRecorder2 folder, open it with a text editor (i.e. Notepad) and go to line #1721
Look for
Code:
Lua.DoString("getglobal(\"ChatFrame1\"):AddMessage(\"|cff2dbbc4ZapRecorder2: |cffffffff " + message + "\",0, 0, 0, 0);");
and replace it with
Code:
Lua.DoString("UIErrorsFrame:AddMessage(\"|cff2dbbc4ZapRecorder2: |cffffffff " + message + "\",0, 0, 0, 0);");
This will output the message as a WoW error message directly to the screen, just like a raid warning.
(Needless to say that HB has to be restarted to take effect of this change.)
But be aware that after an automatic update or re/install of the plugin, this line will be overwritten with the original line again!
This is an inofficial quick fix, so keep an eye on it!
HTH