So it seems to be related to having the visual studio 2015 C++ redistributable.
Try installing this and seeing if it runs.
https://www.microsoft.com/en-us/download/details.a...
I've updated the download on the main page with the redistributable statically compiled within the plugin so users should no longer need the redistributable.
Getting close! Just updated the upload with some more fixes. Seems adding parallelism in some places caused more problems than benefits(and cache-abuse for that matter). I also added some progress-bar feedback that should show on the bottom right of the composition window. Lemme know how it goes and I'm so sorry for the problems you've had to face.. If it still refuses to be stable I'm also totally open to refunding you.
Oh man approximately when does it tend to crash by the way? Any specific actions that seem to cause it before it grows more unstable? Hard to isolate the issue without a crash log but I'll investigate what I can from the symptoms so I can possibly reproduce it on my end. Sorry you're having this issue...
I'm surprised it's able to run at all on 10.10.5 considering I used the OSX 10.11 SDK but I suppose it didn't use any huge and exclusive OSX features.
Hey. Sorry bout the bug, other than the threshold value causing the crash does all else seem alright? Any info about your comp that you might be able to share such as your pixel aspect ratio or resolution? Not sure what would get it to allocate a 15x0 frame though it may have to do with having "adaptive subdivision" on in which it tries to progressively generate the high resolution image from much much lower resolution ones in favor of real-time interaction
If you're able to the Windows Event Viewer might be able to give me much more precise insight on where the crash occurs if you are able to provide it.
The link provided(https://helpx.adobe.com/photos...) has a tutorial on how to use the event viewer. I'll investigate the issue on my end some more as this is the first this specific error is happening. Until then though try disabling "Adaptive Subdivision" and see if that helps at all
This crash log does not appear to make any mention of PixSort though this cautionary event log does mention the that your system is experiencing an excessive 45199 "wakeups" per minute which appears to be mostly safe. Do you have another crash log that you are able to send? Possibly the one immediately before this one is the actual crash-event log.
Hi, having significant issues re-opening a comp made by someone else that uses PixSort - get all the attached issues - AE in an attempt to self regulate seems to delete all the layers with pixsort on it so the file is unusable. When I delete PixSort from my plugins the AEP opens absolutely fine (and alerts me that the plugin is missing). I've done as AE says which is save with a new name. This strips all the PixSort stuff out of the comps making it unusable.
It seems to be from my Smoothening option under the Interval section. It blurs the Interval Mask and when trying to blur the border-most pixels it pulls in a black pixel from the edge:
In your case a solution would be to set the Interval-Smoothen option to 0 for now if it isn't too drastically affecting your results while I work on implementing a better interval-smoothing.
Hey! Sorry about the error you are getting. Did you properly extract the downloaded .zip file into the plugin directory? Something that might cause this are file permission errors during extraction of the zip file. Also what is the exact MacOS version that you are using? (10.12.1, 10.12.3, 10.12.6, etc)
Hello! Sorry you're encountering this problem. It looks like you downloaded the PC version(The ".aex" is for the PC version while the ".plugin" is what Mac OSX uses). Be sure to download and extract PixSort.plugin.zip and drag the extracted PixSort.plugin into the plugin folder. When extracted right the icon in your file browser for PixSort.plugin should change as well.
Hey Christmasham,
That's a very strange bug... Is this the first time this has happened? Is it only with this one composition in particular? Are you sure you don't have the layer that PixSort is applied to set as a guide layer?
Hey, Thanks for the quick reply! — It is the first time it's happened, though this is also the first time using PixSort, but I use plugins like trapcode and don't encounter any issues, I found out I can render out fine if I use the legacy renderer in after effects (instead of media encoder) but this is obviously not ideal as it's extremely limiting in format/codecs/etc.
Can you tell me some more context of what version and OS you are using? I am unable to replicate this using Windows 10, After Effects CC 2018 (15.0.0), Media Encoder CC (12.0).
Are you able to create any other compositions that do the same thing? Such as a very minimal composition where this seems to happen. Also have you tried clearing your media disc cache in After Effects? It is possible that the cache coherency between After Effects and Media Encoder has gotten compromised.
Hey Wunkolo,
Thanks for the reply again, I'm using macOS Sierra 10.12.6,
After Effects CC 2017 14.2.1.34 — do you think this is the root of the problem?
I've purged the cache and tested a new comp but no luck, fortunately being able to render
from after effects directly and converting afterwards is working okay for this project,
I'll update After effects when I can to see if this resolves it.
Thanks!
H
Thank you for your reply.
I followed the exact same steps as on my PC (it works there).
- unziped it, - placed it under the plugin folder (applications/adobeaftereffectCC2019/plug-ins), - and that's it, there should be no problem right ? I use other plugins from videocopilot.net or old Trapcode versions for exemple and they work fine.
Thank you for taking some time to help me ! <3
Very strange that this is happening...
Do you have multiple versions of After Effects installed and might possibly be running a version different to the folder that you are installing it in?(this is something that has happened a couple times to people with install-issues)
When the file has been fully unzipped, PixSort.plugin should have a different icon that will imply that you've got the right file to put into "Applications/Adobe After Effects (version)/Plug-ins"(PixSort.plugin within the PixSort.plugin.zip should go in here). And then it should show under "Wunk Effects" just like in the PC version.
That's very strange that it doesn't show up there. Even OSX is regarding it as a valid plugin but After Effects refuses to recognize it and you mentioned it happening to a previous version of After Effects as well...
Just one more thing to make sure:
on that .plugin file you should be able to right-click>Show package contents to browse the contents of the plugin archive. Within it, verify that the contents look like this:
Particularly that the "PixSort" file is within the MacOS folder as it might imply that you have an older download of the plugin or the initial extraction did not work correctly.
I'm booting up my OSX installs and I can't seem to be able to recreate this issue at all to find out what is going on here exactly unfortunately... Nothing seems to stand out to make it seem to be a locale or filesystem issue either from some of the other tests that I've done and the current upload at the moment is using the latest SDK from Adobe(Oct 2018) and it is using a statically linked OSX that supports version 10.11 or above so it should show up just fine... I can offer a full refund to your stripe purchase(ending in "xqJrF6") if it is not suiting your needs at the moment as I can't think of any other reason for it to not show up... Really sorry about all this
This sounds like a security measure similar to the Windows UAC system of some sort that Mac OSX has.
Maybe check some of the security settings mentioned here? There seem to be other softwares that have this issue as well.
Some others have encountered similar issues like this after upgrading to the latest OSX and I think it's basically the OSX equivalent of Window's UAC authorization to serve as a first line of defense against unsigned software.
There are some other software that run into this issue but there seem to be people finding a resolution in just right clicking and clicking open. Maybe that may work?
Right clicking and then clicking open didn't work for me, but I did find a solution in the reddit link that you attached. After getting the "cannot be opened because the developer cannot be verified," I pressed cancel, and then opened System Preferences > Security & Privacy > General. Under "Allow apps downloaded from:" there was an option to "Allow PixSort anyway." (I don't remember the exact phrasing). After clicking that I closed AE, and reopened it and the plugin worked!
Thank you for your help! I'm a big fan of your work!
Hi Erica,
I'm having the exact same trouble, same windows pop out when i'm clicking the plugin and after closing these the plugin doesn't work anyway.
I've tried to follow your suggestion going to the system preferences, but i simply don't have an option allowing to download apps from anywhere other from app store and verified developers.
Is there anything else you tried that helped you start running the plugin?
Thank you
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?
Hi @wunkolo, I just purchased Pixsort after watching a Youtube tutorial saying how great it is, and looks sick, just not showing up in After Effects once i've extracted it from the Zip and put it into the plugins folder?? I running Adobe CC latest version on a MacBook pro m1 Max
I have a big job on with a tight deadline and really need this sorted asap if possible 
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-...
For sure. To initiate a refund, please contact support with your Transaction ID and they can process the refund.
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-...
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 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.
