Log in

View Full Version : DVDRB Pro v1.24.0 - CCE freezing up

Pages : [1] 2
Craz
22nd May 2007, 17:34
Hi,

I'm using DVDRB Pro v1.24.0 together with CCE v2.66.
I've created an iso with DVDDecrypter v3.5.4.0 from the DVD i'm trying to process (The Departed R2 PAL), but every time I try to run it through dvdrb it causes cce to freeze up at 96,2% at the exact same m2v segment.

Is this a know issue (maybe conflict with something?) or has anyone else experienced the same issue and able to solve it ?

Thanks in advance!
~bT~
22nd May 2007, 17:35
Upgrade and see if u still have the same probs.
Fishman0919
22nd May 2007, 22:50
Hi,

I'm using DVDRB Pro v1.24.0 together with CCE v2.66.
I've created an iso with DVDDecrypter v3.5.4.0 from the DVD i'm trying to process (The Departed R2 PAL), but every time I try to run it through dvdrb it causes cce to freeze up at 96,2% at the exact same m2v segment.

Is this a know issue (maybe conflict with something?) or has anyone else experienced the same issue and able to solve it ?

Thanks in advance!

DVDDecrypter v3.5.4.0 alone is not able to rip The Departed

Try DVDFab HD Decrypter 3.1.1.6 (http://www.dvdfab.com/free.htm)
Craz
23rd May 2007, 17:50
I used dvddecrypter in combination with anydvd 6.1.3.6, but I'll try it again with dvdfab and the latest version of dvdrb vip (1.25).

I'll keep you guys posted if it works or not :)
Fishman0919
24th May 2007, 16:25
Try read this...

http://forum.doom9.org/search.php?searchid=2141687

http://forum.doom9.org/showthread.php?t=81525&highlight=CCE+2.66+lockup
Craz
24th May 2007, 17:14
Ok I tried again.

Ripped the dvd with dvdfab (latest free version I downloaded from the website).
Then used DVDRB VIP v1.25 together with CCE 2.66.

Still same problem, cce freezes at the same point as before (96,2% progress in DVDRB).

@Fishman: I read those topics, but it's just cce that freezes, not my whole system. It's also always at the same point in DVDRB (when it says - Creating M2V for VTS_03 segment 6).
I formatted my pc 2 weeks ago and this is the first dvd I try to backup since the format. Before that (same pc, same hw) it worked great. So I think it might have to do with this specific title ?

I attached the dvdrb log here if it might help giving an insight.
note: the aborted line at the end is because I pushed abort in dvdrb after cce freezing up.
Boulder
24th May 2007, 21:07
Have you tried encoding with HC v0.21?
Craz
24th May 2007, 21:20
I haven't, since I prefer CCE above HC :)
Boulder
25th May 2007, 03:25
Why not give it a go to see whether it's a problem with CCE or DVD-RB;)
Craz
25th May 2007, 07:50
Last night I tried another dvd using DVDRB VIP & CCE 2.66, that worked great. CCE didn't freeze up and I got a perfect backup.

So my guess is the problem lies with the departed disc not with dvdrb/cce or my pc.
Craz
25th May 2007, 17:18
No one that did The Departed with CCE and can tell me what versions of which tools used ?

I'm trying with HC as we speak, but I really would like to backup this disc with CCE.
~bT~
25th May 2007, 17:41
I've done the Departed using DVD-RB v1.24 and CCE SP 2.70.02.12.
Movie was ripped using RipIt4Me v1.7.1.0 in movie & menus mode.
SpazzHH
26th May 2007, 04:37
@Craz

Sounds to me like this could be a decoder problem. What version of DGDecode are you using?
Craz
26th May 2007, 10:13
The attempt with HC was succesful, but I'd really like using CCE for this.

@Bengali: I'll try to upgrade to v2.70

@SpazzHH: I'm using the one that came with the installation package of DVDRB vip 1.25, which is DGDecode v1.4.5 according to the html file that comes along.
jdobbs
26th May 2007, 14:30
CCE 2.66 is four years old, and there have been lots-and-lots of bug fixes since then.
Craz
27th May 2007, 11:50
After upgrading to cce v2.70 it didn't freeze up anymore, but the result is only 4.23GB.

Any ideas how to fix that ?
Boulder
27th May 2007, 12:05
Enable adaptive quant matrices by adding CCEAQM=1 under [Options] in rebuilder.ini and rerun the whole project.
jdobbs
27th May 2007, 12:44
After upgrading to cce v2.70 it didn't freeze up anymore, but the result is only 4.23GB.

Any ideas how to fix that ?The only time I've seen sizing that is not very close to the target 4.32GB is when using OPV.

If you are using OPV, that is well within the range you should expect. Sizing deviations are to be expected for two reasons: 1) The 2% prediction can only get you so close. It's the price you pay for the increased speed. 2) OPV's accuracy is limited to the granularity of the Q factor. In other words, you may find that a single increment in Q would bring you from 4.23GB to a size that won't fit on a DVD-5.
Craz
27th May 2007, 13:01
I didn't use OPV, I used VBR 6 passes.

I've added CCEAQM=1 under [Options] and I'm rerunning the project as we speak.

Also another question: I've enabled "run encoders minimized". That worked great with cce 2.66, but now when using cce 2.70 I don't see the cce job window, but I do get the progress window all the time and I can't minimize or hide that one it seems. Is this just the way cce 2.70 is or did I forgot something ?
jdobbs
27th May 2007, 23:48
No. That's just the way CCE v2.70 works.

Let me know if CCEAQM=1 corrects it. Are you, by chance, doing a movie-only encode. If so sometimes encoder saturation will sometimes prevent it from sizing up. CCEAQM=1 will correct it if that's the case.
therat
28th May 2007, 05:27
I'm having the same undersizing problem with one particular DVD - The Banchwarmers - PAL - Region 4.

I have redone it 4 times now. the first 3 times it always came out at 4,551,861 bytes. I then tried it with CCEAQM=1 and got 4581120000 which is still well under the usual size.

i'm using DVD-RB Pro 1.25 with CCE SP 2.70.02.12 Full backup mode.


[Options]
CCEAQM=1
Mode=1
OneClick=0
ReduceOpt=0
NoWarn=1
AdditionalOutput=1
LogFile=1
QuEncHQ=1
EncoderMinimized=1
RemoveDTS=1
HC_Quality=1
HC_Matrix=1
SkinVersion=12
AudioDub=1
QuEncodeType=0
iDCT=3
GOP=0
DCPrec=0
MainMatrix=Encoder Default
LowMatrix=AUTO-Q2
VLowMatrix=AUTO-Q2
ExtraMatrix=AUTO-Q2
ProCoder_Quality=4
DVD_Label=2
DVD_Name=2.ISO
MovieOnly=0
HalfD1=00
Convert_16_9=00
DisableInterlace=00
ConvertToYUY2=1
CCE=1
Skin=Rebuilder Default
RemoveDC=1
Encode_Processes=1
Completed=10
[Paths]
QuEnc=C:\Program Files\DVD-RB PRO\Encoders\QuEnc\QuEnc.exe
ReJig=C:\Program Files\DVD-RB PRO\Encoders\ReJig\ReJig.exe
HC=C:\Program Files\DVD-RB PRO\Encoders\HC Encoder\HCbatch.EXE
FFMPEG=C:\Program Files\DVD-RB PRO\Encoders\FFMpeg\ffmpeg.exe
ProCoder=C:\Program Files\DVD-RB PRO\Encoders\EclPro\EclPro.exe
DECOMB=C:\Program Files\AviSynth 2.5\plugins\Decomb521.dll
NICAUDIO=C:\Program Files\AviSynth 2.5\plugins\nicaudio.dll
MPEG2DEC=C:\Program Files\DVD-RB PRO\DGDecode.dll
Working=F:\
Output=F:\DVD1\
CCENew=C:\Program Files\Custom Technology\Cinema Craft Encoder SP\cctsp.exe
Source=F:\DVD\DVDRMKE\2\VIDEO_TS\
[Audio]
Selected=111
Remapping=
[Subpictures]
Selected=100111
[CCEOptions]
VBR_bias=25
Quality_prec=16
eclPasses=3
[Setup]
Languages=1111111111111111111111110111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111
sLanguages=1111111111111111111111110111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111


rebuilder log with CCEAQM=1


[12:32:51] Phase I, PREPARATION started.
- DVD-RB v1.25.0
- AVISYNTH 2.5.6.0
- CCE 2.70.2.12 encoder selected.
- "Adaptive Quantizer Matrices" is enabled.
- Source: 2
- VTS_01: 2,545,892 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 122,520 frames.
-- Building .AVS and .ECL files
- Reduction Level for DVD-5: 79.5%
- Overall Bitrate : 6,014Kbs
- Space for Video : 3,597,812KB
- HIGH/LOW/TYPICAL Bitrates: 6,378/5,168/6,014 Kbs
[12:35:10] Phase I, PREPARATION completed in 3 minutes.
[12:35:10] 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
[13:30:21] Phase II ENCODING completed in 55 minutes.
[13:30:21] Phase III, REBUILD started.
- Copying IFO, BUP, and unaltered files...
- Processing VTS_01
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Rebuilding seg 1 VOBID 1 CELLID 2
- Rebuilding seg 2 VOBID 1 CELLID 3
- Rebuilding seg 3 VOBID 1 CELLID 4
- Rebuilding seg 4 VOBID 1 CELLID 5
- Rebuilding seg 5 VOBID 1 CELLID 6
- Rebuilding seg 6 VOBID 1 CELLID 7
- Rebuilding seg 7 VOBID 1 CELLID 8
- Rebuilding seg 8 VOBID 1 CELLID 9
- Rebuilding seg 9 VOBID 1 CELLID 10
- Rebuilding seg 10 VOBID 1 CELLID 11
- Rebuilding seg 11 VOBID 1 CELLID 12
- Rebuilding seg 12 VOBID 1 CELLID 13
- Rebuilding seg 13 VOBID 1 CELLID 14
- Rebuilding seg 14 VOBID 1 CELLID 15
- Rebuilding seg 15 VOBID 1 CELLID 16
- Rebuilding seg 16 VOBID 1 CELLID 17
- Rebuilding seg 17 VOBID 1 CELLID 18
- Rebuilding seg 18 VOBID 1 CELLID 19
- Rebuilding seg 19 VOBID 1 CELLID 20
- Rebuilding seg 20 VOBID 1 CELLID 21
- Rebuilding seg 21 VOBID 1 CELLID 22
- Rebuilding seg 22 VOBID 1 CELLID 23
- Rebuilding seg 23 VOBID 1 CELLID 24
- Rebuilding seg 24 VOBID 1 CELLID 25
- Rebuilding seg 25 VOBID 1 CELLID 26
- Rebuilding seg 26 VOBID 1 CELLID 27
- Rebuilding seg 27 VOBID 1 CELLID 28
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_01_0.IFO
- Updating TMAP table...
- Correcting VTS Sectors...
[13:41:07] Phase III, REBUILD completed in 11 minutes.

Done.
[13:41:07] PREPARE/ENCODE/REBUILD completed in 69 min.


standard rebuilder log


[16:01:03] Phase I, PREPARATION started.
- DVD-RB v1.25.0
- AVISYNTH 2.5.6.0
- CCE 2.70.2.12 encoder selected.
- Source: 3
- VTS_01: 2,545,892 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 122,520 frames.
-- Building .AVS and .ECL files
- Reduction Level for DVD-5: 79.5%
- Overall Bitrate : 6,014Kbs
- Space for Video : 3,597,812KB
- HIGH/LOW/TYPICAL Bitrates: 6,378/5,168/6,014 Kbs
[16:03:23] Phase I, PREPARATION completed in 2 minutes.
[16:03:23] 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
[16:57:15] Phase II ENCODING completed in 54 minutes.
[16:57:15] Phase III, REBUILD started.
- Copying IFO, BUP, and unaltered files...
- Processing VTS_01
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Rebuilding seg 1 VOBID 1 CELLID 2
- Rebuilding seg 2 VOBID 1 CELLID 3
- Rebuilding seg 3 VOBID 1 CELLID 4
- Rebuilding seg 4 VOBID 1 CELLID 5
- Rebuilding seg 5 VOBID 1 CELLID 6
- Rebuilding seg 6 VOBID 1 CELLID 7
- Rebuilding seg 7 VOBID 1 CELLID 8
- Rebuilding seg 8 VOBID 1 CELLID 9
- Rebuilding seg 9 VOBID 1 CELLID 10
- Rebuilding seg 10 VOBID 1 CELLID 11
- Rebuilding seg 11 VOBID 1 CELLID 12
- Rebuilding seg 12 VOBID 1 CELLID 13
- Rebuilding seg 13 VOBID 1 CELLID 14
- Rebuilding seg 14 VOBID 1 CELLID 15
- Rebuilding seg 15 VOBID 1 CELLID 16
- Rebuilding seg 16 VOBID 1 CELLID 17
- Rebuilding seg 17 VOBID 1 CELLID 18
- Rebuilding seg 18 VOBID 1 CELLID 19
- Rebuilding seg 19 VOBID 1 CELLID 20
- Rebuilding seg 20 VOBID 1 CELLID 21
- Rebuilding seg 21 VOBID 1 CELLID 22
- Rebuilding seg 22 VOBID 1 CELLID 23
- Rebuilding seg 23 VOBID 1 CELLID 24
- Rebuilding seg 24 VOBID 1 CELLID 25
- Rebuilding seg 25 VOBID 1 CELLID 26
- Rebuilding seg 26 VOBID 1 CELLID 27
- Rebuilding seg 27 VOBID 1 CELLID 28
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_01_0.IFO
- Updating TMAP table...
- Correcting VTS Sectors...
[17:07:26] Phase III, REBUILD completed in 10 minutes.

Done.
[17:07:26] PREPARE/ENCODE/REBUILD completed in 66 min.


BTW I am using CCE SP with 3 passes
Boulder
28th May 2007, 05:58
Try setting a higher bitrate matrix to begin with.
therat
28th May 2007, 06:15
Try setting a higher bitrate matrix to begin with.

I have it set to decoder default. Any suggestions of a better matrix please?

cheers
Sharc
28th May 2007, 07:49
I have redone it 4 times now. the first 3 times it always came out at 4,551,861 bytes. I then tried it with CCEAQM=1 and got 4581120000 which is still well under the usual size.


Sorry, but I am confused by your numbers and units:
...the first 3 times it always came out at 4,551,861 bytes ...
I think you mean kilobytes rather than bytes.
4,551,861 kB = 4.34 GB

...I then tried it with CCEAQM=1 and got 4581120000 which is still well under the usual size....
Are these really 4'581'120'000 bytes, or do you mean 4'581'120 kB?
4'581'120'000 bytes = 4.27 GB
4'581'120 kB = 4.37 GB
therat
28th May 2007, 08:55
Sorry, but I am confused by your numbers and units:
...the first 3 times it always came out at 4,551,861 bytes ...
I think you mean kilobytes rather than bytes.
4,551,861 kB = 4.34 GB

...I then tried it with CCEAQM=1 and got 4581120000 which is still well under the usual size....
Are these really 4'581'120'000 bytes, or do you mean 4'581'120 kB?
4'581'120'000 bytes = 4.27 GB
4'581'120 kB = 4.37 GB

oops left off the 000. should have been 4,551,861,000 bytes which is 4.23 GB. and yes it was 4,581,120,000 bytes. Both methods were undersize.

This is the only DVD I have ever had trouble with undersizing.

Maybe Boulder is correct and I need a better matrix. Can anyone suggest a good high bitrate matrix to test please?
Sharc
28th May 2007, 09:01
Try this one, for example:

8 8 9 11 13 13 14 17
8 8 11 12 13 14 17 18
9 11 13 13 14 17 17 19
11 11 13 13 13 17 18 20
11 13 13 13 16 17 20 24
13 13 13 16 17 20 24 29
13 14 15 17 19 23 28 34
13 15 17 19 23 28 34 41
8 8 8 9 9 9 9 10
8 8 9 9 9 9 10 10
8 9 9 9 9 10 10 10
9 9 9 9 10 10 10 10
9 9 9 10 10 10 10 11
9 9 10 10 10 10 11 11
9 10 10 10 10 11 11 11
10 10 10 10 11 11 11 12
therat
28th May 2007, 09:07
thanks. will try it now.
therat
28th May 2007, 10:25
unfortunately no better. This time 4,574,464,000 bytes = 4.26 GB
Sharc
28th May 2007, 10:51
Your bitrates (from the log) are quite high. May be the encoder is just saturated, irrespective of the matrix.
Is the original picture soft rather than sharp? Are there not many demanding scenes (action, lot of details). Are there a lot of dark scenes? I don't know the movie.

You may want to try an ever sharper matrix and see if it makes any difference, and still set CCEAQM=1:
8 8 9 9 10 10 11 11
8 9 9 10 10 11 11 12
9 9 10 10 11 11 12 12
9 10 10 11 11 12 13 13
10 10 11 11 12 13 13 14
10 11 11 12 13 13 14 15
11 11 12 13 13 14 15 15
11 12 13 13 14 15 15 16
8 8 9 9 10 10 11 11
8 9 9 10 10 11 11 12
9 9 10 10 11 11 12 12
9 10 10 11 11 12 13 13
10 10 11 11 12 13 13 14
10 11 11 12 13 13 14 15
11 11 12 13 13 14 15 15
11 12 13 13 14 15 15 16

Anyway, if encoder saturation is the reason for the undersizing, one should not care too much about filling the disc to the last byte, as there is little to improve.
Boulder
28th May 2007, 11:01
If you have a rather soft image and want to do some sharpening (you seem to have plenty of bits to spare), using SeeSaw might be a good idea. It'll slow down the encoding though.
Craz
28th May 2007, 11:07
Tried it with the CCEAQM=1 setting, but it's still undersized. This time I got 4.27GB in stead of 4.23GB.

@jdobbs: I'm doing the disc in full backup mode (movie, menus, extras).
How can I try that matrix (where do I use that), or won't that help me ?

My files from the last run (giving the 4.27GB result):

rebuilder.ini


[Options]
CCEAQM=1
Mode=1
OneClick=1
ReduceOpt=2
NoWarn=1
AdditionalOutput=1
LogFile=1
QuEncHQ=1
EncoderMinimized=1
RemoveDTS=0
HC_Quality=1
HC_Matrix=1
SkinVersion=12
AudioDub=1
QuEncodeType=0
iDCT=0
GOP=0
DCPrec=0
MainMatrix=Encoder Default
LowMatrix=Same as Main Feature
VLowMatrix=Same as Main Feature
ExtraMatrix=Same as Main Feature
ProCoder_Quality=4
DVD_Label=DEPARTED
DVD_Name=DEPARTED.ISO
MovieOnly=0
HalfD1=00000
Convert_16_9=00000
DisableInterlace=00000
ConvertToYUY2=1
CCE=3
Skin=Rockas Original
Completed=2
[Paths]
QuEnc=C:\Program Files\DVD-RB PRO\Encoders\QuEnc\QuEnc.exe
ReJig=C:\Program Files\DVD-RB PRO\Encoders\ReJig\ReJig.exe
HC=C:\Program Files\DVD-RB PRO\Encoders\HC Encoder\HCbatch.EXE
FFMPEG=C:\Program Files\DVD-RB PRO\Encoders\FFMpeg\ffmpeg.exe
ProCoder=C:\Program Files\DVD-RB PRO\Encoders\EclPro\EclPro.exe
DECOMB=C:\Program Files\AviSynth 2.5\plugins\Decomb521.dll
NICAUDIO=C:\Program Files\AviSynth 2.5\plugins\nicaudio.dll
MPEG2DEC=C:\Program Files\DVD-RB PRO\DGDecode.dll
Working=C:\DVDPROJECTS\WORK\
Output=C:\DVDPROJECTS\WORK\
CCENew=C:\Program Files\Custom Technology\CCE SP\cctspt.exe
Source=C:\DVDPROJECTS\ROT\DEPARTED\VIDEO_TS\
[Audio]
Selected=110111
Remapping=
[Subpictures]
Selected=111111111111111111111
[CCEOptions]
VBR_bias=25
Quality_prec=16
eclPasses=6


rebuilder.log

[14:01:23] One Click encoding activated...
-----------------
[14:01:24] Phase I, PREPARATION started.
- DVD-RB v1.25.0
- AVISYNTH 2.5.6.0
- CCE 2.70.1.5 encoder selected.
- "Adaptive Quantizer Matrices" is enabled.
- "Steal Space from Extras" mode (25%) is enabled.
- Source: DEPARTED
- VTS_01: 61.807 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 5.311 frames.
-- Building .AVS and .ECL files
- VTS_02: 3.676.499 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 221.445 frames.
-- Building .AVS and .ECL files
- VTS_03: 112.070 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 10.801 frames.
-- Building .AVS and .ECL files
- VTS_04: 69.059 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 5.872 frames.
-- Building .AVS and .ECL files
- Reduction Level for DVD-5: 57,1%
- Overall Bitrate : 3.315Kbs
- Space for Video : 3.940.810KB
- Movie improvement from extra reduction = 1,8%
- HIGH/LOW/TYPICAL Bitrates: 3.943/1.264/3.315 Kbs
[14:05:10] Phase I, PREPARATION completed in 4 minutes.
[14:05:10] Phase II ENCODING started
- Creating M2V for VTS_01 segment 0
- Creating M2V for VTS_01 segment 1
- 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
- Creating M2V for VTS_02 segment 5
- Creating M2V for VTS_02 segment 6
- Creating M2V for VTS_02 segment 7
- Creating M2V for VTS_02 segment 8
- Creating M2V for VTS_02 segment 9
- Creating M2V for VTS_02 segment 10
- Creating M2V for VTS_02 segment 11
- Creating M2V for VTS_02 segment 12
- Creating M2V for VTS_02 segment 13
- Creating M2V for VTS_02 segment 14
- Creating M2V for VTS_02 segment 15
- Creating M2V for VTS_02 segment 16
- Creating M2V for VTS_02 segment 17
- Creating M2V for VTS_02 segment 18
- Creating M2V for VTS_02 segment 19
- Creating M2V for VTS_02 segment 20
- Creating M2V for VTS_02 segment 21
- Creating M2V for VTS_02 segment 22
- Creating M2V for VTS_02 segment 23
- Creating M2V for VTS_02 segment 24
- Creating M2V for VTS_02 segment 25
- Creating M2V for VTS_02 segment 26
- Creating M2V for VTS_02 segment 27
- Creating M2V for VTS_02 segment 28
- Creating M2V for VTS_02 segment 29
- Creating M2V for VTS_02 segment 30
- Creating M2V for VTS_02 segment 31
- Creating M2V for VTS_02 segment 32
- Creating M2V for VTS_02 segment 33
- Creating M2V for VTS_02 segment 34
- Creating M2V for VTS_02 segment 35
- Creating M2V for VTS_02 segment 36
- Creating M2V for VTS_02 segment 37
- Creating M2V for VTS_02 segment 38
- Creating M2V for VTS_02 segment 39
- Creating M2V for VTS_03 segment 0
- Creating M2V for VTS_03 segment 1
- Creating M2V for VTS_03 segment 2
- Creating M2V for VTS_03 segment 3
- Creating M2V for VTS_03 segment 4
- Creating M2V for VTS_03 segment 5
- Creating M2V for VTS_03 segment 6
- Creating M2V for VTS_03 segment 7
- Creating M2V for VTS_03 segment 8
- Creating M2V for VTS_04 segment 0
- Creating M2V for VTS_04 segment 1
[21:00:52] Phase II ENCODING completed in 415 minutes.
[21:00:53] Phase III, REBUILD started.
- Copying IFO, BUP, and unaltered files...
- Processing VTS_01
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Updating NAVPACKS for VOBID_01
- Rebuilding seg 1 VOBID 2 CELLID 1
- Updating NAVPACKS for VOBID_02
- 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 seg 0 VOBID 1 CELLID 1
- Updating NAVPACKS for VOBID_01
- Rebuilding seg 1 VOBID 2 CELLID 1
- Updating NAVPACKS for VOBID_02
- Rebuilding seg 2 VOBID 3 CELLID 1
- Rebuilding seg 3 VOBID 3 CELLID 2
- Rebuilding seg 4 VOBID 3 CELLID 3
- Rebuilding seg 5 VOBID 3 CELLID 4
- Rebuilding seg 6 VOBID 3 CELLID 5
- Rebuilding seg 7 VOBID 3 CELLID 6
- Rebuilding seg 8 VOBID 3 CELLID 7
- Rebuilding seg 9 VOBID 3 CELLID 8
- Rebuilding seg 10 VOBID 3 CELLID 9
- Rebuilding seg 11 VOBID 3 CELLID 10
- Rebuilding seg 12 VOBID 3 CELLID 11
- Rebuilding seg 13 VOBID 3 CELLID 12
- Rebuilding seg 14 VOBID 3 CELLID 13
- Rebuilding seg 15 VOBID 3 CELLID 14
- Rebuilding seg 16 VOBID 3 CELLID 15
- Rebuilding seg 17 VOBID 3 CELLID 16
- Rebuilding seg 18 VOBID 3 CELLID 17
- Rebuilding seg 19 VOBID 3 CELLID 18
- Updating NAVPACKS for VOBID_03
- Rebuilding seg 20 VOBID 4 CELLID 1
- Rebuilding seg 21 VOBID 4 CELLID 2
- Rebuilding seg 22 VOBID 4 CELLID 3
- Rebuilding seg 23 VOBID 4 CELLID 4
- Rebuilding seg 24 VOBID 4 CELLID 5
- Rebuilding seg 25 VOBID 4 CELLID 6
- Rebuilding seg 26 VOBID 4 CELLID 7
- Rebuilding seg 27 VOBID 4 CELLID 8
- Rebuilding seg 28 VOBID 4 CELLID 9
- Rebuilding seg 29 VOBID 4 CELLID 10
- Rebuilding seg 30 VOBID 4 CELLID 11
- Rebuilding seg 31 VOBID 4 CELLID 12
- Rebuilding seg 32 VOBID 4 CELLID 13
- Rebuilding seg 33 VOBID 4 CELLID 14
- Rebuilding seg 34 VOBID 4 CELLID 15
- Rebuilding seg 35 VOBID 4 CELLID 16
- Rebuilding seg 36 VOBID 4 CELLID 17
- Rebuilding seg 37 VOBID 4 CELLID 18
- Rebuilding seg 38 VOBID 4 CELLID 19
- Updating NAVPACKS for VOBID_04
- Rebuilding seg 39 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...
- Processing VTS_03
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Updating NAVPACKS for VOBID_01
- Rebuilding seg 1 VOBID 2 CELLID 1
- Updating NAVPACKS for VOBID_02
- Rebuilding seg 2 VOBID 3 CELLID 1
- Updating NAVPACKS for VOBID_03
- Rebuilding seg 3 VOBID 4 CELLID 1
- Updating NAVPACKS for VOBID_04
- Rebuilding seg 4 VOBID 5 CELLID 1
- Updating NAVPACKS for VOBID_05
- Rebuilding seg 5 VOBID 6 CELLID 1
- Updating NAVPACKS for VOBID_06
- Rebuilding seg 6 VOBID 7 CELLID 1
- Updating NAVPACKS for VOBID_07
- Rebuilding seg 7 VOBID 8 CELLID 1
- Updating NAVPACKS for VOBID_08
- Rebuilding seg 8 VOBID 9 CELLID 1
- Updating NAVPACKS for VOBID_09
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_03_0.IFO
- Updating TMAP table...
- Processing VTS_04
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Updating NAVPACKS for VOBID_01
- Rebuilding seg 1 VOBID 2 CELLID 1
- Updating NAVPACKS for VOBID_02
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_04_0.IFO
- Updating TMAP table...
- Correcting VTS Sectors...
[21:12:20] Phase III, REBUILD completed in 12 minutes.

Done.
[21:12:20] PREPARE/ENCODE/REBUILD completed in 431 min.
Sharc
28th May 2007, 11:10
@therat:
As a test, you could run an OPV prepare and see what you get for the "Q" estimate. If the Q is very low (1 ... 4 for CCE) it would be a clear indication of encoder saturation.
Craz
28th May 2007, 11:23
I also tried OPV just now. This is what the log files says after analyzing (VTS_02 is the main movie):


[12:11:50] One Click encoding activated...
-----------------
[12:11:51] Phase I, PREPARATION started.
- DVD-RB v1.25.0
- AVISYNTH 2.5.6.0
- CCE 2.70.1.5 encoder selected.
- "Adaptive Quantizer Matrices" is enabled.
- "Steal Space from Extras" mode (25%) is enabled.
- "One Pass VBR (w/analysis)" mode is enabled.
- Source: DEPARTED
- VTS_01: 61.807 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 5.311 frames.
-- Building .AVS and .ECL files
- VTS_02: 3.676.499 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 221.445 frames.
-- Building .AVS and .ECL files
- VTS_03: 112.070 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 10.801 frames.
-- Building .AVS and .ECL files
- VTS_04: 69.059 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 5.872 frames.
-- Building .AVS and .ECL files
- Reduction Level for DVD-5: 57,1%
- Overall Bitrate : 3.315Kbs
- Space for Video : 3.940.810KB
- Analyzing VTS_01 for optimal Q factor.
-- TargetSize (sectors):25.610
-- Sampling 108 of 5311 frames.
-- Predicted size (sectors) at Q=53: 21.686
-- Predicted size (sectors) at Q=40: 25.052
-- Predicted size (sectors) at Q=38: 25.727
- Q Value selected: 38
- Analyzing VTS_02 for optimal Q factor.
-- TargetSize (sectors):1.899.919
-- Sampling 4440 of 221445 frames.
-- Predicted size (sectors) at Q=30: 1.383.379
-- Predicted size (sectors) at Q=18: 1.850.150
-- Predicted size (sectors) at Q=17: 1.902.059
- Q Value selected: 17
- Analyzing VTS_03 for optimal Q factor.
-- TargetSize (sectors):46.160
-- Sampling 217 of 10801 frames.
-- Predicted size (sectors) at Q=60: 87.698
-- Predicted size (sectors) at Q=142: 56.504
-- Predicted size (sectors) at Q=217: 46.361
- Q Value selected: 217
- Analyzing VTS_04 for optimal Q factor.
-- TargetSize (sectors):28.273
-- Sampling 120 of 5872 frames.
-- Predicted size (sectors) at Q=53: 23.896
-- Predicted size (sectors) at Q=40: 27.597
-- Predicted size (sectors) at Q=38: 28.331
- Q Value selected: 38
- Movie improvement from extra reduction = 1,8%
- HIGH/LOW/TYPICAL Bitrates: 3.943/1.264/3.315 Kbs
[12:21:56] Phase I, PREPARATION completed in 10 minutes.
[12:21:56] Phase II ENCODING started
- Creating M2V for VTS_01 segment 0
- Creating M2V for VTS_01 segment 1
Sharc
28th May 2007, 11:38
@therat:
I just noticed that your movie is 80 minutes only. It will be difficult to fill a DVD-5 without driving the encoder into saturation.

@craz
I did that disc in OPV. Q=17 for CCE default matrix and Q=8 for Avamat6 aka Auto-Q1. Even OPV hit the target size reasonably well. The bitrate redistribution by OPV was significant, btw.
I did not do it in VBR multipass, though.
therat
28th May 2007, 11:39
In my case it's definately saturation. I just realised the movie is only 75 minutes long and I only backup the main menu and movie. Most 90 -100 minute movies fit untouched on a dvd5 but strangely this one doesn't.

Thanks anyway guys.

cheers

@sharc
only just noticed your reply. You're right, definately saturation.
Craz
28th May 2007, 11:41
@craz
I did that disc in OPV. Q=17 for CCE default matrix and Q=8 for Avamat6 aka Auto-Q1. Even OPV hit the target size reasonably well. The bitrate redistribution by OPV was significant, btw.
I did not do it in VBR multipass, though.

So we share the same Q value in OPV mode then.
Would another matrix make a difference in VBR multipass? If so which one would you suggest?
I have never changed the matrix, so I don't have any experience with that.
therat
28th May 2007, 11:51
@therat:
As a test, you could run an OPV prepare and see what you get for the "Q" estimate. If the Q is very low (1 ... 4 for CCE) it would be a clear indication of encoder saturation.

well that test was bizarre. Came up with Q = 61


[20:41:39] Phase I, PREPARATION started.
- DVD-RB v1.25.0
- AVISYNTH 2.5.6.0
- CCE 2.70.2.12 encoder selected.
- "Adaptive Quantizer Matrices" is enabled.
- "One Pass VBR (w/analysis)" mode is enabled.
- Source: 2
- VTS_01: 2,545,892 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 122,520 frames.
-- Building .AVS and .ECL files
- Reduction Level for DVD-5: 79.5%
- Overall Bitrate : 6,014Kbs
- Space for Video : 3,597,812KB
- Analyzing VTS_01 for optimal Q factor.
-- TargetSize (sectors):1,825,890
-- Sampling 2460 of 122520 frames.
-- Predicted size (sectors) at Q=17: 2,286,079
-- Predicted size (sectors) at Q=22: 2,265,332
-- Predicted size (sectors) at Q=29: 2,222,285
-- Predicted size (sectors) at Q=37: 2,142,407
-- Predicted size (sectors) at Q=46: 2,031,939
-- Predicted size (sectors) at Q=53: 1,937,318
-- Predicted size (sectors) at Q=57: 1,880,316
-- Predicted size (sectors) at Q=59: 1,852,312
-- Predicted size (sectors) at Q=60: 1,838,288
- Q Value selected: 61
- HIGH/LOW/TYPICAL Bitrates: 6,378/5,168/6,014 Kbs
[20:48:47] Phase I, PREPARATION completed in 7 minutes.


I expected 1 or 2 but 61???
Sharc
28th May 2007, 11:58
@craz:
I don't think that changing the matrix will help in your case, as you are far away from saturation with your bitrates and with the Q=17 for the default matrix.
I wouldn't go for 6-pass VBR. It is a waste of time only without any measurable benefit. 3 passes are fine (optimum) for multipass VBR with CCEAQM=1. With CCEAQM=0, 2 passes will normally be sufficient.
Sharc
28th May 2007, 12:22
well that test was bizarre. Came up with Q = 61

I expected 1 or 2 but 61???

I wouldn't have expected 61 either. It contradicts the saturation, in a way. What is the (technical) quality of the original? Noisy, blocky? Is it VBR or CBR?
therat
28th May 2007, 12:57
I wouldn't have expected 61 either. It contradicts the saturation, in a way. What is the (technical) quality of the original? Noisy, blocky? Is it VBR or CBR?

Original doesn't appear blocky or noisy at all. Not sure how to tell if it's VBR or CBR.

I got this from GSpot

DVD "VOB" format
MPEG-2 Program Stream << { 1 vid, 3 aud, 3 other }
"Sys Bitrate: 10080 kb/s VBR

No idea if it's right tho
Craz
28th May 2007, 13:10
@craz:
I don't think that changing the matrix will help in your case, as you are far away from saturation with your bitrates and with the Q=17 for the default matrix.
I wouldn't go for 6-pass VBR. It is a waste of time only without any measurable benefit. 3 passes are fine (optimum) for multipass VBR with CCEAQM=1. With CCEAQM=0, 2 passes will normally be sufficient.

I just finished OPV mode and the resulting VIDEO_TS folder is only 4.25GB. So the problem exists also in OPV mode.

dvdrbuilder.log when running OPV mode:


[12:11:50] One Click encoding activated...
-----------------
[12:11:51] Phase I, PREPARATION started.
- DVD-RB v1.25.0
- AVISYNTH 2.5.6.0
- CCE 2.70.1.5 encoder selected.
- "Adaptive Quantizer Matrices" is enabled.
- "Steal Space from Extras" mode (25%) is enabled.
- "One Pass VBR (w/analysis)" mode is enabled.
- Source: DEPARTED
- VTS_01: 61.807 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 5.311 frames.
-- Building .AVS and .ECL files
- VTS_02: 3.676.499 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 221.445 frames.
-- Building .AVS and .ECL files
- VTS_03: 112.070 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 10.801 frames.
-- Building .AVS and .ECL files
- VTS_04: 69.059 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 5.872 frames.
-- Building .AVS and .ECL files
- Reduction Level for DVD-5: 57,1%
- Overall Bitrate : 3.315Kbs
- Space for Video : 3.940.810KB
- Analyzing VTS_01 for optimal Q factor.
-- TargetSize (sectors):25.610
-- Sampling 108 of 5311 frames.
-- Predicted size (sectors) at Q=53: 21.686
-- Predicted size (sectors) at Q=40: 25.052
-- Predicted size (sectors) at Q=38: 25.727
- Q Value selected: 38
- Analyzing VTS_02 for optimal Q factor.
-- TargetSize (sectors):1.899.919
-- Sampling 4440 of 221445 frames.
-- Predicted size (sectors) at Q=30: 1.383.379
-- Predicted size (sectors) at Q=18: 1.850.150
-- Predicted size (sectors) at Q=17: 1.902.059
- Q Value selected: 17
- Analyzing VTS_03 for optimal Q factor.
-- TargetSize (sectors):46.160
-- Sampling 217 of 10801 frames.
-- Predicted size (sectors) at Q=60: 87.698
-- Predicted size (sectors) at Q=142: 56.504
-- Predicted size (sectors) at Q=217: 46.361
- Q Value selected: 217
- Analyzing VTS_04 for optimal Q factor.
-- TargetSize (sectors):28.273
-- Sampling 120 of 5872 frames.
-- Predicted size (sectors) at Q=53: 23.896
-- Predicted size (sectors) at Q=40: 27.597
-- Predicted size (sectors) at Q=38: 28.331
- Q Value selected: 38
- Movie improvement from extra reduction = 1,8%
- HIGH/LOW/TYPICAL Bitrates: 3.943/1.264/3.315 Kbs
[12:21:56] Phase I, PREPARATION completed in 10 minutes.
[12:21:56] Phase II ENCODING started
- Creating M2V for VTS_01 segment 0
- Creating M2V for VTS_01 segment 1
- 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
- Creating M2V for VTS_02 segment 5
- Creating M2V for VTS_02 segment 6
- Creating M2V for VTS_02 segment 7
- Creating M2V for VTS_02 segment 8
- Creating M2V for VTS_02 segment 9
- Creating M2V for VTS_02 segment 10
- Creating M2V for VTS_02 segment 11
- Creating M2V for VTS_02 segment 12
- Creating M2V for VTS_02 segment 13
- Creating M2V for VTS_02 segment 14
- Creating M2V for VTS_02 segment 15
- Creating M2V for VTS_02 segment 16
- Creating M2V for VTS_02 segment 17
- Creating M2V for VTS_02 segment 18
- Creating M2V for VTS_02 segment 19
- Creating M2V for VTS_02 segment 20
- Creating M2V for VTS_02 segment 21
- Creating M2V for VTS_02 segment 22
- Creating M2V for VTS_02 segment 23
- Creating M2V for VTS_02 segment 24
- Creating M2V for VTS_02 segment 25
- Creating M2V for VTS_02 segment 26
- Creating M2V for VTS_02 segment 27
- Creating M2V for VTS_02 segment 28
- Creating M2V for VTS_02 segment 29
- Creating M2V for VTS_02 segment 30
- Creating M2V for VTS_02 segment 31
- Creating M2V for VTS_02 segment 32
- Creating M2V for VTS_02 segment 33
- Creating M2V for VTS_02 segment 34
- Creating M2V for VTS_02 segment 35
- Creating M2V for VTS_02 segment 36
- Creating M2V for VTS_02 segment 37
- Creating M2V for VTS_02 segment 38
- Creating M2V for VTS_02 segment 39
- Creating M2V for VTS_03 segment 0
- Creating M2V for VTS_03 segment 1
- Creating M2V for VTS_03 segment 2
- Creating M2V for VTS_03 segment 3
- Creating M2V for VTS_03 segment 4
- Creating M2V for VTS_03 segment 5
- Creating M2V for VTS_03 segment 6
- Creating M2V for VTS_03 segment 7
- Creating M2V for VTS_03 segment 8
- Creating M2V for VTS_04 segment 0
- Creating M2V for VTS_04 segment 1
[13:42:30] Phase II ENCODING completed in 81 minutes.
[13:42:30] Phase III, REBUILD started.
- Copying IFO, BUP, and unaltered files...
- Processing VTS_01
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Updating NAVPACKS for VOBID_01
- Rebuilding seg 1 VOBID 2 CELLID 1
- Updating NAVPACKS for VOBID_02
- 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 seg 0 VOBID 1 CELLID 1
- Updating NAVPACKS for VOBID_01
- Rebuilding seg 1 VOBID 2 CELLID 1
- Updating NAVPACKS for VOBID_02
- Rebuilding seg 2 VOBID 3 CELLID 1
- Rebuilding seg 3 VOBID 3 CELLID 2
- Rebuilding seg 4 VOBID 3 CELLID 3
- Rebuilding seg 5 VOBID 3 CELLID 4
- Rebuilding seg 6 VOBID 3 CELLID 5
- Rebuilding seg 7 VOBID 3 CELLID 6
- Rebuilding seg 8 VOBID 3 CELLID 7
- Rebuilding seg 9 VOBID 3 CELLID 8
- Rebuilding seg 10 VOBID 3 CELLID 9
- Rebuilding seg 11 VOBID 3 CELLID 10
- Rebuilding seg 12 VOBID 3 CELLID 11
- Rebuilding seg 13 VOBID 3 CELLID 12
- Rebuilding seg 14 VOBID 3 CELLID 13
- Rebuilding seg 15 VOBID 3 CELLID 14
- Rebuilding seg 16 VOBID 3 CELLID 15
- Rebuilding seg 17 VOBID 3 CELLID 16
- Rebuilding seg 18 VOBID 3 CELLID 17
- Rebuilding seg 19 VOBID 3 CELLID 18
- Updating NAVPACKS for VOBID_03
- Rebuilding seg 20 VOBID 4 CELLID 1
- Rebuilding seg 21 VOBID 4 CELLID 2
- Rebuilding seg 22 VOBID 4 CELLID 3
- Rebuilding seg 23 VOBID 4 CELLID 4
- Rebuilding seg 24 VOBID 4 CELLID 5
- Rebuilding seg 25 VOBID 4 CELLID 6
- Rebuilding seg 26 VOBID 4 CELLID 7
- Rebuilding seg 27 VOBID 4 CELLID 8
- Rebuilding seg 28 VOBID 4 CELLID 9
- Rebuilding seg 29 VOBID 4 CELLID 10
- Rebuilding seg 30 VOBID 4 CELLID 11
- Rebuilding seg 31 VOBID 4 CELLID 12
- Rebuilding seg 32 VOBID 4 CELLID 13
- Rebuilding seg 33 VOBID 4 CELLID 14
- Rebuilding seg 34 VOBID 4 CELLID 15
- Rebuilding seg 35 VOBID 4 CELLID 16
- Rebuilding seg 36 VOBID 4 CELLID 17
- Rebuilding seg 37 VOBID 4 CELLID 18
- Rebuilding seg 38 VOBID 4 CELLID 19
- Updating NAVPACKS for VOBID_04
- Rebuilding seg 39 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...
- Processing VTS_03
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Updating NAVPACKS for VOBID_01
- Rebuilding seg 1 VOBID 2 CELLID 1
- Updating NAVPACKS for VOBID_02
- Rebuilding seg 2 VOBID 3 CELLID 1
- Updating NAVPACKS for VOBID_03
- Rebuilding seg 3 VOBID 4 CELLID 1
- Updating NAVPACKS for VOBID_04
- Rebuilding seg 4 VOBID 5 CELLID 1
- Updating NAVPACKS for VOBID_05
- Rebuilding seg 5 VOBID 6 CELLID 1
- Updating NAVPACKS for VOBID_06
- Rebuilding seg 6 VOBID 7 CELLID 1
- Updating NAVPACKS for VOBID_07
- Rebuilding seg 7 VOBID 8 CELLID 1
- Updating NAVPACKS for VOBID_08
- Rebuilding seg 8 VOBID 9 CELLID 1
- Updating NAVPACKS for VOBID_09
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_03_0.IFO
- Updating TMAP table...
- Processing VTS_04
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Updating NAVPACKS for VOBID_01
- Rebuilding seg 1 VOBID 2 CELLID 1
- Updating NAVPACKS for VOBID_02
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_04_0.IFO
- Updating TMAP table...
- Correcting VTS Sectors...
[13:53:42] Phase III, REBUILD completed in 11 minutes.

Done.
[13:53:43] PREPARE/ENCODE/REBUILD completed in 102 min.
Sharc
28th May 2007, 13:43
@craz
After all, and in my understanding:
DVDRB defines a default target size of 2236400 sectors. From what I see from your logs you did not change this default target size.
One sector equals 2048 bytes, hence 2236400 sectors equal 4'580'147'200 bytes = 4.2656 GB.
The OPV resulted in 4.25 GB which is almost perfect. One can really not expect better accuracy from OPV.
Digga
28th May 2007, 13:55
as a sidenote, you maybe want to update your CCE SP to the newest version.
Sharc
28th May 2007, 14:33
.... and yes it was 4,581,120,000 bytes. Both methods were undersize.

This is the only DVD I have ever had trouble with undersizing.


@therat:
I think we were hunting a phantom. See post#42.
The DVDRB default target size is 2236400 sectors = 4'580'147'200 bytes. So when you got 4,581,120,000 bytes with CCEAQM=1 the size was just perfect! No undersizing or encoder saturation at all.
Sharc
28th May 2007, 15:57
... and finally, I think it is better to stick to sectors or bytes, and avoid the "gigabytes" discussion because of the ambiguous definitions:
ISO defines 1 gigabyte as 1'000'000'000 bytes, whereas in computer science it is 2^30 = 1,073,741,824 bytes. This causes a lot of confusion.

DVD-RB defines the default target size of a DVD-5 as 2'236'400 sectors = 4'580'147'200 bytes.
A standard DVD-R SL for example has a maximum capacity of 2'298'496 sectors or 4'707'319'808 bytes. Means that DVDRB leaves some reasonable margin for sizing errors by the encoding process and slight capacity differences between DVD-R and DVD+R.
Boulder
28th May 2007, 19:06
I use 2258000 and the size with a 2-pass encode is always 10-20MB below the limit for a DVD+R (unless there is saturation).
Craz
28th May 2007, 19:46
@craz
After all, and in my understanding:
DVDRB defines a default target size of 2236400 sectors. From what I see from your logs you did not change this default target size.
One sector equals 2048 bytes, hence 2236400 sectors equal 4'580'147'200 bytes = 4.2656 GB.
The OPV resulted in 4.25 GB which is almost perfect. One can really not expect better accuracy from OPV.

So the resulting size is considered normal in OPV mode, and would be adjusted towards 4.32GB (the usual size I get with DVDRB) when running in multipass vbr mode ?
Craz
28th May 2007, 19:50
I use 2258000 and the size with a 2-pass encode is always 10-20MB below the limit for a DVD+R (unless there is saturation).

If I would adjust the value in dvdrb for this dvd, would it increase my resulting size, or would it make no difference from the resulting size (4.27GB) I got now ?
Boulder
28th May 2007, 20:55
It should increase the size - but there is a risk of oversizing if you do OPV encodes.
Sharc
28th May 2007, 21:22
So the resulting size is considered normal in OPV mode, and would be adjusted towards 4.32GB (the usual size I get with DVDRB) when running in multipass vbr mode ?
Normally the size for multipass VBR will be very close to the specified target sectors. This number can be set in the rebuilder.ini. See the DVDRB help file. If you do not set anything in rebuilder.ini, the default value will be taken which is 2'236'400 sectors = 4'580'147'200 bytes, equivalent to 4.27 GB.
You can also tweak the target size with the DVDRB editor, if you prefer, to fill your disc more. However, I am sure you won't notice a quality improvement of the final encode just because you add another 50 MB or so. You may however run into an oversizing problem which is more troublesome to cure.

OPV always has the risk of size inaccuracy, that means typically some undersizing, but sometimes oversizing. There is no real remedy against the OPV size inaccuracy.