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

I've found what I believe is causing at least some of the #0003 and #0004 errors in v0.60 -- and it's not configuration errors. I'm working on a fix. Looks like there is going to have to be a v0.60c.

 

Sophocles...thanks for the input. I just finished LOTR-Fellowship with RB.60/CCE Basic 2.69 Retail. No problems.

While I was able to "solve" my buffer overflow problem as discussed above, I went through several changes in a short period. This, unfortunately, makes it difficult to positively identify what I did that solved the buffer overflow. I realize now that I may have only used one drvie, like brobear, when I got my first successful encode. I know that I had 2 drives installed...but did I use 2 drives? I only had one encode before having to do a fresh install...and this is what I really believe solved the problem. It could have also been the newer versions of RB and Remake Pro that got installed. Anyway, I just had too many trial programs that I had removed...which tends to corrupt files...to think that this wasn't the main problem. After all, others were having success with the older versions.

 

jdobbs

Glad to hear about it. We're trying to broaden our search a bit because something in our current efforts are missing. Something besides RB alone. Some people never have problems, some a few, and some have many. What makes them different?


When you make .60c available let us know.
_X_X_X_X_X_[small]Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth."[/small]

 

Sophocles

Sadly most popular software packages are cracked and passed out all over the
internet. One might think that one would NOT ask for support on a product that
came into one's hands in a questionable manor However that is just my outlook.

In the event that this thread starts to ask for detailed specs on an end-users
machine, I see problems. Most end-users don't know what RPM, BIOS, DMA,
or IRQ from there ABC. A guide might be in order to aid such users. This
speculation is not true for power users or tech heads as the case might be.

 

Gnomex

Good point we'll have to make it easier for them by asking them the right questions and then providing simple directions to the right answers. It sounds like the good old AD forum to me.

We aren't out to torment them only to find out what the causes of their problems are. I don't personally care if they're using cracked versions or not, I'm not a cop. But if their withholding information from us that results in a significant amount of our time then when does our time become wasted? We should at least know something about the versions of software they're using if we're to effectively resolve their issues.

 

I've posted v0.61 (I decided too many single letter extensions might get confusing).

What you mentioned is one of my dilemmas. There are many possibilities as to what is different between systems. DVD-RB relies on some of the DLLs that are shipped with Windows. Sometimes other apps "update" these (even in a downward direction). Most of the time the cause is a hidden MPEG2DEC3.DLL or AVISYNTH.DLL -- if you've been around the scene for a while, experimenting a lot, you'd be surprised how many of these you'll find with a disc search. Of course in some circumstances you have to look in the system registry to find which of a particular .DLL is active.

Those are just a couple possible causes of "strange" behaviour. When I get to version 1.00 I will wrap this all in an installation package that will solve some of this -- but with the number of changes I'm making in beta I hesitate to wrap it.

 

jdobbs

Thanks for the info. Too many success stories for the unsuccessful ones to be caused by RB only. I agree that there's a potential of a dll mess. I can't speak for its affect on avisynth I don't know enough about it.

 

Sophocles ,

I personally don't care how a person came to get there software. However, I
see a problem when a person is confused with odd behavior with a product
when the product might be unstable in nature due to a fast hack that did
some dammage to the executable. Lets face it the cost of CCE is cheap
for what it does.

 

Gnomex

Agreed! I too think that CCE is well worth the price, I paid for it. Right now I'm more interested in the causes of their problems than I am in how they got their software, that's for them to resolve for themselves.

 

Sophocles,

I just hope that the problems that people are reporting are due to O/S ~ Hardware
conflicts and not due to software that was cracked badly. The first two items
are enough to make the most die-hard support reach for there extra strong
cup of java.

 

jdobbs DVD-RB v0.61 has solved both my #0003 and #0004 errors!!! I used a previously saved project (made with DVD-RB v0.60) that made it through the encode process. (In this case I decided to try The Punisher).
So since I had already setup DVD-RB I used the old configuration file for the newest version. I opened the .rbd project file then pressed rebuild and 15 minutes later it completed!!!
I haven't burned it yet but I will shortly. I will also compare it with my DVD Shrink produced disc. (I used reauthor mode, deep analysis, sharp AEC.)
Again I thank all of you for helping me out. I would also like to recommend that anyone that has been unable to get this working and gave up to try the newest version!

 

jimmy3220...that is really good news. Thanks for the feedback, also.

jdobbs...good work!!!

 

The following link to check/download the latest Rebuilder version has been added to the FAQ's (#10).
http://forum.doom9.org/showthread.php?s=&threadid=75452

 

It's me again. Ok now I got DVD-RB v0.61 working and rebuilding. Now I have a new found problem. Now for some reason the Video_TS DVD-RB is producing will not exceed 2.7 GB! I haven't tried any of the advanced settings yet. I opened the Rebuilder file from one of the projects with RB-OPT v0.15. It indicates that the Video size is 100%, DVD estimated size 4424 MB, RB TargetSectors 2236303. What should I do in order to use much more of the disc? I would also like to note that I am using Daemon Tools mounted iso as the source, just in case that has an effect.
I am going to try using CCETargetSectors=2260000 and see if that will pump up the size a bit.

 

[bold]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.......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)......[/bold]

Same with me only I solved the problem by reverting to CCE basic 2.67 from 2.69 and all remake problems went away. I'm still using 2.67 subscribing to the "if it ain't broke" theory....

The problems are so far reaching and wide ranging that it seems everyone's case is different which in itself presents a problem. Systems are different, they don't come from cookie cutters. Then you add in software issues, it's amazing we get positive results at all!


[bold]I just hope that the problems that people are reporting are due to O/S ~ Hardware
conflicts and not due to software that was cracked badly. The first two items
are enough to make the most die-hard support reach for there extra strong
cup of java[/bold]

Amen, brother! It's one of the reasons I became so exasperated with this and the other thread dealing with Rb/CCE. That, or they were using trial versions and leading us to believe they were using purchased Basic versions. It makes ya wanna pour Jack in that coffee and throw your hands up, which , I must confess, I did.

Cudos to you guys who have stayed the course(vurbal,doc, soph, 6402...) and to jdobbs for what I think is an excellent software. I may be ready to jump back in the fray, after another coffee, of course.....lol

 

jimmy, that's where brobear's problem arose, once he got it going, he had sizing issues and had to put it all on the same drive. That cured the problem. Also, using Daemon Tools with an ISO shouldn't make any difference.
_X_X_X_X_X_[small] [bold]GO VOLS![/bold]..Dell Media4600,XP,Pentium 4 @2.80GHz/800Mz,512MB,280HDw/8MB,17"flat panel,AIO-A920,8xDVD-ROM,integrated5.1 audio,HPdc4000,PlextorPX-708UF,LiteOn832S-DL[/small]

 

If DVD-RB determines 100% compression -- that normally means the source will already fit on a DVD-5, and you shouldn't run DVD-RB against it (just burn it).

 

LOL, that's true! It means O% compression, what a dummy I am. lol

 

Oh I forgot to mention that the original disc size is 5.7 GB. Also The Punisher which I tried to do is around 8 GB. Both were reduced to 2.7 GB.

 

bigorange,

Now heres an interesting question to ponder. Has moving the files from one hard drive fixed the problem due to hardware limitations or software configuration problems. It makes you wonder.