I Re-Authored the Movie-Only of the DVD "Lost in Translation", with one Audio track and it was above 99%+ so the result turned out to be excellent. Out of curiosity, I also used DVD2ONE for comparison pusposes, and burned two different backup DVDs. PQ aside, DVD Shrink 3.1.6(B) created a DVD that froze at around One Hour and 5 Minutes, plus some seconds. It was the scene where the hyper Britney Spears look-alike is singing in the bar, and Bill Murray and Scarlet Johansson are senaking by her, trying not to be recognized. In fact, there were two freezes. Which I assume is the DVD player reacting to a pseudo layer break. But I'm only speculating. On the DVD2ONE, I had no freezes. The Layer Break is within the vicinity of the freeze, around one hour and 4 minutes. I checked the output of DVD Shrink with IFOEDIT, and it looks like the Type Code was changed properly from 0 to 8. Any suggestions how to get more information as to why/what happened? Lastly, if anyone else has had a similar problem, please share your experience. Thanks, Gary
BACKUP NOTES on February 19, 2004: ----------------------------------------------------- MOVIE TITLE: LOST IN TRANSLATION - NTSC/R1 DVD Shrink 3.1.5 (1) I picked Re-Author Mode and dragged Title 16 to left column. . (2) Audio: AC3 5.1-ch English = ON; All other Audio = OFF. (3) All Subpicture = OFF. (4) Video = 99.1%. (5) I did Re-Author and then Backup. Why is Deep analysis happening? It should go right into ENCODING. (6) Now its done with Analysis, its doing ENCODING. Still scratching head why analysis phase. (7) Its done, I inspected the option for DEEP ANALYSIS and its gray'd out. However, it did do that Analysis phase. Out of curiosity, I tried a second time by following the same steps, and it did not go through deep analysis the second time. I am not dreaming that it did analysis the first time I tried. ************************************************************** ORIGINAL DVD LAYER BREAK IS: ************************************************************** Cell 14 V/C Id: 1/14 time: 00:01:04.15 / 30 fps [pos: 00:58:31.05] [Frames: 105335] Cell_14: Cell type (Angle) 0 [00] Seemless Playbak = NO ************************************************************** AFTER DVD SHRINK RE-AUTHOR, ANALYZE, BACKUP: ************************************************************** Cell_14: Cell type (Angle) type 8 [08] Seemless Playback = YES ************************************************************** TESTED THE OUTPUT OF DVD SHRINK 3.1.5: ************************************************************** PLAYED DVD-R (RitekG04-Pioneer A05) in Daewoo DVG-3000 (Cheap DVD Player). No Freezes!!! When I used DVD Shrink 3.1.6 Beta 2, I got two freezes: (a) 00:01h:05m:05s (b) 00:01h:05m:35s Also, DVD2ONE did not have any problems with freezing. I will try a friend's DVD player which is not a cheap Daewoo. I have read where there is a System Clock Reference synching problem with some DVD players. ---------------------------------------------------------------------- I found the following explanation at another web site: "layer breaks are one of those misnomers (an inaccurate name) that has grown out of IfoEdit identifying clock discontinuities as possible layer breaks, as an aid to splitting a DVD. A clock discontinuity is when the system clock reference (SCR), a running value used for synchronization, has been interrupted. Most usually it has been set back to zero because the 2 pieces of video were encoded seperately. The last "phantom" chapter of many movies is an example of this. It also occurs during a layer break sometimes, which is where it got its name. Playback is not seamless over a discontinuity in a lot of players, causing a pause. If the SCR has been replaced with a new continously inceasing value, the marks can be removed. The true layer break code, six or more sectors of all zero bytes, is removed by the DVD reader, and never seen by PC software." --by mpucoder
A bug in v3.1.6 has been confirmed, but it apparently exists in all v3.1.x versions too (which I find quite puzzling as my tests can only show it in v3.1.6b). :confused: