Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums VEGAS Pro DVDA2 burns “Blank” DVD

  • DVDA2 burns “Blank” DVD

    Posted by Kevin Mccarthy on June 9, 2005 at 8:24 pm

    My DVDA2 has just burned 2 “blank” DVDs. The info appears to be written to the DVD but no player will recognize it, including the burner in my system. DVDA tells me the burn was successful..(no error messages) but it appears to not be finalizing the disc as each player says it is a blank disc. Could any setting changes (I have not knowingly changed anything) cause this? Up untill now it has worked perfectly. Any suggestions? I have a client waiting for an approval…isn’t that always the case!!! Thaks everyone.

    Mary Waitrovich replied 20 years, 11 months ago 6 Members · 5 Replies
  • 5 Replies
  • Mike Kujbida

    June 10, 2005 at 4:44 am

    This is one of the main reasons why I don’t use DVDA to do a burn. Instead, I “prepare” the files and use RecordNow Max to do the actual burning.
    Do you have another app (Nero?) that you can try?
    Does your burner only support -R blanks and you accidentally used a +R?
    If all else fails, try a re-install of DVDA.

    Mike

  • Margie Marfi

    June 10, 2005 at 4:39 pm

    Hi,

    I had trouble off and on with my Sony burner. It could burn + and – and had the capability of USB or firewire connection to the CPU. I changed it from the USB connection to the firewire connection and haven’t had trouble since. Also noticed that I need to have the (external) burner on when I turn on the computer or I’ve had trouble there also with DVDA.

    Best wishes,
    Margie

  • Seth Bloombaum

    June 10, 2005 at 7:32 pm

    This could easily be bad media. Try another brand?

  • Jim Murphy

    June 10, 2005 at 9:19 pm

    To avoid coasters I use a +RW disc first. I also “prepare” in DVDA, then use RecordNow Max to make a “data disc.” I have not had any problems doing it this way. Jim

  • Mary Waitrovich

    June 11, 2005 at 11:44 am

    When I had this problem, it turned out to be the firewire connection. Restarting was all it took.

    Mary Waitrovich
    UW-Madison

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy