Log in

View Full Version : - Possible dropped frame(s) [ 8116 ]


casperse
19th November 2006, 15:09
Hi

I get this error when rebuilding but cant see any error on the encoding?

- Possible dropped frame(s) [ 8116 ] noted in this segment, continuing...

Anyway to make sure I dont have corrupt or missing frames?

Cheers
Casperse

EDITED: No OC on my system I have a 200+ of encodings on this PC with tha same setup and encoder never seen this before? (Just updated from version DVD Rebuilder v1.11.0 Pro to DVD Rebuilder v1.12.1 Pro)
Either there is some new changes in DVDrebuilder or the ripped DVD is causing this (Archos) etc...
-----------------
[11:43:48] Phase I, PREPARATION started.
- DVD-RB v1.12.1
- AVISYNTH 2.5.6.0
- CCE 2.70.2.4 encoder selected.
- VTS_01: 2.813.428 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 214.075 frames.
-- Building .AVS and .ECL files
- Reduction Level for DVD-5: 77,5%
- Overall Bitrate : 3.754Kbs
- Space for Video : 3.923.888KB
- HIGH/LOW/TYPICAL Bitrates: 4.611/400/3.754 Kbs
[12:04:59] Phase I, PREPARATION completed in 21 minutes.
[12:15:10] Phase II ENCODING started
- Creating M2V for VTS_01 segment 0
- Creating M2V for VTS_01 segment 1
- Creating M2V for VTS_01 segment 2
- Creating M2V for VTS_01 segment 3
- Creating M2V for VTS_01 segment 4
- Creating M2V for VTS_01 segment 5
- Creating M2V for VTS_01 segment 6
- Creating M2V for VTS_01 segment 7
- Creating M2V for VTS_01 segment 8
- Creating M2V for VTS_01 segment 9
- Creating M2V for VTS_01 segment 10
- Creating M2V for VTS_01 segment 11
- Creating M2V for VTS_01 segment 12
- Creating M2V for VTS_01 segment 13
- Creating M2V for VTS_01 segment 14
- Creating M2V for VTS_01 segment 15
- Creating M2V for VTS_01 segment 16
- Creating M2V for VTS_01 segment 17
- Creating M2V for VTS_01 segment 18
- Creating M2V for VTS_01 segment 19
- Creating M2V for VTS_01 segment 20
- Creating M2V for VTS_01 segment 21
- Creating M2V for VTS_01 segment 22
- Creating M2V for VTS_01 segment 23
- Creating M2V for VTS_01 segment 24
- Creating M2V for VTS_01 segment 25
- Extracting Video for VTS_01 segment 26
- Extracting Video for VTS_01 segment 27
[14:50:49] Phase II ENCODING completed in 155 minutes.
[14:51:16] 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
- Rebuilding seg 4 VOBID 1 CELLID 5
- Rebuilding seg 5 VOBID 1 CELLID 6
- Rebuilding seg 6 VOBID 1 CELLID 7
- Rebuilding seg 7 VOBID 1 CELLID 8
- Rebuilding seg 8 VOBID 1 CELLID 9
- Rebuilding seg 9 VOBID 1 CELLID 10
- Rebuilding seg 10 VOBID 1 CELLID 11
- Rebuilding seg 11 VOBID 1 CELLID 12
- Rebuilding seg 12 VOBID 1 CELLID 13
- Rebuilding seg 13 VOBID 1 CELLID 14
- Rebuilding seg 14 VOBID 1 CELLID 15
- Rebuilding seg 15 VOBID 1 CELLID 16
- Rebuilding seg 16 VOBID 1 CELLID 17
- Rebuilding seg 17 VOBID 1 CELLID 18
- Rebuilding seg 18 VOBID 1 CELLID 19
- Rebuilding seg 19 VOBID 1 CELLID 20
- Rebuilding seg 20 VOBID 1 CELLID 21
- Possible dropped frame(s) [ 8116 ] noted in this segment, continuing...
- Rebuilding seg 21 VOBID 1 CELLID 22
- Rebuilding seg 22 VOBID 1 CELLID 23
- Rebuilding seg 23 VOBID 1 CELLID 24
- Rebuilding seg 24 VOBID 1 CELLID 25
- Rebuilding seg 25 VOBID 1 CELLID 26
- Rebuilding seg 26 VOBID 1 CELLID 27
- Updating NAVPACKS for VOBID_01
- Rebuilding seg 27 VOBID 2 CELLID 1
- Updating NAVPACKS for VOBID_02
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_01_0.IFO
- Updating TMAP table...
- Correcting VTS Sectors...
[15:04:11] Phase III, REBUILD completed in 13 minutes.

Done.
- Versions :
-- Rebuilder: v1.12.1
-- CCE SP Version: 2.70.2.4
-- ReJig Version: 0.5.0.5
-- QuEnc Version: 0.6.1.0
-- HC Version: 0.16.0.1
-- DGDECODE Version: 1.4.5
-- AVISYNTH: 2.5.6.0

jdobbs
19th November 2006, 17:27
Can send me (at dvd-rb@dvd-rb.com) your REBUILDER.ECL file? Also, what disc are you encoding?

One thing you might try in case the encoder crashed during the last pass on that segment... take the area of the the ECL containing data for V02002000001021 and copy/paste it into ITEM.ECL. Then load ITEM.ECL into CCE as a project and run it. After that attempt the REBUILD again.

casperse
19th November 2006, 19:24
I just did the encode and rebuild with the old version of DVDrebuilder Pro...It worked fine (Using same source folder: Davinci Code - No new rip to disc).

Now I will go back to the new version and try it again...I DONT BELIVE THAT IT IS REBUILDER...Maybee a "glitch" or fragmented drive etc "Ghost in the machine" so to speak Because I have never seen this before....

I will post my findings ASAP after the third encode & rebuild.

Cheers
Casperse

jdobbs
19th November 2006, 19:54
I just did that one (NTSC, R1 Version) the other day -- no problems with v1.12.1 at that time. Any chance you may have accidentally hit a keystroke at the time that segment was encoding and it exited CCE? I've seen that happen. If it was on the second or later pass it would show that (missing frames) symptom.

casperse
19th November 2006, 19:58
This is the PAL version...But again it did make it with the same source...Encoding again now.

Cheers
/Casperse

casperse
20th November 2006, 19:20
Okay I have done the rebuild + Encoding with the new version 3 times and everything is fine....With the same source folder and the same installation on the same PC....

I can not explain why it gave dropped frames in the beginning...
Any way DVDrebuilder could give me a warning in the end?

Sometimes you dont think about scrolling through the Logs....:D

Thanks Jdobbs! for the quick reply but this was a "Ghost in the Machine"....

jdobbs
20th November 2006, 21:00
Unfortunately DVD-RB has no way of knowing if the encoder completed the file successfully (with the correct number of frames) during the ENCODE phase. In order to do that I'd have to scan the M2V file and count the number of frames after each segment is encoded -- which would add a lot of time to an already time consuming process.

I think I had it stop when it got that error (during the REBUILD phase) at one time in the past -- but I got a lot of complaints about stopping rather than completing the remaining segments, so I made it just give the warning instead.

casperse
21st November 2006, 22:22
Actually with the new dual core CPUs it not so time consuming to encode anymore just around "realtime" with 4 passes :D

But I can see what you mean what if the Error of dropped frames also was listed in the end...of the rebuild log that way nobody would miss it. with all the segments you have to go through the log every time, and since I have never seen this error before I never look for it :)

jdobbs
21st November 2006, 23:06
That's a good idea. I'll add a message at the end that says something to the effect of "ERROR(S) ENCOUNTERED during REBUILD -- Review LOG"

casperse
22nd November 2006, 08:27
Great that way nobody can miss it! Thanks love this program!:D