Final size (short?)

[jeo]

was encoded this 3 sources:

SWIII = 7,79Gb (8.370.749.440bytes) steal space from extras=25% with HC(normal(default)),filters: tweak(hue=0, sat=1, bright=6, cont=1).FFT3DFilter(bt=-1,sharpen=0.5)

5th Element = 4,07Gb (4.377.313.280bytes) with cce2.5(vbr_Passes=2),filter: FFT3DFilter(bt=-1,sharpen=0.3)

Sky Captain = 7,92Gb (8.505.655.296bytes) but used shrink(no compression) to separate main movie+one extra = 5,12Gb (5.501.550.592bytes) with cce2.5(vbr_Passes=3),filter: no used!

i have the same final size in all : 4,32Gb (4.642.875.392bytes)

why is so short?

regards

[blutach]

That's the default value set by Rebuilder.

If you want bigger, open Rebuilder.ini and in the [Options] section add this line:

target_sectors=2265000

That should get you to 4.36Gb. Beware - it might get you over.

Regards

[jeo]

That's the default value set by Rebuilder.

well,it means that RB is working perfectly!

thanks!

[jeo]

informations only (free version user):

adjust in rebuilder.ini [options] :

TargetSectors=2260000

give me 4,35Gb(4.681.138.176 bytes)

another hint:
read the link posted and jdobbs opinions first!!
Removing of 500 minimum bitrates improves results

min_bitrate=300

(tested using cce encoder)
if you have one old standalone(i have one),
don't use less than min_bitrate=300
but if you have one pretty new use 100 without any fear!

regards for all!

[blutach]

It seems that this improves CCE output (wouldn't know, don't use it).

Regards

[TBL]

If you want bigger, open Rebuilder.ini and in the [Options] section add this line:

target_sectors=2265000

adjust in rebuilder.ini [options] :
TargetSectors=2260000

Hello.

I'd just like to ask which one of these it is, target_sectors or TargetSectors?

Thanks in advance.

[jeo]

hello TBL and

is TargetSectors=
(2260000 for 4,35Gb worked perfectly without oversize)
read more hints in the Hidden Settings thread.

regards

[blutach]

Yep - sorry about that. But I still use 2265000

Regards

[TBL]

Thanks for the welcome and clarification

[conair]

TargetSectors settings don’t seem to make any difference when I use DVD-RB Pro+HC16 in “One Pass VBR (w/analysis)" mode. I tried different settings between defaults – 2400000. I get always the same result 4.21GB (4313MB). But when I use CCE and TargetSectors 2255000 I get constantly 4.37GB (4478MB)

[jeo]

DVD-RB Pro+HC16 in “One Pass VBR (w/analysis)" mode

HC????....in RB free version OPV is for cce only!

RB pro have this option for HC encoder?
(i can't find about it in the guides )

[jdobbs]

TargetSectors settings don’t seem to make any difference when I use DVD-RB Pro+HC16 in “One Pass VBR (w/analysis)" mode. I tried different settings between defaults – 2400000. I get always the same result 4.21GB (4313MB). But when I use CCE and TargetSectors 2255000 I get constantly 4.37GB (4478MB)

They still work... but the sizing accuracy of any encode will swing when using OPV... that's the price you pay for the small sampling/time savings.

[jdobbs]

HC????....in RB free version OPV is for cce only!

RB pro have this option for HC encoder?
(i can't find about it in the guides )

The pro version does OPV for HC also.

[apfraats]

hmmm to what I today use is :

CCETRAGETSECTORS=2256400, which gives 4.34-4.36 output, always fitting.
MIN_BITRATE=0, which never never gives problems, and finally my CCE blocking problems are gonne in most sources.
VBR_BIAS=0

Also it looks from bitrate veiwer graphs that 2.7.2.4 compared to 2.67.x.x has much more dynamic bitrate swings. In one second it changes bitrate by 6000 Kbps in some cases !!!. So the bitrate graph shows a lot more dynamic with huge swings in bitrate.
A also get much mch better results with high compression difficult sources, no blocking anymore !!!
It looks like 2.7.2.4 is more VBR then 2.66/2.67 at the VBR_BIAS=0 setting.


I tried CCE compiling a full back movie using blankclip(framecount)

And CCE gives as lowest 210 Kbps/sec and would't go below that.
So a real 0-situation is probably never reached.
This was at a Q of 1 so perfecteclty encoded.
HC evens falls down to 180 Kps/sec on a complete black source.

So if you wanna test compatibility with players make a 'black movie' DVD.

Then if you use CCE 2.7.4.2 there is an undersizing problem, probably due to saturation in some segments.

I have had two DVD's from a couple of 70 where the output was undersized.

And be aware that (at least it was told to me) in practise a DVD+R can have a little bit less capacity than a DVD-R, so you can have problems using 4.36 GB on a DVD+r, while a DVD-R will cause no problems.

I'm finally pretty happy using CCE 2.7.2.4 with MIN_BITRATE=0 and VBR_BIAS=0. It now compresses most difficicult sources with great results.

What I could before not do as there was vlocking occuring, now can be done easily without any artifacts.

However I always use CCE's natural filter setting that behaves like a low pass filter, isn't infuencing picture quality noticable but prevents high frequencies in video to reach the encoder.

Even at 16* zoom on the TV I don't notice blocking any more.

and NATURAL FILTER doens't do any harm to picture quality.

It probably blocks some unnatural high frequencies that could interfer with the encoder.

[jeo]

CCETRAGETSECTORS

.....it's a typo,right?