View Full Version : JM10.1 H.264/AVC Reference Software win32 binaries.
Sharktooth
14th October 2005, 20:00
Changelog: http://www.webalice.it/f.corriga/h264/CHANGES.TXT
Sources: http://iphome.hhi.de/suehring/tml/download/
Binaries: http://www.webalice.it/f.corriga/h264/jm10.1.7z *
* Built with VS2003.
Sirber
14th October 2005, 20:47
Should it be crappier than x264? :)
Suchy
15th October 2005, 00:22
It's freeware or OpenSource?
Manao
15th October 2005, 07:12
There's no notion of freeware or opensource for the JM, it's the reference encoder. It means that everybody can access the code ( like OS project ), but the licence isn't GPL nor LGPL.
The JM has a better raw coding efficiency than x264. However, it's 100x times slower, and it doesn't have a ratecontrol nor a bframe decision.
That means that for DVD ripping / encoding, it's totally useless.
bond
15th October 2005, 11:34
its nice for testing avc features not yet available in other encoders :)
Tommy Carrot
15th October 2005, 11:48
The JM has a better raw coding efficiency than x264.
I'm not really sure about that. I made some tests with very dumbed down settings (no rdo, 1 ref frame, no b-frames, etc.) and x264 was very clearly better with similar settings. It was not only more detailed, but the motions were more accurate and fluid as well. Of course i cannot exclude the possibility that the ref. encoder has great quality with every quality/efficiency improving feature enabled, but i'm not patient enough to do a test with them. :D
Manao
15th October 2005, 21:57
Well, if you prevent the JM to use its tools, of course, it'll be less efficient. JM was primarily designed to work in RD, using it without that is only a loss of time.
Tommy Carrot
15th October 2005, 23:00
Actually i tried to run a test with rdo and the other options, but i had to interrupt it after the encoder finished only with ~1800 frames in half a day (damn, it's hopelessly slow). But even judging from the quality of that short segment, i still cannot say it would have better quality than x264.
Then again, this just proves that the devs did a great job on x264, it's not only many times faster, but in most cases it has even better quality, at least in my opinion anyway. :)
omion
16th October 2005, 08:51
It looks like this can only take raw YUV files. What's the easiest way to convert AVI to raw?
Even though JM wasn't designed for human consumption (it's definitely geared toward encoder developers), I'd still like to try out all the bells and whistles :D
Kopernikus
16th October 2005, 10:22
You can use ffdshow and select"output"->"store frames to external file", and select "uncompressed" as codec.
omion
17th October 2005, 00:43
Thanks. I didn't think of using ffdshow.
Magno
18th October 2005, 12:03
what does "RD" ("RDO") mean?
I read it everywhere but nobody says what that means...
bond
18th October 2005, 12:14
what does "RD" ("RDO") mean?
I read it everywhere but nobody says what that means... :readrule: :readfaq:
unmei
18th October 2005, 12:17
Rate Distortion (Optimization)
http://en.wikipedia.org/wiki/Rate-distortion_theory
bonds is fast ..and i like his answer better :)
Magno
18th October 2005, 14:45
I have read the FAQ, have read the rules and have studied for two years the H.264 standard and I still can't see where is talked about RD on it. Maybe it is explained in some appendix I haven't, but the term "Rate Distorsion" doen't appear in the standard, so I supposse it is not implemented on JM (not sure as I haven't check it) and so, I supposed "RD" DIDN'T mean "Rate Distorsion". This cofused me:
Well, if you prevent the JM to use its tools, of course, it'll be less efficient. JM was primarily designed to work in RD, using it without that is only a loss of time.
Thank you both, anyway :D
stephanV
18th October 2005, 15:02
RD isn't part of any standard. You can apply it to virtually any codec. (and that info is in the MPEG4 AVC sticky!)
Magno
18th October 2005, 15:14
Ooops! I printed that guide but I didn't pay attention to that point. Sorry.
:stupid:
bond
18th October 2005, 16:18
I have read the FAQ, have read the rules and have studied for two years the H.264 standard and I still can't see where is talked about RD on it. Maybe it is explained in some appendix I haven't, but the term "Rate Distorsion" doen't appear in the standard, so I supposse it is not implemented on JM (not sure as I haven't check it) and so, I supposed "RD" DIDN'T mean "Rate Distorsion".hm you read the sticky? lemme quote what it says there:
Rate Distortion Optimisation (RDO):
RDO allows the encoder to make the most efficient coding decisions whenever it has to choose between different choices (for example when it comes to inter/intra decisions, motion search...)
RDO is not a tool defined by the AVC/H.264 specs, but it's a new decision making approach which was first introduced by the H.264 reference software. Other codecs can also make use of RDO, like XviD's VHQ Mode enables RDO already for exampleand give you a strike for rule 1 :o
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.