Thanks, Don, I am currently testing.
It seems that I can enforce mod2 incl. top and left already right now. In my tests with the value 2 for ct and cl it simply did not crop. From the user perspective this is not what would be expected, however it is better than to force mod4 and then at some point depending on the driver version to remove that restriction. And of corse it would be worse if mod2 would crash it or would detroy the video, but that does not seem to be the case.
Any additional thoughts?
OT: I do not get anymore mail messages for topics I have subscribed to. The mail adress I use here is ok as I receive other mails (and no, they are not in my spam folder). Is that only me or a general issue?
Thanks, Don, I am currently testing.
It seems that I can enforce mod2 incl. top and left already right now. In my tests with the value 2 for ct and cl it simply did not crop.
Yes, that is what I expect. But gonca reported otherwise so I asked for the stream to check that.
From the user perspective this is not what would be expected, however it is better than to force mod4 and then at some point depending on the driver version to remove that restriction. And of course it would be worse if mod2 would crash it or would destroy the video, but that does not seem to be the case.
Any additional thoughts?
I agree. We can go with a warning in the manual and hope for a timely fix from nVidia.
OT: I do not get anymore mail messages for topics I have subscribed to. The mail address I use here is ok as I receive other mails (and no, they are not in my spam folder). Is that only me or a general issue?
I'll check into it and report back. I wasn't aware of any issues.
For gonca's stream, it behaves as I expected: cl=2 does not crop anything from the left, but due to the reduction in width by 2, it effectively crops the right by 2.
I started using 2053.165 after old 2053 (first release I guess) and got a problem with dgindexnv. I opened .m2ts from bluray and made a .dgi. Coded area is 1920*1088 in both cases. First release crops 8 pixels from bottom and 1920*1080 frame looks normal in avisynth, equal to ffvideosource, for example. But release 165 crops 16 pixels from bottom and then resizes to 1920*1080. So it looks stretched in avisynth. In the dgindexnv window frame looks normal at the same time. I'll upload screens tomorrow.
No templates or cropping in dgsource() were used.
(One minute from Waterworld TV Cut without audio and subs).
If we open "cropping tool" in menu there's bottom crop 8 pixels already. To fix 1088 problem I guess. It seems it crops twice.
And there's another problem. With mkv. Coded size is always wrong. Height is always bigger then in "display size". Difference is that "bottom crop" in cropping tool. And video get cropped and stretched after dgsource.
Good, thanks. Can you give me an MKV that you think shows wrong coded size? Coded size is an elementary stream thing, not a container thing, so being MKV should be irrelevant.
Sure, we know that 165 has issues. But does the fix I posted work for you? I want to slipstream it soon so a prompt reply will be appreciated. Thank you.