HELL YEAH I'm also slowly chipping away at Sai2 support in the meantime as well!
Wunkolo
Creator of
Recent community posts
Is there a specific version that you are encountering this issue on? Something like 25.1.0 or 25.3.0?
There seems to be some reported issues with 25.3 causing black frames that will require one to clear their cache:
https://www.reddit.com/r/AfterEffects/comments/1laqb9b/just_a_heads_up_the_new_2...
Hey! This was a change introduced December of last year to bring it into conformance with how After Effects and Graphics APIs and such work. Apologies for the disruption this might have introduced!
https://wunkolo.itch.io/pixmap/devlog/844001/bmap-compatibility
Hey! This seems to be due to anti-aliasing trying to blend between two UV values that are at extremes. For example. One pixel with a UV coordinate at 1.0 might be next to another with a coordinate at 0.0. A naïve anti-aliasing filter will try to blend between these two pixels and create a value like 0.5. This causes the strange artifact at the seams that you see here. You will want to ensure that the UV pass you export does not have any additional filtering or anti-aliasing so that it does not introduces these intermediate values. I believe in C4D's render-settings you can set Anti-Aliasing to "None" and it should remove these seems.
Oh you're right! The link seems to be a removed Vimeo link now. I don't have access to C4D at the moment but there does seem to be some media on how to get a UV pass out of C4D for other plugins out there, with the only difference being to use PixMap. Despite using a different plugin, it looks what the person does here should work too!
What you may also need to do is go to Settings>Privacy & Security and there should be an option for PixMap after getting the "unidentified developer"-message that you may click "Open Anyway" on. After doing that, it should run normally! Either that or right-click PixMap.plugin and click "Open" just once and it should stop trying to block it from running within After Effects.
Also, PixMap is completely free! You may put $0.00 into the amount to donate and get the download.
This is a known issue introduced with Adobe After Effects 25.2 in particular, causing lots of other people's plugins to break as well on MacOS in particular.
https://x.com/DaveChap/status/1909237942536577222
I would suggest downgrading to 25.1 if you can, or possibly getting some of the newer updates that may address this issue in particular. I'll be looking into this issue on my end too.
This is a known issue introduced with Adobe After Effects 25.2 in particular, causing lots of other people's plugins to break as well on MacOS in particular.
https://x.com/DaveChap/status/1909237942536577222
I would suggest downgrading to 25.1 if you can, or possibly getting some of the newer updates that may address this issue in particular.
This is a known issue introduced with Adobe After Effects 25.2 in particular, causing lots of other people's plugins to break as well on MacOS in particular.
https://x.com/DaveChap/status/1909237942536577222
I would suggest downgrading to 25.1 if you can, or possibly getting some of the newer updates that may address this issue in particular.
Just making extra-sure, you are getting this message when you drag and drop it from the Effects panel? Trying to be sure of what you mean by "Open it after downloading". It should not be dragged-and-dropped into the After Effects window or opened with File>Open and just needs to be placed into the plugin folder and it will show up in the Effect panel.
What you may also need to do is go to Settings>Privacy & Security and there should be an option for PixDither after getting the "unidentified developer"-message that you may click "Open Anyway" on. After doing that, it should run normally! Either that or right-click PixDither.plugin and click "Open" just once and it should stop trying to block it from running within After Effects.
Hey! Just making sure, you're putting the extracted 'PixDither.plugin'-folder within the zip into `Applications/Adobe After Effects (version)/Plug-ins` correct? Did you get any messaging about an "unknown developer" at any point? Do you get this message upon trying to apply the effect from the Effect panel?
Are you on MacOS? There seems to be a widespread issue involving After Effects 25.2 in particular and I suggest downgrading for now or waiting for a newer version that possibly resolves the issue.
See here for more info: https://itch.io/post/12668362
This seems to be a common issue with 25.2 in particular it looks like, effecting many plugins on MacOS in particular.
I'd suggest going back to 25.1 until a solution is found. Either 25.3 will have a fix for this and/or Adobe will give us plugin developers some new guidance to get our plugins to start working again. Sorry for the issue!
Thanks your your interest! You're absolutely right that I should broaden the impact here by supporting other video editing software rather than just touching the Adobe ecosystem. I have certainly been considering porting my plugins over into OpenFX, which would allow it to support Cavalry and Autograph and Davinci and Sony Vegas and beyond! I have been slowly chipping away at reading the SDK documentation before I do a solid jump in and I am hoping to find an OpenFX software to call home to do most of my development with(I've been eyeing Davinci Resolve a bit lately). I've been slowly shaping my After Effects code to be more modular and lend itself better to OpenFX as well! So def be on the look out for something like that happening, though no promises of a time-frame at this moment. Hearing your interest in this happening though is very valuable to me for when I make that effort.
Yep! I get ya. I haven't gotten to it just yet due to some other priorities right now for this time of the year but I'll get to it! In this case, After Effect's built in sampler function considers the origin of the pixel at the top-left of the Texel. And it just needs a (0.5, 0.5) texel-offset (0.5/width, 0.5/height).
https://ae-plugins.docsforadobe.dev/effect-details/graphics-utility-suites.html#...









