|
Experiencing Difficulty Using DVD RB and CCE? If So, Then Ask Your Questions Here.
|
|
AfterDawn Addict
1 product review
|
19. September 2004 @ 10:39 |
Link to this message
|
|
jimmy3220
Well you heard it from three experienced users.
" Please Read!!! Post your questions only in This Thread or they will go unanswered:
Help with development of BD RB: Donations at: http://www.jdobbs.com/. |
|
Advertisement
|
|
|
|
|
64026402
Senior Member
|
19. September 2004 @ 11:30 |
Link to this message
|
|
I agree.
A clean start is needed to keep from spending to much time chasing ghosts.
Donald
|
AfterDawn Addict
1 product review
|
19. September 2004 @ 11:32 |
Link to this message
|
|
I believe that now makes four, but who's counting? LOL
" Please Read!!! Post your questions only in This Thread or they will go unanswered:
Help with development of BD RB: Donations at: http://www.jdobbs.com/. |
|
jimmy3220
Newbie
|
20. September 2004 @ 04:17 |
Link to this message
|
|
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?
|
Senior Member
|
20. September 2004 @ 05:40 |
Link to this message
|
|
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?
This message has been edited since posting. Last time this message was edited on 20. September 2004 @ 06:06
|
|
jimmy3220
Newbie
|
20. September 2004 @ 08:23 |
Link to this message
|
|
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.
|
Senior Member
|
20. September 2004 @ 09:32 |
Link to this message
|
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.).
|
|
addicta
Newbie
|
20. September 2004 @ 10:46 |
Link to this message
|
|
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.
Never knows best . . .
|
AfterDawn Addict
1 product review
|
20. September 2004 @ 12:41 |
Link to this message
|
|
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.
" Please Read!!! Post your questions only in This Thread or they will go unanswered:
Help with development of BD RB: Donations at: http://www.jdobbs.com/. This message has been edited since posting. Last time this message was edited on 20. September 2004 @ 13:43
|
AfterDawn Addict
|
20. September 2004 @ 13:31 |
Link to this message
|
|
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.
 GO VOLS ! |
AfterDawn Addict
1 product review
|
20. September 2004 @ 13:48 |
Link to this message
|
|
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.
" Please Read!!! Post your questions only in This Thread or they will go unanswered:
Help with development of BD RB: Donations at: http://www.jdobbs.com/. |
AfterDawn Addict
|
20. September 2004 @ 13:51 |
Link to this message
|
Altho a lot of the problems has been with trial versions of CCE SP, I tend to agree. Not everyone was using trial versions.
GO VOLS !
|
AfterDawn Addict
1 product review
|
20. September 2004 @ 13:59 |
Link to this message
|
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.
" Please Read!!! Post your questions only in This Thread or they will go unanswered:
Help with development of BD RB: Donations at: http://www.jdobbs.com/. |
Senior Member
|
20. September 2004 @ 15:53 |
Link to this message
|
|
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.
This message has been edited since posting. Last time this message was edited on 20. September 2004 @ 16:12
|
AfterDawn Addict
1 product review
|
20. September 2004 @ 16:09 |
Link to this message
|
|
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.
" Please Read!!! Post your questions only in This Thread or they will go unanswered:
Help with development of BD RB: Donations at: http://www.jdobbs.com/. This message has been edited since posting. Last time this message was edited on 20. September 2004 @ 16:22
|
|
jdobbs
Senior Member
|
20. September 2004 @ 16:22 |
Link to this message
|
|
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.
|
Senior Member
|
20. September 2004 @ 16:31 |
Link to this message
|
|
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.
This message has been edited since posting. Last time this message was edited on 20. September 2004 @ 16:31
|
AfterDawn Addict
1 product review
|
20. September 2004 @ 16:31 |
Link to this message
|
|
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.
" Please Read!!! Post your questions only in This Thread or they will go unanswered:
Help with development of BD RB: Donations at: http://www.jdobbs.com/. This message has been edited since posting. Last time this message was edited on 20. September 2004 @ 16:34
|
|
Gnomex
Member
|
20. September 2004 @ 16:50 |
Link to this message
|
|
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.
Disclaimer: Any errors in spelling, tact, or fact are transmission errors.
|
AfterDawn Addict
1 product review
|
20. September 2004 @ 17:18 |
Link to this message
|
|
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.
" Please Read!!! Post your questions only in This Thread or they will go unanswered:
Help with development of BD RB: Donations at: http://www.jdobbs.com/. |
|
jdobbs
Senior Member
|
20. September 2004 @ 17:19 |
Link to this message
|
|
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.
This message has been edited since posting. Last time this message was edited on 20. September 2004 @ 17:20
|
AfterDawn Addict
1 product review
|
20. September 2004 @ 17:30 |
Link to this message
|
|
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.
" Please Read!!! Post your questions only in This Thread or they will go unanswered:
Help with development of BD RB: Donations at: http://www.jdobbs.com/. |
|
Gnomex
Member
|
20. September 2004 @ 17:44 |
Link to this message
|
|
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.
Disclaimer: Any errors in spelling, tact, or fact are transmission errors.
|
AfterDawn Addict
1 product review
|
20. September 2004 @ 17:59 |
Link to this message
|
|
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.
" Please Read!!! Post your questions only in This Thread or they will go unanswered:
Help with development of BD RB: Donations at: http://www.jdobbs.com/. |
|
Advertisement
|
|
|
|
Gnomex
Member
|
20. September 2004 @ 18:20 |
Link to this message
|
|
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.
Disclaimer: Any errors in spelling, tact, or fact are transmission errors.
|
