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

You're welcome. A lot of encoding is getting a feel for how things work with a program. The hands on aspect is where you really learn. Instructions just get you pointed in the right direction. Good luck and have fun.

 

I have been trying to get DVD RB to work on my computer for a while. It runs great, but I end up with DVD files that are over 8 GB, far too big to fit on a single disc. That is larger than the movie was in the first place.

I am using:

DVD Rebuilder v.95 Freeware Version
CCE SP v. 250

My Rebuilder.ini:
[Options]
Mode=1
OneClick=0
ReduceOpt=0
NoWarn=1
AdditionalOutput=1
LogFile=1
QuEncHQ=1
EncoderMinimized=1
RemoveDTS=0
HC_Quality=1
HC_Matrix=1
SkinVersion=3
Skin=Windows Standard
AudioDub=0
idct7Opt=1
CCE=0
HalfD1=000
Convert_16_9=000
DisableInterlace=000
Completed=3
CCETargetSectors=2260000
[Paths]
QuEnc=C:\Program Files\DVD-RB\Encoders\QuEnc\QuEnc.exe
ReJig=C:\Program Files\DVD-RB\Encoders\ReJig\ReJig.exe
HC=C:\Program Files\DVD-RB\Encoders\HC Encoder\HCbatch.EXE
ProCoder=C:\Program Files\DVD-RB\Encoders\EclPro\EclPro.exe
DECOMB=C:\Program Files\AviSynth 2.5\plugins\Decomb521.dll
MPEG2DEC=C:\Program Files\DVD-RB\DGDecode.dll
Working=R:\Media\Video\Work\
Output=R:\Media\Video\Output\
CCENEW=C:\Program Files\EclCCE\EclCCE.exe
Source=E:\VIDEO_TS\
CCE250=C:\Program Files\EclCCE\EclCCE.exe
[CCEOptions]
VBR_bias=25
Quality_prec=16
eclPasses=2
[Audio]
Selected=11
[Subpictures]
Selected=1111

Any ideas?

Thanks,

(Spirit)

 

Are you looking at the entire folder created by RB or just the VIDEO_TS folder that has the movie? When you go to burn, you only burn the VIDEO_TS or the ISO File. Whichever you chose as the output option for your project. If that isn't the situation, then the easiest solution is to follow the instructions and use the ROCKAS installer and reload the setup. Most real problems stem from faulty setups or being too creative with the settings. Sometimes it's an idea to clear out the configuration files and set everything back to default.

 

Yeah, it's only the VIDEO_TS folder. Each VTS_01_*.VOB is definitely over a gig and there are 8 of them. I didn't mess around with any settings other than what was described in the tutorial. Is there maybe some other order of installation that needs to be followed?

Thanks,

(Spirit)

 

are you sure cce is being called properly/at all?

do you have a log file?

 

UncasMS

I agree with uncasMS, it sounds as though there was no encoding taking place. In the folder with your encoded movie should be a D2VAVS folder as well, if it's not there then you don't have RB pointing to CCE or the right version of CCe.

 

CCE Opens during Encoding process and seems to be working. I do have a D2VAVS folder, but it is in my "Work" Folder and the VIDEO_TS folder is saved in the "Output" folder.

Here's my log.

-----------------
[09:56:56] Phase I, PREPARATION started.
- VTS_01: 3,605,207 sectors.
-- Scanning and writing .D2V file
-- Embedded null records found
-- Processed 274,048 frames.
-- Building .AVS and .ECL files
- VTS_02: 48,041 sectors.
-- Scanning and writing .D2V file
-- Processed 4,237 frames.
-- Building .AVS and .ECL files
- Reduction Level for DVD-5: 56.9%
- Overall Bitrate : 2,779Kbs
- Space for Video : 3,937,360KB
- HIGH/LOW/AVERAGE Cell Bitrates: 3,401/887/2,779 Kbs
[10:03:30] Phase I, PREPARATION completed in 7 minutes.
[22:43:07] Phase II ENCODING started
- Creating M2V for VTS_01 segment 0
- Creating M2V for VTS_01 segment 1
- Creating M2V for VTS_01 segment 2
- Creating M2V for VTS_01 segment 3
- Creating M2V for VTS_01 segment 4
- Creating M2V for VTS_01 segment 5
- Creating M2V for VTS_01 segment 6
- Creating M2V for VTS_01 segment 7
- Creating M2V for VTS_01 segment 8
- Creating M2V for VTS_01 segment 9
- Creating M2V for VTS_01 segment 10
- Creating M2V for VTS_01 segment 11
- Creating M2V for VTS_01 segment 12
- Creating M2V for VTS_01 segment 13
- Creating M2V for VTS_01 segment 14
- Creating M2V for VTS_01 segment 15
- Creating M2V for VTS_01 segment 16
- Creating M2V for VTS_01 segment 17
- Creating M2V for VTS_01 segment 18
- Creating M2V for VTS_01 segment 19
- Creating M2V for VTS_01 segment 20
- Creating M2V for VTS_01 segment 21
- Creating M2V for VTS_01 segment 22
- Creating M2V for VTS_01 segment 23
- Creating M2V for VTS_01 segment 24
- Creating M2V for VTS_01 segment 25
- Creating M2V for VTS_01 segment 26
- Creating M2V for VTS_01 segment 27
- Creating M2V for VTS_01 segment 28
- Creating M2V for VTS_01 segment 29
- Creating M2V for VTS_02 segment 0
- Creating M2V for VTS_02 segment 1
- Creating M2V for VTS_02 segment 2
- Creating M2V for VTS_02 segment 3
- Creating M2V for VTS_02 segment 4
[00:14:55] Phase II ENCODING completed in 91 minutes.
[00:34:27] Phase III, REBUILD started.
- Copying IFO, BUP, and unaltered files...
- Processing VTS_01
- Reading/processing TMAP table...
- Rebuilding segment 0 VOBID: 1 CELLID: 1
- Rebuilding segment 1 VOBID: 1 CELLID: 2
- Rebuilding segment 2 VOBID: 1 CELLID: 3
- Rebuilding segment 3 VOBID: 1 CELLID: 4
- Rebuilding segment 4 VOBID: 1 CELLID: 5
- Rebuilding segment 5 VOBID: 1 CELLID: 6
- Updating NAVPACKS for VOBID_01
- Rebuilding segment 6 VOBID: 2 CELLID: 1
- Updating NAVPACKS for VOBID_02
- Rebuilding segment 7 VOBID: 3 CELLID: 1
- Updating NAVPACKS for VOBID_03
- Rebuilding segment 8 VOBID: 4 CELLID: 1
- Rebuilding segment 9 VOBID: 4 CELLID: 2
- Rebuilding segment 10 VOBID: 4 CELLID: 3
- Rebuilding segment 11 VOBID: 4 CELLID: 4
- Possible dropped frame(s) noted in this segment, continuing...
- Updating NAVPACKS for VOBID_04
- Rebuilding segment 12 VOBID: 0 CELLID: 0
- Possible dropped frame(s) noted in this segment, continuing...
- Updating NAVPACKS for VOBID_00
- Rebuilding segment 13 VOBID: 4 CELLID: 4
- Possible dropped frame(s) noted in this segment, continuing...
- Rebuilding segment 14 VOBID: 4 CELLID: 5
- Rebuilding segment 15 VOBID: 4 CELLID: 6
- Updating NAVPACKS for VOBID_04
- Rebuilding segment 16 VOBID: 5 CELLID: 1
- Rebuilding segment 17 VOBID: 5 CELLID: 2
- Rebuilding segment 18 VOBID: 5 CELLID: 3
- Rebuilding segment 19 VOBID: 5 CELLID: 4
- Rebuilding segment 20 VOBID: 5 CELLID: 5
- Rebuilding segment 21 VOBID: 5 CELLID: 6
- Updating NAVPACKS for VOBID_05
- Rebuilding segment 22 VOBID: 6 CELLID: 1
- Updating NAVPACKS for VOBID_06
- Rebuilding segment 23 VOBID: 7 CELLID: 1
- Rebuilding segment 24 VOBID: 7 CELLID: 2
- Rebuilding segment 25 VOBID: 7 CELLID: 3
- Rebuilding segment 26 VOBID: 7 CELLID: 4
- Rebuilding segment 27 VOBID: 7 CELLID: 5
- Rebuilding segment 28 VOBID: 7 CELLID: 6
- Updating NAVPACKS for VOBID_07
- Rebuilding segment 29 VOBID: 8 CELLID: 1
- Updating NAVPACKS for VOBID_08
- WARNING: VOB Count Old: 8 New: 9
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_01_0.IFO
- Updating TMAP table...
- Processing VTS_02
- Reading/processing TMAP table...
- Rebuilding segment 0 VOBID: 1 CELLID: 1
- Updating NAVPACKS for VOBID_01
- Rebuilding segment 1 VOBID: 2 CELLID: 1
- Updating NAVPACKS for VOBID_02
- Rebuilding segment 2 VOBID: 3 CELLID: 1
- Updating NAVPACKS for VOBID_03
- Rebuilding segment 3 VOBID: 4 CELLID: 1
- Updating NAVPACKS for VOBID_04
- Rebuilding segment 4 VOBID: 5 CELLID: 1
- Updating NAVPACKS for VOBID_05
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_02_0.IFO
- Updating TMAP table...
Correcting VTS Sectors...
[01:22:42] Phase III, REBUILD completed in 48 minutes.

Done.

 

spirit18
While you're at it, paste the configuration file from the RB folder.

 

My Rebuilder.ini is a couple posts above...

 

spirit18

You have CCE set to the wrong path. Your INI files says that you're using version 2.50 but the path is set to CCE new. Set the path for CCE 2.50 and try again. In fact you have CCE set twice, which versions do you have?

 

I have CCE SP v 2.50

 

You have CCE set to CCE new. Delete your INI file and redo setup and set the path to CCE 2.50 only.

 

what cpu do you have?

 

AMD Athlon XP 2500+ Barton, why? That shouldn't have anything to do with it...

 

spirit18

Trust me just redo your setup and make sure that you point RB to the right version of CCE.

 

yes and no

it has nothing to do with oversizing

my reason for asking, however, is this:
you're dealing with a title of ~150min or more which was encoded in ~90 with 2 passes - this is amazingly fast imho

the following rebuild process took ~40min which is extremely slow

so before wondering too much i thought to ask for the cpu used

 

Your hardware can affect an encode but the more likely culprit is here.
This is an extraction from your RB file.

You have a selection for CCENEW and another for CCE250. If you have both versions then it's not a problem as long as you make the appropriate selection under CCE options. If you don't have CCE 2.67 or higher installed then you just might have a setup problem.

 

i dont fully second that

both paths lead to ONE folder containing eclcce.exe - no problem so far

in case two different version were installed and should be used, then two different locations for eclcce.exe will be needed in order to call both version (e.g. 2.5 + 2.67) independantly

but even if 2.5 and 2.6x were installed and selected via MODE menu only one of them will be started with the current setup - the very cce*.exe which eclcce.exe calls

thus the setup should not lead to a problem

 

UncasMS

Look back and you'll see that he said he only had version 2.5.

That's what I said. I use more than one version of CCE too but if I was using 2.50 and I selected CCE new it won't work.

 

I think that the double calls to CCE were in there because when I originally set it up I set it for CCE SP, but then realized I had CCE SP 2.50 so I changed the Options>CCE whatever to CCE 2.50. It just didn't take out the call to the newer version because there's no way to delete it. I removed the call from the .ini folder after you guys pointed it out though, and it is running right now.

Also, whoever pointed out the extremely fast encoding, I wouldn't say my processor is incredibly speedy, and it's running at 95% during the process. Is there a reason this might be happening? Cause CCE is definitely opening and it says its encoding, so it's not like it's just skipping some process.

Thanks,

(Spirit)