# Anti Aliasing issues **URL:** \ **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:** 20\ **Page:** 1
**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:** [April 29, 2022, 4:30pm UTC](https://forum.logik.tv/t/anti-aliasing-issues/5699/1 "2022-04-29T16:30:13Z")
This is my first significant amount of phone comps since moving to Flame on Mac. 2022.3. HD plate, 1500x3000 flat art, bilinear/perspective transform. The text seems unusually jagged, though the rest of the art looks alright. I don’t remember ever seeing this in linux, but again, it’s been awhile. Incidentally a coworker also mentioned it, and he used to be a linux guy too. Screenshots attached. What’s more curious is EWA+Linear: it looks extra blurry, not nicely filtered. Am I crazy, or is this how it’s always been? Viewer filtering is on, but you see this in renders. And I’ve flipped all the options in node/batch prefs to no avail. My solve was to resize the comp to UHD, and resize back to HD in Action. A resize/lanczos node brought back the same jaggies. ![Screen Shot 2022-04-28 at 9.06.38 AM](https://us1.discourse-cdn.com/flex020/uploads/thedepartmentofexternalservices/original/2X/5/5f7c7c45a9c64432a578b70771b9f9bced66a65a.jpeg) ![Screen Shot 2022-04-28 at 9.04.51 AM](https://us1.discourse-cdn.com/flex020/uploads/thedepartmentofexternalservices/original/2X/1/1518ef739d7c4520bb7690ddf12b3197c9353933.jpeg) ![Screen Shot 2022-04-28 at 9.03.25 AM](https://us1.discourse-cdn.com/flex020/uploads/thedepartmentofexternalservices/original/2X/7/7beb494331ec035577c59c02a8ded92ee70fb9b1.jpeg) ---
**Author:** ![andy\_dill](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/andy_dill/32/15475_2.png) [@andy\_dill](https://forum.logik.tv/u/andy_dill)\ **Post date:** [April 29, 2022, 5:24pm UTC](https://forum.logik.tv/t/anti-aliasing-issues/5699/2 "2022-04-29T17:24:27Z")
that bottom one is definitely…odd. Try lowering hte AA radius to 0.5 and see if that helps on frame 2 ---
**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:** [April 29, 2022, 5:35pm UTC](https://forum.logik.tv/t/anti-aliasing-issues/5699/3 "2022-04-29T17:35:01Z")
Resize using Lanczos from big to small is a bad idea. It’s designed to go from small to big. Typically Anisotropic is better for surfaces rotated to camera like your shot. I’d try that. If not, then blur it. ---
**Author:** ![hBomb42](https://avatars.discourse-cdn.com/v4/letter/h/bbce88/32.png) [@hBomb42](https://forum.logik.tv/u/hBomb42)\ **Post date:** [April 29, 2022, 5:48pm UTC](https://forum.logik.tv/t/anti-aliasing-issues/5699/4 "2022-04-29T17:48:59Z")
Kinda what @Randy said. I can’t see how big the phone is in your HD plate, but 1500x3000 artwork is pretty highres. A really, REALLY good Action trick to get around having to crank the bejeebus out of AA when scaling down high-rez artwork is to pre-blur it. You won’t even be able to tell. The jaggies will clean right up and you’ll probably be able to get away with just 1 sample and EWA. ---
**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:** [April 29, 2022, 6:08pm UTC](https://forum.logik.tv/t/anti-aliasing-issues/5699/5 "2022-04-29T18:08:50Z")
Thanks. .5 AA radius still goofy looking. Aniso still goofy looking. Pre-blur helps, but the text legibility suffers quickly, and i still see some suspicious jaggies. FWIW the phone is maybe 600 pixels in vertical size on screen. So medium close up. I’ll keep fooling around with it when I get downtime. ---
**Author:** ![hBomb42](https://avatars.discourse-cdn.com/v4/letter/h/bbce88/32.png) [@hBomb42](https://forum.logik.tv/u/hBomb42)\ **Post date:** [April 29, 2022, 6:21pm UTC](https://forum.logik.tv/t/anti-aliasing-issues/5699/6 "2022-04-29T18:21:25Z")
Are you mucking about in linear? If you’re converting a white rec709 insert to acescg or something it might be the values going nuclear that’s messing you up. ---
**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:** [April 29, 2022, 6:29pm UTC](https://forum.logik.tv/t/anti-aliasing-issues/5699/7 "2022-04-29T18:29:47Z")
You don’t need artwork that big. Resize it down first using Shannon to something more 1:1 ish and you should be fine. ---
**Author:** ![andy\_dill](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/andy_dill/32/15475_2.png) [@andy\_dill](https://forum.logik.tv/u/andy_dill)\ **Post date:** [April 29, 2022, 6:31pm UTC](https://forum.logik.tv/t/anti-aliasing-issues/5699/8 "2022-04-29T18:31:46Z")
Artwork must be print resolution!!!111! ---
**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:** [April 29, 2022, 6:42pm UTC](https://forum.logik.tv/t/anti-aliasing-issues/5699/9 "2022-04-29T18:42:46Z")
There is a matchbox called FX HWAA I think, that sometimes does wonders on aliasing, not sure about here. You put it after your comp. ---
**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:** [April 29, 2022, 6:45pm UTC](https://forum.logik.tv/t/anti-aliasing-issues/5699/10 "2022-04-29T18:45:07Z")
All rec709 videospace. Attaching a shot: resized artwork to 1/3 with shannon, Still goofy looking. I swear it feels like my Flame is whacked out, normally this stuff looks ok with just EWA and 1 sample, right? Or have I been too long out of the screen comp game? Let me tell you how many times we’ve changed the text copy and the time and date… now that’s been enjoyable. ![shannon](https://us1.discourse-cdn.com/flex020/uploads/thedepartmentofexternalservices/original/2X/5/5ac92a9ebb9462b19a601c1b6b1be1a78c0c346c.jpeg) ---
**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:** [April 29, 2022, 6:47pm UTC](https://forum.logik.tv/t/anti-aliasing-issues/5699/11 "2022-04-29T18:47:49Z")
Weird. Hit Preview. Does that help? And just in case turn off Z Buffer if there are any other surfaces in there. Also, look at your artwork source. Is THAT funky in Flame? ---
**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:** [April 29, 2022, 6:48pm UTC](https://forum.logik.tv/t/anti-aliasing-issues/5699/12 "2022-04-29T18:48:44Z")
Are you on Discord? I’ve got a minute between renders if you wanna/can share your screen. ---
**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:** [April 29, 2022, 6:53pm UTC](https://forum.logik.tv/t/anti-aliasing-issues/5699/13 "2022-04-29T18:53:29Z")
Preview doesn’t help. Z buffer has been off. It’s just art and the BG plate. Artwork looks fine when it’s flat. Would appreciate a discord share, but expecting client call shortly. Maybe we can circle back again when it’s slower? thanks guys for all the suggestions! ---
**Author:** ![Sinan](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/sinan/32/155_2.png) [@Sinan](https://forum.logik.tv/u/Sinan)\ **Post date:** [April 29, 2022, 7:06pm UTC](https://forum.logik.tv/t/anti-aliasing-issues/5699/14 "2022-04-29T19:06:50Z")
Is this per chance a geometry and not a surface? I have had similar problems with geo. ---
**Author:** ![andy\_dill](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/andy_dill/32/15475_2.png) [@andy\_dill](https://forum.logik.tv/u/andy_dill)\ **Post date:** [April 29, 2022, 7:24pm UTC](https://forum.logik.tv/t/anti-aliasing-issues/5699/15 "2022-04-29T19:24:07Z")
it’s a dumb question, but is motion blur on? ---
**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:** [April 29, 2022, 7:26pm UTC](https://forum.logik.tv/t/anti-aliasing-issues/5699/16 "2022-04-29T19:26:12Z")
Not a geo. just a plain old surface. Tried moblur on and off ---
**Author:** ![SamE](https://avatars.discourse-cdn.com/v4/letter/s/e36b37/32.png) [@SamE](https://forum.logik.tv/u/SamE)\ **Post date:** [April 29, 2022, 7:37pm UTC](https://forum.logik.tv/t/anti-aliasing-issues/5699/17 "2022-04-29T19:37:25Z")
I highly recommend turning off filtering in the viewer. It’s hard to know what pixels you are making when you have filtering on. With filtering off, view it at 100%, or even 200% or 400%. It’s the only way you can actually judge filtering of the image. Turning down softness in the action Anti-aliasing prefs might eke out a bit more apparent sharpness. If you’ve been working in 4k a lot, going back to HD everything in HD looks soft. ---
**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:** [April 29, 2022, 7:46pm UTC](https://forum.logik.tv/t/anti-aliasing-issues/5699/18 "2022-04-29T19:46:48Z")
Actually (I’m not sure for how long it has been this way) filtering is “off” when the viewer is at 100%. ---
**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:** [April 29, 2022, 7:57pm UTC](https://forum.logik.tv/t/anti-aliasing-issues/5699/19 "2022-04-29T19:57:51Z")
I do have a screenshot from a 100% viewer, but probably shouldn’t post that as commercial has’t aired. However it’s got the jaggies. And I did do filtering on/off and whole number zooms just to be sure! Anyhow, legal just changed and a date on a phone just changed. Off to appease the legal gods. Again appreciate the troubleshotting ---
**Author:** ![pixelmixer](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/pixelmixer/32/2994_2.png) [@pixelmixer](https://forum.logik.tv/u/pixelmixer)\ **Post date:** [April 30, 2022, 2:59pm UTC](https://forum.logik.tv/t/anti-aliasing-issues/5699/20 "2022-04-30T14:59:24Z")
Almost looks like source was tagged as field rate. [Next page](https://forum.logik.tv/t/anti-aliasing-issues/5699.md?page=2)