DVD starts then stops! Help!

[KeithXP]

Let me start this thread over. I backed up a DVD using various methods using IfoEdit and CCE. The quality is phenomenal. I play the DVD using IfoEdit "DVD Play" button and with PowerDVD and WinDVD and all is great. As soon as I burn it with Prassi PrimoDVD, the DVD doesn't work. I go back and open each .ifo file with IfoEdit to compare it to the original and they have changed. No info comes up in any .ifo besides the vts_06_0.ifo that contains the movie. Somehow doing the burn process these files have changed.

1. Can PrimoDVD change files like that?
2. What causes this? A bad .ifo configuration?

I have managed to get the DVD to play by pushing pause immediately when the DVD is loaded. Then I push play and the movie begins. At this point I can get into the movie and all is good.

Does any of this ring a bell?

Help,
Supreme Newbie KeithXP

:confused:

[klona]

vts_01_ is needed to be fully DVD spec compatible, so that perhaps your problem with your standalone.

On my side, i am still unlucky with a DVD with extra ripped but menu still there to play in my Sony DVP-715S (Great device but more bitching than my wife !)

[KeithXP]

What burn software are you using? I'm thinking that PrimoDVD could be screwing it up too.

Help,
KeithXP

[gxal]

My sony 715 works perfectly with tdk and skc disks and make sure to have an audio_ts directory burned

[klona]

I have no AUDIO_TS dir on my DVDr...
I will try on next one. Thx.

[vwo]

another option, if the movie plays correctly in ifoEdit/WinDVD/etc.. is to use the image option under ifoEdit and then burn the image with PrimoDVD (I have had problems burning some discs, and apparently that is a problem with windowsXP). the burned image file should run okay on the standalone.

[KeithXP]

vwo -

That did it! I just made an image and burned it. Do you have any idea why burning the VIDEO_TS directory using Prassi PrimoDVD would not work just as good.

Weird. 5 DVD-R discs later- SUCCESS! Good learning experience.

KeithXP

[gxal]

I use Nero without a problem.I am not burning an image.
Everything fine with sony 715

[vwo]

keithxp

I think it has something to do with either Windows itself or with PrimoDVD in particular... apparently, Windows XP has some problems with burning DVD's, and primoDVD has its own internal "checks" that sometimes gets screwed up (I noticed that the problem can be seen right at the beginning of the burning process... look at the status line - right at the beginning, before you see "Initializing disc" you see that PrimoDVD burns a bit to the disc (directory?) - but instead of showing something like "burning 1.7KB out of 3.7GB", it will say "burning 1.7KB out of 1.7KB" - that's a sure sign that the disc is not correct. Whenever I have problems with primoDVD, I make sure to do one more check with ifoedit to make sure all pointers/files/folders are ok, then test play with winDVD, and if all checks up, I do create the image, and that seems to do the trick. As an aside, the AUDIO_TS folder (empty) is recommended by most people, but I have seen some commercial DVD's that do not have it.

If you don't mind going through the "extra" step, I would recommend doing an image for all burns, but, by my personal experience, this type of problem is sporadic at best (maybe one out of every 50 or 60 burns)
good luck

[KeithXP]

vwo -

Exactly. I will heed that advice. The extra step is not a problem at all. I am glad my initial learning is over. One successful backup down.

KeithXP

[klona]

Ok. I get lots of trouble with XP+Stomp RecordNOW Max, doing Standalone compatible DVDR.

What I found :

You need a VTS_01 IFO BUP at least to be compatible even if not needed
I put dummy files for _0.vob and _1.vob also (needed ?)
AUDIO_TS dir need to be there, even empty
As stated by KeithXP and vwo in this post , it's working a lot better doing the image from IfoEdit, and this way you cannot forget the final Get_VTS !
More you can use Daemon tools to mount it on a virtual DVDROM and play it from winDVD (or as I do Creative player with DXR board which is nearly like a standalone, from compatibility problem point of view)