PDA

View Full Version : Can't seek in retail DVD


JimmyBarnes
2nd September 2008, 07:30
I have a retail DVD (blockbuster movie, not a cheapie) and while it plays OK, seek is disabled. You can only go from one place to another in the movie using chapter forward or back - very annoying if you miss something and want to go back 10 seconds or so and look at it again.

A title search of "seek" in this forum found a few hits with the same problem but no solution to mine.

The movie is contained in a single PGC, so multi PGC is not the problem.

I retried remaking using DVDRemake Pro 3.6.3 with Enable all operations, but this did not fix - so PUOs are not the problem.

VTS_TMAPTI is not blank, it contains some 1900 entries, but maybe there's something in there which is preventing seeking,
and the correct value would fix it???

Your suggestions please

TIA

JB

Alex_ander
2nd September 2008, 07:50
The movie is contained in a single PGC
It's not enough to have all the movie within a single PGC.
Do you also mean there are no other PGCs in the title of that #?

JimmyBarnes
2nd September 2008, 09:13
It's not enough to have all the movie within a single PGC.
Do you also mean there are no other PGCs in the title of that #?

All I can tell you is:

In "Video Title Set 1", under "Program Chains", the entire movie is contained in "PGC 1 (title 1)" which contains 30 programs.

In "Video Title Set 1", under "Program Chains", the only other PGC is "PGC 2 (title 2)" which contains 1 program only. This is the movie trailer.

blutach
2nd September 2008, 09:22
Why have you cross posted Please re-read rule 8.

Eliminate VOB PUOps. Do this with PgcEdit's PUO plugin.

Regards

Alex_ander
2nd September 2008, 10:49
In DVDRemake you can look at the PUO status by right-clicking on PGC -> 'Set prohibited operations' - all the boxes should be unchecked in case your previous 'enable all operations' for VTS or DVD worked properly.

P.S.
Also there is such a thing as 'restricted' attribute for individual cells (column 'restricted' in 'programs' tab), editable from r-click -> 'edit block attributes.'

JimmyBarnes
2nd September 2008, 11:21
Why have you cross posted Please re-read rule 8.

I have deleted the other post

Eliminate VOB PUOps. Do this with PgcEdit's PUO plugin.


Is this different from what I have already done? ["using DVDRemake Pro 3.6.3 with Enable all operations"]

JimmyBarnes
2nd September 2008, 11:36
In DVDRemake you can look at the PUO status by right-clicking on PGC -> 'Set prohibited operations' - all the boxes should be unchecked in case your previous 'enable all operations' for VTS or DVD worked properly.

Yes they are all unchecked indicating "Enable all operations" worked as intended


P.S. Also there is such a thing as 'restricted' attribute for individual cells (column 'restricted' in 'programs' tab), editable from r-click -> 'edit block attributes.'

All entries in the "Restricted" column are "no"

JimmyBarnes
2nd September 2008, 12:08
If one makes alterations to a DVD, is there any way to see the effect without actually burning a DVD? i.e. to see if the seek problem has been fixed

In the case here the DVD content is more than 4.4 GB so requires a DL DVD and there are no DVD±RW DL commonly available.

Taurus
2nd September 2008, 13:33
Create an ISO from your VIDEO_TS with IMGBurn or any DVD burning engine you might own.
Mount the ISO Image with Daemon Tools or the like.
You can watch and explore like a real DVD from Windows Explorer.

JimmyBarnes
2nd September 2008, 13:42
Create an ISO from your VIDEO_TS with IMGBurn or any DVD burning engine you might own.
Mount the ISO Image with Daemon Tools or the like.
You can watch and explore like a real DVD from Windows Explorer.

Cool thanx for the tip.

BTW I SOLVED the seek problem. As usual the devil is in the detail.

I had previously unchecked only some PUOs or not for the entire DVD. This time I did "Enable all operations" in DVDRemake 3.6.3 at the very top of the DVD tree i.e. "DVD". I exported the remade DVD, burnt to yet another DVD+R DL, and found it seeked normally.

Thanx to everyone who contributed and I hope this discussion helps at least some others who might have this problem. None of the other threads re this problem ever seemed to come to a "fixed" conclusion.