129 replies to this topic

[null54]

This plug-in hosts Adobe® Photoshop® 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.
 

$ USD $ GBP £ EUR € JPY ¥ CAD $ AUD $

File version 1.0.4.6.
 PSFilterPdn.zip   139.99K   1647 downloads


 
PSFilterShim

This file runs 32-bit Photoshop plugins on a 64-bit OS and must be placed in the Effects folder.

[Ego Eram Reputo]

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

Attached Thumbnails

• 

[null54]

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

File version updated to 1.0.1.0.

[Frontcannon]

This is incredible O_O

[null54]

This plugin should be stable.

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

[Ego Eram Reputo]

Done.

[Lance McKnight]

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, 22 December 2010 - 11:55 PM.

[null54]

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

[Rick Brewster]

http://blog.getpaint...ness-proposals/

Let's get this plugin some more attention.

[pyrochild]

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

[pyrochild]

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]

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, 23 December 2010 - 02:34 AM.

[null54]

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]

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]

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]

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]

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]

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]

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]

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