Procoder Oversize

[Don Francesco]

Hi to all,
I am a newbee in this forum, so please spare in case of a stupid posting

Since a few days I use Rebuilder Pro 1.01 Final together with Procoder 2.

Since this version I do have the problem with oversized output, although I use the targetsector as default.

The output with the default value of targetsector was about 4650 mb.

Then I tried targetsectors=2137972 which led to an output of about 4250 MB
(it should be 4420 MB when you use the formula of this thread)

Now I am a little confused as usually the default was working fine up to this version 1.01 ...

Does this depend on the movie? Why doesn't the default value work anymore? It is very time consuming to figure out which value fits.
Do the values differ from now on depending on the movie?

Maybe there is someone who might help somehow
Thanks in advance
Don

P.S.: by the way, hi Uncas

[UncasMS]

is that you, robert?
^_~

i havent had sizing problems so far with 1.01 and procoder2
does it happen with more than this one title?

are we talking about a normal movie or about some sort of an episode dvd?

[blutach]

Hi Don. Best to use RBOpt first, which is very accurate (to 3Mb).

Robot1's formula is Actual = TargetSectors * 2 * 1.013 / 1024

Regards

[Don Francesco]

is that you, robert?

Indeed I am

i havent had sizing problems so far with 1.01 and procoder2
does it happen with more than this one title?

It happens to all titles I tested yet ( 3 different Jams Bond, one commedy and one drama (Patriarchin).

I uninstalled a former version (0.95 ?? Don't remember), then installed the new one ...

Hi Don. Best to use RBOpt first, which is very accurate (to 3Mb).

Robot1's formula is Actual = TargetSectors * 2 * 1.013 / 1024

Regards

Thanks, I 'll check it and give it a try ...

[UncasMS]

did you try other encoders like cce or hc as well?

maybe you could try a 2 pass encoding with cce (dont go for opv as this may yield peculiar sizes as well)

[Don Francesco]

Not yet, I 'm interested in HC, but first I 'll try RBOpt.

[UncasMS]

fine - give it a go

[Don Francesco]

Hm, I am a little bit confused about the actual HC release?
Which one is the one recommended 015 or 016?

The release 015 was delivered together with rebuilder 1.01.

Is this the one I should use?

[Don Francesco]

Ah, and one more info.
Yesterday I tried again one movie (James Bond Diamantenfieber(Diamonds are forever).
I blanked some trailer stuff with vobblanker, made one more try and the result was much more accurate although yet too large (about 4580 mb).
Right now I try the same together with RBOpt.

I'll keep you uptodate ...

[UncasMS]

hc 016 is said to have some flaws - for the time being i personally havent come across one yet

the latest hc016 test release 2 worked fine for me with numerous titles

so imho you could use either one: 015 or 016

[Don Francesco]

Ok, Rebuilder worked fine with RBOpt, almost the optimum of space (4.685.381.632 Bytes).
Right now I give HC a chance

*edit* with HC 015 and no RBOpt ...

[blutach]

Don,

I would use RBOpt with HC, too.

Regards

[Don Francesco]

Yes blutach,
this will be the next step

[Don Francesco]

Ok, the combination rebuilder and hc (without RBOpt) created an output with exactly 4.641.857.536 bytes, which is almost as exact as rebuilder, procoder and RBOpt.

I didn't compare the quality yet, but this wasn't the intention of the discussion.

But it proofs, that there must be a little "difference" in calculating the output size

[UncasMS]

like i said: procoder2 was always right on spot for me so there is hardly anything i could suggest except for uninstalling rb + procoder completely and starting from scratch