Version 2.0 less compatable than 1.0

SChadder wrote on 9/8/2004, 12:26 PM
I'm sorry I spent the money to upgrade to 2.0 as the DVDs from the same projects won't play on our "test" player, but only in newer players.

I've tried projects that work fine in version 1.0, and making a simple project from in 2.0 from scratch and I run into the same problem.

When I insert the DVD It plays the first video instead of the menu. If hit stop it twice, and press play it will play the menu, but the links to none of the other videos work.

We've had great luck with version 1.0 so I guess I'll have to reinstall it as compatability is more important than bells and whistles.

The "test" player is a Koss that is a couple of years old.

Comments

GaryKleiner wrote on 9/8/2004, 8:53 PM
What happens when you prepare the project with DVDA 2.0, and burn it with 1.0?

Gary
TorS wrote on 9/8/2004, 11:20 PM
When I burn a DVD+R disc in DVDA 1 it is automatically set to book type DVD ROM, which makes it compatible to all but a few extremely picky or awkward players. In DVDA 2 (I think) book type has to be set manually. Could that be it?
Tor
ScottW wrote on 9/9/2004, 5:58 AM
The problem appears to be (to me anyway), that the layout of the VOB files has changed rather dramtically between 1.0 and 2.0. In fact the IFO structure has changed as well, but I think it's the VOB structure causing the problem.

In 1.0 the main menu ends up in VTS_01_1.VOB, with 2.0 the main menu seems to end up in VTS_01_0.VOB with the first movie content ending up in VTS_01_1.VOB.

The thing I find insteresting is that in both 1.0 and 2.0, the command to take you to the main menu specifies VTS 1, title 1 - I've not puzzled out the mapping between title numbers and file naming, but this could be a bug in DVDA 2.0 if the title number is supposed to map directly to the number in the VOB.

I would guess the newer players seem to not make assumptions about mapping title numbers to filenames and actually examine the VOB files to see what's available - so VTS 1, title 1 would map to VTS_01_0.VOB if it was present, or it would map to VTS_01_1.VOB if the _0 wasn't present.

Since I don't have access to a player that doesn't work, I can't verify the theory.

You could *try* renaming VTS_01_1.VOB to VTS_01_2.VOB and VTS_01_0.VOB to VTS_01_1.VOB to see if that fixes the issue with accessing the menu, though it probably will break access to the movie(s).

--Scott
SChadder wrote on 9/9/2004, 9:10 AM
Yes that sounds possible. The problem is definitely in the authoring and not the burning. I'll give it a try, perhaps I can fudge the menu actions to match the changed file names.

Thanks
SChadder wrote on 9/9/2004, 2:11 PM
Drat. Changing the file names didn't work. Thanks for the idea, back to version 1.0

Shane