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

prospeed, yeah it was getting intense in here... I'll help fix it up


You are right about the folder aspect, brobear. I have yet to get a recode to work, once I do and start a bunch of backups, I will get organized... hopefully :þ

I am rebuilding now so I will let you know about our tweeks.

 

Hopefully all goes well. Did you edit the "rebuilder-Configuration Settings" file by inserting the configuration settings that I provided?

 

I set my rebuilder settings to the ones that you provided and I got a better outcome.. the video accually moves now. It is rather pixilated and looks like this. This is the Dreamworks logo after the intro.

http://images.filecloud.com/11801/Terminal_Encode2.JPG

I would also like to note that atleast now the VIdeo_TS folder is the correct size.. :/

 

Little addition on my part: I noticed too that the dir with all the files to be rebuild was rather small.
It churned out a 4.5GB end product anyway after rebuilding. Don't know where it got it from...

 

jugbugs

There's a problem in your setup someplace because the pixelation that you showed points toward an avisynth problem. Go to your destination folder and using Windows Media player open one of the .avs files and read the message.

 

Hi I am having trouble with dvd rebuilder. I am trying to backup Dodgeball, and the end product is about 4.8 GB, too large to fit on a dvd+r. I have checked the ini file as shown below

[Paths]
CCE250=C:\Program Files\Cinema Craft Encoder SP v2.67.00.27\cctsp.exe
MPEG2DEC=D:\Backup\DVD Shrinking\DVD Rebuilder 0.7.8\DGDecode.dll
DECOMB=D:\Backup\DVD Shrinking\DVD Rebuilder 0.7.8\Decomb521.dll
Source=C:\DODGEBALL_WS\DVDREMAKE\
Working=C:\DODGEBALL_WS\
Output=C:\DODGEBALL_WS\OUTPUT\
[Options]
EncoderMinimized=1
LogFile=1
AdditionalOutput=1
CCE=0
HalfD1=0000
Convert_16_9=0000
DisableInterlace=0000
ReduceOpt=1
DynamicBitrate=1
Completed=2
NoWarn=1
OneClick=1
[Setup]
Languages=1111111111111111111111110111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111
sLanguages=1111111111111111111111110111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111
[CCEOptions]
VBR_bias=30
Quality_prec=20
eclPasses=5
[Audio]
Selected=11110000





Any suggestions?

 

I am not sure as to what avs file and where.. but I looked in the D2VAVS folder and found a bunch of 1KB files which opened and played nothing w/o any errors.

 

@payamn

You have selected the wrong CCE version -- your INI path shows that the path for CCE version 2.50 is pointing to CCE v2.67. That has confused the encoder and it is encoding at Constant Bitrate (CBR), causing your encode to oversize.

Go into SETUP and point "Path to CCE SP (New)" to CCE 2.67. Then under the Options/CCE Options menu, select "CCE SP"

With that you should be good to go.

 

jugbugs,
As we've been saying all along, besides the setup problem, you appear to have a problem with the AviSynth setup. You never said which version of AviSynth you have installed. Whatever, there still appears to be a problem there. The best thing to do would be to go into "Add and Remove Programs" in the control panel and remove AviSynth. Then go to the AviSynth program folder in windows and delete any remnants left behind. Then go to the AviSynth downloads and choose one of the 2.5 versions. I'm using AviSynth 2.56 (beta 1). Let the Avisynth load into the default folder. Then download and install the 1.2.0 DGDecode.dll (or earlier) decoder plugin into the AviSynth plugins folder. Set the path to the decoder plugin in Options -> Setup in RB. (Note the 1.2.1 DGDecode will not work with the current RB)
Here is a link to a listing of sites for the components I mentioned. You'll also find links where you can purchase CCE Basic.
http://www.zentarium.com/forums/showthread.php?threadid=214

(Do not try to use 1.2.1 with current versions of RB.)

 

Heh, heh, heh, ... Paradox.

 

payamn

You have under

[Paths]

CCE250=C:\Program Files\Cinema Craft Encoder SP v2.67.00.27\cctsp.exe

should say:

"CCENEW"=C:\Program Files\Cinema Craft Encoder SP v2.67.00.27\cctsp.exe

Check your folders directory's(C:\ and or D:\), and if "D:\" is your DVD Rom and you're decoding and burning at the same time, then I'm saying you shouldn't do it on the on the fly unless you have a resource wealthy PC with 1 gig of memory or better and using Win2k or Win XP. CCE is CPU intensive, and uses up all of your CPU cycles. Even using undemanding applications and multi tasking can ruin the process.

I write all of this and then jdobbs posts before.

 

I was using Whatever avisynth that was in the installer. I went ahead and got the new beta one as well as a new DGdecoder. Now I get an error before encode. What is this no M2V error I am getting now?

 

You need to stick with the recommended DGDECODE.DLL. The new versions have been modified greatly and don't work with DVD-RB.

I also wouldn't recommend using a beta with a beta... that's a formula for trouble. Use the AVISYNTH from the installer.

 

Again!


jdobbs hasn't had a chance to work with newer applications that RB uses to complete the encoding process with. A change in each application's parameters can affect the instructions that RB sends to it.

 

Okay jdobbs, Where do I go from here, what have I done wrong to get an output like this?

http://images.filecloud.com/11801/Terminal_Encode2.JPG

 

I'm just now checking some variations in the setup. I got the same M2V error as jugbugs on the latest AviSynth and DGDecode setup. I reinstalled the earlier version of 2.56 AviSynth with the latest DGDecode.dll and it's running as I type this. With the prior AviSynth beta and the DGDecode I've backed up over 20 movies without a single error. Guess I should have tested better before suggesting the latest AviSynth beta 2.

 

jugbugs

It's in your setup, you have so many encoders listed that you might have created a wrong link. Remove everything and then do your steup all over again. If it doesn't work then restore everything to where you were. I'd even recommend that you keep everything on the same disk.

 

jugbugs
here is the link for 2.5.5 AviSynth. All you need to do is download and change in this version. As I said, I'm now running the encode and the problem was the beta 2. The earlier beta 1 of the same version worked exceptionally well. I didn't realize the new changes would affect RB so much. All you need to do is click the link and the 2.5.5 AviSynth download will come up. This is a tested and stable version.
http://prdownloads.sourceforge.net/avisynth2/AviSynth_255.exe?download
As I write this, I'm well into the encode with the 1.2.0 DGDecode.dll and AviSynth 2.56 (beta 1). I'll let you know how it comes out in a couple of hours.

 

On that latest image, we told you that was the AviSynth. I believe jdobbs will agree on that. And that would have been with the installer. As I mentioned a clean install of AviSynth should cure the problem. Just don't use the 2.56 (beta 2). As we've seen that version delivers the M2V error. The 2.55 I supplied a link for should work well. The later 2.56 up through alpha appear to work. I haven't checked them all. And as I said, I've been working with beta 1 without troubles.

 

@jugbugs

Try the encode with QuEnc... that will tell you if it is AVISYNTH or DGDECODE. It looks like the encoder, however... I can't remember where, but I seem to remember a reported hacked version of CCE that was doing this kind of goofy encoding...