Aborting during encode might cause error in dvd playback?

[scoob19]

Hi, recently i copied a couple of movies that i own using dvd rebuilder pro and cce. Sometimes my computer will freeze up during encoding (possibly because i have my computer overclocked and cce doesnt agree with it), but then I can just restart dvd rebuilder and continue the encoding process.

So i gave a couple movies to my sister-in-law to watch, and she said that during playback the movie stopped a couple times, and had to skip to the next chapter to continue the movie. Ive never experienced this problem myself but Im thinking that maybe it was due to my computer freezing and then restarting dvd rebuilder...anyone ever have this problem?

[scoob19]

I may have found what my problem is from reading some old posts, but id still like some input if possible so i can be sure.

It seems that dropped frames is the issue.

I am using Rebuilder Pro with CCE SP 2.70 (5 pass, no filters) with an overclocked system. I read that this combination will be too much stress on the system and cause problems. Looking back through my logs, i dont get dropped frames all that often, i think its happened on 3 movies.

Below is the log of one of the movies:

[15:06:11] Phase I, PREPARATION completed in 7 minutes.
[15:12:54] Phase II ENCODING started
- Creating M2V for VTS_04 segment 0
- Creating M2V for VTS_04 segment 1
- Creating M2V for VTS_04 segment 2
- Creating M2V for VTS_04 segment 3
- Creating M2V for VTS_04 segment 4
- Creating M2V for VTS_04 segment 5
- Creating M2V for VTS_04 segment 6
- Creating M2V for VTS_04 segment 7
- Creating M2V for VTS_04 segment 8
- Creating M2V for VTS_04 segment 9
- Creating M2V for VTS_04 segment 10
- Creating M2V for VTS_04 segment 11
- Creating M2V for VTS_04 segment 12
- Creating M2V for VTS_04 segment 13
- Creating M2V for VTS_04 segment 14
- Creating M2V for VTS_04 segment 15
- Creating M2V for VTS_04 segment 16
- Creating M2V for VTS_04 segment 17
- Creating M2V for VTS_04 segment 18
- Creating M2V for VTS_04 segment 19
- Creating M2V for VTS_04 segment 20
- Creating M2V for VTS_04 segment 21
- Creating M2V for VTS_04 segment 22
- Creating M2V for VTS_04 segment 23
- Creating M2V for VTS_04 segment 24
- Creating M2V for VTS_04 segment 25
- Creating M2V for VTS_04 segment 26
- Creating M2V for VTS_04 segment 27
- Extracting STILLS for VTS_04 segment 28
[19:46:22] Phase II ENCODING completed in 274 minutes.
[19:46:29] Phase III, REBUILD started.
- Copying IFO, BUP, and unaltered files...
- 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
- Rebuilding seg 3 VOBID 1 CELLID 4
- Rebuilding seg 4 VOBID 1 CELLID 5
- Rebuilding seg 5 VOBID 1 CELLID 6
- Possible dropped frame(s) [ 2 ] noted in this segment, continuing...
- Rebuilding seg 6 VOBID 1 CELLID 7
- Possible dropped frame(s) [ 5840 ] noted in this segment, continuing...
- 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
- Rebuilding seg 21 VOBID 1 CELLID 22
- Rebuilding seg 22 VOBID 1 CELLID 23
- Possible dropped frame(s) [ 2164 ] noted in this segment, continuing...
- 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
- Rebuilding seg 27 VOBID 1 CELLID 28
- Updating NAVPACKS for VOBID_01
- Rebuilding seg 28 VOBID 2 CELLID 1
- Updating NAVPACKS for VOBID_02
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_04_0.IFO
- Updating TMAP table...
- Correcting VTS Sectors...
- Building ISO Image...
- ISO Image successfully created.
[20:10:52] Phase III, REBUILD completed in 24 minutes.


Those are some pretty big numbers next to dropped frames....so next I am going to go back to my factory settings and try again to see if this solves the problem.

1. Anything else I should be doing besides not overclocking?
2. Is the dropped frames caused during the encoding process or the rebuilding process? If I get a "dropped frames" error, would doing the rebuild again maybe fix the problem, or would I have to encode again?
3. If I browse the internet while encoding, will this lead to dropped frames in any way?

Thanks!

[Fishman0919]

Dropped frame are mostly 1 of 2 things....

1) CCE is crashing on those segments because of overclocking.

2) CCE is crashing because of a bad rip.

CCE SP 2.70 (5 pass, no filters) with an overclocked system.

Try not overclocking and see what happens.

What did you use to rip the disc... try to re-ripping the disc.

[Rippraff]

1. Anything else I should be doing besides not overclocking?
Don't overclock that much. Use a hardware stress test like Prime95.
2. Is the dropped frames caused during the encoding process or the rebuilding process? If I get a "dropped frames" error, would doing the rebuild again maybe fix the problem, or would I have to encode again?

Your encoder crashed due to overclocking so you've to encode again.
3. If I browse the internet while encoding, will this lead to dropped frames in any way?

It won't harm if your system runs stable which is obviously not the case. ;)

Cu Rippraff

[zacoz]

I am using Rebuilder Pro with CCE SP 2.70 (5 pass, no filters) with an overclocked system.

You might want to consider not overclocking so extremely and reduce the number of passes to say 3. It should still finish quicker and I can't imagine you'd be able to tell a difference to the 5 pass.

[scoob19]

Thank you for the input guys.

I've stopped overclocking, so hopefully that will do the trick.

Its been a number of years since i built my computer, probably over 4 years, its been overclocked the whole time. Back in the beginning i did use Prime95 to stress the cpu and its been pretty stable other than using DVD Rebuilder.

What did you use to rip the disc... try to re-ripping the disc.
I use AnyDVD to rip.

You might want to consider not overclocking so extremely and reduce the number of passes to say 3. It should still finish quicker and I can't imagine you'd be able to tell a difference to the 5 pass.
You're right, i probably wouldnt. A few weeks ago I encoded a movie with a bitrate of about 3500, so changed the passes from 3 to 5, and its been on that setting ever since.

[RickA]

Greets,

I agree with Zacos, jdobbs, many others and the docs from CCE. Which state that passes beyond 3 are approaching diminishing returns and most likely will not yield a noticeable improvement.

Even though Prime95 may say you are stable, CCE can find flaws / weak links if they are there. Same as x264. I have been a fan of CCE for years but have recently been gravitating towards HCenc more and more. Especially since getting a quad core and HCEnc being more SMP friendly in utilizing all cores more fully than CCE. The quality of the two encoders seem very much on par. You may wish to give HCenc a try if you have not already.

Cheers,
Rick

[rayvt]

Even though Prime95 may say you are stable, CCE can find flaws / weak links if they are there.

I have found that the best stress test is to boot up Linux and then do a recompile/rebuild of te GCC compiler. I've had systems that prime95 said were rock solid, but the gcc rebuild would fail. Back off the overclock and gcc rebuild became rock solid.

Gcc uses a lot of indirect links & pointers during its operation, so it is very sensitive to the least little failure. Many other programs are rather tolerant of bad addresses, etc.