Trying to backup a flipper to DVD+R DL while retaining menus

[rdkapp]

Thanks for the good wishes r0lZ, but I'm afraid to say that I ran into the exact same problem processing the "splits" in VB 2.1.3.0 beta 4; however, this time it reached 99% before freezing up. The log stated something similar, like:

Title VOB Fixing Pointers Started
VTS 01: Fixing VOB pointers in 13 Cells of 25
Fixing Cell #13, VID=2 CID=1

I'm not 100% sure of the numbers, because I didn't write them down, but the words were spot on. I can run it again, if it will help.

Do you think deleting the tiny cell in disc 2 could be causing this problem in VB 2.1.3.0 beta 4? Do you know a simpler workaround, or do I have to go back to VB 2.1.2.0 to do the "splits?"

Also, one thing I was noticing when doing the splits in VB 2.1.3.0 beta 4 (which, BTW, was much easier), is that even though I matched the exact scene, the time was off as much as 55 seconds. Most were less than that, however. I went with matching the exact scene over the time, but, is the time secondary to matching the exact scene, or is time the primary consideration?

[r0lZ]

When VB fixes the big cell, it is normal that it works silently during several minutes, as it has to read the 4GB or 5GB file from your hard disc, and fix some values on the fly. This could take almost the same time than ripping a single-layer DVD. But VB should finish its work after some time. Are you sure it was really hung?

Deleting the tiny cell is certainly not the problem, if you have correctly removed it from the VOBs with PgcEdit and FixVTS. Leaving it there can be problematic.

I don't understand why the cell times are off, as they should be equal (in duration) than in the original DVD. Note also that the time displayed by PgcEdit is the duration and the END time of the current cell. So, when loaded in VB, the big cell (containing side 2) begins at 0:00, which is the beginning of the first chapter of side 2. The beginning of the next chapter should be equal to the end time of chapter 1 of side 2, as displayed by PgcEdit. Anyway, you have to split the cells at the beginning of each chapter. Maybe VB has a bug when it computes the elapsed time.

I have never had similar problems with VB, but it is true that I use it only to replace tiny cells by single short cells, not by a huge film like you did. I haven't paid attention to the timings, as I have only used the Split Cell feature to create custom chapters, and never to duplicate predefined chapters points.

Sorry, but I can't help much more.

[jsoto]

@r0lZ
Thanks for answering...

Thanks for the good wishes r0lZ, but I'm afraid to say that I ran into the exact same problem processing the "splits" in VB 2.1.3.0 beta 4; however, this time it reached 99% before freezing up. The log stated something similar, like:

Title VOB Fixing Pointers Started
VTS 01: Fixing VOB pointers in 13 Cells of 25
Fixing Cell #13, VID=2 CID=1

I'm not 100% sure of the numbers, because I didn't write them down, but the words were spot on. I can run it again, if it will help.
[/code]

The precentage means the MBytes wrtten versus the total MB to be written, but Fixing pointers phase is not taken into account in the statistisc, because the VOB is already written to the disk; in this phase some internal pointers are being re-writen in the same file/s, and, as r0lZ said, it takes some time...
From your logs, seems VB hangs when trying to fix the cell #13, which is the last one...(according the log, 13 cells have to be fixed)... I'll take a look to see if I can reproduce the problem.
I've understood you do not have this problem in the previous version, do you? Are you able to FIX pointers in VB 2.1.2?

Also, one thing I was noticing when doing the splits in VB 2.1.3.0 beta 4 (which, BTW, was much easier), is that even though I matched the exact scene, the time was off as much as 55 seconds. Most were less than that, however. I went with matching the exact scene over the time, but, is the time secondary to matching the exact scene, or is time the primary consideration?

Elapsed time shown in preview dialog is the "Cell elapsed time", and it is just read from the VOB.... I cannot understand why it is not fully accurated... With which numbers are you doing the comparation?

For sure, the scene (and not the time) is what you have to use to select the IFrame. Please use next and prev buttons to show it in the screen.

jsoto

[r0lZ]

@jsoto
Thanks for answering... ...as I am now puzzled.

[rdkapp]

When VB fixes the big cell, it is normal that it works silently during several minutes, as it has to read the 4GB or 5GB file from your hard disc, and fix some values on the fly. This could take almost the same time than ripping a single-layer DVD. But VB should finish its work after some time. Are you sure it was really hung?

Yes, I'm sure. Earlier, with the "replace" procedure, I tried 3 or 4 times with VB Beta 4, and left my computer for significant periods of time (probably over an hour in one instance), only to come back to it stuck at 73% and showing "Not Responding." During the "split" procedure, I was at my computer and watched it stay at 99% for several minutes with no progress on the log and it eventually showed "Not Responding," at a similar point in the log. VB 2.1.2.0 worked just fine on the "replace" procedure in an amount of time that was not extraordinary. I guess I'll have to suck it up and use VB 2.1.2.0 to do the splits also.

Just for grins, I tried the "splits" again, but didn't split the last couple of chapters. I was hoping that VB 2.1.3.0 beta 4 would at least be successful splitting most of the chapters and then I could go in and split the remaining ones with VB 2.1.2.0. No such luck. The same thing happened. Here's a screen shot:



I actually have a log saved just prior to it reaching the point shown above (where it hung). If it will help, I'll post it. Just let me know.

Deleting the tiny cell is certainly not the problem, if you have correctly removed it from the VOBs with PgcEdit and FixVTS. Leaving it there can be problematic.

OK. I'm pretty sure I removed it correctly. Besides, VB 2.1.2.0 worked just fine on the "replace" procedure.

I don't understand why the cell times are off, as they should be equal (in duration) than in the original DVD. Note also that the time displayed by PgcEdit is the duration and the END time of the current cell. So, when loaded in VB, the big cell (containing side 2) begins at 0:00, which is the beginning of the first chapter of side 2. The beginning of the next chapter should be equal to the end time of chapter 1 of side 2, as displayed by PgcEdit. Anyway, you have to split the cells at the beginning of each chapter. Maybe VB has a bug when it computes the elapsed time.

I have never had similar problems with VB, but it is true that I use it only to replace tiny cells by single short cells, not by a huge film like you did. I haven't paid attention to the timings, as I have only used the Split Cell feature to create custom chapters, and never to duplicate predefined chapters points.

Sorry, but I was incorrect on the time discrepancies of the cells. It was late and I wasn't thinking clearly. The biggest discrepancy was not 55 seconds; it was less than 1 second. I went back through, and there were 5 chapters with time differences, the smallest being 0:00.05 and the largest being 0:00.92. Are those minimal discrepancies meaningful or a problem?

Now, for jsoto's post:

. . . I've understood you do not have this problem in the previous version, do you? Are you able to FIX pointers in VB 2.1.2?

Thanks for joining in jsoto. I appreciate your help. No, I have not had the problem in VB 2.1.2.0. When I replaced a tiny cell in disc 1 with the entire disc 2 movie, VB 2.1.3.0 beta 4 hung at 73% several times, and each time the log said:

Title VOB Fixing Pointers Started
VTS 01: Fixing VOB pointers in 1 Cells of 13
Fixing Cell #13, VID=2 CID=1

, but VB 2.1.2.0 was successful with the replacement with no hitches. I haven't tried "splitting" with VB 2.1.2.0 yet, because it's a much more time consuming task, but I would guess that it will work just like it did before and like it did with the replacement. I'm hoping you guys can figure out a workaround before I actually take on the task. <INPUT onclick="doEmoticon(this.form.body,eList,64);retur n false;" type=image alt=:hope src="http://pages.sbcglobal.net/sabertooth/emoticons/crossfingers.gif">

Elapsed time shown in preview dialog is the "Cell elapsed time", and it is just read from the VOB.... I cannot understand why it is not fully accurated... With which numbers are you doing the comparation?

For sure, the scene (and not the time) is what you have to use to select the IFrame. Please use next and prev buttons to show it in the screen.

jsoto

Actually, the time differences are not as great as I first reported. See my response to r0lZ above. I am comparing it with the cell times and preview of disc 2 opened up in VB 2.1.2.0. And, I am using the Next and Prev buttons when marking the split.

[jsoto]

I did a quick test (well, it takes some time...) and the problem didn't happen to me.

BugFix: VobBlanker was not launching the fixing pointer phase when a
cell number mismatch was detected replacing cells/pgcs

This was a bugfix in 2.1.3. That means 2.1.3 launches automatically the fixing pointers phase, but 2.1.2 doesn't.
Could you please manually force the fixing phase in 2.1.2 and check if 2.1.2 does not hang?
[EDIT]
To manually force the fixing phase, just activate the checkbox "Fill always VOB SYNCI/SRI pointers in Titles" in MoreSettings dialog.
[/EDIT]

I didn't change anything in this part of the code...

If 2.1.2 also hangs, may be there is something wrong in the VOB (it still could be a bug in VB)... I'm interested.., may be I could compile a test version with more log details during the fixing phase.

I went back through, and there were 5 chapters with time differences, the smallest being 0:00.05 and the largest being 0:00.92. Are those minimal discrepancies meaningful or a problem?

No, don't worry about them. I've seen such kind of (minimum) differences in some originals...

jsoto

[r0lZ]

The biggest discrepancy was not 55 seconds; it was less than 1 second. I went back through, and there were 5 chapters with time differences, the smallest being 0:00.05 and the largest being 0:00.92. Are those minimal discrepancies meaningful or a problem?

When you push the slider all the way to the right, you select the beginning of the last VOBU of the current cell. Since the last VOBU of a cell must have a duration between 0.5 and 1.2 seconds, the differences you have noticed are normal. To see a more accurate cell duration, use PgcEdit's cell table (although it is possible, especially with ARccOS protected DVDs that the duration stored in the IFOs are wrong, but VB should have fixed them anyway.)

I hope jsoto will be able to help you more than I did!

[jsoto]

OK, I've uploaded a new beta (beta5) with more logging capabilities.

http://download.videohelp.com/jsoto/betas/

Just start VobBlanker once and exit (to create the key)
Open the Registry in regedit and
change to "1" the value of the key
HKEY_CURRENT_USER\Software\jsoto's tools\VobBlanker\General\LogFixingPacks

After that, when fixing pointers, your log will look like:

VTS 01: Fixing VOB pointers in 1 Cells of 28
     Fixing Cell # 27, VID=2  CID=15
       #Navs: 508,  #AudInCell[0]=3575  #AudInCell[1]=0
        VOBU#: 0,  File: VTS_01_1.VOB, LBA 10425 
        VOBU#: 1,  File: VTS_01_1.VOB, LBA 10719 
        VOBU#: 2,  File: VTS_01_1.VOB, LBA 11029 
        VOBU#: 3,  File: VTS_01_1.VOB, LBA 11321 
        VOBU#: 4,  File: VTS_01_1.VOB, LBA 11604

Let me know what you see in the log...
jsoto

[rdkapp]

Could you please manually force the fixing phase in 2.1.2 and check if 2.1.2 does not hang?

To manually force the fixing phase, just activate the checkbox "Fill always VOB SYNCI/SRI pointers in Titles" in MoreSettings dialog.

I didn't change anything in this part of the code...

If 2.1.2 also hangs, may be there is something wrong in the VOB (it still could be a bug in VB)... I'm interested.., may be I could compile a test version with more log details during the fixing phase.

jsoto

After the adjustment, VB 2.1.2 also hung in the fixing phase. See the screenshot:



The only things I've done to the original VOB files are: (1) remove a tiny cell at the end of the movie on disc 2 with PgcEdit; and (2) replace a tiny cell at the end of the movie on disc 1 with the modified movie from disc 2 with VB, which is where the fixing error first arose.

jsoto, I saw your follow up post about Beta 5. I will download it and make the adjustment to the registry a little later (I have a prior obligation). After the registry adjustment, do you want me to try to split the large last cell again?

[jsoto]

After the adjustment, VB 2.1.2 also hung in the fixing phase.

Ah! this makes more sense...

The only things I've done to the original VOB files are: (1) remove a tiny cell at the end of the movie on disc 2 with PgcEdit; and (2) replace a tiny cell at the end of the movie on disc 1 with the modified movie from disc 2 with VB, which is where the fixing error first arose.

May be the problem is related with your material, and not with the splitting process.
Please try fixing pointers in disc2 "as it is". Just open it in VB, activate "Fix always SYNCI/SRI in Titles" and process.
Do it using the beta5 and LogFixingPointers enabled
If this test hangs please try to isolate the faulty cell:
- Select blank all the menus (you have to do it one by one)
- Select blank all the titles except the faulty cell (you can use the main menu "Titles->blank all" , and, after that select your cell and click on "keep")
- Process in VB w/o adjusting VOB pointers
- Open the (small) DVD generated (only one true cell, all the rest are blanked) and try to adjust VOB pointers on it, processing the DVD in keep mode with "Fix always SYNCI/SRI pointers in titles" activated.
- If fails, please try to upload the cell (or the whole small DVD) to a site like rapidshare. I'd like to take a look and fix the problem.

jsoto, I saw your follow up post about Beta 5. I will download it and make the adjustment to the registry a little later (I have a prior obligation). After the registry adjustment, do you want me to try to split the large last cell again?

Try it again only if the previous test pass w/o errors.

jsoto

[rdkapp]

May be the problem is related with your material, and not with the splitting process.
Please try fixing pointers in disc2 "as it is". Just open it in VB, activate "Fix always SYNCI/SRI in Titles" and process.
Do it using the beta5 and LogFixingPointers enabled

It didn't hang. It finished with no errors, warnings, or notes. The log is attached.

I activated "Fix always SYNCI/SRI in Titles" and then PROCESSed; however, I wasn't sure what you meant by "LogFixingPointers enabled?" Is that the same thing as "Fix always SYNCI/SRI in Titles?"

[r0lZ]

I suppose jsoto means "LogFixingPacks".

Just start VobBlanker once and exit (to create the key)
Open the Registry in regedit and
change to "1" the value of the key
HKEY_CURRENT_USER\Software\jsoto's tools\VobBlanker\General\LogFixingPacks

To start regedit, go to Start -> Run, and type regedit in the dialog box.

[rdkapp]

I suppose jsoto means "LogFixingPacks".

To start regedit, go to Start -> Run, and type regedit in the dialog box.

Hmm, maybe so. I did adjust the registry as instructed, but I was a little confused by his instruction to activate "Fix always SYNCI/SRI in Titles" (which I did), using "beta5 and LogFixingPointers enabled." I thought he might be referring to a setting in VB 2.1.3 beta 5. I poked around, but couldn't find such a setting, but the log is as he described, just w/out errors.

[jsoto]

Yes, I meant LogFixingPacks..., sorry

LogFixingPacks: Nothing to do in VB process itself, just outputs in the Log file one line each time a Nav Pack is fixed. I was expecting to see where the process hangs...

"Fix always SYNCI/SRI in Titles". Used to force a fixing pointers phase. Not needed (it is redundant) in 2.1.3 when splitting, because VB automatically activates this phase if needed. Required in 2.1.2 because (due to a bug) VobBlanker was not automatically activating this phase when needed.

Well, I'm puzzled now...
beta 5 fixes a bug when cutting+split (nothing to do with this issue), but nothing more...
And your log shows a successful process! (with LogFixingPacks activated, but succesful)
I assume that beta5 w/o LogFixingPacks (just change it to zero) also works...



jsoto

[jsoto]

Ah! May be your log is the process of disc 2 "as it is"?

So, please try to reproduce the hang splitting the cell with LogFixingPacks activated, just to see where the process hangs...

jsoto