analytics

Re: Any plugin(s) sought but not implemented / available? I'm talking about digital editing in general - solutions to existing problems community is asking for. By "problems" I mean anything loosely defined as such: fancy effects currently possible to do only manually, perhaps AI for some intelligent processing, productivity features, processing and workflow automation, etc. Usually, people look for an idea, and then they start looking for problems to be solved by it. This is the other way around: existing problems calling for solution(s). Here's my item: it seems that selection tools, like magic wand, have limited functionality as far as criteria for selecting "similar" pixels could be. Luminance is one of them, but it may be completely unsuitable for certain editing tasks. Feel free to chime in with your item(s). Thanks in advance.

Adding some setting is nice, but involves additional dev work as well as writing additional instructions / explanations. Feature like this is not easy to explain to someone non-technical - i.e. how Effects folder should be cleaned and why prior to activating recursive feature. So if all that could be avoided and make things simpler, the better. One approach to achieve this, i.e. preventing same dll from being loaded twice or more times (e.g. one unzipped into a subfolder under Effects, and one copied into Effects folder) is to enforce 'first-found-first-loaded' procedure - as the dll is loaded, file hash is added to loaded-dlls collection list so that the exact same one found elsewhere is skipped. This would avoid any need for GUI settings and other complications, plus feature could be shipped enabled without any worry. There could be some other things to watch out for, e.g. versioning, but nothing too complicated to do.

Perhaps, some of PDN's direct contributors could comment on recursive-folder-plug-ins loader feature from the design perspective and how much time it'd take to implement it? Thank you.

My apologies in advance if this is already in PDN v4 - I'm still using 3.5 for work and have not had a chance to try it. Currently, all plug-ins' dlls need to be put into Effects folder. That's all good, but after a while, this folder ends up being a mess - full of dlls without having a clean and easy way to know which ones are from which pack. It's very hard and time consuming to remove packs one no longer wants. Etc, etc. Solution: Simply make PDN look not only in Effects folder but in any subfolders there too. That way, one would be able to simply create a folder with arbitrary name, paste all the XYZ pack's dlls there and use them. If that pack is no longer needed or wanted, deleting that folder would cleanly remove it. This would also allow one to organize plug-ins in any way one wants and track what's installed, etc. Many other benefits too. I think this would be one great feature! What do you say? Please feel free to chime in! P.S. Thanks for all the work by the way. Additional note I forgot to mention originally: this feature would search recursively through subfolders for dlls, i.e. not only first level, but any depth.