![]() |
PSPI: Running Photoshop plug-ins in GIMP |
|
Tor Lillqvist (tml) GIMP Pages -- Windows port |
PSPIPspi is a GIMP plug-in that runs 3rd-party Photoshop plug-in filters. I wrote it in 2001, and it initially worked on Windows only. Then nothing much happened until now (March 2006) when it became available also on Linux. All that was needed, basically, was for somebody to try building it using winegcc. Possibly building and running it on Linux might have worked already years ago, but nobody tried... Thanks to Mukund for trying it on Linux and reporting the success! Where to find Photoshop plug-in filters that are any good?Google is your friend. You will find time-limited or functionally limited demo versions of commercial filters, and "freeware" filters. A lot of the 3rd-party filters that you can find on the net are mostly crap, though, and don't do anything particularily exciting that one couldn't do with GIMP already. There are some exceptions though. I think that for instance many filters from Flaming Pear are highly regarded. You can find time-limited demo versions, and some giveaway fully functional ones from their site. Some magazines that come with "cover" CD-ROMs, like Computer Arts, often include commercial Photoshop filters on the CD-ROMs. They might for instance be slightly older versions than those that you need to pay full price for. Photoshop plug-in filters (for the Windows version of Photoshop, which is what we are talking about here) are actually Windows DLLs, which are dynamically loaded into the plug-in host process's address space. They are files with the extension .8bf, though, not .dll. (GIMP plug-ins, on the other hand, are separate processes.) Unlike GIMP plug-ins, 3rd-party Photoshop plug-ins don't use any common user interface library. (GIMP plug-ins use GTK+, obviously.) This is because 3rd-party Photoshop plug-ins are usually available both for the Windows and Macintosh versions of Photoshop. Typically each company uses some homegrown widget library, with a look and feel that is widely different than the normal Windows common control look and feel, or the GTK+ look and feel. What is in the binary packages?WindowsThe Windows package includes just pspi.exe. Put it in your GIMP plug-ins folder. LinuxThe Linux packages include three files:
Copy pspi and pspi.exe.so to your personal GIMP plug-ins folder, typically ~/.gimp-2.4/plug-ins . When you run GIMP it will issue a warning "wire_read(): error" as pspi.exe.so can't be started directly. (The pspi script can, though, and is from GIMP's point of view a GIMP plug-in.) This warning is harmless (GIMP just ignores that file then), but if you want to avoid it, move pspi.exe.so somewhere else and modify the pspi script to point to its new location instead. After starting GIMP, go to the Xtns:Photoshop Plug-in Settings and enter the folder where you are going to keep the 3rd-party Photoshop plug-ins (.8bf files) that you want to use in GIMP. Preferrably you should use an initially empty folder for this, and then install (copy) Photoshop plug-ins there one by one, verifying that each works. It isn't really useful to rush and install a shitload of Photoshop plug-ins at once and assume they all will work under pspi. There is also a tarball with the object files. You can try to use those if the binaries don't work on your distro. Use winegcc to link, add the gimp plug-in libraries (output of pkg-config --libs gimp-2.0), -ladvapi32 and -lgdi32. Check the src/Makefile.am for details. LicensingI license the pspi source code under the so-called MIT licence. I used to use the GPL, but I guess that doesn't make much sense for software whose very purpose is to load proprietary modules. Whether using proprietary Photoshop plug-ins through pspi with the GPL GIMP causes any legal or moral problems I have no idea. I doubt it has any legal ramifications as long as you don't package together proprietary Photoshop plug-ins with GIMP and pspi and redistribute the combination. As for moral problems, well, if you don't like the idea, don't use pspi. DownloadsThe Windows, SUSE and Ubuntu packages are by me. The Fedora Core 5 packages are provided by Veit Wahlich <cru |at| zodia |dot| de>.
|