Solved Rendering Blu-ray disc stopped before compilation using Vegas Pro 19

I have installed Vegas Pro 19 (as part of the Pro Edit package) and created a small test video (just to 10 secs).
Now I want to create a bluray image.
First I get the message that I am logged in without admin rights. OK, that’s right, but should not be an issue.
I choose "render image only": The file path is: G:\Video\test.iso.
Vegas Pro 19 starts rendering  'Render video', 'Render audio', and 'Compilation is being prepared 0%'. Now I get an error:  Error connecting to an IPC port: the system cannot find the specified file.After repeating the process I get the error message: Status: Two different objects were found that are assigned to the same URI, "/b9f68e89_6b18_4361_bea9_f1f2bf3494f5/Callback".The folder for temporary files is G:\Vegas\ (I tried it also with the default file path for temporary folders. Didn't work either)
In the tempory directory I see a folder ~BdMux004eb7bb with an M2V file and a Wav64 File and several other files. Seems that the work was nearly finished. Just compilation didn't find a file....

I also uninstalled Vegas Pro 19, restarted the PC, reinstalled Vegas Pro and did several reboots. Until now no success.Do you have any suggestions? It seems that this issue happens with earlier versions too, but no solution worked for me until now.What else can I do? As I live in Austria I could ask for a refund within the first 14 days. So if I don’t get it working, I will certainly do this and go back to my old Movie Studio 16. After all these fakes with Movie Studio 18 I’m quite frustrated with Vegas/Magix at the moment.

Hello Roland

I have just done a test with Vegas Pro 19 and was able to create a Blu-ray.iso file without any problems.
I have not had reports from other users of the same problem.
This would indicate there is problem on your computer and/or with the settings you are using.

1. The warning about Admin rights happens for me as well. I think this is related to Windows file permissions.
If you run Vegas Pro "As the Administrator", that warning message will go away.
To run Vegas Pro as the administrator, right-click the Vegas Pro 19 program icon on your Desktop and select Run as administrator.

2. To rule out any accidental program changes you may have made, I recommend you perform a full program reset.
This will default all settings back to factory defaults and also clean the temporary files cache.
Reset instructions here:
www.moviestudiozen.com/doctor-zen-faq/573-how-to-reset-sony-software-to-default-settings#a1

3. Please note that if you are trying to save files directly to an External Hard Drive, this can sometimes cause problems with Vegas, dues to Windows 10 file permissions.
To rule out problems with using an External Hard Drive, I recommend you save your files inside your default Windows 10 Documents folder, which normally has the best permissions set for it.

4. Please take a screen shot of the Burn Blu-ray disc dialogue window, so that I can see the exact settings you have selected, then upload a copy of the screen shot to the forum here.

When I did my successful create .iso test, these are the exact settings that worked for me:

 

Regards
Derek



 

2ND ADDITIONAL MESSAGE !!!

After I posted my first reply to you, I remembered an old forum post about a similar problem.
I recommend you read this:
www.moviestudiozen.com/forum/movie-studio-platinum/1795-movie-studio-14-platinum-burn-error-failed-to-connect-to-an-ipc-port#9138

And then read this:
www.vegascreativesoftware.info/us/forum/rendering-error-message-i-haven-t-seen-before--91973/

I have to add that am upgrading von Movie Studio 16 to Vegas Pro 19. Perhaps this could be the reason for the issue.

I have found a solution, which works well now. Basically I did two steps:

•         Use the working ‘bdmux’ version from my old Movie Studio 16.
•          Change the path for temporary files to the old path used by Movie Studio 16.

The first step was originally mentioned as solution to the same issue in vegas pro 15. You can find it as “OldSmoke’s solution” in www.vegascreativesoftware.info/us/forum/problem-making-blue-ray-iso-in-vp15--108589/ . To use the old working version you have to, rename the folder C:\Program Files\VEGAS\VEGAS Pro 19.0\bdmux to something like bdmux-backup. Then go to the bdmux folder of the older working version of Movie Studio or Vegas Pro. In my case C:\Program Files\VEGAS\Movie Studio Platinum 16.0\bdmux. Copy this folder to C:\Program Files\VEGAS\VEGAS Pro 19.0\bdmux. By doing this you have replaced the original bdmux version of Vegas Pro 10 by the older working bdmux of Movie Studio 16.This step alone leads to another error: Access to path "C:\Users\rolan\AppData\Local\VEGAS" not allowed.As this path is the default path for temporary files in Vegas Pro, the second thing it had to do was changing the path for temporary files to the old path used by my Movie Studio 16.This can be done by “options/settings” and path for temporary files:In my case I had to change it to C:\Users\rolan\AppData\Local\Sony\Movie Studio Platinum\12.0\Interestingly Sony Movie Studio Version 12!!! This was the first version I had installed on my PC (my PC is not so old as version 12; with an i7-6700, 4Ghz, 32MB I can still work very well).Now the bluray image rendering is working as it should and with any bluray settings I have tested until now. As I don’t think, that the bdmux software has really changed, I can live with this workaround.I have no rationale for this strange workaround. Personally I don't think that it has something to do with .NET. And I don't think that it is a new issue of Vegas Pro 19. I used Movie Studio 12, 14, 16 on my PC. I also installed 18 (but only used it one day, lol), and now Vegas Pro 19. I could imagine, that by installing trial versions in addition to already installed older versions, the Windows registry gets somehow mixed up with old and new information for Movie Studio and Vegas Pro. Perhaps something went wrong, when the names got changed from Sony to Magix/Vegas. How knows.

I had no issues with saving images directly to external harddisks in the past and now it is working well again.

I reported this issue also to the support. Let's see if and what solution they offer.

Thanks for your detailed report back.

I have never experienced this problem on my own computer, using the same versions that caused a problem for yourself.
It sounds like another X-file, that only occurs when the user has installed a certain combination of programs.

Over the years, I have regularly re-installed Windows on my computers, by doing a "clean install".
I have found this is the best way to eliminate strange problems that happen out of the blue.
A clean install of Windows is the only way to repair the Windows Registry if something weird has happened.

I never knew how to set the "run as administrator"  mode.  Very helpful. Thanks

Charles Gross