Jump to content
How to Install Plugins ×

PSFilterPdn (01-18-2024)


null54

Recommended Posts

Tried it with LunarCell. This screenshot is the UI. Impressive (deep Darth Vader voice)!

post-48727-129246185697_thumb.png

Link to comment
Share on other sites

The FlamingPear filters should now not crash when used through the repeat effect command.

File version updated to 1.0.1.0.

PdnSig.png

Plugin Pack | PSFilterPdn | Content Aware Fill | G'MICPaint Shop Pro Filetype | RAW Filetype | WebP Filetype

The small increase in performance you get coding in C++ over C# is hardly enough to offset the headache of coding in the C++ language. ~BoltBait

 

Link to comment
Share on other sites

This plugin should be stable.

If a moderator chooses, this thread can be moved to Plugins - Publishing Only

PdnSig.png

Plugin Pack | PSFilterPdn | Content Aware Fill | G'MICPaint Shop Pro Filetype | RAW Filetype | WebP Filetype

The small increase in performance you get coding in C++ over C# is hardly enough to offset the headache of coding in the C++ language. ~BoltBait

 

Link to comment
Share on other sites

Forgive my ignorance, but should I be searching the web for PS filters, and if so, where do I install them?

Edited by Lance McKnight

Officially retired from this forum. Have a nice day.

Link to comment
Share on other sites

You can install them anywhere you like as long as you add the location to the Search Directories list. ;)

PdnSig.png

Plugin Pack | PSFilterPdn | Content Aware Fill | G'MICPaint Shop Pro Filetype | RAW Filetype | WebP Filetype

The small increase in performance you get coding in C++ over C# is hardly enough to offset the headache of coding in the C++ language. ~BoltBait

 

Link to comment
Share on other sites

How does this handle 32-bit filters (i.e. almost all of them) running in 64-bit Paint.NET?

xZYt6wl.png

ambigram signature by Kemaru

[i write plugins and stuff]

If you like a post, upvote it!

Link to comment
Share on other sites

Wish list:

  • Make it work regardless of bittedness
  • Populate the Search directories by default with Paint.NET\Effects and Photoshop\Plug-ins
  • Integrate the filters into Paint.NET's menu structure

Fractalius works (if I force Paint.NET into 32-bit mode), which is awesome.

  • Upvote 1

xZYt6wl.png

ambigram signature by Kemaru

[i write plugins and stuff]

If you like a post, upvote it!

Link to comment
Share on other sites

I concur with Pyrochild. I downloaded a few filters, and if they aren't 64-bit, they won't show up on the list as it shown in your UI.

Edit: What I did was I made a subdirectory within the Paint.NET User File. But, I got to agree with pyrochild's suggestion.

Edit #2: I did a quick search for running 32-bit plug-in on a 64-bit system. Here's the article if anyone's interested.

Edited by Lance McKnight

Officially retired from this forum. Have a nice day.

Link to comment
Share on other sites

How does this handle 32-bit filters (i.e. almost all of them) running in 64-bit Paint.NET?

Since 32-bit dlls can't be loaded into a 64-bit process Paint.NET can not use the 32-bit plugins, as Photoshop only went 64-bit in CS4 the list of 64-bit plugins is rather limited. :(

Wish list:

  • Make it work regardless of bittedness
  • Populate the Search directories by default with Paint.NET\Effects and Photoshop\Plug-ins
  • Integrate the filters into Paint.NET's menu structure

Fractalius works (if I force Paint.NET into 32-bit mode), which is awesome.

As for the search directories searching the Paint.NET Effects directory would work, searching the Photoshop plug-in directory seems pointless as the filters installed with photoshop would most likely not run (unless perhaps if you are running Photoshop 3.0 :D).

Integrating with the menu system is tricky as the plugin systems are so different, and I see no easy way to do this.

PdnSig.png

Plugin Pack | PSFilterPdn | Content Aware Fill | G'MICPaint Shop Pro Filetype | RAW Filetype | WebP Filetype

The small increase in performance you get coding in C++ over C# is hardly enough to offset the headache of coding in the C++ language. ~BoltBait

 

Link to comment
Share on other sites

Since 32-bit dlls can't be loaded into a 64-bit process Paint.NET can not use the 32-bit plugins, as Photoshop only went 64-bit in CS4 the list of 64-bit plugins is rather limited. :(

The solution here is to use a surrogate process. Paint.NET's 64-bit process talks to a separate 32-bit process that in turn loads all the plugins.
As for the search directories searching the Paint.NET Effects directory would work, searching the Photoshop plug-in directory seems pointless as the filters installed with photoshop would most likely not run (unless perhaps if you are running Photoshop 3.0 :D).
It's not for the filters installed with Photoshop, it's for the filters someone with Photoshop has installed. It makes sense that someone who installed a filter into Photoshop would want to be able to use the same one in Paint.NET without installing it in multiple locations.
Integrating with the menu system is tricky as the plugin systems are so different, and I see no easy way to do this.

This is indeed tricky, not because the plugin systems are different, but because Paint.NET polls its plugins for a list of Effect-derived types at startup to populate the Effects menu. I can help you with this - the solution requires getting messy with C++/CLI or IL(D)ASM.

  • Upvote 1

xZYt6wl.png

ambigram signature by Kemaru

[i write plugins and stuff]

If you like a post, upvote it!

Link to comment
Share on other sites

The solution here is to use a surrogate process. Paint.NET's 64-bit process talks to a separate 32-bit process that in turn loads all the plugins.

The hardest part with that would be the cross process communication, unfortunately delegates probably are not cross process that would make things a lot simpler. :(

It's not for the filters installed with Photoshop, it's for the filters someone with Photoshop has installed. It makes sense that someone who installed a filter into Photoshop would want to be able to use the same one in Paint.NET without installing it in multiple locations.

That would work as long as there are no Adobe filters in the same folder(s).

This is indeed tricky, not because the plugin systems are different, but because Paint.NET polls its plugins for a list of Effect-derived types at startup to populate the Effects menu. I can help you with this - the solution requires getting messy with C++/CLI or IL(D)ASM.

So basically use a wrapper around the PS filters that allows PDN to load them as effects in the menu.

PdnSig.png

Plugin Pack | PSFilterPdn | Content Aware Fill | G'MICPaint Shop Pro Filetype | RAW Filetype | WebP Filetype

The small increase in performance you get coding in C++ over C# is hardly enough to offset the headache of coding in the C++ language. ~BoltBait

 

Link to comment
Share on other sites

The solution here is to use a surrogate process.

Yes, although easier said than done.

Paint.NET's 64-bit process talks to a separate 32-bit process that in turn loads all the plugins.

No it doesn't. I've thought about it ... but the reasons for wanting to use a surrogate process are related to isolation and stability, not bitness.

64-bit ftw

The Paint.NET Blog: https://blog.getpaint.net/

Donations are always appreciated! https://www.getpaint.net/donate.html

forumSig_bmwE60.jpg

Link to comment
Share on other sites

No it doesn't. I've thought about it ... but the reasons for wanting to use a surrogate process are related to isolation and stability, not bitness.

No, I meant that's how it would be implemented. In this plugin.

xZYt6wl.png

ambigram signature by Kemaru

[i write plugins and stuff]

If you like a post, upvote it!

Link to comment
Share on other sites

32-bit plugins will now work on a 64-bit OS and Paint.NET's Effects directory is now searched by default.

File version updated to 1.0.2.0. :)

PdnSig.png

Plugin Pack | PSFilterPdn | Content Aware Fill | G'MICPaint Shop Pro Filetype | RAW Filetype | WebP Filetype

The small increase in performance you get coding in C++ over C# is hardly enough to offset the headache of coding in the C++ language. ~BoltBait

 

Link to comment
Share on other sites

32-bit plugins will now work on a 64-bit OS and Paint.NET's Effects directory is now searched by default.

File version updated to 1.0.2.0. :)

*thumps you on the back* Thanks! Off to play with it.

Officially retired from this forum. Have a nice day.

Link to comment
Share on other sites

32-bit plugins will now work on a 64-bit OS and Paint.NET's Effects directory is now searched by default.

File version updated to 1.0.2.0. :)

Very nice, thank you :)

xZYt6wl.png

ambigram signature by Kemaru

[i write plugins and stuff]

If you like a post, upvote it!

Link to comment
Share on other sites

A bug with the alpha channel handling has been fixed.

File Version updated to 1.0.2.1.

Wait... I'm no expert on this sort of thing but does this, to an extent, mean compatibility with Topaz filters? If so, it's like Christmas come a few days late. :)

The Topaz Detail filter seems to work with no problems so they should now be compatible.

PdnSig.png

Plugin Pack | PSFilterPdn | Content Aware Fill | G'MICPaint Shop Pro Filetype | RAW Filetype | WebP Filetype

The small increase in performance you get coding in C++ over C# is hardly enough to offset the headache of coding in the C++ language. ~BoltBait

 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...