![]() The QSV encode on an i5-3570 took under 45 minutes. For an older film like this it's usually at the higher end. The software encodes run 6-15 hours with these settings. The difference that you would really notice in day to day use was the time. I tested on a 32 inch screen at about 2 feet to spot the differences. The picture in both was very good but it was just a tiny bit softer in the QSV encoding if you looked VERY closely when right up near the screen. In both cases the resulting file was 11GB. In QSV mode those latter two settings go away so I just used the constant quality slider at 20. I include the best quality track I can in passthrough and an AAC encoded copy of the same track with the appropriate channel count. In software mode I'll set the 圆4 tuning dropdown to film or animation as appropriate to the source, and set the x264 preset to Very Slow to shrink the file a bit. My usual profile is handbrake high-profile with the constant quality slider set to 20. I used a film with a fairly grainy picture. Are there any steps I am missing?ĭid a bit of testing with QSV encoding compared to software h264 in handbrake. I apologize for jumping the gun on saying that encoding with QSV lessened encode times as B.S.Īfter using this very helpful guide, I have verified that my Pentium G3220 does support QSV and I have it enabled in bios and under the screen resolution, however I am not seeing the option to encode with QSV using handbrake. Humble pie has been served, and it doesn't taste too horrible, since I figured it out on my own. particularly steps 5-9, I now have Handbrake using Intel QuickSync to encode Fool's Gold from 1920x1080 to 1280x720p with 4000 kpbs and it's taking just a little over 30 minutes. By following this quick guide that ensured that Intel QuickSync was enabled. Found out that there was a little more I needed to do with my hardware before I'd start to have success. and after the name calling of those claiming fast encode times previously in this thread, I did a little more research on how to utilize Intel QuickSync within Handbrake. ![]() Apparently I wasn't.Īfter attempting several encodes, after fiddling with Handbrake trying to figure out how to speed things up. So I figured I was done with configuring my hardware. So I enabled it and viola Handbrake gave me the H.264 Intel QSV option. Initially Handbrake didn't see my Intel graphic chip because my BIOS had it disabled. I've got two ATI 6850 cards SLI and Intel HD graphics onboard. Let me start off by telling you my setup in regards to video cards. I figured out why my encodes were still taking over an hour even while I had Intel QSV selected. I've been known to make mistakes every once in a while. Looks like I'm going to have to admit that I'm wrong. Just a quick FYI - this is purely for 'i' series encoding - apparently AMD and Nvidia cards have their own hardware encoder but they don't offer them for free so Handbrake can't use them Edited Jby steelman1991 Changes like that can add time to the encode, so it seems does encoding VC1 streams, though nothing excessive. ![]() ![]() I don't have issues with the default settings, using 'high profile', as I said earlier, the only changes I make is to include 'forced subtitles' where necessary, or to change the 'audio' options (note there is no TrueHD passthrough - the options are downmix to DD, or re-encode to FLAC - in mkv container only). The 'myriad' of options remain and its up to each individual to decide how much they need or want to use them. This seems to have gone now from your reports I just wanted a "best" setting but you seem to have to fiddle with it for every source type. ![]() The problem I always had was determining what settings to use in handbrake, there are a myriad of options and very little explanation for the layman. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |