It parses those directly from it so there’s no need to recompile the whole MPlayer package just to use these new things. I only need to compile x264 (with shared libs enabled) and MEncoder will directly see and use the new option(s) added to libx264. Instead you’re forced in waiting whenever the HB devs update x264 internally. Yes, and that “Bizzare” feature is exactly the one that does not allow you to link to external libs which you can upgrade to offer new functionality and speed improvements, as is the case with x264. QT interface will be accepted into the build tree.Ĭheers Malcolm °¿° (Linux Counter #276890) Hopefully in the near future (I haven’t checked the forum lately) the I use packman on this system though for smplayer (watching hdtv) and One of the major reasons I like handbrake is because of the ‘Bizarre’įeature I can install it as a standalone application without the need > Why should we do weekly snapshot builds ?Īnd why should they do weekly snapshot builds of HandBrake? Certainlyīecause users of their repository prefer to be able to always use theĪs this appears to be a rather stressy work I’ve offered to assistĭid you not point at the src rpm, would have possibly saved two days > The reason we didn’t package HandBrake before now is that it is a > SO STAY TUNED, THE PACKAGES SHOULD BE AVAILABLE BY MONDAY. > lot of warnings from rpmlint, which I’ll fix before pushing it to the > I’m now submitting it to our Build Service instance and expecting a > I’ve been working on HandBrake 0.9.3 for two days now, and finally Theįollowing is the reply of the packman team regarding my request to Thanks for your reply microchip, I knew I’d receive a post from you. You must see the light before you can talk about “The Art Of Encoding” If you can’t encode from command line, understand all the options and what they do/how they work and know how to handle different types of content, then you’re not an encoding guru It’s only a requirement for clueless noobs who don’t know what they are doing or for people who have been baby fed with GUI interfaces all their lives, like the Windows noobs for example ![]() I don’t know if this has changed, as I said, and it may very well be possible now to link HB to external libx264 which can only be a good thing.Īs for encoding. So if you are like me who always recompiles x264 from git whenever a change is made to it or something new is added, you’re stuck in using HB with the built-in version until they update it to latest x264 from git - this is certainly not an option for me as I aways use latest x264 with mencoder. Also, and I don’t know if this is true anymore since I haven’t touched HB in quite some time, but in the past HB used to use a built-in libx264 which means that it restricted you in using the provided libx264 version only as there was no external linking possible. Yes, HB is a pain in the to compile and certainly to package. Why should we do weekly snapshot builds ?Īnd why should they do weekly snapshot builds of HandBrake? Certainly because users of their repository prefer to be able to always use the “bleeding edge” of HandBrake.Īs this appears to be a rather stressy work I’ve offered to assist (which I would love to do by the way). It already took me 3 or 4 hours of work so far. It uses a bizarre build system with lots of in-tree libraries. The reason we didn’t package HandBrake before now is that it is a major pain in the bottom to package. ![]() So stay tuned, the packages should be available by Monday. ![]() I’m now submitting it to our Build Service instance and expecting a lot of warnings from rpmlint, which I’ll fix before pushing it to the Packman repository. I’ve been working on HandBrake 0.9.3 for two days now, and finally managed to package it locally. The following is the reply of the packman team regarding my request to include Handbrake in their repository:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |