Experiencing Difficulty Using DVD RB and CCE? If So, Then Ask Your Questions Here.
|
|
p200002
Junior Member
|
10. September 2004 @ 18:30 |
Link to this message
|
Update you guys on the DVDRB 0.58. I tried it with CCE SP 2.67.00.27. It works.
This message has been edited since posting. Last time this message was edited on 10. September 2004 @ 18:56
|
Advertisement
|
![_](https://cdn2.afterdawn.fi/v3/spacer.gif) ![_](https://cdn2.afterdawn.fi/v3/spacer.gif) |
|
Staff Member
2 product reviews
|
10. September 2004 @ 19:12 |
Link to this message
|
That's good to know since I may be getting my old copy back, at least for a while. It seems that my former workplace has a copy nobody is using right now, and my old supervisor may let me use it if I backup some of his movies for him.
|
Gnomex
Member
|
10. September 2004 @ 19:14 |
Link to this message
|
Hmm...
Never considered that. That test will have to wait until I have a little time to work with.
|
AfterDawn Addict
1 product review
|
10. September 2004 @ 19:33 |
Link to this message
|
Hmm! Things sometimes take time, let us know how it works for you.
" 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
|
10. September 2004 @ 19:58 |
Link to this message
|
RE: #0003 ERRORS
I may have stumbled upon something... ...I just installed RB .58 (with CCE Basic), and sent a Remake Pro edited movie through in 1-click mode. I got the #0003 error at the beginning of the Rebuild stage. I checked the RB config file, and it was normal. So, I changed things back to the .57/CCE Basic setup ... which has always worked for me.
I was about to erase all the files and start over, when I wondered what would happen if I went to 3-click mode, and tried to manually initiate the Rebuild step with .57. Well, it started, finished, went through Nero, and I now have a perfect backup.
I've not read where anyone has tried to manually finish the Rebuild process after getting the #0003 error, and so I'm thinking this may be a workaround solution to the #0003 error. While I did the Rebuild with .57, I'm thinking .58 would have worked just as well.
EDIT: This theory turned out to be false as indicated in a few posts down from here. I am leaving this post here in case anyone wonders if it is possible to manually over-ride the #0003 error.
.
.
I am always doing that which I can not do, in order that I may learn how to do it. (Pablo Picasso)
This message has been edited since posting. Last time this message was edited on 10. September 2004 @ 20:47
|
64026402
Senior Member
|
10. September 2004 @ 19:58 |
Link to this message
|
Gnomex
For starters, click the no error messages setting in rebuilder.
I do recommend putting rebuilder, CCE and AVIsynth on E: drive.
What is your computer specs. Are you overclocked?
What OS are you using.
My biggest concern on the CCE error is CCE itself possibly having a conflict with something. Get the 2.67 version for testing. 2.69 should work fine but we need to rule out a version or conflict problem.
Donald
|
64026402
Senior Member
|
10. September 2004 @ 20:09 |
Link to this message
|
Doc
I have done the 3 click after a failed rebuild 0003 error without success.
The .58 may have caused this particular error.
If you could remove the TS files and rebuild with .58 again to verify this it would be helpfull.
Donald
This message has been edited since posting. Last time this message was edited on 10. September 2004 @ 20:10
|
Senior Member
|
10. September 2004 @ 20:17 |
Link to this message
|
I don't know if I understand. There were files in the video_ts folder when .57 Rebuild failed. These files have now changed (obviously). Are you suggesting I delete these files, and see what happens with .58 (and maybe .57 again) with no files in the video_ts folder?
.
.
I am always doing that which I can not do, in order that I may learn how to do it. (Pablo Picasso)
This message has been edited since posting. Last time this message was edited on 10. September 2004 @ 20:49
|
64026402
Senior Member
|
10. September 2004 @ 20:27 |
Link to this message
|
When I do a rebuild over I usually delete the failed rebuild files but it should to it anyway.
I just wanted to be sure the .58 would error again with the same files. One click or 3 click it should not help or hurt.
Donald
|
64026402
Senior Member
|
10. September 2004 @ 20:32 |
Link to this message
|
I have had my best results with .57 so if .58 has some sensitivity to remake files then I might wait to use it as the main rebuilder program. I will test it though.
Donald
|
Senior Member
|
10. September 2004 @ 20:35 |
Link to this message
|
6402 ... excellent call. I tried .58 again, and got the #0003 at exactly the same place (it stopped at the 62.5 MB file size point both times). Right now .57 is running again without a problem.
I guess we'll have to keep looking for a solution. So much for my theory...
.
.
I am always doing that which I can not do, in order that I may learn how to do it. (Pablo Picasso)
This message has been edited since posting. Last time this message was edited on 10. September 2004 @ 20:38
|
64026402
Senior Member
|
10. September 2004 @ 20:38 |
Link to this message
|
.57 had cleared up a 0003 on Terminator2 that was run through remake that I had done on .56 so I am happy with it.
Donald
|
64026402
Senior Member
|
10. September 2004 @ 20:40 |
Link to this message
|
Have you had any problems with .57 ?
Donald
|
Senior Member
|
10. September 2004 @ 20:44 |
Link to this message
|
I've not had a single problem. I am also using current versions of Remake Pro and CCE Basic 2.69.
My problems were with RB .56 and a couple of older versions of RMP. I never had a #0003 problem with just straight Decrypter files.
.
.
I am always doing that which I can not do, in order that I may learn how to do it. (Pablo Picasso)
|
64026402
Senior Member
|
11. September 2004 @ 03:51 |
Link to this message
|
That settles it. I'll use .57 until the next version.
Hopefully we'll get angles and interleave capabilty before long.
Donald
|
DX5
Newbie
|
11. September 2004 @ 08:19 |
Link to this message
|
Hi all
I am new to DVD rebuilder. I have config the software as webmaster's instruction. When I click on the DVD rebuilder icon, it says runtime error 7.
My PC is
P4 1.6G
512 DDR ram
Forgive me if I have come to the wrong place!
Thanks.
|
AfterDawn Addict
1 product review
|
11. September 2004 @ 09:40 |
Link to this message
|
DX5
What versions of CCE, DVD RB, and avisynth are you using?
" 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
|
11. September 2004 @ 10:40 |
Link to this message
|
Donald and other members,
Over the last few weeks I ran into this error with CCE BASIC
[ERROR]
"Cinema Craft Encoder Basic has encountered a problem and needs to close. We are sorry for the inconvenience"
[PROBLEM]
This problem occurs when "RCE Protection" is on the source DVD. Any movie that is ripped with this type of error will fail during the "Re-Build" process.
I 10:19:50 DVD Decrypter Version 3.5.1.0 started!
I 10:19:50 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 1)
I 10:19:50 Initialising SPTI...
I 10:19:50 Searching for SCSI / ATAPI devices...
I 10:19:50 Found 1 CD-RW and 1 DVD±RW!
W 10:19:52 Possible RCE Protection Found!
W 10:19:52 Media region code: 1
[SOLUTION]
Use a background DVD Decrypter in conjunction with the standard "DVD Decrypter". This error has also occurred using other third party backup tools like "DVD Shrink" in uncompressed mode.
I used a trial version of AnyDVD in this solution. This fix has worked on all movies that failed in the past. Hope this helps someone else with unexpected CCE problems.
|
AfterDawn Addict
1 product review
|
11. September 2004 @ 11:07 |
Link to this message
|
Gnomex
Thank you for that info and it's nice to have you aboard. I've never had that particular problem and I also use AnyDVD.
" 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 11. September 2004 @ 11:08
|
Gnomex
Member
|
11. September 2004 @ 11:33 |
Link to this message
|
Sophocles,
Thanks for the welcome! Most of the users on this thread are not professional computer users. I have found making an effort to document a problem clearly may help someone in the future. We all started some-where and learning is what brings us all here.
|
Wingdings
Newbie
|
11. September 2004 @ 11:43 |
Link to this message
|
I just backed up Paycheck with DVD-RB 5.8 Beta and CCE SP 2.67.00.27, all extras included. I ripped it with DVD Decrypter 3.2.1.0 I think it was.
Anyway, I followed the guide on AD (the one directed to noobs) and ended up with an output size of 6.03 GB.
I followed the guide by 100%, except for using CCE SP instead of CCE Basic.
Here's my config file:
[Options]
OneClick=1
NoWarn=1
AudioDub=0
idct7Opt=1
CCE=1
LoadPlugin=1
RemoveDTS=1
Completed=1
[Paths]
CCENEW=E:\Program\Cinema Craft Encoder SP v2.67.00.27\cctsp.exe
MPEG2DEC=E:\Program\DVD-Rebuilder\MPEG2Dec3dg.dll
Source=D:\PAYCHECK\VIDEO_TS\
Working=D:\WORKSPACE\
[Setup]
Languages=1111111111111111111111110111111111111111111111111111111111111111111111111111111111111111111111111111111111111110111111111111111111111111111
sLanguages=1111111111111111111100110111111111111111111111111111111111111111111111111111111110011111111111111111111111111110111111111111111111111111111
[CCEOptions]
VBR_bias=25
Quality_prec=16
eclPasses=2
How do I solve this?
Thanks in advance.
EDIT:
System specs:
AMD Athlon64 3200+
MSI K8N Neo Platinum Edition
Corsair Value Select PC3200 1 GB
400 GB HDD
Windows XP Professional SP1
EDIT2:
I've tried running RP-Opt and it tells me that the estimated output size is 4424 MB.
This message has been edited since posting. Last time this message was edited on 11. September 2004 @ 11:47
|
AfterDawn Addict
1 product review
|
11. September 2004 @ 11:45 |
Link to this message
|
Gnomex
I've noticed that people with home built system's seem to have fewer problems than those with commercially built system's. It could mean that home builts' are better performers, or just as llkely that buiders have a greater working knowledge of their hardware. I've never owned a commercial PC. My first was built by someone else in 1995 and in 1996 I started building my own and have ever since.
" 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
|
11. September 2004 @ 12:14 |
Link to this message
|
Sophocles...I would go along with that...fewer problems with home-builts. In the "early days" building a system had all kinds of compatibility issues, and it made sense to go with a mfg'rd unit. By 1995 the various specs were ironed out, and that's when I went with my first home-built...and have been doing so ever since. The exception was a Compaq P3-500Mhz workstation that I picked up on the cheap, and it was nothing but problems. Most of that had to do with the MoBo being Compaq's design. BTW, my 15 YO son just finished his first build. I spec'd the MoBo and CPU, but he assembled and installed it all incl the S/W from W2k on up.
This message has been edited since posting. Last time this message was edited on 11. September 2004 @ 12:19
|
AfterDawn Addict
1 product review
|
11. September 2004 @ 12:45 |
Link to this message
|
Doc
I've always known you're a builder, so is Donald, jdobbs, Vurbal and more. Many of the others have decided to become software knowledgeable, power-users, and it's interesting how we all approach probems differently. Now that's not to say that our software power-users don't have a significant understanding of hardware or that our builders aren't good with software because we all are and that's what makes it work. But the center of our individual directions have a strong infuence on our approaches to a resolution.
I've played with compaqs, my laptop is an EVO-180.I don't like proprietary sytems because they come with unique maintenance needs. They don't supply restore discs as a service, it's a must for many.
I was able to take the Evo-180 and reformats its hard disc using win2k complete and then I used the restore disk for drivers. Now every year when they assign laptops I get the same PC because they can't erase my files. The restore disc can't access the folder I removed that contained the restore info. I did this because they're the fastest PC's on campus and there are only 4 of them.
" 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
|
![_](https://cdn1.afterdawn.fi/v3/spacer.gif) ![_](https://cdn2.afterdawn.fi/v3/spacer.gif) |
|
Gnomex
Member
|
11. September 2004 @ 12:50 |
Link to this message
|
Sophocles,
I agree with you. You never know what you are really getting with a mass produced machine. I used to sell HP/Compaq and several other makes of machines. All I can say about this is I would never purchase one. It's a gamble and too many people get shorted when it comes down to it.
|