115 replies to this topic

[taoyue]

The plugin is hosted on Microsoft Codeplex: http://psdplugin.codeplex.com/

The latest version of the plugin is 2.3.0, released on January 26, 2013.

Please keep sending in those bug reports! The more PSD files I can collect, the more reliable the plugin will become. The PSD file format is complicated and underspecified, and it is only through user bug reports that I can discover some of the more exotic edge cases.

--

This is the thread for the currently-maintained version of the Photoshop PSD file plugin. The old thread (locked), for versions 1.0.6 and before, is located at: http://forums.getpai...op-file-plugin/

Edited by taoyue, 26 January 2013 - 07:23 PM.

[taoyue]

Version 1.0.7 of the plugin has just been posted to Codeplex: http://psdplugin.codeplex.com/

This release delivers further performance improvements over version 1.0.6. Specifically, loading is about 5x as fast, and saving is about 1.5x as fast as in the previous version.

Combined with the previous performance improvements, the plugin is now quite zippy. For example, converting a 2000x3000 test image with 7 layers on a 2.4 GHz Intel Core 2 Quad Q6600 (64-bit Windows 7) takes:

[*:1l6vo2io]With version 1.0.7, 1 second for loading, and 3 seconds for saving.
[*:1l6vo2io]With version 1.0.4, 20 seconds for loading, and 37 seconds for saving. 1.0.4 was the last version of the plugin before development halted in 2007.
Note: these numbers do not include time spent on file I/O -- they measure only the time taken to convert between the PSD and Paint.NET representations of the image.

I now consider performance of the plugin to be more-or-less acceptable. A 7-layered 2000x3000 image is significantly larger than most images that I work with in Paint.NET. Moderate-sized PSD files with only a few layers can now be loaded and saved without noticeable delay.

The next major task will be to reduce the size of saved PSD files.

[Frontcannon]

I am very glad to hear that!

[flip]

[strike]THIS WORKS THANK YOU VERY MUCH.[/strike] This works thank you very much.

[scoutchuck]

Sweet!

[L3ron]

Hey, it's very nice to see that ther is an update of the plugin!

It works perfecrtly with my PDN

[taoyue]

Version 1.5.0 of the plugin has been posted to Codeplex: http://psdplugin.codeplex.com/

As you can see by the jump in version number, I consider this to be a big deal. Please report any bugs that you discover through the Issue Tracker on the Codeplex project page.

The biggest improvement is that RLE compression now works fully on save. File sizes are now competitive with Photoshop's. Say goodbye to those 100 MB uncompressed PSD files; your files are now small enough to email. Files saved out by Photoshop are still smaller, since it uses a better compression algorithm. However, the difference is very slight in most cases.

RLE compression does take some additional CPU time to compute, approximately doubling the time it takes to save a file. To compensate, loading and saving have been parallelized at a coarse granularity. So a dual-core machine will perform as well as with version 1.0.7 of the plugin, while a quad-core machine will be faster, period. And since loading had already been incurring the RLE decompression hit, it gets a performance boost even on dual-core machines.

The parallelization is not perfect. The granularity is coarse, and some sequential segments remain. The intention is to improve the parallelization of the plugin after Paint.NET has been retargeted to the .NET Framework 4.0, which includes the Parallel Extensions. Paint.NET has historically remained quite close to the cutting edge of .NET Framework versions, so this should not take too long. The plugin is not the bottleneck for loading PSD files -- Paint.NET takes much longer to render the preview images for the individual layers -- during which the application is mostly unresponsive. Thus, there is no urgency to improve the parallelization.

Further performance improvements in this version, independent of the parallelization:

[*:3jin6no7] Reduction in memory consumption when saving. Thanks to Rick Brewster for his suggestions on the code.
[*:3jin6no7] CMYK files now load twice as fast.
[*:3jin6no7] Lab files now load 3x as fast.

[Servant_Of_Thor]

Brilliant, now I can edit those .psd files I got with the God Of War fansite pack. By the way, the newest version works really fast, not sure why you said it would be slow.

[taoyue]

You will not generally notice any delays until your images get very large. I test on images that take up half a gigabyte of memory in Paint.NET (and save out to 5 MB .PSDs). If you're working with small images with only a few layers, loading and saving will be basically instantaneous.

[jerry533482]

Is there a .PDN plugin for Photoshop?

[taoyue]

Version 1.5.1 of the plugin has been posted to Codeplex: http://psdplugin.codeplex.com/

This version contains some bugfixes:

• Bitmap-mode images can now be loaded. Thanks to dhnc for filing the bug.
• Plugin no longer crashes on files with user masks, or on certain RLE-compressed files. Thanks to Karl Barger for reporting the problem.
• Unicode error fixed. Thanks to K9998 for contributing the patch.

[zordon]

i download this plugin for a psd file http://binaryarmor.b...r-template.html
and it keeps freezing at 95 % maybe the file is to large? im running on paint.net v3.5.5

[Sarkut]

zordon,

Available memory could be an issue.

The file is 75 layers at 1106x1474 pixels.

[taoyue]

Actually, an out-of-memory error should pop up an error message, rather than hanging at 95%. If you do the calculation (http://forums.getpai...indpost__p__890), you'll find that the file uses around 500 MB when loaded into memory.

This problem is caused by a regression introduced in version 1.5.1.

I've uploaded a new version 1.5.2 to Codeplex that fixes this problem. http://psdplugin.codeplex.com/

Edited by taoyue, 06 August 2010 - 07:22 PM.

[zordon]

Actually, an out-of-memory error should pop up an error message, rather than hanging at 95%. If you do the calculation (http://forums.getpai...indpost__p__890), you'll find that the file uses around 500 MB when loaded into memory.

This problem is caused by a regression introduced in version 1.5.1.

I've uploaded a new version 1.5.2 to Codeplex that fixes this problem. http://psdplugin.codeplex.com/

thanks it works now... alittle slow...but it works thanks again guys

[taoyue]

On my machine (quad-core, 3 GB RAM), the file loads in 3 seconds, then Paint.NET locks the UI for another 3 seconds rendering the layer previews. If it's taking a lot longer, then there's something else going on.

(On my machine, Photoshop takes 1.5 seconds to load the same file -- and then it doesn't lock up the UI rendering the previews. So that's about a 4x performance hit.)

[Boerns]

Dear All,
I'm a new user from Paint.net and i'll open a (.eps) Encapsulated data, but with the plugin for Photoshop it not works.
maybe while this is an Adobe Data??
Wich plugin is availible to open a Encapsulated-data ?


Hallo an Alle,
ich bin ein neuer Paint.Net User, ich habe eine .eps Datei Postscript oder verschachtelte Postscript Datei die Datei komt aus Adobe und ich möchte mir diese Datei gerne mit Panint.Net öffnen,
gibt es ein Plug-in zum öffnen dieser Dateien?

i'm happy to hear from User
Björn

[Sarkut]

Boerns,

Only for .psd, not for .eps .

[zordon]

On my machine (quad-core, 3 GB RAM), the file loads in 3 seconds, then Paint.NET locks the UI for another 3 seconds rendering the layer previews. If it's taking a lot longer, then there's something else going on.

(On my machine, Photoshop takes 1.5 seconds to load the same file -- and then it doesn't lock up the UI rendering the previews. So that's about a 4x performance hit.)

each time i take off a layer... paint.net locks up....but then comes back after 10 secs........maybe i just have a crappy video card?.. i have 3g ram

[taoyue]

each time i take off a layer... paint.net locks up....but then comes back after 10 secs........maybe i just have a crappy video card?.. i have 3g ram

This question really isn't related to the plugin -- it's a general question about general usage of Paint.NET.

Every time you remove a layer, Paint.NET will rerender the composite image. This is determined largely by your CPU speed, since you're evidently not running out of RAM. There's very little use of the GPU in Paint.NET.

On my machine, removing a layer on your image takes about half a second. These days, there is a very wide performance range among CPUs. In some circumstances, an Atom can run as much as 4x slower than a Core 2 Solo of the same clock speed.