Anyway, to the encoding parameters. Thanks for listing some
Why do you list resolution constraints for ref? I'm using 6 for all my encodes regardless of res. My poor E8400 can't cope with more and I don't want to waste quality to impatience. So I settled for 6 and left it at that. Is it important for DXVA?
Refer to here which further explains the resolution constraints with the ref setting - X264 Settings - MeWiki
Hm, I do not limit maxrate and bufsize in my encodes. Instead I let x264 decide what's best. But why would I limit maxrate and bufsize? Do DXVA cards have issues with decoding bitrates too high?
I believe (someone correct me if I'm wrong) that bluray will have a maximum rate of around 50MB/s.
analyze: Hm, I'm using x264 through mencoder and I have this: partitions=all:8x8dct. I'm not sure how that's different from the bitmask you stated since I couldn't find an explanation for it (in a rather haste search that is).
I don't know this off the top of my head either (at work right now so I can't go researching either), I just know that anything different from the settings I listed will lead to problems with an encode and DXVA.
Looking at this, I'm tempted to say that the culprit would be analyze / partitions parameter.
Can you confirm? I'd like to know how I must set this parameter so that it works. Can you list the partitions that the bitmask represents?
Yes analyze is a huge culprit 80% of the time with an encode not being DXVA compliant. With the site I use, half the encodes get deleted because whomever made the encode had a value different from that aka DXVA would not function.
Thanks,
Jure
A really good test (also a great way for you to find out what profile someone used on an encode)... download MediaInfo and use it on one of your encodes. Compare the profile results to what I listed up there. If anything is not to those specs, there's a high possibility that that is your problem.
This is how I built my profile over time - just seeing what others were doing and then experimenting on my own. Now I think I have a fantastic profile that usually leads to a film being 80% or less in file size compared to the original film. I just finished Apollo13 this morning and took it from 17GB down to 13GB with minimal quality loss (and that isn't a very good source mind you). You can really tell whether your encode is going well by the SSIM Mean value (I shoot for .98 or higher aka 98% mathematical quality compared to original source) and look at the value for a P frame slice which you want between... 17.99-18.99? Anything less than those numbers (the frame slices not the SSIM Mean) means your wasting space/encoding time and anything more means your quality isn't high enough and you need to change something. Both of those values can be gotten from your megui log read out after a test encode finishes. Add SelectRangeEvery(1500, 30) to your avisynth script to do a test encode... multiply the file size that this yields by 50 and divide by 1024 to get your estimated final encode output and just multiply the time by 50 to see how long your encode will take... then you don't lose anything by not doing 2pass (since with CRF you can't specify a final output size) since again I do CRF encoding (to ensure my quality).
Scotland
