version 0.91 problem (part of the video missing)

[XMEN3]

already on 2 movie...
in some segment cce stops to encode (the reason is unknown) and dvd-rb rebuild the movie anyway, you can see the movie and listen the voice but the video is missing from last frame encoded and the next chapter...
never appened before...
I've tried to encode manually the truncked m2v and rebuilded succesfully.
Sorry already on 3 movies...using batch encode and cce 2.70

[jptheripper]

yeah this is a problem, if cce fails rb has no way of knowing. There are frame checks


try another version of cce, 2.70 is way too buggy.

[XMEN3]

frame check? hehe no way...
91 is buggy

[Rockas]

frame check? hehe no way...
91 is buggy

I don't know how many people are using DVD Rebuilder PRO but I think that they're more than 100 :)

The problem you submited happened to me once... using CCE 2.70.

edit: Do I need to say more?

[XMEN3]

dunno..but i'm using cce 2.70 from dvd-rb 0.84 or so ...and
this appened on all 3 movies i've done with 0.91..
so where's the bug?

I think will be better if dvd.rb does a frames check before rebuild....
Maybe those 100 premiere users didn't watch a movie done after this sunday...

[Rockas]

But it does... doesn't the message appears on the Log file or Status window?

[XMEN3]

sure it warns but continues anyway...
strange but not the same segment of last encode....
Movie is "spartan" italian
same with v90
segment six

[20.17.28] One Click encoding activated...
[20.17.28] 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
-- Encoding resulted in no .M2V, retrying.
- Creating M2V for VTS_01 segment 17
- Creating M2V for VTS_03 segment 0
- 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
[22.01.54] Phase II ENCODING completed in 104 minutes.
[22.01.54] Phase III, REBUILD started.
- Copying IFO, BUP, and unaltered files...
- Processing VTS_01
- Rebuilding segment 0 VOBID: 1 CELLID: 1
- Rebuilding segment 1 VOBID: 1 CELLID: 2
- Rebuilding segment 2 VOBID: 1 CELLID: 3
- Rebuilding segment 3 VOBID: 1 CELLID: 4
- Rebuilding segment 4 VOBID: 1 CELLID: 5
- Rebuilding segment 5 VOBID: 1 CELLID: 6
- Rebuilding segment 6 VOBID: 1 CELLID: 7
- Possible dropped frame(s) [ 4012 ] noted in this segment, continuing...
- Rebuilding segment 7 VOBID: 1 CELLID: 8
- Rebuilding segment 8 VOBID: 1 CELLID: 9
- Rebuilding segment 9 VOBID: 1 CELLID: 10
- Rebuilding segment 10 VOBID: 1 CELLID: 11
- Rebuilding segment 11 VOBID: 1 CELLID: 12
- Rebuilding segment 12 VOBID: 1 CELLID: 13
- Rebuilding segment 13 VOBID: 1 CELLID: 14
- Rebuilding segment 14 VOBID: 1 CELLID: 15
- Rebuilding segment 15 VOBID: 1 CELLID: 16
- Rebuilding segment 16 VOBID: 1 CELLID: 17
- Rebuilding segment 17 VOBID: 1 CELLID: 18
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_01_0.IFO
- Processing VTS_03
- Rebuilding segment 0 VOBID: 1 CELLID: 1
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_03_0.IFO
- Processing VTS_04
- Rebuilding segment 0 VOBID: 1 CELLID: 1
- Rebuilding segment 1 VOBID: 1 CELLID: 2
- Rebuilding segment 2 VOBID: 1 CELLID: 3
- Rebuilding segment 3 VOBID: 1 CELLID: 4
- Rebuilding segment 4 VOBID: 1 CELLID: 5
- Rebuilding segment 5 VOBID: 1 CELLID: 6
- Rebuilding segment 6 VOBID: 1 CELLID: 7
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_04_0.IFO
Correcting VTS Sectors...
[22.17.26] Phase III, REBUILD completed in 16 minutes.

Done.
[22.17.26] PREPARE/ENCODE/REBUILD completed in 120 min.
Batch Job #1 finished in 00120 minutes.
- HIGH/LOW/TYPICAL Bitrates: 4.795/3.724/4.456 Kbs

[Rockas]

Yes it continues... but it warns you that CCE is BUGGY not DVD Rebuilder :D

edit: CCE 2.70 IS buggy not the other versions... at least if we talk about this problem.

[XMEN3]

wich one you got?

...cce? 2.67 is better?

[Rockas]

I usually use 2.50 (I have an Athlon... 2.50 is much quicker on Athlons :))

[roux]

edit: CCE 2.70 IS buggy not the other versions... at least if we talk about this problem.

In what situations other then this one is cce 2.70 buggy? Cause i just started using 2.70

[Fishman0919]

CCE SP 2.70.02 seems to be a hit or miss.... It either work well for you or it's all problems.

[RaistlinMajere]

I had all sorts of problems with 2.70. One day it was working fine and then all the problems started. Tried it on a fresh install and still the same problem. Went back to previous versions of rb and still the same problems. Got fed up with it so went back to 2.67.00.27 and not had a problem since. Over 15 encodes so far

[XMEN3]

anyway now i'll check the rebuild session and, if there's frames missing , I will do the segment manually using the info in rebilder.ecl

[Fishman0919]

I had all sorts of problems with 2.70. One day it was working fine and then all the problems started. Tried it on a fresh install and still the same problem. Went back to previous versions of rb and still the same problems. Got fed up with it so went back to 2.67.00.27 and not had a problem since. Over 15 encodes so far

See, I've done over 150 disc with CCE SP 2.70.02 without any problems... but like I said it's a hit or miss thing with different people.

anyway now i'll check the rebuild session and, if there's frames missing , I will do the segment manually using the info in rebilder.ecl

You can try but it's more likely going to do the samething(from what I read)

[XMEN3]

problem can be the audiodub enabled?
when I must use it...with cce 2.50 or what?
http://forum.doom9.org/showthread.php?s=&threadid=82855&highlight=audiodub

[Fishman0919]

problem can be the audiodub enabled?
when I must use it...with cce 2.50 or what?

With CCE SP 2.50, YES.. it won't hurt with other ver of CCE so you can leave it on.

[Rockas]

Originally posted by Fishman0919
With CCE SP 2.50, YES.. it won't hurt with other ver of CCE so you can leave it on.

If you have an AMD Athlon... i think that 2.50's bug only affects that kind of processors http://www.thestylemachine.com/smileys/disimulo.gif

[Fishman0919]

AudioDub(BlankClip()) is a workaround for a bug in certain CCE versions. Enable this if you're using CCE 2.5 and have an AMD CPU.

Two for Two Rockas...:o

[XMEN3]

every project done in the past 3 days with newer version of dvd-rb gives the same problem...cce 2.70 (that i'm using since 2 months without problems) is crashing randomly in the middle of segments.
Can be a variation of ecl creation done by rebuilder?
I've done a fresh reinstall of windows xp but the problem isn't there.
I've AMD64
Finally but not less important:
I've found a segment with avisynth error message "fault in some address fffff"...
Maybe vitesta ddr setup...
I'll do a memory test...

[jdobbs]

Are you running on an overclocked machine (memory or CPU)? This seems to happen a whole lot more often in that case.

It's not the ECL. In the one case where I saw this happen (out of a a very large number of encodes with v2.70, by the way), that exact ECL, when run it through v2.69 or v2.67, worked perfectly.

[HornyBass]

Originally posted by RaistlinMajere
I had all sorts of problems with 2.70. One day it was working fine and then all the problems started. Tried it on a fresh install and still the same problem. Went back to previous versions of rb and still the same problems. Got fed up with it so went back to 2.67.00.27 and not had a problem since. Over 15 encodes so far

Hello RaistlinMajere,

Were any Distributed Computing client running and/or your comp overclocked at the moment the problems appeared?

[TuRiSOft]

And the problem is not on all OC'ed machines. Mine (Athlon XP-M 2500 running at 2200Mhz) has no problems with 2.70.01.05 or 2.70.02.00.

Anyway I switched to HC since 0.13 . It's a bit slower but it gives real good quality and it's freeware
-WHAT MORE CAN YOU ASK?-

[jdobbs]

I didn't say all OC machines have the problem. I said it seems to be much more likely to happen in that case. The point is that CCE really runs the processor/memory through their paces. If you OC'd and are on the edge of acceptable -- CCE will push you over.

[onesoul]

A very good way to see if your machine is working fine is to run prime95 (mersenne.org), with option torture test - blend (tests cpu and ram). If you can run it for 12 hours (more or less depending on your computer) or it completes an entire cycle (of x number of level tests) without any errors, then you most probably don't have a faulty hardware and/or the actual level of overclock is handled well.

I have a xp2100+ (1.7v) at fsb215mhz*10 synchronous with memory at 2-2-2-5 timings running really sweet here. sorry for ot.

[RaistlinMajere]

Originally posted by HornyBass
Hello RaistlinMajere,

Were any Distributed Computing client running and/or your comp overclocked at the moment the problems appeared?

Nope, it has happened on both of my machines which have entirely different hardware setups. I run everything at safe default values and are very very stable. Especially, my server, it gets rebooted every couple of weeks and is rock solid stable. Never crashes.

Not sure why but 2.70 versions of cce just keep exiting randomly on my machines. It is definately 2.70, as everything else runs perfectly. I have reinstalled to see if that fixes it, no. Tried previous versions of rb, no joy. My machines have very good cooling and i live in a cool climate.

I have seen it happen countless times, the process would be going along nice with the estimated clocks counting fine and for example with a couple of thousand frames to go and maybe 3 minutes on the completion estimate cce just finishes the segment and rb starts up the next one.

Try renecoding the segment and it goes through fine. It's random exits usually between 0 and 4 segments a movie.

Removed 2.70, put 2.67 back on and low and behold everything works perfectly. 20 encodes and climbing

[jdobbs]

I was just wondering... has anyone with an Athlon processor experienced this? Looking back through the posts it seems to be something that is only happening on Intel processors that are using CCE v2.70. Maybe something to do with the extended instructions??? What happens if you unclick the SSE2 extension under the OPTIONS/MISC? Any help? (all my computers use AMD processors, and I'm just not seeing this problem).

[Fishman0919]

2 AMD xp's and 2 AMD 64's... no problems with CCE SP 2.70 at all.

[SpazzHH]

I run Intel P4 CPU's and myself have had no problems with 2.70, but I do understand I'm in the minority. I've always wondered myself if it was memory based. I have 1024mb of Mushkin Hi-Perf Black and have never seen a program with kernal rates like those that CCE rack up while running. I would hate to see what would happen if I only had the minimum 512(what a joke), or a brand of less than top-notch quality.

[jdobbs]

That's an interesting thing about CCE. It will use up most of your memory -- no matter how much you have. I've wondered if memory may play a factor as well. But since it is only v2.70 that has the problem, it probably isn't related. The earlier versions use a lot of memory too.

[XMEN3]

can be the option "run apps minimized" ???
I've done 2 movies with rb 92 beta without this enabled and went ok...
I've also set ram from 290 to 300 like was before the problem...
Maybe ram sold to work at 600 mhz should run at 600....

[jdobbs]

Originally posted by SpazzHH
I run Intel P4 CPU's and myself have had no problems with 2.70, but I do understand I'm in the minority. I've always wondered myself if it was memory based. I have 1024mb of Mushkin Hi-Perf Black and have never seen a program with kernal rates like those that CCE rack up while running. I would hate to see what would happen if I only had the minimum 512(what a joke), or a brand of less than top-notch quality. I don't think you're the minority. I think there are just a handful of users that experience this.

[onesoul]

I would hate to see what would happen if I only had the minimum 512(what a joke) I have 512 :p (2*256mb) running dual channel ddr. Although it isn't that much these days, it's (still) sufficient.

[RaistlinMajere]

well both my systems are athlons, a Xp2200 and a Xp2700, so its not exclusive to intel.

Both systems have 2x512Mb Crucial ECC ram with additional heat spreaders added running at spd settings, one on a via board one on a nvidia board. So I very much doubt its the ram.

Both systems run fine and handle io intensive apps such as ifoedit with ease. Using 2.67 I can batch encode 5 dvd's which takes a day or so and they all come out perfect.

I build computer systems for a living and built both my systems so I think the problem is software related not hardware.


Could avisynth be the problem? I am using 255. I know there are newer versions but they are beta. Which version do you recommend Jdobbs?

[jdobbs]

That's the version I use as well. I think the chance that it is AVISYNTH is extremely low. AVISYNTH is also used when you load the other versions of CCE or HC -- and none of them have problems.

I have little doubt that the problem is v2.70... but what I don't understand is why it is unique to certain systems. The only problem I've personally had with 2.70 was on the HBO whitescreen and the sensitivity of the new engine to high end demand. I raised the calculation for maximum bitrate (I was previously conservative) and even that one went away. I use 2.70 (either basic or SP) for most of my personal encodes now -- and have never had a missing frame or a missing M2V.

[RaistlinMajere]

not to worry. I'll stick with 2.67.00.27 as I can't really tell the difference between encodes with them. I noticed the difference between 2.5 and 2.67 mainly better transitions between scene changes but not from 2.67-2.70. Besides the minimize function works better with this version.

If it aint broke I am not going to try and fix it lol

[blueboyec]

I used 2.67.00.27 and never had problems and installed 2.7 and started to have problem. Can't go back to 2.67.00.27 because I copied over it:( !

[Alxemi]

Guys, i started having this problem like all of you, with the 2.70 version, but when i returned to 2.67 i had the same problem... After a lot of trying i found that the problem was not CCE, or DVDRB, was my CPU temperature!! Better ventilation or some underclocking fixed my encodes completely, even with all the 2.70 versions.

Weird , because i already had that temperature when i started encoding with cce 2.67, and the problems started when i changed to 2.70, so i was pointed like you to a codec problem.

For your information:
Mi CPU is a AMD Athlon XP 3000+ (real cpu clock 2.16ghz) It was at 63 Celsius degrees (145.4 Fahrenheit degrees) while encoding, which results in bad encodes.
Underclocking it to 1.87 real ghz, it gave me 58.5 Celsius (137.3 Fahrenheit) while encoding, which results in perfect encodes.

So my recomendation, check your CPUs temperature! ;)

[psychoxxx]

I am using DVDRB 0.91 freeware and CCE 2.67.00.27 on an Intel P4 550 (3.4Ghz) with 1GB (dual channel 512MB x 2). This is the 1st time dropped frames happened to me. The original movie is 5.37GB but the encoded result is only 1.97GB. :confused: Any idea how to solve this? Thanks in advance. Below is the rebuilder log.

[06:49:39] One Click encoding activated...
-----------------
[06:49:40] Phase I, PREPARATION started.
- VTS_01: 2,816,687 sectors.
-- Scanning and writing .D2V file
-- Processed 133,968 frames.
-- Building .AVS and .ECL files
- Reduction Level for DVD-5: 78.8%
- Overall Bitrate : 6,325Kbs
- Space for Video : 4,314,120KB
- HIGH/LOW/AVERAGE Cell Bitrates: 6,342/6,303/6,325 Kbs
[06:57:13] Phase I, PREPARATION completed in 8 minutes.
[06:57:13] Phase II ENCODING started
- Creating M2V for VTS_01 segment 0
- Creating M2V for VTS_01 segment 1
[10:01:25] Phase II ENCODING completed in 184 minutes.
[10:01:25] Phase III, REBUILD started.
- Copying IFO, BUP, and unaltered files...
- Processing VTS_01
- 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: 1
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_01_0.IFO
- Updating TMAP table...
Correcting VTS Sectors...
[10:11:42] Phase III, REBUILD completed in 10 minutes.

Done.
[10:11:44] PREPARE/ENCODE/REBUILD completed in 202 min.

[Rockas]

Have you tried 0.93?

[borgraf]

[06:57:13] Phase II ENCODING started
- Creating M2V for VTS_01 segment 0
- Creating M2V for VTS_01 segment 1
[10:01:25] Phase II ENCODING completed in 184 minutes.
[10:01:25] Phase III, REBUILD started.
...
- Rebuilding segment 0 VOBID: 1 CELLID: 1
- Possible dropped frame(s) noted in this segment, continuing...
It's interesting that there are only 2 segments. Segment 0 could be very large, perhaps even the whole movie. I'm not sure how CCE would react to that, how much memory it would need. Maybe someone with more CCE experience could throw in a couple of cents :)

edit: bad parsing

[jdobbs]

Did you modify any of the processing or change anything after PREPARE? The reason I ask is that DVD-RB has internal coding that will not allow segments that large... :sly:

How long is the video (in minutes)?

[psychoxxx]

I think I did not modify anything after PREPARE as I used one click mode. I just pressed Backup DVD and went to bed. Under Video Title Sets, there is only one item: VTS_01. It is 5501 MBytes. The movie is 93 mins long. There are no menu, no extras, only 1 audio and 1 subtitle. VBR Bias is 0, Quality Prec is 28 and VBR Passes is 5. I have Undot() in AVS Filter Editor. I will try 0.93 and report asap. :o Thanks a lot.

BTW, my PC's bios show that the CPU is around 40 degrees Celsius. I do not overclock as I don't know how.

[jdobbs]

This is not an overclocking problem. I'm pretty sure at least one of your segments is to large to process... that's why I asked how many minutes long it was. Rebuilder will force a segment break at 60,000 frames -- which in PAL would be about 40 minutes, NTSC about 33 minutes.

[psychoxxx]

Thank you very much for the answer. I guess there is no way it can be fixed. Version 0.93 produced the same result. :( Wish I could afford DL discs.....

[jdobbs]

No -- it should work. Could you tell me how long the video is?

[psychoxxx]

.....VTS_01. It is 5501 MBytes. The movie is 93 mins long. It is NTSC 16:9. There are no menu, no extras, only 1 audio and 1 subtitle....

I tried adding chapter points (would that help?) using Ulead MovieFactory 4 and 3.5, both came to a halt at 75% just after a few minutes. No change at all even after 11 hours.

Then I tried Tmpgenc DVD Author, I successfully added chapter points but the subtitle disppeared. :confused:

Psycho