View Full Version : Oversizing, v1.12.1
Jeff Mott
9th November 2006, 02:42
I am encoding the film 'Take the Lead,' but the result is 4.39 GiB -- too big for a DVD-5 disc. I've attached the log and ini files because I really don't know what to look for. If anyone needs anything else to find the problem, let me know. Any insight is appreciated.
blutach
9th November 2006, 07:22
Can't see your INI file yet as jdobbs has not approved the attachments, but if you have a TargetSectors line in it, reduce it by 5000. Also, OPV has been known to oversize; perhaps a 2 pass would be in order?
Next time, you can attach text files using cut and paste, if you like. :)
Regards
Jeff Mott
9th November 2006, 07:35
[Options]
Mode=1
OneClick=1
ReduceOpt=0
NoWarn=1
AdditionalOutput=0
LogFile=1
QuEncHQ=1
EncoderMinimized=1
RemoveDTS=1
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=TAKE THE LEAD
DVD_Name=TAKE THE LEAD.ISO
MovieOnly=0
HalfD1=000000000
Convert_16_9=000000000
DisableInterlace=000000000
ConvertToYUY2=1
CCE=2
Skin=Teck Original
EncoderPriority=1
Encode_Menus=1
ImgBurnWrite=1
Completed=1
[Paths]
DECOMB=C:\Program Files\AviSynth 2.5\plugins\Decomb521.dll
MPEG2DEC=C:\Program Files\DVD-RB PRO\DGDecode.dll
Working=C:\Documents and Settings\Jeff Mott\Desktop\DVD-RB\
Output=C:\Documents and Settings\Jeff Mott\Desktop\DVD-RB\
CCEBasic=C:\Program Files\Custom Technology\Cinema Craft Encoder Basic\cct2.exe
Source=C:\DOCUMENTS AND SETTINGS\JEFF MOTT\DESKTOP\TAKE THE LEAD\
[Audio]
Selected=11111111111
Remapping=
[Subpictures]
Selected=11111111
Jeff Mott
9th November 2006, 07:42
Note: Minor editing to shorten text. Cuts from the log are shown by an ellipsis and used where there are many redundant lines.
- Detected ANGLE and/or INTERLEAVING on source.
[11:25:44] One Click encoding activated...
-----------------
[11:25:45] Phase I, PREPARATION started.
- DVD-RB v1.12.1
- AVISYNTH 2.5.6.0
- CCE 2.70.1.4 encoder selected.
- VTSM_01: 87,191 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 5,933 frames.
-- Building .AVS and .ECL files
- VTS_01: 2,587,407 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 168,421 frames.
-- Building .AVS and .ECL files
- VTS_02: 69,532 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 6,436 frames.
-- Building .AVS and .ECL files
- VTS_03: 45,263 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 4,176 frames.
-- Building .AVS and .ECL files
- VTS_04: 115,529 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 7,931 frames.
-- Building .AVS and .ECL files
- VTS_05: 146,855 sectors.
-- ANGLE and/or INTERLEAVING is present.
-- Scanning and writing .D2V & .AVS files
- Processed 286.8MB ILVU section...
-- Processed 11,730 frames.
-- Building .AVS and .ECL files
- VTS_06: 736,146 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 78,656 frames.
-- Building .AVS and .ECL files
- VTS_07: 51,120 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 4,506 frames.
-- Building .AVS and .ECL files
- VTS_08: 115,426 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 11,331 frames.
-- Building .AVS and .ECL files
- Reduction Level for DVD-5: 47.5%
- Overall Bitrate : 2,715/2,172Kbs
- Space for Video : 3,308,348KB
- HIGH/LOW/TYPICAL Bitrates: 8,168/400/2,172 Kbs
[11:32:41] Phase I, PREPARATION completed in 7 minutes.
[11:32:41] Phase II ENCODING started
- Creating M2V for VTSM_01 segment 0
- Creating M2V for VTSM_01 segment 1
- Creating M2V for VTSM_01 segment 2
- Creating M2V for VTSM_01 segment 3
- Creating M2V for VTSM_01 segment 4
- Creating M2V for VTSM_01 segment 5
- Creating M2V for VTSM_01 segment 6
- Creating M2V for VTSM_01 segment 7
- Creating M2V for VTSM_01 segment 8
- Creating M2V for VTSM_01 segment 9
- Creating M2V for VTSM_01 segment 10
- Creating M2V for VTSM_01 segment 11
- Creating M2V for VTSM_01 segment 12
- Creating M2V for VTSM_01 segment 13
- Extracting STILLS for VTSM_01 segment 14
- Extracting STILLS for VTSM_01 segment 15
- Extracting STILLS for VTSM_01 segment 16
- Extracting STILLS for VTSM_01 segment 17
- Extracting STILLS for VTSM_01 segment 18
- Extracting STILLS for VTSM_01 segment 19
- Extracting STILLS for VTSM_01 segment 20
- Extracting STILLS for VTSM_01 segment 21
- Extracting STILLS for VTSM_01 segment 22
- Extracting STILLS for VTSM_01 segment 23
- Extracting STILLS for VTSM_01 segment 24
- Extracting STILLS for VTSM_01 segment 25
- Extracting STILLS for VTSM_01 segment 26
- Extracting STILLS for VTSM_01 segment 27
- Extracting STILLS for VTSM_01 segment 28
- Extracting STILLS for VTSM_01 segment 29
- Extracting STILLS for VTSM_01 segment 30
- 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
- Extracting STILLS for VTS_01 segment 19
- Creating M2V for VTS_02 segment 0
- Creating M2V for VTS_02 segment 1
- Creating M2V for VTS_02 segment 2
- Extracting STILLS for VTS_02 segment 3
- Creating M2V for VTS_03 segment 0
- Creating M2V for VTS_03 segment 1
- Creating M2V for VTS_03 segment 2
- Extracting STILLS for VTS_03 segment 3
- Creating M2V for VTS_04 segment 0
- Creating M2V for VTS_04 segment 1
- Creating M2V for VTS_04 segment 2
- Creating M2V for VTS_04 segment 3
- Creating M2V for VTS_04 segment 4
- Creating M2V for VTS_04 segment 5
- Creating M2V for VTS_04 segment 6
- Extracting STILLS for VTS_04 segment 7
- Creating M2V for VTS_05 segment 0
- Creating M2V for VTS_05 segment 1
- Creating M2V for VTS_05 segment 2
- . . .
- Creating M2V for VTS_05 segment 219
- Creating M2V for VTS_05 segment 220
- Creating M2V for VTS_06 segment 0
- Creating M2V for VTS_06 segment 1
- Creating M2V for VTS_06 segment 2
- Extracting STILLS for VTS_06 segment 3
- Creating M2V for VTS_07 segment 0
- Extracting STILLS for VTS_07 segment 1
- Creating M2V for VTS_08 segment 0
- Creating M2V for VTS_08 segment 1
- Creating M2V for VTS_08 segment 2
- Extracting STILLS for VTS_08 segment 3
[15:27:36] Phase II ENCODING completed in 235 minutes.
[15:27:36] 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
- Updating NAVPACKS for VOBID_01
- Rebuilding seg 19 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
- Updating NAVPACKS for VOBID_03
- Rebuilding seg 3 VOBID 4 CELLID 1
- Updating NAVPACKS for VOBID_04
- 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
- 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
- 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
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_04_0.IFO
- Updating TMAP table...
- Processing VTS_05
- Reading/processing TMAP table...
- Processed 286.8MB ILVU section...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Rebuilding seg 1 VOBID 1 CELLID 2
- Rebuilding seg 2 VOBID 1 CELLID 3
- . . .
- Rebuilding seg 42 VOBID 1 CELLID 43
- Rebuilding seg 43 VOBID 1 CELLID 44
- Rebuilding seg 44 VOBID 2 CELLID 1
- Rebuilding seg 45 VOBID 2 CELLID 2
- Rebuilding seg 46 VOBID 2 CELLID 3
- . . .
- Rebuilding seg 86 VOBID 2 CELLID 43
- Rebuilding seg 87 VOBID 2 CELLID 44
- Rebuilding seg 88 VOBID 3 CELLID 1
- Rebuilding seg 89 VOBID 3 CELLID 2
- Rebuilding seg 90 VOBID 3 CELLID 3
- . . .
- Rebuilding seg 130 VOBID 3 CELLID 43
- Rebuilding seg 131 VOBID 3 CELLID 44
- Rebuilding seg 132 VOBID 4 CELLID 1
- Rebuilding seg 133 VOBID 4 CELLID 2
- Rebuilding seg 134 VOBID 4 CELLID 3
- . . .
- Rebuilding seg 174 VOBID 4 CELLID 43
- Rebuilding seg 175 VOBID 4 CELLID 44
- Rebuilding seg 176 VOBID 5 CELLID 1
- Rebuilding seg 177 VOBID 5 CELLID 2
- Rebuilding seg 178 VOBID 5 CELLID 3
- . . .
- Rebuilding seg 218 VOBID 5 CELLID 43
- Rebuilding seg 219 VOBID 5 CELLID 44
- Updating NAVPACKS for VOBID_01
- Updating NAVPACKS for VOBID_02
- Updating NAVPACKS for VOBID_03
- Updating NAVPACKS for VOBID_04
- Updating NAVPACKS for VOBID_05
- Rebuilding seg 220 VOBID 6 CELLID 1
- Updating NAVPACKS for VOBID_06
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_05_0.IFO
- Updating TMAP table...
- Processing VTS_06
- 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
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_06_0.IFO
- Updating TMAP table...
- Processing VTS_07
- 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_07_0.IFO
- Updating TMAP table...
- Processing VTS_08
- 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
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_08_0.IFO
- Updating TMAP table...
- Processing VTSM_01
- Rebuilding seg 0 VOBID 1 CELLID 1
- Rebuilding seg 1 VOBID 1 CELLID 2
- Updating NAVPACKS for VOBID_01
- Rebuilding seg 2 VOBID 2 CELLID 1
- Updating NAVPACKS for VOBID_02
- Rebuilding seg 3 VOBID 3 CELLID 1
- Updating NAVPACKS for VOBID_03
- Rebuilding seg 4 VOBID 4 CELLID 1
- Updating NAVPACKS for VOBID_04
- Rebuilding seg 5 VOBID 5 CELLID 1
- Rebuilding seg 6 VOBID 5 CELLID 2
- Updating NAVPACKS for VOBID_05
- Rebuilding seg 7 VOBID 6 CELLID 1
- Updating NAVPACKS for VOBID_06
- Rebuilding seg 8 VOBID 7 CELLID 1
- Updating NAVPACKS for VOBID_07
- Rebuilding seg 9 VOBID 8 CELLID 1
- Updating NAVPACKS for VOBID_08
- Rebuilding seg 10 VOBID 9 CELLID 1
- Updating NAVPACKS for VOBID_09
- Rebuilding seg 11 VOBID 10 CELLID 1
- Updating NAVPACKS for VOBID_10
- Rebuilding seg 12 VOBID 11 CELLID 1
- Updating NAVPACKS for VOBID_11
- Rebuilding seg 13 VOBID 12 CELLID 1
- Updating NAVPACKS for VOBID_12
- Rebuilding seg 14 VOBID 13 CELLID 1
- Updating NAVPACKS for VOBID_13
- Rebuilding seg 15 VOBID 14 CELLID 1
- Updating NAVPACKS for VOBID_14
- Rebuilding seg 16 VOBID 15 CELLID 1
- Updating NAVPACKS for VOBID_15
- Rebuilding seg 17 VOBID 16 CELLID 1
- Updating NAVPACKS for VOBID_16
- Rebuilding seg 18 VOBID 17 CELLID 1
- Updating NAVPACKS for VOBID_17
- Rebuilding seg 19 VOBID 18 CELLID 1
- Updating NAVPACKS for VOBID_18
- Rebuilding seg 20 VOBID 19 CELLID 1
- Updating NAVPACKS for VOBID_19
- Rebuilding seg 21 VOBID 20 CELLID 1
- Updating NAVPACKS for VOBID_20
- Rebuilding seg 22 VOBID 21 CELLID 1
- Updating NAVPACKS for VOBID_21
- Rebuilding seg 23 VOBID 22 CELLID 1
- Updating NAVPACKS for VOBID_22
- Rebuilding seg 24 VOBID 23 CELLID 1
- Updating NAVPACKS for VOBID_23
- Rebuilding seg 25 VOBID 24 CELLID 1
- Updating NAVPACKS for VOBID_24
- Rebuilding seg 26 VOBID 25 CELLID 1
- Updating NAVPACKS for VOBID_25
- Rebuilding seg 27 VOBID 26 CELLID 1
- Updating NAVPACKS for VOBID_26
- Rebuilding seg 28 VOBID 27 CELLID 1
- Updating NAVPACKS for VOBID_27
- Rebuilding seg 29 VOBID 28 CELLID 1
- Updating NAVPACKS for VOBID_28
- Rebuilding seg 30 VOBID 29 CELLID 1
- Updating NAVPACKS for VOBID_29
- Updated VTSM_C_ADT.
- Updated VTSM_VOBU_ADMAP.
- Updated IFO: VTS_01_0.IFO
- Correcting VTS Sectors...
- Writing to Disc...
- The disc was successfully written.
[20:29:26] Phase III, REBUILD completed in 302 minutes.
Done.
[20:29:26] PREPARE/ENCODE/REBUILD completed in 544 min.
blutach
9th November 2006, 09:40
It took 5 hours to do the rebuild????? Even with 220 segments in one of the VTSs, there's something wrong there.
Regards
Jeff Mott
9th November 2006, 10:39
That probably includes that time that it was waiting for me to say 'Ok' to the message that the data would not fit on the disc.
blutach
9th November 2006, 11:26
Long time making up your mind. :)
Regards
jdobbs
9th November 2006, 12:28
Is this the NTSC version? The reason I ask is that I've done that disc... I'll do it again just to be sure. What did you use to rip it?
Rippraff
9th November 2006, 14:03
Is this the NTSC version?
I guess yes, as you won't see this on PAL sources. ;)
- Overall Bitrate : 2,715/2,172Kbs
Cu Rippraff
Jeff Mott
9th November 2006, 14:12
NTSC version—yes. I don't recall which ripper I used, but I always try _DVD Decrypter_ first, and if that fails then I use _DVDFab Decrypter_.
laserfan
9th November 2006, 16:48
I too had an oversize with 1.12.1--I recall having used the Editor to blank some stuff, and then when I re-allocated the saved space to the Feature, I selected "4.34Gb" which according to the window was "Target within limits" (I use default targetsectors).
Just wondering Jeff did you use the editor like this?
Also to others: Is 4.34 SUPPOSED to be OK, or should I always target 4.32Gb instead? I was only over by 2Mb, but I had to run the thing thru Shrink before burning... Not a big deal but thought I'd throw this out here.
Rippraff
9th November 2006, 17:12
Just wondering Jeff did you use the editor like this?
No he didn't.
Also to others: Is 4.34 SUPPOSED to be OK, or should I always target 4.32Gb instead?
I guess there'll be different opinions. ;)
I'm working with higher values (4.37 GB) but I always use excellent media (Taiyo Yuden 8x) which give also good quality on the outer edge of the discs. I don't use OPV with these high target sectors and every now and then I got an oversized result, but in these rare cases I just reencode the credits.
But I haven't tried 1.12.1 so far.
Cu Rippraff
blutach
9th November 2006, 22:18
Depending on if the encoder is accurate, 4.34 should be fine.
Regards
Jeff Mott
10th November 2006, 16:06
I just had the exact same issue again; this time with the movie _Cars_.
jdobbs
10th November 2006, 17:26
Could you also check your output directory? It's possible you may have some additional subdirectories (junk) in your DVDFILES folder left by some other package (I've seen it happen). There should be nothing there except AUDIO_TS and VIDEO_TS. The AUDIO_TS directory should be empty and the VIDEO_TS folder should have nothing but IFO, BUP, and VOB files. If you find anything else -- delete it.
If that's not it, something is definitely wrong with your setup... I've done both of those DVDs (at least the NTSC version) and they came out correctly sized. I'd suggest you uninstall everything (including CCE and AVISYNTH). Then install CCE first, followed by DVD-RB installation (using the full installer). The DVD-RB Installer will install AVISYNTH for you.
Jeff Mott
10th November 2006, 20:32
I uninstalled RB and deleted the program files directory for it, then installed it again. _Cars_ compressed correctly after this. I'm trying _Take the Lead_ now. I'm expecting this to work now as well, though I'll still post back to let you know if it has. I don't know what went wrong with the first install of RB, but whatever it was appears to be fixed now.
Voodoochild
10th November 2006, 21:04
I used latest version last night. I always aim for 4.32G and got exactly that.
I always do 3 pass, CCEAQM = 1
Strange maybe u should try another movie, just to see if three really an over size issue or it's just this DVD...
jdobbs
10th November 2006, 22:55
@Jeff Mott
Well I definitely owe you an apology of some kind. I just redid "Take The Lead" -- and it came out to 4.39GB. Don't know what happened since the last time I did it. This only thing I can think that changed is that I used CCE Basic this time (to match your setup), and last time I used CCE SP. I doubt that's related, though.
That's the first oversize I've ever personally experienced.
I'll do some investigating and give you an update (probably tomorrow). I think I may do "Cars" again too, just to see.
jdobbs
10th November 2006, 23:41
Interesting. I think it actually is the fact that it is being encoded with CCE Basic. I looked at it and there are a huge number of segments -- and many of them (most?) are small (less than 60 frames). There are sometimes problems in CCE when you try to encode very short segments if there isn't plenty of bitrate -- so I've instituted a minimum bitrate for segments that have less than 60 frames (in CCE SP, however, it's handled a little differently). Normally it wouldn't make enough of a difference to worry about correcting for it -- but with the large number of short segments in that DVD it seems to be enough to push it over.
I'll keep checking to be sure, and if I find this is truly the cause, I'll go back through my code and add corrections in size for the actual bitrate used on short segments.
I'm glad this came up again. I did a search and someone reported something similar in this link (http://forum.doom9.org/showthread.php?t=115957&highlight=take+the+lead) and when I tested it (using CCE SP), it came out a little larger than usual (4.35GB) but still small enough for a DVD-5. In that report there were some other surrounding issues that made it difficult to narrow down.
Good catch.
Jeff Mott
11th November 2006, 17:37
_Take the Lead_ came out oversized again, so it was apparently a very strange fluke that _Cars_ worked on its second try.
Thanks, jdobbs. It's good to hear you're working on it. DVD-RB is mad sexy. Keep up the good work! :)
jdobbs
11th November 2006, 17:58
It's probably more likely that "Take The Lead" is the fluke. I don't know what they used to author that disc... but the VOBID/CELLID numbering in the ILVU section is a mess, and that's what's causing the tiny segments. VTS_05 is broken out into 220 distinct VOBID/CELLID combinations, and for no reason I can see.
techmule
14th November 2006, 05:41
Have you tried changing the encoders HC, CCE, procoder ???, it might be that a new version of encoder is causing this problem like HC 19.1 ??
Jeff Mott
7th December 2006, 20:15
Hi, jdobbs. I'm sure this isn't what you wanted to hear, but I'm still getting a slightly oversized backup on _Take the Lead_ with v1.20.4. The image size came out to 4,502 MB (roughly 4.4 GB). :(
It'd be nice if I could just switch to CCE-SP to solve this problem, but there's no way I can shell out $2,000 for it.
jdobbs
7th December 2006, 20:57
Hmmm... I'll look at it again.
Jeff Mott
8th December 2006, 02:07
Sorry. My mistake. I updated RB on my laptop, but not on my desktop, where my ripped files for _Take the Lead_ were. The new version worked perfectly. Thanks, jdobbs!
jdobbs
8th December 2006, 04:46
Good news. Thanks.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.