No longer recognizes burner...

jrazz wrote on 7/13/2005, 7:27 PM
I am using a Sony dru-710a double layer burner. It is internal iede. I used it just fine with DVDA2 & 3 with no problems. I am currently using dvda3a and have burned with this build.
The problem started when I attempted to burn a double layer dvd. (I can still burn using Nero, or an ISO file burner as well as Windows XP built in burning- the point is that it is not a faulty drive or wiring). While setting up the options to burn a double layer disc, the only option I had for a burner was ISO image.
What happened? I can still use Nero, but there have been no upgrades or anything and now it just won't recognize my drive. I don't know if it was coincedence or if it really had something to do with the double layer discs, but now I cannot get it to burn to a 4.7gig disc. Any help would be greatly appreciated.

Comments

jrazz wrote on 7/14/2005, 8:42 PM
Anybody got anything on this? Is this something that I should pose to Sony directly?
Thanks.
DGrob wrote on 7/16/2005, 10:28 AM
Have a similar problem with a new installation. AMD 64 dual core running XP Pro. Have an NEC DVD_RW ND-3520A with dual layer. Burn DVDA menu only lists the ISO device option.

I've done the "search." Tried inserting media after starting Burn dialogue, DVDA still doesn't see the burner. BTW, Nero burns the DVD just fine.

Darryl
jrazz wrote on 7/16/2005, 1:15 PM
Sony... anybody,
Do you have anything thing on this. I have not changed any hardware settings or added any new software (except the occasional update from Microsoft). Since I originally posted, I have updated to DVDA3.0b from 3.0a.
ScottW wrote on 7/16/2005, 1:28 PM
Well you shouldn't necessarily expect a response from Sony; if you have a problem you should consider filling out a formal problem report. This is pretty much a peer support forum and folks from Sony respond only occasionally.

Here's my cut at it - DVDA has a long history of not working with a wide variety of burners and/or media. DVDA 3 was supposed to improve things in this area, but while there may be some improvement, clearly there's room to do better. No doubt a large part of the problem is that there are so many different burner manufacturers and such that may or may not correctly implement the interface, that unless you focus an enormous amount of effort on just testing with various burners (like I assume Nero does) and fixing identified problems (or working aorund them), customers are going to encounter these situations.

My feeling is that it's just not worth getting stressed about. DVDA is an authoring program, and a good one for what it does. It's not a burning program. So I just use Nero to do my burning (or CopyToDVD). Sure, people scream and jump up and down frequently about how DVDA should burn, etc., etc., but is it really worth getting that stressed out about something that's not likely to change considering how much a moving target new burners are?

It's my own opinion that they should strip out the burning part of DVDA entirely and partner with Nero to bundle the Nero burning engine with DVDA.

Just my 2 bits.
--Scott
DGrob wrote on 7/16/2005, 3:58 PM
Scott, thanks for jumpin' in. Agreed that DVDA3 is a fine authoring program, bit disconcerting when a "state of the art," dual-layer, burner doesn't show up. BTW, I can't even get Vegas 6 to extract audio from CDs, the combo drive doesn't show up there either!

Comforting that Nero will make it all go. (Though I haven't tried dual layer yet).

May just plug a new Plextor and be done with it. Planned on upgrading to BluRay or whatever anyway. Maybe just frameserve my HD out to H264 and burn that.

Darryl
JJKizak wrote on 7/17/2005, 8:02 AM
V6b and DVDA-3a see the Plextor 716a and the Pioneer 109 just fine.
The 716 will give you a deeper, richer burn even with the 8x discs.

JJK
jrazz wrote on 7/17/2005, 12:16 PM
Thanks for all the response. I will continue using Nero; it is just puzzling to me that up to a certain point, the sony double layer burner was recognized and worked fine and now all of a sudden it's not recognized at all.