View Full Version : MBAFF and its effects
sabeelmk
26th January 2009, 08:29
Dear members
can anyone please any links for a proper understanding/papers(other than the H264standard) on MBAFF. and the affects of MBAFF on other modules especially like H264 Deblocking filter.
Thank you
sabeel
Dark Shikari
26th January 2009, 08:30
The spec (http://www.itu.int/rec/T-REC-H.264-200711-I/en)
G_M_C
26th January 2009, 09:47
The spec (http://www.itu.int/rec/T-REC-H.264-200711-I/en)
Speaking of MBAFF, i remember seeing a posting of yours saying "MBAFF, coming to a x264 revision near you". Can you update us on the progress of this addition ?
Dark Shikari
26th January 2009, 09:50
Speaking of MBAFF, i remember seeing a posting of yours saying "MBAFF, coming to a x264 revision near you". Can you update us on the progress of this addition ?Delayed indefinitely due to the discovery that the original patch, supposedly working but written by retarded monkeys, was in fact the latter, but not the former.
G_M_C
26th January 2009, 11:18
Delayed indefinitely due to the discovery that the original patch, supposedly working but written by retarded monkeys, was in fact the latter, but not the former.
:p
You do know that monkey have the abillity to evolve do you ? Granted it'll take quite a bit of time ... and i dont know if we live long enough to see the improvement :D
It might indeed be a better idea to have the pach developed by other beeings ;)
Guest
26th January 2009, 15:05
I'm confused now. The version of x264 I have has the --interlaced option. Has it been removed? How is it not working?
Dark Shikari
26th January 2009, 18:13
I'm confused now. The version of x264 I have has the --interlaced option. Has it been removed? How is it not working?The MBA in MBAFF stands for macroblock-adaptive, which x264 has never been.
Guest
26th January 2009, 18:32
I know what it stands for. So you must be saying that it encodes all macroblocks as interlaced. I can live with that. My encodes with --interlaced seem to be fine.
Vitos
26th January 2009, 18:38
By the way, what are the drawbacks of encoding interlaced without --interlaced flag specified (assuming that lack of interlaced flag in encoded file is no problem)?
Dark Shikari
26th January 2009, 18:39
I know what it stands for. So you must be saying that it encodes all macroblocks as interlaced. I can live with that. My encodes with --interlaced seem to be fine.Correct.By the way, what are the drawbacks of encoding interlaced without --interlaced flag specified (assuming that lack of interlaced flag in encoded file is no problem)?Vastly less efficient encoding.
Vitos
26th January 2009, 18:51
Good to know. I asked because the only regularly updated x264 QuickTime component (http://www003.upp.so-net.ne.jp/mycometg3/) for Mac doesn't provide this setting yet. However even without, it can encode interlaced content faster and more efficiently than Apple's h264 implementation... ;)
Ranguvar
30th January 2009, 04:06
That's not exactly hard to do... :p
Apple's H.264 implementation is a *****, both encoding and decoding. I don't think I'll get much (any?) disagreement here.
Sharktooth
30th January 2009, 04:14
was about to post the same...
however, why apple picks some standards, create a half-ass and crappy implementation of them for the CrapTime(tm) framework and then after a few trials they just give up selling the crap as it is?
i cant find an answer...
PS: i forgot they add some proprietary stuff here and there... just in case...
Ranguvar
30th January 2009, 04:37
CrapTime(tm)
I prefer Quick**** ;)
ajp_anton
30th January 2009, 04:52
I prefer Quick**** ;)****? Yes. Quick? No.
CruNcher
30th January 2009, 10:19
hehe and the chaos continues more and more content producer use quicktime as download option and aside WMV guess what retains better details an creates less artifacts it's a shame for the H.264 Standard, would be even better if they start using DivX H.264 of course optimal would be x264 in reality anything is better then Apples Encoder for promoting H.264 vs VC-1 but since a lot Pros like to use Macs and Apples Editing solutions this will continue.
WorBry
1st February 2009, 16:31
So you must be saying that it encodes all macroblocks as interlaced. I can live with that. My encodes with --interlaced seem to be fine.
Correct.
So it is, in effect, PAFF interlace encoding then ??
Guest
1st February 2009, 16:35
So it is, in effect, PAFF interlace encoding then ?? Depends on what you mean by "in effect".
WorBry
1st February 2009, 16:43
OK, to rephrase:
So it is actually PAFF interlace encoding then ??
bob0r
1st February 2009, 16:48
Question about MBAFF/PAFF (http://forum.doom9.org/showthread.php?t=120317)
Guest
1st February 2009, 17:25
So it is actually PAFF interlace encoding then ?? Of course not. It's MBAFF with all macroblocks coded as interlaced.
Since you don't understand the terms you use in your question, how can the answer possibly be of any use to you?
JohannesL
1st February 2009, 20:45
****? Yes. Quick? No.
Slow****!
Esurnir
1st February 2009, 21:19
Why are you all complaining about Quicktime, It's a PR guy DREAM of a software, you can compare your software against it without looking completely ridiculous ! (like comparing against JM)
WorBry
1st February 2009, 22:29
Question about MBAFF/PAFF (http://forum.doom9.org/showthread.php?t=120317)
Thanks bob0r.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.