It works OK for me. VP14 and Sound Forge 11. Windows 10 version 1511. There's a thread on it here (that I don't have time to read right now): https://www.vegascreativesoftware.info/us/forum/vegas-13-wave-hammer-surround-demo--97230/

OMG...not this wave hammer thing again! 13 broke WH and it took forever for SCS to get around to fixing the activation issue.

Thanks for all of the input. I reinstalled a previous version of Vegas (ver. 10) and now WH shows up as registered in ver. 14.  Had been working properly in ver. 13 till 14 was installed.

(ammended) Well that didn't last long.  As soon as a previously edited file was opened in any Vegas version WH reverted to DEMO mode.  

One more discovery...if an older editlist is opened that had used WH prior to VP 14 it reverts to demo mode.  However, if it's deleted and WH is reintroduced the new addition of WH works as registered.  Can anyone reproduce this?

I have the same or a similar Wave Hammer issue:

I have used Vegas Pro since version 9, and used VP13 from debut until 14. Besides video I do a great amount of multi track audio production and I really like VP for that.  I have experienced a new issue of audible beeps, even when I'm not playing a track in Vegas Pro 14.  I searched some old Sound Forge forums and there were comments about plugins.  

The problem I experienced was on a project where used Wave Hammer on the master audio bus.  If I bypass the plugin, it goes away. If I choose another plugin, like Vegas Compressor, that works fine.  But, I really like Wave Hammer and have many custom settings

If I render a .wav or Mp3, or any video file, with Wave Hammer activated, I get the beeps in the render.

So, it's beeping at rest (nothing playing) and also will be added to the render.   

I opened an earler version of the project using VP13... and it works fine with Wave Hammer, however the new 14 VP has this issue with (at least) Wave Hammer.  Since wave hammer came with the program, anyone know how to fix/adjust to fix this problem?

Thanks!

Hi, this is what I've found.  When I add a "FX Package" that I had created in a previous verion of VP that included Wave Hammer and another plug-in the beeping starts.  If I remove WH and then add WH again it no longer beeps or shows up in demo mode.  It's not consistant that when opening edit lists from previous VP versions WH will beep, but I find that replacing it consistantly changes the status to registered vs demo.  Please let me know if you can duplicate this.

I have the same issue as davestudios. I was re-installing Sound Forge a while back (using up my licences) thinking it would re-install Wave Hammer, but now I just opened a Vegas project and found that as Dave pointed out, it is in demo mode and is automatically beeping when on the master track. When I moved it to an audio track, it only beeps when you play the track. This happens in Veg 13 and 14.

I am still having this same issue, which forces me to pre-process audio tracks--or mixes--in Sound Forge, then replace each on the VP14 timeline. On older projects, using VP13, same issue when I try to use in VP14... there is a decent set of audio processors that work properly in Vp14, but, come on, why don't they fix thus Wave Hammer issue or state that it doesn't work properly ??