Hi Nick, just confirmed AOK

I just completed an edit on vp16 build 307 and had these same errors indicating that it is not fixed

1 cannot connect to ipc

created temporary folders on same drive rather than the default locations which resolved this issue. But gave rise to the

Unable to complete ...two instances of ....

even trying to render small loop section gives rise to this issue trying to burn blue ray.

didnt have this issue in 11,12,14, did not had the opportunity to try it on 15

any help please

Here the same issue.
No problem on VPro 14 and 15 but it stops at "Preparing compilation" in VPro 16.

BTW.
No problem for me because that option I don't use anymore since 6 years.

Confirmed. Here too there is the same problem.

Help needed please,

Additional info, I find this highly unacceptable from software claiming to be professional having key functionality not working correctly

I have VP 16 build 307, and trying to burn BD 1920x1080 50i either 10Mb/s or 16Mb/s gives exactly the same error. Renders video (9 hours ++, renders audio, and when it tries to compile it flags this error, ISO nowhere to be found. VP14 never had these issues, wasted two days trying to resolve.

I tried setting all the file locations to the same SSD drives, same drive as source files to no avail. on some occasions it shows a different error,

tried 60 second loop render with the same error as the first.

Program set to run as administrator, previous versions no issues.

Laptop HP 8760W, I7 2670QM quad core, 2.2GHz, 20GB memory, 2 x 1TB SSD's C:, G:. with build in Blue ray writer, windows 10 pro 64 bit latest build as of 1st Jan 2019.

Interesting unrelated observation, under my registered products in the main Magix area and the support area are different, in the support area the VP 16 suite is missing! whilst it is shown in the main Magix area, a case of  left hand not knowing what the right hand is doing?

Any help appreciated, 

P.S. thanks to Nick Hope for directing to this thread.

 @andreas-georgiou

The workaround for this problem is on page 1 of this topic.

I would like to take this opportunity to also wish everyone a happy, healthy, prosperous and blessed new year 2019.

As a significant portion of my work is in 3D, I usually do not use DVDA as so far had no need for menus etc. and did not have the spare time to spend in addition to editing and rendering for the creation of menus also I think DVDA does not fully support 3D menus etc.?

So this menu options to burn Blue ray (and 3D) is very crucial for my workflow.

Many Thanks Joelson-Forte,

I do have VP14 but not sure if the temporary solution disables any templates or introduces other VP14 instabilities?

VP14 I find suffers from crashes on my system and hence the reason for updating to VP15 and then VP16 in the hope that they address the issues. VP16 far more stable on my machine with GPU disabled.

I still think that this should be top priority for the coding team to address as it is a key menu option and needs to function correctly.

@andreas-georgiou

I agree with you. I did the temporary patch procedure here and it works fine without causing problems in Vegas pro 16.

I do have VP14 but not sure if the temporary solution disables any templates or introduces other VP14 instabilities?

No problem to use the bdmux file of C:\Program Files\VEGAS\VEGAS Pro 14 or 15\bdmux in Vpro 16 as OldSmoke gave as a solution.
Go to that file in version 16 and change the name to C:\Program Files\VEGAS\VEGAS Pro 16.0\bdmuxold.
Than copy/paste that file of version 14 or 15 into version 16 .
You than see this

With me it worked.
But the first thing you have to do is upgrade VPro 16 to the latest build.

Again thanks,

Just rendered a small loop clip successfully having followed the suggestion, so the problem must be in one of the DLL's or other files in that folder?

Do you find render times slower?

Rendering seems to be far slower than VP16 though, I will restart machine and retry as it will end up taking days to render at around 1 frame per second (VP16 around 10FPS - although died at the end!-).

@andreas-georgiou Could you please report this issue via a support request? The issue was fixed in VP15 build 216 and so is probably no longer in the developers' backlog, and there is no guarantee that they follow these posts.

Thanks Nick,

Just did, waiting for a response, as an update I did manage to successfully burn a BD following the solution provided here in this forum, alas had my first VP16 crash when I tried to carry out some minor edit on the timeline following the successful burn without restarting, (Split a clip to remove a section-VP16 locked up)

Hi Nick,

Fairly prompt response from Magix,

"Hello

Thank you for your message.

This is now escalated to QA and Development teams, to be resolved in a future application update.  Thank you for reporting this issue. 
--
Best regards,
E*** ***"

Have to check if resolved in build 352 although not sure if this update has replaced the old folder we copied with a new build 352 version.

Thanks again

Andy