DVD Rebuilder 1.10.7 target output too big?

[umkay316]

I just recently upgraded and the output size of the files are over 4.39 gb(or the whole dvd size)? The last move I did was Take the Lead and that output size was a little over 4500mb and then I did it again and the ourput size was over 5000mb... Never had the problem in the past, why now? Thanks

I am using CCE 2.67 retail at steal 50% and half D1 size and half space for extras.

[Rippraff]

at steal 50% and half D1 size and half space for extras.
Don't use this combination (http://forum.doom9.org/showthread.php?t=113756). ;)

Cu Rippraff

[umkay316]

what should use to maximize the quality in the main video, but keeping everything else?

[Susana]

steal 50% and half d1 = 50%(50%)=25% very bad image quality, isn't it ?

[jdobbs]

Choose Half/Half or Reduce Extras 50% -- but I wouldn't recommend doing both at the same time. steal 50% and half d1 = 50%(50%)=25% very bad image quality, isn't it ?In fact it will be even worse than 25%. If the overall reduction rate is 50% to begin with, and you steal 50% followed by half/half (50%) you end up trying to reduce something to 12.5% of its original size. (.5 x .5 x .5). Using all in combination may be asking the encoder to do the impossible. It may also be brushing up against the minimum bitrate, which could explain the oversize.

@umkay316
Use the reduction options judiciously. Select one type of reduction rather than combinations.

[GZZ]

I have found what might be issue, when getting to large output. Its when you do a prepare on a DVD, then go to the Preview/edit and have clicked the Use beta (test) view/edit. If you then try to play around with some of the sliders, but then press exit and it ask you to abandon change and you say yes (no change should be applied) then for some reason my DVD came out at 5.5 GB eventhough it should have saved any changes. So after I had encoded and found out it was to large. I ran a new prepare and didn't go to the preview/edit, just saved project file started encoding and it came out perfectly in size.

I need to test it again, but maybe the change in the segment editor does apply eventhough you press cancel on exit.

GZZ

[umkay316]

I retried it again... and it was too big still... it came out to be 4.43 gb? Can you manually set it at a targte output size?

I also only did steal 50% this time...

[umkay316]

Can anyone help? The output size is still ocming out around 4.43gb?

[Rippraff]

Post your RB.ini and the log file.

Cu Rippraff

[danpos]

Can anyone help? The output size is still ocming out around 4.43gb?

Why don't you shrink it to right file size using DVDShrink? In this case, this solution is simple, fast and doesn't hurt. :D

Regards,

[jdobbs]

Using a TargetSectors value larger than default?

[umkay316]

why would the larger targetsector than default make my output smaller? How do you change the TargetSectors?

[jdobbs]

Can anyone help? The output size is still ocming out around 4.43gb?This isn't smaller.

[schumanist]

My first post here. Thanks for a wonderful product, jdobbs.

I wonder if Take the Lead isn't protected by the overhead of Lots of little segments in VTS05. I'll attach the entire status log but this exerpt illustrates what I'm talking about. I've tried with QENC, HC and AutoQMat (which crashes on this movie only).
All should be the latest. Ripped with DVDFab. R1

[08:58:10] One Click encoding activated...
-----------------
[08:58:11] Phase I, PREPARATION started.
- DVD-RB v1.10.8
- QuEnc 0.7.1.0 encoder selected.
- VTS_01: 2,587,407 sectors.
.
.
.

- Creating M2V for VTS_05 segment 216
- Creating M2V for VTS_05 segment 217
- Creating M2V for VTS_05 segment 218
- 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:19:13] Phase II ENCODING completed in 373 minutes.

All other settings were Default. I tried various "Steal" and "Half D1" options only after it failed with all 3 encoders. The recovered size was always returned (as it was supposed to) to make a too big image. Even tried to convert some segments to slideshows but I still need to learn more about the editor.

[jdobbs]

Welcome to the forum, schumanist!

Wow. I looked at your log and I've never seen or even heard of a REBUILD that took that long. I always expect 20 mins for REBUILD. Was your disc close to capacity? A disc with that many segments isn't typical -- but I've done them before without any issues.

Is this the NTSC version? If so I'll pick it up today and test it.

[jdobbs]

Wow. VTS_05 on that disc is a real mess. It uses ILVU for angles -- and from the appearances it seems that every ILVU unit has been designated with a unique VOBID/CELLID. I can't imagine what authoring software would make a mess like that...

I'm running the backup now for testing. It should work fine -- but I can see how it might slow things down.

On that disc you might be better to add the line:

ILVU_ENCODE=0

to the "[Options]" area of REBUILDER.INI before encoding. That will force Rebuilder to keep the ILVU sections intact (similar to the way the freeware version does it).

Don't forget to remove that line after the encode, though. It could hurt the quality of other ILVU discs.

I'll look at the code and see if there is any way to recognize this scenario and adjust for it.

[jdobbs]

Well -- my job completed and the size was 4.35GB -- larger than typical but well within the limits. My REBUILD took 25 minutes total, so I don't think the large number of cells or goofy format of the disc has a lot of impact. I'd say the only difference in our methods was that I used AnyDVD to rip -- but I don't think that's significant. Just to be sure, I'll rip it with DVD Fab and run it again.

I have to guess that your disc may have been getting close to capacity (causing excessive overhead during writes) at the time of your REBUILD, or some other activity (Virus Scan maybe?) was taking processor time. That's the only explanation I can think of why yours would take that much longer than mine.

Could you post your REBUILDER.INI file?

[schumanist]

< Wow. I looked at your log and I've never seen or even heard of a < REBUILD that took that long.

Could it have included the time it took for me to acknowledge the ImgBurn oversize warning? That was probably several hours before I got to it. Source and target was on G: with enough room (45GB), 2.5GHz P4, 1GB DDR, running cool, no virus scan or any other task running then, and no Internet. D2VAVS directory on different drive (C:) with 99GB free and a recent defrag. G: might need a defrag.

I don't think that rebuild time was typical. If it is, then I'll post back. Ripped another since I sent you the Log so I'm not sure how useful the ini file is but here it is anyway. Thank you for all your hard work. Finding a new revision of RB-Pro in my inbox starts my whole day better.

[jdobbs]

Could it have included the time it took for me to acknowledge the ImgBurn oversize warning? That was probably several hours before I got to it.Yes that's it.

According to your INI file you aren't using CCE -- you are using AutoQmatEnc. Have you changed it since the report?

[schumanist]

According to your INI file you aren't using CCE -- you are using AutoQmatEnc. Have you changed it since the report?

I have not purchased CCE in spite of everyone's raving about it. If the biggest difference is speed, I can live with it. I'll look for a comparison somewhere.

I got oversized iso's with each encoder: QEnc, HC, and I think I even tried the rejig transcoder. AutoQMat crashed on this movie (Take the Lead) but has been performing flawlessly in 3-pass mode on all other movies. If there is a newer version out, and it is not bundled with your update, then I have probably not changed it. I'll check its website.

I'm also going to try reripping since I might have had a bad original. Your success with the same movie means there is something else afoot and it's probably my problem, not yours.

This time I'll be more consistent with keeping the log, ini, and iso file size distinct for each encoder or option used.

Thanks for all your time, jDobbs.