Blu-Disc Studio MX: Muxing Terminated

[Jim Simon]

Using version 2.1.121 under Windows 7 Pro 64 bit.

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.

[Alexey Kolesnikov]

Try the latest beta, but pay attention - project format slightly changed in this version - keep a copy of the project before using this version.

[Jim Simon]

Thanks. I'm skeptical of installing beta software on a production machine, though.

Ideally I'd love to find out what's going wrong with the process and get it working in the current version.

[Alexey Kolesnikov]

The basic idea of installing beta is that it could already be fixed.

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.

[Jim Simon]

Thank you for the assistance.

I installed the beta (2.1.0.253), but the issue still exists. I get the below log along with an empty Output folder.

2:24:29 PM - Saving...
2:24:29 PM - Preparing...
2:24:29 PM - Adding video asset for "Main Menu"
2:24:34 PM - (notice) Popup Menu not specified in movie "Performance"
2:24:34 PM - Adding video asset for "Performance"
2:24:39 PM - Adding audio asset #1 for "Performance"
2:24:44 PM - (notice) Popup Menu not specified in movie "Journey to Arangetram"
2:24:44 PM - Adding video asset for "Journey to Arangetram"
2:24:49 PM - Adding audio asset #1 for "Journey to Arangetram"
2:24:53 PM - (notice) Popup Menu not specified in movie "Meet the Band"
2:24:53 PM - Adding video asset for "Meet the Band"
2:24:58 PM - Adding audio asset #1 for "Meet the Band"
2:25:03 PM - (notice) Popup Menu not specified in movie "Photo Session"
2:25:03 PM - Adding video asset for "Photo Session"
2:25:08 PM - Adding audio asset #1 for "Photo Session"
2:25:12 PM - (notice) Popup Menu not specified in movie "Guests Dinner"
2:25:12 PM - Adding video asset for "Guests Dinner"
2:25:18 PM - Adding audio asset #1 for "Guests Dinner"

2:25:23 PM - Step 1/4 ...
2:25:24 PM - Step 1/4: done
2:25:24 PM - Step 2/4 ...
2:25:24 PM - Step 2/4: done
2:25:24 PM - Step 3/4 ...
2:25:25 PM - Step 3/4: done
2:25:25 PM - Step 4/4 ...
2:25:25 PM - Step 4/4: done
2:25:25 PM - starting mux process...
2:25:30 PM - finished mux process

2:25:30 PM - Terminated!

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.

Here's the project zipped up with 1 minute assets.

http://depositfiles.com/files/qu9nnvutp

[Alexey Kolesnikov]

Hi Jim!

Thanks for sample project.

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).

[Jim Simon]

Thank you, Alexey! The new Beta build did the trick.

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.

[Alexey Kolesnikov]

Hi Jim!

The problem is in muxer limitation.