After completing the authoring process, I set to compile using the internal muxer and begin the process. All seems to be going well right up to the actual muxing, which takes about 5 seconds, throws up a Terminated! message, and leaves with with a completely empty output folder.

Send your project with video and audio streams to me and then we will see the problem and fix it. If your video and audio are large enough, you can cut the first 1 minute and send all these one-minute samples instead of a full audio/video.

As a note of possible interest, after installing the beta version, it tried to install a copy of .NET Framework, but that installation failed. The error message said the process needs to be elevated. This happened with an Admin level account in Windows 7, not a Guest account, so I wonder if maybe the installer might need a tweak to correct that.

The software seems to run fine despite the .NET failure, so I don't know if that's relevant to the muxing failure or not.

Try the latest beta - it's updated. One of the problems was the muxer supports only wav's with the standard fmt-field (16 bytes) - I made a workaround for this (direct support of these wav's will be added later).

I was unable to find any information online about the fmt-field of .wav files that didn't require a degree in computer engineering. The files used for the project were exported from Adobe Premiere Pro using Adobe Media Encoder (both 2015 version). The only user options for such files are number of channels, sampling rate and bit depth. As those parameters for both the original files and the 'fixed' files seemed to be identical, I'm very curious about exactly what was fixed? Is Adobe software not writing .wav files correctly? I've not had any issues with those files in any other software, so this whole experience has me very curious.