# Anti Aliasing issues

**URL:** <https://forum.logik.tv/t/anti-aliasing-issues/5699>\
**Category:** Flame Questions\
**Tags:** aliasing\
**Created:** [April 29, 2022, 4:30pm UTC](https://forum.logik.tv/t/anti-aliasing-issues/5699 "2022-04-29T16:30:13Z")\
**Posts on this page:** 17\
**Page:** 3

<div class="post-metadata">

**Author:** ![PlaceYourBetts](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/placeyourbetts/32/6852_2.png) [@PlaceYourBetts](https://forum.logik.tv/u/PlaceYourBetts)\
**Post date:** [May 3, 2022, 10:16am UTC](https://forum.logik.tv/t/anti-aliasing-issues/5699/43 "2022-05-03T10:16:29Z")

</div>

That is very curious. I checked it on my Mac. Both 2020 and 2022 exhibit the same behaviour.

I will test it again in the morning on the Linux.

---

<div class="post-metadata">

**Author:** ![ytf](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/ytf/32/109_2.png) [@ytf](https://forum.logik.tv/u/ytf)\
**Post date:** [May 3, 2022, 12:35pm UTC](https://forum.logik.tv/t/anti-aliasing-issues/5699/44 "2022-05-03T12:35:03Z")

</div>

I have some time today. I’d love to take a look at this. I’ve experienced similar things in the past.

---

<div class="post-metadata">

**Author:** ![hBomb42](https://avatars.discourse-cdn.com/v4/letter/h/bbce88/32.png) [@hBomb42](https://forum.logik.tv/u/hBomb42)\
**Post date:** [May 3, 2022, 2:57pm UTC](https://forum.logik.tv/t/anti-aliasing-issues/5699/45 "2022-05-03T14:57:14Z")

</div>

I just loaded the setup on my z840 and am seeing the same issue. I can’t get the thin vertical parts of the letters in the text message to not alias. If I turn on motion blur I mostly don’t notice, but if I look closely I can still see it.

---

<div class="post-metadata">

**Author:** ![ytf](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/ytf/32/109_2.png) [@ytf](https://forum.logik.tv/u/ytf)\
**Post date:** [May 3, 2022, 2:58pm UTC](https://forum.logik.tv/t/anti-aliasing-issues/5699/46 "2022-05-03T14:58:58Z")

</div>

Is that setup available someplace? I don’t see a link in the thread

---

<div class="post-metadata">

**Author:** ![hBomb42](https://avatars.discourse-cdn.com/v4/letter/h/bbce88/32.png) [@hBomb42](https://forum.logik.tv/u/hBomb42)\
**Post date:** [May 3, 2022, 3:01pm UTC](https://forum.logik.tv/t/anti-aliasing-issues/5699/47 "2022-05-03T15:01:06Z")

</div>

It’s in discord

---

<div class="post-metadata">

**Author:** ![randy](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/randy/32/6122_2.png) [@randy](https://forum.logik.tv/u/randy)\
**Post date:** [May 3, 2022, 3:10pm UTC](https://forum.logik.tv/t/anti-aliasing-issues/5699/48 "2022-05-03T15:10:08Z")

</div>

now its here  
[aliasing setup.zip](https://forum.logik.tv/uploads/short-url/9wTslDj9tjoHyvsxqxOZF3JWjRU.zip) (1.3 MB)

---

<div class="post-metadata">

**Author:** ![ytf](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/ytf/32/109_2.png) [@ytf](https://forum.logik.tv/u/ytf)\
**Post date:** [May 3, 2022, 3:44pm UTC](https://forum.logik.tv/t/anti-aliasing-issues/5699/49 "2022-05-03T15:44:36Z")

</div>

Same here on Linux. Turning up HWAA helps.

---

<div class="post-metadata">

**Author:** ![aaronneitz](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/aaronneitz/32/3874_2.png) [@aaronneitz](https://forum.logik.tv/u/aaronneitz)\
**Post date:** [May 3, 2022, 4:26pm UTC](https://forum.logik.tv/t/anti-aliasing-issues/5699/50 "2022-05-03T16:26:00Z")

</div>

Thanks for cross posting that Randy. HWAA only affects the outside edges for me.

---

<div class="post-metadata">

**Author:** ![GPM](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/gpm/32/4224_2.png) [@GPM](https://forum.logik.tv/u/GPM)\
**Post date:** [May 3, 2022, 4:59pm UTC](https://forum.logik.tv/t/anti-aliasing-issues/5699/51 "2022-05-03T16:59:13Z")

</div>

Curious if you’ve tried this comp in another software, and did you see similar results?

---

<div class="post-metadata">

**Author:** ![ytf](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/ytf/32/109_2.png) [@ytf](https://forum.logik.tv/u/ytf)\
**Post date:** [May 3, 2022, 5:06pm UTC](https://forum.logik.tv/t/anti-aliasing-issues/5699/52 "2022-05-03T17:06:20Z")

</div>

Your original had AA set to 8. If you set that to 1 and turn the HWAA up to x64 you will see a slight improvement. If you keep AA set to one and switch HWAA to different values, you should see a marked difference.

---

<div class="post-metadata">

**Author:** ![aaronneitz](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/aaronneitz/32/3874_2.png) [@aaronneitz](https://forum.logik.tv/u/aaronneitz)\
**Post date:** [May 3, 2022, 6:54pm UTC](https://forum.logik.tv/t/anti-aliasing-issues/5699/53 "2022-05-03T18:54:14Z")

</div>

I did briefly try it in AE. But it looks worse by a mile. I haven’t kept up with AE though, so I might be missing some AA options (I have it in full res, best quality, full raster, flipped between bilinear and bicuic).

---

<div class="post-metadata">

**Author:** ![GPM](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/gpm/32/4224_2.png) [@GPM](https://forum.logik.tv/u/GPM)\
**Post date:** [May 3, 2022, 7:47pm UTC](https://forum.logik.tv/t/anti-aliasing-issues/5699/54 "2022-05-03T19:47:05Z")

</div>

Nuke?

---

<div class="post-metadata">

**Author:** ![aaronneitz](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/aaronneitz/32/3874_2.png) [@aaronneitz](https://forum.logik.tv/u/aaronneitz)\
**Post date:** [May 3, 2022, 7:51pm UTC](https://forum.logik.tv/t/anti-aliasing-issues/5699/55 "2022-05-03T19:51:56Z")

</div>

No Nuke for this old horse.

---

<div class="post-metadata">

**Author:** ![Jeff](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/jeff/32/9305_2.png) [@Jeff](https://forum.logik.tv/u/Jeff)\
**Post date:** [May 3, 2022, 9:24pm UTC](https://forum.logik.tv/t/anti-aliasing-issues/5699/56 "2022-05-03T21:24:16Z")

</div>

I pulled in that batch and took a look. My two cents is just that those anti-aliasing lines that you’re seeing are “just what it looks like” at that angle and that resolution.

I think the reason that no work-around anyone has suggested has worked is because something’s gotta give when you scale text down that significantly, and to that extreme an angle. When you view it at 100%, the anti-aliasing lines are nearly imperceptible. When you zoom way in to 400% that’s when you can see the issue and it becomes a problem, but to my eye it plays fine at 100%, especially with motion blur turned on.

---

<div class="post-metadata">

**Author:** ![PlaceYourBetts](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/placeyourbetts/32/6852_2.png) [@PlaceYourBetts](https://forum.logik.tv/u/PlaceYourBetts)\
**Post date:** [May 3, 2022, 10:42pm UTC](https://forum.logik.tv/t/anti-aliasing-issues/5699/57 "2022-05-03T22:42:18Z")

</div>

This is a great case study @aaronneitz

I had another play on linux when I got back into work and to @Jeff 's point. Yup it is just what it does at that angle.

I always do my screen comps using perspective grid and stage one I get a stabilized, straightened clip of the phone for me to comp. At this angle it looks great but put the perspective grid back on and all of that crunchy stuff you have been seeing comes back. Now I would be happy to have this level of softness (RHS) when I use EWA+Linear but I can imagine how frustrating it would be if a client was requesting “sharper, sharper”.

 ![aliasing](https://us1.discourse-cdn.com/flex020/uploads/thedepartmentofexternalservices/original/2X/6/67d0213b2f405ca57eca44f9f4c1173baf61b2b3.jpeg)

---

<div class="post-metadata">

**Author:** ![hildebrandtbernd](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/hildebrandtbernd/32/3038_2.png) [@hildebrandtbernd](https://forum.logik.tv/u/hildebrandtbernd)\
**Post date:** [May 3, 2022, 11:33pm UTC](https://forum.logik.tv/t/anti-aliasing-issues/5699/58 "2022-05-03T23:33:43Z")

</div>

These are tiny typos having lines being smaller than 1 pixel, so having it sharp and also readable is technically impossible.

Instead of rezising it down after a UHD Action, add a 2D transform to half the size. Then use the resize to crop out the sides. Somehow the 2D trans does the EWA+Linear a little bit different than the action.

If the client still want’s to have it more readable, make the typo bigger/thicker

---

<div class="post-metadata">

**Author:** ![aaronneitz](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/aaronneitz/32/3874_2.png) [@aaronneitz](https://forum.logik.tv/u/aaronneitz)\
**Post date:** [May 4, 2022, 12:55am UTC](https://forum.logik.tv/t/anti-aliasing-issues/5699/59 "2022-05-04T00:55:44Z")

</div>

Make it bigger! Funny enough, half these shots were blown up over 200% already. No one thinking ahead when they shot it.

Welp. Let’s call this goose cooked!

[Previous page](https://forum.logik.tv/t/anti-aliasing-issues/5699.md?page=2)
