itch.io

The effect is working correctly, but the layer itself is scaled down to %16.7 of its original size so After Effects introduces additional filtering and averaging and sub-pixeling.

Try clicking this "/" symbol until it is stair-steppy to disable the additional filtering that After Effects introduces.

https://helpx.adobe.com/after-effects/using/layers.html#layer_image_quality_and_...

When you render it out, be sure to use "Current Settings" when exporting so it does not re-introduce that additional filtering anymore.

Another solution is to apply it to an adjustment layer rather than this scaled-down layer.

Ah we're getting somewhere! SaiThumbs might not be handling the external drive properly. Did it use to work for your external drive before and now it isn't? Maybe try running Disk Cleanup and clear your thumbnails cache like so:

Can you tell me some information about your system?

I don't have a lot of information at the moment to look at this issue much further unfortunately...

Oh jeeze sorry this is happening.

Is this correlated with configuration or system changes that have happened recently like a Windows-Update or driver-installation of some sort?

It should already be compatible! Are you getting an error of some sort?

Hey! Does the issue seem to happen even with a very minimal case scenario? (a still image or simple animation)

I want to try and re-create the issue on my end so I may look into it!

Hey there! Another user here might have had a similar issue as yours. Does enabling the "EnableLUA" registry-setting fix the issue? It might be that it does not have proper permissions. Be sure to run the installation scripts as an administrator as well.

I am facing the error problem only in deep glow & displacer pro

I am not the author of Deep Glow & Displacer Pro, these are made by https://www.plugineverything.com/.

Unless you are having this issue with B.Carve or PixDither, you should be reaching out to them for support.

What I am saying is that I notice of all the plugins you mentioned not working suddenly are exclusively GPU accelerated, but you're saying some non-GPU accelerated ones are having the same issue. You've made a post both on PixDither and on B.Carve though which is adding to the confusion. Another user on another one of my GPU-accelerated plugins seemed to have a similar issue here.

One way to diagnose the issue is to upload the log file somewhere to see what's going on:

Try uploading the `.crash` file somewhere for me to inspect. In the meantime I might suggest updating/reinstalling your graphics drivers and perhaps even the latest Visual Studio C++ redistributable(the x64 link in this case) in case that is a possible cause.

So this is a PixDither issue? Not B.Carve?

You mention that Deep Glow and Displacer Pro are having this issue in your image. Are you getting with with B.Carve too?

You made another post over on PixDither as well so I am not sure how to interpret your issue.

It sounds like you are having issues with GPU-accelerated After Effects plugins in particular, which might indicate issues with your graphics driver.

 Some others have had situations like this and some have had luck by just right-clicking the plugin file and clicking "Open" at least once. Try some of these solutions!

https://support.apple.com/lv-lv/guide/mac-help/mh40616/mac

https://github.com/hashicorp/terraform/issues/23033#issuecomment-539736692

https://community.vcvrack.com/t/rack-cant-be-opened-because-apple-cant-check-it-...

Is there any other thing that might have happened that correlates to when it stopped working? I'm getting a little stumped as to what it might be now after doing some more digging😥. Would you be able to provide a sample .sai file(it could just be a blank canvas or a squiggle or something) that fails to generate a thumbnail in explorer? What version of Sai are you using?

I've uploaded a new build with some more recent fixes that you may try out! Let me know how it goes. 

You can be sure that you have the latest build by right-clicking the .dll file and going into the "Details" panel to ensure the year is 2023 rather than 2018(The previous build was from 2018 and lots of fixes have happened since then.

Hmm still looking into this, what version of Windows are you currently on? Had you upgraded your Windows version before it stopped working?

Hey! Just to make sure, are you using saithumbs-x64.zip or saithumbs-x86.zip? When you extract the installer files and run the installer, is the .dll located somewhere stable such as next to your Sai installation folder?

Have you tried clearing your thumbnail cache? You can clear your thumbnail cache by running "Disk Cleanup" and selecting "Thumbnails" before cleaning. This should get Windows to re-generate all of the thumbnails entirely and invalidate any that it may already have.

You're so very welcome! So glad to help!

Can you please post a screenshot or something of the issue? I am not sure what specific error message you are running into. Is this similar to the issue other people have mentioned in the Bug-Thread where the solution is to right-click and press "open" on PixDither.plugin at least once?

Just following up to say that PixSort now supports Apple-Silicon MacOS!

For sure. To initiate a refund, please contact support with your Transaction ID and they can process the refund.

Seems to be related to the fact that the application is "technically" unsigned and MacOS wants you to allow it explicit permissions, but it is not clear how to do so for a plugin. Some others have had situations like this and some have had luck by just right-clicking the plugin file and clicking "Open" at least once. Try some of these solutions!

https://support.apple.com/lv-lv/guide/mac-help/mh40616/mac

https://github.com/hashicorp/terraform/issues/23033#issuecomment-539736692

https://community.vcvrack.com/t/rack-cant-be-opened-because-apple-cant-check-it-...

Just updating to say that PixDither now works with Apple-Silicon based macs!

Apple-Silicon support has been added as of today! Thank you all for your patience 🙏🙏 Let me know of any new bugs you may have ran into over on the bugs thread!

Haha really I tried my best to ask around for a machine to remote into and even tried to setup a Virtual Machine of some kind using VirtualBox and Docker and such but it turned out to be too much of a headache that just refused to provide a stable workspace since Apple really only wants OSX software to be compiled on OSX hardware! So I just bit the bullet and bought a minimum-viable 8GB M2 Mac Mini and it should be coming today! Before, I used a Virtual Machine on my Intel workstation but with the latest Apple-Silicon stuff...that is no longer feasible so it's about time I just give in and get some Mac hardware around as a build and test server. Expect an Apple-Silicon port either the end of this month or the first half of march. I'll be sure to be loud about it once it's done!

Apple-ARM support is currently in the works! Aiming for a release this half of the year.

I'll try for this half of the year for sure.  I can guarantee at the very least I want to try and get an OSX Virtual Machine setup and try to cross-compile some kind of ARM version for people to at least try and test, even if I don't have the hardware myself.

No news just-yet on a proper Apple-ARM release. I have yet to have access to Apple's proprietary compilation toolchain to assemble together a proper release though I might be able to set up an updated x64-based virtual machine or utilize a remote build server like GitHub actions and cross-compile an Apple-ARM build from it but won't be able to test and verify the ARM build on actual hardware.

Once I can secure a proper development pipeline though, I'll be updating all of my Pix-series plugins over to support Apple-ARM.

Oh wow that's a curious bug. Could you provide any more info relating to this like your GPU and driver version and such in the Bug Thread?

This seems to be an artifact with trying to accumulate some very flowy vector-field values onto a raster pixel grid, causing it to "miss" some pixels while integrating streamlines. Basically, it will increment the current pixel into the next pixel by sampling the vector-field, but will "miss" the diagonal pixel that it may have touched along the way without knowing that it crossed two pixels rather than one. 🤔

This might take some time to figure out how to remedy without breaking previous projects(and hypothetically adding custom vector field support), but I'll try and look into it without changing the core algorithm too much.

For now, one way to remedy this is to put the PixSort on its own layer with "Interval Matte" view mode and use the "Median" filter with a 1px radius and enable the "Operate On Alpha Channel" option

For sure! Sent it over 👌Sorry for the trouble.

Hey there! I responded to your email as well. Unfortunately PixSort does not currently support ARM-based M1/M2 Macs. 😖This is stated on the page for PixSort as well.

If you'd like I can begin the refund process for your purchase.

Looks like you're right! It seems I only uploaded the MFR-enabled OSX build onto the site and not the Windows build. It should be updated now with MFR enabled!

PixSort does support multi-frame rendering!

Hey! Thanks for bringing this up. After Effects definitely has a level of abstraction involving color-spaces before those color values get fed to a plugin. It looks like the original issue you described is from it feeding sRGB-colorspace pixels to the plugin based on how all the darker color values clamp over to black super easily. Linear space colors is definitely the solution in this case!

At the moment no! This plugin does not work with Apple-M1s.

The disclaimer is on the page as well:

Thank you! We can debug this further over email. 👌

I'm having some trouble on my end trying to re-create the situation at the moment. Creating a composition in adobe after effects and rendering+encoding it out from adobe media encoder.

Would you be able to provide more context or a minimal setup that you can send(wunkolo at gmail dot com) that recreates the situation?

The only thing I can imagine is that it may possibly be a caching issue of some kind. Where it is picking up old cached frames rather than actually rendering the Pixel-Sorted-ed frames somehow.

Could you try clearing your cache and seeing if that helps somewhat?

Currently in the works of securing a pipeline to create Apple-Silicon builds! It may take some time but it's certainly a priority of mines to get it to work properly on Apple-ARM.

The full log would help yes! Even if it is super long. If it is too large to attach here then feel free to email me at wunkolo at gmail dot com