Burning problem with Santa

Discussion in 'Video - Software discussion' started by AVI_Miami, Oct 28, 2005.

  1. AVI_Miami

    AVI_Miami Member

    Joined:
    Oct 28, 2005
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    11
    I'm at my wits end. I have tried over and over to create a DVD from an AVI movie. When I add media to the list and click on Create DVD, it will go through the entire encoding process (usually about 90 minutes).
    Then when finished, it prompts me to burn the DVD. I click ok and the burn starts.
    Now, this happens EVERY time...at around 90~95% into the burn, I get a popup with some hexadecimal address and the burn is terminated.
    I have a very large stack of 'coasters' now.
    The encoded VOB files are saved in the TEMPDVD folder. If I merge them and open the single VOB with Virtual Dub Mod, it will encode as usual, So I don't believe there is a problem with the encoding.
    My comp has 512mb ram with the page file set at 1500mb. There are 20GBfree space on the drive. Processor is P4, OS=XP pro.
    I have uninstalled the Santa cleaned the registry and re-installed it. Same problem.
    Because the burn stops at the lead out[or whatever it is on DVD, they wont play].
    Has anyone out there run across this and is there a fix?
    Thx
     
  2. scf_au

    scf_au Regular member

    Joined:
    Sep 12, 2004
    Messages:
    2,869
    Likes Received:
    0
    Trophy Points:
    46
    Try just encode with DVDSanta without burning. Then go check to see if you have all the files intact (video_ts folder, ifo, vob) under the TempDVD folder. Also, click on the Vido_ts.ifo file to see if the movie plays o.k..

    If yes, try burn with another program (e.g. Nero).

    Good luck!
     
  3. AVI_Miami

    AVI_Miami Member

    Joined:
    Oct 28, 2005
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    11
    I didn't want to complicate my problem, but yes-I have tried to burnthe resultant Video_ts with NERO. After about 60% in the burn, I get the 'tracking error' popup. I have tried other DVD burning progs and the same thing always happens. Now, this only happens with the VOBs and IFOs that Santa encode. I can burn everything else with NERO without problems.
    I can burn the DVD in data mode with the video_ts files but in a standard DVD player it is useless.
    Again, this seems to be a problem ONLY with the encoded files that Santa makes.
    Could there be some kind of encryption that is preventing the burn?
    This is war. I'm going to win over DVDSanta no matter what it takes.
    Yes,I know about other progs and all, but I NEED to know why It is not
    working on my comp...
    thx.
     
  4. scf_au

    scf_au Regular member

    Joined:
    Sep 12, 2004
    Messages:
    2,869
    Likes Received:
    0
    Trophy Points:
    46
    So did the movie play alright after encoding with DVDSanta (but before the final burning)?

     
  5. AVI_Miami

    AVI_Miami Member

    Joined:
    Oct 28, 2005
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    11
    yes, perfectly. I can use file merger that comes with ACE mega codec pack to produce a single VOB file then Virtual dub Mod to encode it back to an AVI.
    The single VOB plays perfect as does the resultant AVI.
    There is just noway to make a DVD from the Santa encode.
     
    Last edited: Oct 30, 2005
  6. scf_au

    scf_au Regular member

    Joined:
    Sep 12, 2004
    Messages:
    2,869
    Likes Received:
    0
    Trophy Points:
    46
  7. AVI_Miami

    AVI_Miami Member

    Joined:
    Oct 28, 2005
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    11
    I downloaded DVDSanta Version 4.0 and everything works now. I was using version 3.4. So, it looks like the problem is over, even though I would have liked to know why or what caused the trouble.
    Thank you for the response.
     
  8. scf_au

    scf_au Regular member

    Joined:
    Sep 12, 2004
    Messages:
    2,869
    Likes Received:
    0
    Trophy Points:
    46
    Could be firmware related, but who cares so long as the problem is solved?

    *_*

     

Share This Page