Has the latest Windows 11 update killed DVDA 6.0?

Dexcon wrote on 4/30/2024, 9:05 AM

I have attempted to 'Prepare' a project may times over the last few days in DVDA 6.0. The Prepare and Burn worked successfully about a month or so ago in Windows 11. With the project, the Prepare took 1 Hours 35 minutes and the burn a slightly shorter time. After the last Windows 11 update/s (now 23H2), Prepare now takes around 6 hours and ends with the following error screen:

... but with no .iso file created.

This has happened many times but an .iso file was successfully created 3 days ago - but not since.

Other information: it's the same project in Vegas Pro rendered using exactly the same render template as previous renders; and the AC-3 audio rendered in VP16 using exactly the same audio render template. The new media has been replaced in DVDA6 in exaclty the same way as I've done many times over the years and without a problem.

Further, I tried Preparing a months old project with the then existing media and it encountered the same problem. I even tried copy/pasting the video/audio media with one particular project into an older Windows 10 computer - and the same thing happened. Something must have happened with Windows that has killed DVDA.

I know that DVDA is not often used these days, but has anybody else experienced this?

I guess that I'll have to try TMPGEnc Authoring Works 7.

Comments

Dexcon wrote on 5/1/2024, 5:42 AM

THE ANSWER: W11 23H2 has NOT killed DVDA 6.0.

After a lot of internet searching including CoPilot, I found a few posts on various forums about the Tempuri error. A MovieStudioZen forum thread from 2019 provided the solution, that being that the 'prepare' and 'temporary' folders in the Preferences/Burning window needs to remain set to their default folders on the C drive. Mine weren't - they were manually set to folders on the E drive.

https://www.moviestudiozen.com/forum/dvd-architect-studio/2249-error-when-trying-to-burn-blu-ray-disc

Having set them back to their default settings, DVDA has today successfully created an .iso file. It did take 6 hours to create, but I now realise why earlier .iso creations only took 95 minutes. At the time, I was just changing the audio track - the video render had previously been done over a month ago so didn't need to be rendered again. But over the last couple of days, I've using a new video render from Vegas Pro so, what I didn't take into account, is that the video had to be rendered again in DVDA.

Right now, the burn progress to a BD disc is at about 25% so things are looking good (hope I haven't spoken too soon).

So it's a giant PHEW!!! DVDA 6.0 still lives.

I'll leave this thread on the forum just in case somebody else gets the Tempuri error because they've changed the Burning folders away from the default settings.

Dr Zen wrote on 5/3/2024, 12:13 AM

Hi Dexcon.
I saw your original post the other day and was eagerly waiting to hear if you had found a solution. I almost fired up DVD Architect to check it, but I'm extremely busy at the moment and decided to wait.

I'm very happy to find out that the epic forum thread on my forum, in which I was the chief investigator, was able to help you out. I just quickly re-read that entire forum post and have now remembered what a mammoth effort it was to find the solution. Sometimes running a forum becomes extremely exhausting, but when I hear stories like yours, it makes it all worthwhile 😊

Cheers,
Derek (aka Doctor Zen) from Movie Studio Zen.

Dexcon wrote on 5/3/2024, 12:53 AM

@Dr Zen ... Hi Derek

I suspected that it might have been your good self running that forum. And what a relief it was to find the solution - so many thanks for all your hard work back in 2019.

I couldn't help but ask myself why the destination for those Burning folders were able to changed away from the C drive if the program wasn't going to work but then a comment I read on another forum from 2014 (I think it was) noted that Microsoft had closed that Tempuri website (it had something to do with XML if I recall correctly). Perhaps originally DVDA's Burning folder destinations could be changed to another drive/folder because Tempuri's website would then be called upon by DVDA, but that accessibility vanished when the Tempuri website was shut down. That's my voodoo reasoning anyway.

At least DVDA continues to work - and in fact is burning a BD disk right now.

Many thanks again.

Cheers

Conrad