possible dropped frames

[sreg0r]

Hi, i recently rebuilded the black books series1 DVD and got some droppped frame errors. This was done using CCE 2.67 and DVD-Rb PRO 1 RC4.1
I also remember seeing some errors about a .m2v file that was not created but it was retried and it worked. Now i have had a look at the output and everything seems fine but these error messages are worrying me some. I am a bit of a noob so could someone tell me how i can go straight to the spot where the suspected error occured? that way i can verify if the problem did/not occur.
thanks ALex.


[19:48:50] Phase III, REBUILD started.
- Copying IFO, BUP, and unaltered files...
- Processing VTS_01
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Rebuilding seg 1 VOBID 1 CELLID 2
- Rebuilding seg 2 VOBID 1 CELLID 3
- Rebuilding seg 3 VOBID 1 CELLID 4
- Possible dropped frame(s) [ 4 ] noted in this segment, continuing...
- Rebuilding seg 4 VOBID 1 CELLID 5
- Possible dropped frame(s) [ 26 ] noted in this segment, continuing...
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_01_0.IFO
- Updating TMAP table...
- Processing VTS_02
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Rebuilding seg 1 VOBID 1 CELLID 2
- Rebuilding seg 2 VOBID 1 CELLID 3
- Rebuilding seg 3 VOBID 1 CELLID 4
- Rebuilding seg 4 VOBID 1 CELLID 5
- Possible dropped frame(s) [ 31 ] noted in this segment, continuing...
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_02_0.IFO
- Updating TMAP table...
- Processing VTS_03
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Rebuilding seg 1 VOBID 1 CELLID 2
- Possible dropped frame(s) [ 13 ] noted in this segment, continuing...
- Rebuilding seg 2 VOBID 1 CELLID 3
- Rebuilding seg 3 VOBID 1 CELLID 4
- Rebuilding seg 4 VOBID 1 CELLID 5
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_03_0.IFO
- Updating TMAP table...
- Processing VTS_04
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Rebuilding seg 1 VOBID 1 CELLID 2
- Rebuilding seg 2 VOBID 1 CELLID 3
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_04_0.IFO
- Updating TMAP table...
- Processing VTS_05
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Possible dropped frame(s) [ 23 ] noted in this segment, continuing...
- Rebuilding seg 1 VOBID 1 CELLID 2
- Possible dropped frame(s) [ 12 ] noted in this segment, continuing...
- Rebuilding seg 2 VOBID 1 CELLID 3
- Possible dropped frame(s) [ 11 ] noted in this segment, continuing...
- Rebuilding seg 3 VOBID 1 CELLID 4
- Rebuilding seg 4 VOBID 1 CELLID 5
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_05_0.IFO
- Updating TMAP table...
- Processing VTS_06
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Rebuilding seg 1 VOBID 1 CELLID 2
- Rebuilding seg 2 VOBID 1 CELLID 3
- Rebuilding seg 3 VOBID 1 CELLID 4
- Rebuilding seg 4 VOBID 1 CELLID 5
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_06_0.IFO
- Updating TMAP table...
- Processing VTS_07
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Rebuilding seg 1 VOBID 1 CELLID 2
- Rebuilding seg 2 VOBID 1 CELLID 3
- Rebuilding seg 3 VOBID 1 CELLID 4
- Rebuilding seg 4 VOBID 1 CELLID 5
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_07_0.IFO
- Updating TMAP table...
- Processing VTS_08
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_08_0.IFO
- Updating TMAP table...
Correcting VTS Sectors...
[20:05:04] Phase III, REBUILD completed in 17 minutes.

Done.

[jptheripper]

wow, i have never seen a dropped frame ever in 100+ disks. Are you sure you had a clean rip of your disk?

[jdobbs]

I think this may be an indication that your system or your copy of CCE isn't stable. Some of those segments are missing over a second of video. If your CCE is a "variant" of the trial version -- you may want to switch to HC Encoder and try it.

You should be able to view the differences by opening the AVS directly and comparing it with the .M2V (use Microsoft Media Player).

[Skunk]

I also have recently got the same error, but I have numbers in the thousands for dropped frames. What causes this? I run my DVDs through DVDRemake before rebuilding. Could cells I have hidden cause this? I ran the movie in question (Hellboy, which has beeen edited to hell to mix content from 2 disks onto one) through Procoder, but will retry with HC once I get a chance. In the meantime, any feedback would be much appreciated.

[jdobbs]

Normally that is an indicator that the encoder crashed after only partially encoding the M2V file. The only time I've seen that happen is on unstable systems -- it seems to happen on certain versions of CCE SP v2.70 on overclocked computers.

[apfraats]

Yep, JDOBBS is very right here !!!

I just a little overclocking in the past, and even the heavest test-programs did fine !

But CCE didn't !!!

CCE is assemby programmed and it turn out to be very sensitive regarding to not 10000% full stable and overclocked systems.


I just overcocked from 166 to 172 Mhz with an ATHLON XP 300+ and tested it toroughly with dedicated programs.

No problems were found, but running CCE did leave corrupted m2v files !

When I canged back to 166 Mhz, CCE worked perfectly !!

Just to notice....

[shipdriver]

I recently upgraded from an Intel 540 3.2Ghz CPU to an Intel 670 3.8Ghz, with no overclocking on an Intel 915GEV motherboard, and DVD-RB has ceased working properly when using filters. It will encode some random number of frames per segment, usually less than 72, and then move on to the next segment. I have RC5.1 installed using the Rockas installer. I tried an older decoder "Decode100fix" and it still did not work. I tried different scripts and tested them in AVSEditor and RB-Opt, where they worked. CPU temp is fine (for a Prescott) being around 70C at 100% CPU load (45C at idle). Stability tests work fine. If I use no filter, it works normally.

[jdobbs]

What filter? That may be where the trouble lies.

[shipdriver]

I use scripts with either Convolution3D or MipSmooth for denoising and Limited Sharpen for sharpening. They worked fine in DVD-RB before the CPU upgrade. I will do some more tweaking and checking to see if something changed in my AviSynth plugins folder or something like that.

[shipdriver]

I got it going with MipSmoother/Limited Sharpen. Somehow some older .dlls got into my AviSynth plug-in folder. I copied in the newest ones in (specifically masktools, warpsharp, avsfilter) and it is chugging right along. :D
Thanks!

EDIT 7Sep05: I did notice one thing, though. If I set SetMemoryMax to greater than 1024 (I have 2GB of RAM), it will only encode a few frames for each segment. I tried 2048 and 1536, but when I set it back to 1024, it worked fine.

[Skunk]

Sorry it took so long to get back. For anyone that was interested in my results of the re-encode, I was able to get rid of this problem simply by trying the movie with HC encoder instead of Procoder.

[Taurus50]

I am using the FREE Installerversion 0.96 all default setting and HC encoder. So far I have not been able to reach any palyable result. Want to see the rebuilt-log?

[18:40:56] Phase III, REBUILD started.
- Copying IFO, BUP, and unaltered files...
- Processing VTS_01
- Reading/processing TMAP table...
- Rebuilding segment 0 VOBID: 1 CELLID: 1
- Rebuilding segment 1 VOBID: 1 CELLID: 2
- Possible dropped frame(s) noted in this segment, continuing...
- Rebuilding segment 2 VOBID: 1 CELLID: 3
- Possible dropped frame(s) noted in this segment, continuing...
- Rebuilding segment 3 VOBID: 1 CELLID: 4
- Possible dropped frame(s) noted in this segment, continuing...
- Rebuilding segment 4 VOBID: 1 CELLID: 5
- Possible dropped frame(s) noted in this segment, continuing...
- Rebuilding segment 5 VOBID: 1 CELLID: 6
- Possible dropped frame(s) noted in this segment, continuing...
- Rebuilding segment 6 VOBID: 1 CELLID: 7
- Possible dropped frame(s) noted in this segment, continuing...
- Rebuilding segment 7 VOBID: 1 CELLID: 8
- Possible dropped frame(s) noted in this segment, continuing...
- Rebuilding segment 8 VOBID: 1 CELLID: 9
- Possible dropped frame(s) noted in this segment, continuing...
- Rebuilding segment 9 VOBID: 1 CELLID: 10
- Possible dropped frame(s) noted in this segment, continuing...
- Rebuilding segment 10 VOBID: 1 CELLID: 11
- Possible dropped frame(s) noted in this segment, continuing...
- Rebuilding segment 11 VOBID: 1 CELLID: 12
- Possible dropped frame(s) noted in this segment, continuing...
- Rebuilding segment 12 VOBID: 1 CELLID: 13
- Possible dropped frame(s) noted in this segment, continuing...
- Updating NAVPACKS for VOBID_01
- Rebuilding segment 13 VOBID: 2 CELLID: 1
- Possible dropped frame(s) noted in this segment, continuing...
- Rebuilding segment 14 VOBID: 2 CELLID: 2
- Possible dropped frame(s) noted in this segment, continuing...
- Rebuilding segment 15 VOBID: 2 CELLID: 3
- Possible dropped frame(s) noted in this segment, continuing...
- Rebuilding segment 16 VOBID: 2 CELLID: 4
- Possible dropped frame(s) noted in this segment, continuing...
- Rebuilding segment 17 VOBID: 2 CELLID: 5
- Updating NAVPACKS for VOBID_02
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_01_0.IFO
- Updating TMAP table...
- Processing VTS_02
- Reading/processing TMAP table...
- Rebuilding segment 0 VOBID: 1 CELLID: 1
- Rebuilding segment 1 VOBID: 1 CELLID: 2
- Updating NAVPACKS for VOBID_01
- Rebuilding segment 2 VOBID: 2 CELLID: 1
- Possible dropped frame(s) noted in this segment, continuing...
- Rebuilding segment 3 VOBID: 2 CELLID: 2
- Updating NAVPACKS for VOBID_02
- Rebuilding segment 4 VOBID: 3 CELLID: 1
- Possible dropped frame(s) noted in this segment, continuing...
- Updating NAVPACKS for VOBID_03
- Rebuilding segment 5 VOBID: 4 CELLID: 1
- Updating NAVPACKS for VOBID_04
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_02_0.IFO
- Updating TMAP table...
- Processing VTS_07
- Reading/processing TMAP table...
- Rebuilding segment 0 VOBID: 1 CELLID: 1
- Possible dropped frame(s) noted in this segment, continuing...
- Updating NAVPACKS for VOBID_01
- Rebuilding segment 1 VOBID: 2 CELLID: 1
- Updating NAVPACKS for VOBID_02
- Rebuilding segment 2 VOBID: 3 CELLID: 1
- Possible dropped frame(s) noted in this segment, continuing...
- Updating NAVPACKS for VOBID_03
- Rebuilding segment 3 VOBID: 4 CELLID: 1
- Updating NAVPACKS for VOBID_04
- Rebuilding segment 4 VOBID: 5 CELLID: 1
- Possible dropped frame(s) noted in this segment, continuing...
- Updating NAVPACKS for VOBID_05
- Rebuilding segment 5 VOBID: 6 CELLID: 1
- Updating NAVPACKS for VOBID_06
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_07_0.IFO
- Updating TMAP table...
- Processing VTS_08
- Reading/processing TMAP table...
- Rebuilding segment 0 VOBID: 1 CELLID: 1
- Possible dropped frame(s) noted in this segment, continuing...
- Updating NAVPACKS for VOBID_01
- Rebuilding segment 1 VOBID: 2 CELLID: 1
- Updating NAVPACKS for VOBID_02
- Rebuilding segment 2 VOBID: 3 CELLID: 1
- Possible dropped frame(s) noted in this segment, continuing...
- Updating NAVPACKS for VOBID_03
- Rebuilding segment 3 VOBID: 4 CELLID: 1
- Updating NAVPACKS for VOBID_04
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_08_0.IFO
- Updating TMAP table...
- Processing VTS_09
- Reading/processing TMAP table...
- Rebuilding segment 0 VOBID: 1 CELLID: 1
- Rebuilding segment 1 VOBID: 1 CELLID: 2
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_09_0.IFO
- Updating TMAP table...
- Processing VTS_10
- Reading/processing TMAP table...
- Rebuilding segment 0 VOBID: 1 CELLID: 1
- Rebuilding segment 1 VOBID: 1 CELLID: 2
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_10_0.IFO
- Updating TMAP table...
- Processing VTS_11
- Reading/processing TMAP table...
- Rebuilding segment 0 VOBID: 1 CELLID: 1
- Rebuilding segment 1 VOBID: 1 CELLID: 2
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_11_0.IFO
- Updating TMAP table...
- Processing VTS_13
- Reading/processing TMAP table...
- Rebuilding segment 0 VOBID: 1 CELLID: 1
- Possible dropped frame(s) noted in this segment, continuing...
- Rebuilding segment 1 VOBID: 1 CELLID: 2
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_13_0.IFO
- Updating TMAP table...
- Processing VTS_15
- Reading/processing TMAP table...
- Rebuilding segment 0 VOBID: 1 CELLID: 1
- Possible dropped frame(s) noted in this segment, continuing...
- Rebuilding segment 1 VOBID: 1 CELLID: 2
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_15_0.IFO
- Updating TMAP table...
- Processing VTS_17
- Reading/processing TMAP table...
- Rebuilding segment 0 VOBID: 1 CELLID: 1
- Possible dropped frame(s) noted in this segment, continuing...
- Rebuilding segment 1 VOBID: 1 CELLID: 2
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_17_0.IFO
- Updating TMAP table...
Correcting VTS Sectors...
[18:47:41] Phase III, REBUILD completed in 7 minutes.

Done.

I'm done too.

Anyone who has a clue?

[Harrysmiith]

I notice that a number of people have tended to put this down to unstable or overclocked systems. A while ago I had this problem and it had nothing to do with overclocking. I can not advise as to the cause. One day everything was fine. I then updated DVD Rebuilder and tried out Avisynth 2.56. The the "possible dropped frames" started. Uninstalling made no difference. A reformat a fresh install solved the problem. If you want/need to avoid a full reinstall I would suggest removing all DVD related programs followed by running a couple of aggressive registry editing programs and then reinstall. The cause is an instability no doubt but not necessarily hardware related.