Look for an answer on the COW.
Thanks Dave!, I replied to you there.
You should know that in the latest version of AE (22.214.171.124) there is a small bug regarding EXR images. I don't know of any workarounds.
If that is not the problem this can easily happen when vectors are included in an image and the image is not precisely lined up on the pixel grid or when the height and width are odd numbers. You can also have this problem if there is a layer that is slightly offset.
I did not look at your image because the download path was too convoluted.
Here is the image size data for your file as seen in the ProEXR plug-in:
dataWindow (box2i): [0, 0, 853, 479]
displayWindow (box2i): [0, 0, 852, 478]
For some reason, the two are different. Any idea why?
Photoshop uses the dataWindow while Premiere and After Effects use displayWindow, so that's the reason for the discrepancy. More information here.
No idea, i rendered those with 854 vs 480. Blender opens it normal at 854 vs 480, so does photoshop. When i open in photoshop, then go image size, there you can see it's the correct size.
Also when you just open in photoshop, then save it. Then after effects imports it at 854 vs 480. I really don't know what's going on.
I fixed the blur issue with the anchor points, . I had to adjust the anchor points (it shiftd half points)
thanks for your reply btw!
When Photoshop re-saves, it sets the displayWindow to the same as dataWindow. This sounds to me like a bug in Blender, or maybe a setting you can fix.
This blog post tells you how to get After Effects to use dataWindow instead of displayWindow. But really the file has probably been written wrong. Nuke would give you a result similar to After Effects and Premiere. From the blog post:
If you want to use the raw dataWindow as previous versions did, you have to enable the feature by editing AE's preference file, setting the "Enable displayWindow dialog" preference to 1. Once that has been done, hold down the Shift key when importing a file and a dialog will appear, letting you choose between displayWindow and dataWindow.
Yes, indeed. I think something is wrong with the render it self. Btw thanks for the link. Really helped me understand it. I'm a beginner so it's all new to me