PSFilterPdn (2019-01-04)

[null54 381]

This plug-in hosts Adobe® Photoshop®-compatible filter plug-ins under Paint.NET.

Many filters should run although some may have issues, both Flaming Pear's LunarCell as well as their Free Plugins  work correctly.

For instructions on installing 8bf filters see Installing 8bf filters.

 

This plugin is compatible with Paint.NET 3.5.11 and 4.0.x.

 

Download

PSFilterPdn.zip

Place both PSFilterPdn.dll and PSFilterShim.exe in your Effects folder.

 

 

Effects->8bf Filter...

 

Source Code

  https://github.com/0xC0000054/PSFilterPdn

[Ego Eram Reputo 2,168]

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

[null54 381]

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

File version updated to 1.0.1.0.

[Frontcannon 4]

This is incredible O_O

[null54 381]

This plugin should be stable.

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

[Ego Eram Reputo 2,168]

Done.

[Lance McKnight 4]

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

Edited December 22, 2010 by Lance McKnight

[null54 381]

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

[Rick Brewster 1,145]

http://blog.getpaint.net/2010/12/22/photoshop-filters-and-more-silly-business-proposals/

Let's get this plugin some more attention.

[pyrochild 335]

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

[pyrochild 335]

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.

[Lance McKnight 4]

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 December 23, 2010 by Lance McKnight

[null54 381]

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 ).

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

[pyrochild 335]

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 ).

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.

[null54 381]

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.

[Rick Brewster 1,145]

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

[pyrochild 335]

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.

[null54 381]

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.

[Lance McKnight 4]

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.

[pyrochild 335]

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

[Kemaru 44]

Hooray, thank you! This is really great.

[Rubrica 14]

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.

[null54 381]

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.

[Rubrica 14]

Thank you SO much.

[PeterPawn 0]

I can't get this to work. I must be doing something wrong but there's no instructions. I put the dll file where it's supposed to be, I see it in PdN but you can't close the dialogue box. What's the exe file for?

Edited December 28, 2010 by PeterPawn