OPV encoding error: CCE flag set incorrect???

[hoozdapimp]

I am using 2.66 SP with DVD-RB 0.52
After it determines the Q, I get this error message from CCE:

cce encoding failed: OPV VBV ovf frame #24 (00:00:01:02) I 52936 max 51756.71 rel 1179.29.1.02 qsv 97.62 -> 97.64

I have no idea what that means. After I click ok, it skips the encode and moves onto the next one. I have steal bitrate from extras at 25% on, if that makes any difference.

[wmansir]

See this thread: http://forum.doom9.org/showthread.php?s=&threadid=58361&highlight=opv+vbv

The problem is most likely due to insufficient bitrate for very complex material (it's probably just a few tough frames). Is this an extra segment or the main movie? If it's an extra you could try turning steal space from extras off, or perhaps try Half-D1.

[hoozdapimp]

thanks for the reply!

I am backing up Sex and the City episodes (6 episodes per disc + 300mb of extras).

This problem is happening in the HBO static scenes as mentioned in that link you sent. I tried upgrading from 2.67.00.11 to .23, but it didn't help. I don't really want to cut out that part of every single episode (nor would I know if that's possible to do using Rebuilder), since every episode has it's own AVS file that would need to be edited. Any other suggestions?

[Joergen]

Like wmansir said, that static scene is the highest possible bitrate scenario afaik. Every pixel changing from white to black 50/60 times per second completely random. Probably the same reason (mega bitrate) why some people's standalones hang in that scene and return to the menu.

Instead of cutting it, you could try tweaking that cell using RBOpt, and drop its bitrate.

[hoozdapimp]

joergen: thanks! you beat me to a reply before i could edit my post...anyways...

I just re-read that thread and saw a post that I missed last time. It said to turn ON dvd compliance in CCE so that the vbv buffer would be at it's maximum. In the 'rebuilder.ecl' file I noticed that for the file that is crashing in CCE there is an entry that had 'dvd=0'. I'm not sure if that is for dvd compliant, but I changed it to 1 just for the heck of it, and it seems to get past the part that was crashing before! Now I ask, what are the effects of using this dvd=1 setting, and will it be ok to use it using DVD-RB? If so, should dvd=1 be default for DVD-RB to ensure this doesnt' happen more frequently?

[hoozdapimp]

jdobbs, or anyone else that knows for sure, can you please comment on whether or not the dvd=0 flag should be set to 1, or if it will cause harm to set it to 1??

[jdobbs]

Originally posted by hoozdapimp
jdobbs, or anyone else that knows for sure, can you please comment on whether or not the dvd=0 flag should be set to 1, or if it will cause harm to set it to 1?? CCE has this flag inconsistently implemented. If you set it to "1" and are using newer versions of the software (definitely CCE Basic) -- it will take any "FILM" sources (23.976fps) and automatically convert them to 29.97fps -- that's not good and will significantly affect quality and bitrate.

A second negative affect is that it will convert any source to 720x480 or 720x576 by padding it with black bars... so half-d1 or CIF input will be centered on a large backdrop.

You can still be DVD compliant without the DVD=1 setting... DVD-RB sets the parameters correctly for compliance.

[wmansir]

I just encountered this error with the new Curb Your Enthusiasm Season 2 (disc 1, episode 3 to be specific). Damn HBO and that opening logo. Anyway I switched over to CCE 2.5 to see how it would handle it, because I don't recall ever seeing this error in 2.5.

Long story short is that CCE 2.5 didn't generate the error message, but it did freeze up at the same spot. CPU usage was still at 100% but the program became non-responsive. So if anyone encounters that behavior it could be related to this problem.

I got by the problem area by inserting the following line

temp=trim(105742,136585)
temp.trim(0,182).blur(.5)++temp.trim(183,0)

The Blur(.5 ) function decreased complexity enough so that CCE didn't choke. Of course it would have looked like garbage if the video wasn't just random noise, and the blur function is horribly slow for what it does. But it is a quick and dirty solution for the HBO logo.

EDIT: Just noticed this was my 1000th post. Yay!