View Full Version : Bits/(Pixel*Frame) in h264
pasta03
26th October 2006, 15:49
Hey!
In the xvid coincidence if we want to have the wonderful quality Bits/(Pixel*Frame) should take out about 0.28 - 0.30.
My question is:
what should be Bits/(Pixel*Frame) for the h264 codec so that the quality was wonderful.
nurbs
26th October 2006, 16:10
http://forum.doom9.org/showthread.php?t=109907&highlight=bits+pixel+frame
DarkZell666
26th October 2006, 17:39
The [Bits/(Pixel*Frame)] (aka. bpf) doesn't mean much, it all depends on the source.
However, IIRC, for h264, ~0.15 looks good.
Sagittaire
26th October 2006, 18:45
doesn't mean anything ...
little example:
http://jfl1974.free.fr/upload/superman.mp4
http://jfl1974.free.fr/upload/XMenIII.mp4
video 1920*1088 at 2 mbps
BPF = 2 000 000 / (1920 *1088 * 25) = 0.04
Quality is not so bad for BPF at 0.04 ... isn't it ... lol
DarkZell666
26th October 2006, 19:32
Lol, sorry, I forgotten to mention: at standard definition (<720x576), ~0.15 looks good ... =)
But really, those samples are a real CPU-trashing experience ... :x
Don't tell me they play smoothly on your system ... O_O
Mc Onyx
30th October 2006, 12:01
I was quite suprised they play on mine, are those samples encoded by x264 or are they Apple MOV in mp4 container?
Blue_MiSfit
3rd November 2006, 22:33
Pretty nice, but the Xmen trailer was very slow decoding on my 3500+ venice even with CoreAVC Pro. What settings were used to encode that? It feels like CABAC to me!! :)
smok3
3rd November 2006, 23:21
superman is:
x264 - core 43 svn-394M - H.264/MPEG-4 AVC codec - Copyleft 2005 - http://www.videolan.org/x264.html - options: cabac=1 ref=5 deblock=1:0:0 analyse=0x3:0x133 me=hex subme=6 brdo=1 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 chroma_qp_offset=0 slices=1 bframes=3 b_pyramid=1 b_adapt=1 b_bias=0 direct=2 wpredb=1 bime=1 keyint=250 keyint_min=25 scenecut=40 pass=1 crf=25 rceq='blurCplx^(1-qComp)' qcomp=0.75 qpmin=10 qpmax=51 qpstep=4 ip_ratio=1.25 pb_ratio=1.33
so yep, there is cabac :) and this was quality based encoding as it seems, experts may tell you more...
Blue_MiSfit
4th November 2006, 23:33
CABAC murders HD decoding speed.. :)
Not a bad trailer though. I found it killed a bit too much detail on faces etc in high complexity scenes. I was amazed by the detail on Patrick Stewart's eye-bags though :D
I would probably do it at CRF 22 or something :)
akupenguin
5th November 2006, 00:28
The cost of cabac is proportional to bitrate, while the cost of most other parts of the codec is proportional to the number of pixels. So in that .04 bpp stream, cabac makes less speed difference than it does normally.
arfster
5th November 2006, 05:48
Not a bad trailer though. I found it killed a bit too much detail on faces etc in high complexity scenes.
Bit much to ask for significant detail in 1.5mbit 1080i :D
Blue_MiSfit
6th November 2006, 14:30
@akupenguin:
thanks for the clarification, I didn't realize that!
1.5 mbps not enough for perfect 1080i
nonsense!!!! BACK TO WORK!! :devil:
Seriously though, I was pretty impressed. A tiny bit of noise on playback helped it look better too...
~MiSfit
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.