Problems with Burning all of a sudden

StormCrow wrote on 12/14/2005, 5:52 AM
I brought a file rendered to MPEG2 in from Vegas and built a DVD in DVDA 3.0b and then rendered/prepared/burned it using DVDA. Burned successfully and then I went to burn another and it gave me the dreaded burn error message. The DVD is 102% full which DVDA always fluffs up a bit so I know I can always fit 105% on the DVD with no problems so far. Well without anything changing what so ever when I went to burn another copy of the same exact DVD in DVDA I got the burn error after it finished? The DVD plays fine until near the end of the DVD and then it starts hesitating and eventually locking up. So I took the one good DVD that I was able to burn in to NERO 7 Ultimate and tried to copy it. I'm getting errors copying it also. So I had to tell Nero to ignore read errors.

What I am now doing is just bringing the prepared file in to Nero to burn but the one thing it will not do is let me pull the Jacket Cover in with the file prepared in DVDA? It seems that the Sony software must be putting the Jacket Cover somewhere it should not be. Any ideas how I can rectify this?

Comments

dand9959 wrote on 12/14/2005, 11:50 AM
I had a similar burn problem...though it happened on my first burn. DVD was about 70% full. In one player (out of 5 tested), the DVD would play fine until near the end, then hesitate, then lock up.

After several iterations, with the same result, I found that applying a Broadcast Colors filter to the whole production (Conservative Setup setting) seemed to fix the problem.

Now, I can't say for sure if applying that filter worked, or if some other random thing in my system actually fixed the problem for this particular burn.
StormCrow wrote on 12/14/2005, 2:25 PM
Well I honestly hope to God that it is something else other than a filter that may need to be applied. That would be crazy if it was something like that.

I'm using Windows XP Home SP1
Sony DRU-710A
P4 3.0GHz Processor
1 gig Corsair XMS memory
Sony DVDA 3.0b

This problem did not exist previously and just popped up. There has been no new installs on this machine at all or any software or hardware removed. This is what is so perplexing about this.
dand9959 wrote on 12/14/2005, 2:41 PM
This only happened to me since moving to Vegas6. I never had a problem like this beforehand.
StormCrow wrote on 12/15/2005, 4:30 AM
Anyone from Sony ever check this site out and offer any help?
StormCrow wrote on 12/15/2005, 8:01 AM
Weird update on this problem I have been having burning with DVDA 3.0b.

This morning I downloaded the new updates for windows XP from Microsoft for SP1 and security updates and the malicious tool removal software. I rebooted after that and then ran SpyWareBlaster and Ad-Aware back to back and removed the problems they found. I then booted up DVDA and tried to burn a DVD with it. IT WORKED! So I tried to burn another and it worked. I've now burned a total of three DVD's and they all work fine and burned succesfully.

So what could have caused this problem? This is just too freaky and i'm worried that this same thing may happen again down the road when a really pressing deadline is approaching.
StormCrow wrote on 12/16/2005, 12:03 PM
Problem is back again... I've been able to burn maybe 6 good DVD's and all day today get this error maessage from DVDA 3.0b. Unbelieveable!

'SFMMCX'-(17)
'atapi'-(0)
-'SONY DVD RW DRU-710A BYX2'-(0)
Module sfmmcx.cpp Line 2311
The command completed successfully.
No sense.

Status: 00000000
Command:
Sense: 00 00 00
Info: 00 00 00 00
Specific: 00 00 00
Extra:
StormCrow wrote on 12/19/2005, 1:48 PM
Newest update on this problem. I'm seriously beginning to think that the problem lies with the DVDA 3.0b software and not my computer. It appears as though DVDA 3.0b is very finicky with the media you use to burn. After many successful burns I could not get it to burn on RitekRidata and switched to Verbatim and it burned the first two fine and then gave the same error messages on the third burn attempt. So I then took the RitekRidata media in to my other computer and tried burning using DVDA 3.0b on that computer... the attempt failed with the same error massage as the other computer gave me. The burners are different with the main edit computer having a Sony DRU-710A and the office computer has a Sony DW-U10A burner. I then booted up DVDA 2.0 and tried burning a DVD and it burned no problem on the RitekRidata media that DVDA3.0b has problems with. I ordered Sundya morning some of those Taiyo Yuden blank DVD's and will see if those will work. If so I don't mind buy them but have got to say I wish Sony would step forward and make DVDA 3.0 as stable as Vegas other wise this guy may end up switching over to FCP Studio and going in a whole otehr direction. I've been with Sony since Vegas 4.

What is causing these problems? Anybody?
StormCrow wrote on 12/22/2005, 8:07 PM
Hope this helps someone out but I decided to try a different media other than the Ritek / Ridata that had been working for me and then all of a sudden stopped working or giving good burns. I ordered some Taiyo Yuden DVD's and so far the first three have burn without fail so perhaps all along it was the media and I had just gotten a bad batch of the Ritek / Ridata DVD's.
vkrhodes wrote on 1/4/2006, 8:37 AM
No the problem still occurs with me. I have tried all kinds of media as Sony suggest. I have burned over 400 dvd's with previous versions of Architect and have never encountered this problem until I updated to the "C" version. I create the DVD in Architect and then actually burn it with Nero, which stinks. Architect has the option to create and burn and should work.
My error message;
THE DISK IS NOT OF A MEDIA TYPE SUPPORTED BY THIS DRIVE

'SFMMCX'-(17)
'ultra'-(2)
-'SONY DVD RW DRU-700A VY08'-(2)
Module sfmmcx.cpp Line 1795
The drive is not ready.
The disc can't be written. It is an incompatible format.

Status: 00020202
Command: 2a 00 00 00 0e 20 00 00 20 00
Sense: 02 30 05
Info: 00 00 00 00
Specific: 00 00 00
Extra: 00 00 00 00 00 00 00 00 00 00
johnmeyer wrote on 1/4/2006, 9:25 AM
Problems that come and go are generally NOT the fault of the software program. While computer software sometimes seems to exhibit human tendencies, that is usually more a result of how we view things than how they actually act.

The point is that a computer program, by its nature, does the same thing every single time. If you experience different outcomes when doing the exact same thing more than once, you should be looking elsewhere for the culprit. Certainly the fact that your adware programs found problems makes me suspicious that your computer may not be 100% hale and healthy.

I'd also be suspicious of the DVD burner, even if it is relatively new. I have only lost one hard disk in twenty-five years, and only one computer motherboard, but I've lost six CD-ROM and DVD drives in the past five years. They are the worst-made component in your computer. They fail all the time, often after burning only a few hundred discs.

Media is also a likely culprit. I always buy top-notch media, but I got curious a few months back and on a whim bought 25 super-cheap, no-brand discs online. The quality of these is unbelievably bad. You can see clear through the darn things. You can actually see defects in the dye, just by looking at them with the naked eye. The dye doesn't even make it all the way to the edge on some discs. Each disc looks different. Take a look at this site, and click on the links that talk about media and DVD burners:

Digital FAQ