Experiencing Difficulty Using DVD RB and CCE? If So, Then Ask Your Questions Here.

I forgot to mention that my operating system is Windows XP Pro SP1.

 

jimmy3220

I don't think your hardware is the problem but it could be your operating system or a software confict. Many such difficulties as yours were resolved with a clean re install of XP.
_X_X_X_X_X_[small]Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth."[/small]

 

Sophocles,

I agree with you. Systems that have been tweeked over and over have problems that can not be fixed using "Clean and Fix" tools. A clean install not only inproves system preformence, but also has a tendency to free up a lot of hard drive space as a bonus.

 

Somtimes when one operating system gets corrupted and their registry is a clutterend mess then a clean re install certainly helps.

 

If a straight Decrypter file cannot make it through the most recent versions of Decrypter, RB, and CCE, then I would highly suspect it's an OS problem. A reformat/clean install has been the answer for many.

My suggestion would be that any more time spent trying to get things to work would be wasteful, and that a clean install is the next best move. If this doesn't work, then we should look to hardware.

 

jimmy3220

Well you heard it from three experienced users.

 

I agree.
A clean start is needed to keep from spending to much time chasing ghosts.

 

I believe that now makes four, but who's counting? LOL

 

Well I reformatted my hard drive and then reinstalled Windows XP Pro. I still get the #0003 error. What should I do now? Is the MPEG plugin on this website the correct one?

 

jimmy3220 .. yes, that plugin works. Would you post the settings from your most recent configuration file?Also, at what point did you get the #0003 error this time?

Also, I don't use ISO files with RB-CCE, and so I don't know if there is a greater probability of getting a buffer overflow error using this approach. Perhaps some other users could comment on this?

 

Again I would like to thank everyone for their much needed inout. I get the #0003 buffer overflow error at the beginning of the Rebuild process. So far everytime the preparation and encoding processes have worked. Also the resulting Viedo files are playable mening that the menus work and it plays part of the movie which was successfully rebuilt. My current DVD-RB configuration file looks like this:

[Options]
OneClick=0
NoWarn=1
AudioDub=0
idct7Opt=1
LoadPlugin=1
[Paths]
CCEBasic=C:\Program Files\Custom Technology\Cinema Craft Encoder Basic\cct2.exe
MPEG2DEC=C:\Program Files\AviSynth 2.5\plugins\MPEG2Dec3dg.dll
Source=F:\VIDEO_TS\
Working=C:\DVD REBUILDER PROJECT\
[CCEOptions]
VBR_bias=25
Quality_prec=16
eclPasses=2

The reason I am using mounted isos is that for me the encoding process is significantly reduced by more than a hour as opposed to using files. I guess i will play around with it a bit.

 

Your setup looks like it is in order. According to jdobbs, RB's developer, the buffer overflow problem is due to a non-compliant data stream. As you are actually in the rebuilding process, this would likely point to an anomaly within your decrypted file. I would suggest using a different DVD, and ripping in file mode. I am also thinking you might succeed using Smartripper. Use the Backup option tab, and then Start. (Don't worry about the other settings.).

 

I'm actually getting this error too.
I was using dvdrb .60 and was getting it in the same spot, as you.
I actually just went back to .59 because I wasn't having issues with it.

 

I did batch processing using .60 last night and both movies came out perfectly. These 0003 and 0004 errors have become an annoyance to both helpers and users. I wish I could point at any one thing but there doesn't seem to be any and yet there must be some common denominator. This thread was partly started to find it.

Why does RB/CCE work for some people all the time like me who has never had an issue with it?

Everyone I think we need to start looking at the systems that are experiencing problems and their hardware, installed software, drivers and codecs. We have to be missing something.
_X_X_X_X_X_[small]Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth."[/small]

 

I think you're right soph, I never had a problem either til i used remake and since switching on CCE, that has no longer been an issue either.

 

bigo


We're going to have to start getting technical specs on peoples systems. Some boards chipsets such as SiS and via, have had problems with video card drivers. Are we talking helping people with budget systems? They have fast CPU's but everything else is a bottleneck. We have to missing something.

 

Altho a lot of the problems has been with trial versions of CCE SP, I tend to agree. Not everyone was using trial versions.

 

I got to the point where I began assuming a trial version only to discover that many are not. I'm certain that there are hacked version of the trial version of CCE SP which could also explain some of the errors but many are using registered versions of CCE Basic.

 

My initial buffer overflow problem was with edited Remake files (100% failure). Non-edited Decrypter files went through fine. The buffer overflow happened immediately at the beginning of Stage 3/Rebuild. I was using a Matsonic MB with a VIA chipset. No graphics card. I had 512 MB 266 DDR Samsung, P4-2.66 533 FSB. I also had a 5400 RPM C and 7200 RPM D drive (Maxtors). I was also using RB .56, CCE Basic 2.69, and RemakePro 2.2.3. My OS is Win2k SP4.

My first edited Remake went through when I switched out the C drive, and put in a 7200 RPM (this was my D, which was a C clone). When I went to clone the C to the new D drive, things went sideways, and I had to do a complete install at that point. RB and Remake Pro had just come out with with new versions, and so these got upgraded in the new install. Things went smoothly without buffer overflows until installing RB .58 recently. I switched back to .57 and things have gone fine. I will have a movie entering the the RB.60 rebuild stage in about another hour. I'll advise the results.

I think that it is also important to note where in the rebuild cycle the #0003/4 occurs. With RB .58, it happened a few minutes into the cycle...not at the beginning as before. I was then able to successfully run the pre-rebuild files through .57 without redoing the entire 3-1/2 hour process.

I, too, believe we are missing something if we are always getting the straight facts. However, we have to presume that we are. We should recognize, however, that if someone is using a cracked version of CCE, they may be reluctant to say anything.

 

Doc

Excellent post, exactly what we needed and lots of information.

If you have a problem and you want to post it here then review Doc's example. Also if you're using cracked software and not telling us then you might also be intentionally or unintentionally sending us on endless “wild goose chases" looking for answers to incomplete questions. We need to accurately get the feedback we ask for if we're to help.

_X_X_X_X_X_[small]Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth."[/small]