HandBrake

Source is 25 fps constant. I tried Interlace Detection - doesn't help. Then I set Constant Frame Rate = 50 fps and this do the trick! :D HB 1.4.2 + Yadif BOB (Constant 50fps) = 2603.08 kbps (+11 % versus 25 fps) , this is perfect! But now, why is that? If source is constant fps, why VFR matter? Why ...

If your source is 25 fps constant, and you're doing yadif bob without interlace detection, you can use Constant Frame Rate and set it to 50 fps in HandBrake. Hi Rodeo! I don't have problem with Frame Rate, I got correct and expected FPS in all cases, 25fps with just Yadif and real 50fps with Yadif ...

Description of problem or question: Hi! This bug exists for 2 years since HandBrake 1.3.0 with x265 v.3x. I decided to create a new Topic instead of old one . :) With all versions of HB since 1.3.0 BOB deinterlace filter gives much higher bit rate than it should be. Here are the numbers: Old good H...

I will say, if you're feeling the need to disable SAO, you probably need tune Grain anyway. Tune Grain will lead to much higher bitrate, can be a few times higher and much slower encoding. NoSAO has almost none effect on bitrate, just a few kbps but picture will be without blurriness. I tend to use...

<r>No, just x265. Should i check x264 too?<br/> <br/> Perhaps it doesn't matter but in new 1.3.0 syntax of deinterlace filter is changed, now:<br/> <br/> <B><s>[b]</s>HB 1.3.0 yadif/default/off: <e>[/b]</e></B><br/> + filters<br/> + Deinterlace (mode=3)<br/> <br/> <B><s>[b]</s>HB 1.3.0 yadif/bob/off...

No one kind soul wanna help me to shed a light to the bob deinterlace problem? :( I want to point out at this particular lines: > HB 1.3.0 yadif/bob/detectionOff: encoded 1512 frames, 1925.56 kb/s , Avg QP:26.47 mux: track 0, 1512 frames, 14563289 bytes, 3847.63 kbps , fifo 2048 At muxing stage ther...

aq-mode=1 vs aq-mode=2 test Here's my 30sec sample from neighbor topic: https://megaupload.is/f7xf09B7n6/handbrakebobtest_rar Shared settings: Deinterlace: yadif / default / detectionOff Codec: H265 / framerate: SameAsSource + Variable / RF20 / preset: medium / tune: none / profile&level: auto ...

Yes, it is expected. The x265 team changed this here: https://bitbucket.org/multicoreware/x265/commits/b14834a9d1c1864ea7e94d9cfed4e33f37e767c6 Please also note, that in the newer version of x265 the way the slower and veryslow preset works has changed: http://x265.org/revamped-veryslow-slower-pres...

You don't even need to look at old 1.2.2
As I said, just in 1.3.0 new default aq-mode=2 versus forced old aq-mode=1 gives very different bitrate.

PS. I don't use any hardware accelerators.

Description of problem or question: Previous HandBrake 1.2.2 used x265 2.9 with aq-mode=1 by default. New HandBrake 1.3.0 uses x265 3.2.1 with aq-mode=2 by default (since x265 v3.0). For some reason this new default aq-mode=2 at few short tests gives me 30-60% more bitrate than aq-mode=1 or old HB ...

Description of problem or question: With new HB 1.3.0 I have anomaly high bitrate when doing BOB deinterlace comparing to regular deinterlace and any deinterlace used in HB 1.2.2 Steps to reproduce the problem: Load interlaced sample. Here's one 30sec sample 576i: https://megaupload.is/f7xf09B7n6/h...