DVD Architect Pro 5.2 error when preparing Blu-ray

[Nigel O’neill]

Scott

Is your prepare folder pointing to a drive that is getting full?

Intel i7 920, 12GB RAM, ASUS P6T, Vegas Pro 10 (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[Scott Gammans]

Hi Nigel,

It’s not even close to full.

I noticed at the Sony DVD Architect discussion forum that a couple of users had reported the same problem and they thought it had something to do with the Microsoft .NET 2.0 framework not being installed correctly. The thing is, I’m running DVD Architect Pro 5.2 on a Windows 7 Ultimate 64-bit O/S, so there is no .NET 2.0 redistributable to fix. Win 7 installs .NET 3.5 as the base framework, and you can’t install .NET 2.0 on Windows 7 (the installer aborts with a message that Win 7 already includes .NET 3.5).

I see that you are also running Windows 7/64… have you heard of .NET 2.0 not being installed correctly as a possible cause?

Thanks!

[Rob Franks]

Why are you rendering 24p if your original is interlaced??

Which encoder are you using… the pro or studio encoder? (You need to use the pro encoder for blu ray) Also… make sure you’re rendering a SEPARATE M2V and AC3 file. Let DVDa mux them.

[Nigel O’neill]

I’ll check my setup tonight and post tonight (12 hours from now). Typically when producing for Blu-ray, I render to an HDV intermediary from Vegas e.g. HDV 1080/50i so I can use DVD Architect to create both a DVD or Blu-ray disc. One of my clients wanted both. This does mean DVDA has to do the heavy down conversion to DVD and I don’t think DVDA is a multithreaded application in the true sense. When looking at task manager, only 1 core is getting a workout whilst the others are idle. I would have last done this on DVDA 5.0 successfully, and it takes about 12 hours to author a 4 hour blu-ray disc using this method.

Just out of curiousity, have you tried using DVDA 5.0? See if it gets around this problem.

FYI, you can have both Versions installed.

You might want to try creating an ISO using a much smaller file so you can prove the process actually works before increasing the content.

Intel i7 920, 12GB RAM, ASUS P6T, Vegas Pro 10 (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[Scott Gammans]

Hi,

I’m rendering at 24p to get the look of film.

Yes, I rendered separate *.m2v and *.ac3 streams. The error was occurring when creating the *.iso.

Since this was an almost-new install of Win7/64, I opted to do a fresh reinstall of the O/S. Volia! Problem resolved. No idea what the problem was, but I am a software engineer and I also had Microsoft Visual Studio 2010 and the .NET 4.0 framework installed before… maybe one of those was the conflict. Now that I appear to have a stable editing environment I think I will just run my dev tools on a separate boot environment.

Thanks!

[Scott Gammans]

Hi,

Thanks, but as you can see above I went for the nuclear option and resolved my issue with a fresh O/S reinstall. Wish I knew what the conflict was. I think from now on I’m going to run a simple test suite (e.g., render an *.m2v, mux an *.iso) after any further software installs to ensure I don’t break anything.

Thanks!

[Stephen Crye]

Scott, thanks for this important clue!

I’ve been struggling with some other (possibly related ) DVDA 5.2 problems for the last 3 days. As part of my testing, I tried to create a new BD project, received the same error:

Warning: An Error occurred while writing a file.
Error 0x80131604 (message missing)

I recalled seeing a .Net 4.0 Windows Update come through during a recent Patch Tuesday. I normally am very leery of .Nyet , and usually don’t apply them. For some reason my radar was down and I let Windows install it. (I’m running Win 7 Pro x64) . Nothing obviously bad seemed to happen until these bizarre DVDA problems surfaces 3 days ago.

I just did a system restore back to 9.7.2011, and guess what? No more Error 0x80131604!

GRRRRR….

Here the link to the other problem I’m fighting. Stand by for test results after going back to the restore point.

Steve

[Stephen Crye]

HOORAY!!

Getting rid of stupid .Net 4.0 also solved the “DVD Architect 5.2 Pro burns suddenly will not play in DVD players” problem!!

This is by far most baffling and counter-intutive DVDA problem I have ever suffered. It has left me drained and wondering if I should just give up and move to a mud hut…

I’ll update the other threads. Hopefully other people will benefit from my pain ..

Scott, thanks again for the clue that provided relief!

Steve

Win7 Pro X64 on Dell T3400 MultiTB SATA 8 GB RAM Vegas 10e x64 DVDA 5.2

[Scott Gammans]

You’re very welcome.

Incidentally, I have not yet upgraded to the latest release of Sony Vegas 10.0 (10.0e Build 738 64-bit) so I don’t know whether this problem has been addressed in that release. But on the version I have (10.0c Build 470 64-bit), it definitely does not play nice with the Microsoft .NET 4.0 framework.

[Stephen Crye]

Hi;

Everyone, all my DVDA problems were solved by the DVDA 5.2 build 133.

No more strange problems with .NET.

Sony admits in the release notes that this was a bug!

The horrible Sony “free” support took 3 weeks to respond. By then I had already solved it.

I’m happy, but drained by the troubleshooting effort.

Steve

Win7 Pro X64 on Dell T3400 MultiTB SATA 8 GB RAM Vegas 10e x64 DVDA 5.2 Sony HDR-CX550V