DVD Architect Pro 5.2 error when preparing Blu-ray

[Bill Mcfadden]

I too am getting the same error message when trying to prepare a Blu-ray disc for a large wedding project that was rendered as separate chapters on Vegas Pro 11. I have just over two hours of material in 22 separately rendered M2t files, at 1440×1080 resolution & 29+ frame rate. DVDA is the Pro version 5.2 and Build number 135, which didn’t correct the problem for me. I’m not sure about the Net Framework thing, but I’ll check and post about that.

My project is 17+gigs and I’ve gotten different results trying to burn to a single layer 25 gig BRD. Sometimes, I get halfway through the prepare process, and get the error. I was very hopeful last night when it got to 72%, well past the halfway mark, and went to bed. This morning I see it got to 83% (with 1 min remaining?) before sending up the same error message again, after a 5 hour prep.

I am running Win7 Pro, an Intel quad-core i7 2600k, 64 bit OS, @ 3.40 Ghz with 12 gigs of ram. I am preparing to a 3 terabyte drive with over 2 terabytes free space. I should have plenty of muscle here, right?

I am not computer paranoid, but I’m not an expert either, so re installing the OS or getting rid of key elements makes me feel more than a little uneasy, without clear instructions.

My client is expecting to get this in a week. Can anyone please help me? Please send separate email to BikeRidinBill@gmail.com if you can help. Thanks!!! 😉

[Bill Mcfadden]

@ Steven – you mentioned the DVDA Pro 5.2 Build 133 solved your BRD prepare error problem. Did you upgrade to that build, or did you roll back to it? I have Build 135 and it sure hasn’t solved any problems for me.

Secondly, you mentioned removing MS Netframe 4.0 from your system as a fix too. I see it in Programs under Control Panel, but can I just remove it without any consequence, or is something else not going to work correctly if I do that? Not sure what it’s for exactly, as I’m not at the software engineering level, knowledge-wise. If I delete it (remove it) will that fix my problem, ya think?

[Scott Gammans]

You might have to do what I did: Partition your disk, and create a partition that doesn’t have .net 4.0 on it. Once I did that, Vegas worked like a pro.

[Bill Mcfadden]

Thanks for the reply Scott. One thing you did not mention is whether or not your installation of Sony Vegas Pro (I have ver 11) is now residing on the partition without, or with, the NET framework on it.

Also, I don’t know that I’ll have time to implement that solution right now. To finish the project, I may have to opt NOT to burn a Blu-ray disc, and just give them the next best thing. Very disappointing though, that Sony would not create a fix for this problem, or at the very least, a step by step instruction sheet, considering how many people have been affected by their software bug, especially when it should be working as advertised to begin with.

I’m hoping that there may be another way to fix this that doesn’t involve partitioning, reformatting, etc., drives as part of the solution… particularly since it seems that different people have found different fixes to this problem. It doesn’t exactly instill confidence about following advice, when the advice differs so dramatically.

[Bill Mcfadden]

I should add that my OS, and primary programs, all reside on a single, internal, 100 gig solid state drive. Many of my other programs reside in two other drives, one 500 gig, 5400 rpm internal drive, and another 360 gig USB 3.0 drive.

Unfortunately, there is insufficient room on my C drive to create a partition, and as it is I have to watch over updates, installations, and recycle bin files so they don’t add up and encroach upon my free space, which can cause problems with rendering in Vegas if they add up too much. Right now, I think I have about 36-38 gigs of free space, which seems to run things very well with no problems… save this one regarding NET Framework and DVDA Pro 5.2.

Is there no other way to effectively deal with this problem? Has Sony washed their hands on this “bug” that they supposedly admitted to, leaving no other fix in sight? 🙁

Thanks for your help!