[ANN] standalone PSD -> Gimp XCF converter

T
Posted By
toby
Dec 23, 2010
Views
1725
Replies
4
Status
Closed
Hi,

I’d like to announce a command-line tool which converts PSD or PSB files to layered XCF (v1), in RLE or uncompressed formats. I am aware that Gimp imports PSD, but I’ve seen it reported that some files do not import in layers, while this utility always produces a layered XCF. Also, there may be situations where this conversion is required but neither Photoshop nor Gimp is available.

* supports 8-bit RGB, Grey Scale and Indexed modes
* portable (tested on OS X, Linux, Windows)
* open source (GPL)
* very fast
* may help to recover damaged PSDs – based on the robust psdparse code

Limitations:
* currently converts image layers only
* does not yet convert image masks

Binaries (OS X Intel/PPC, Win32) and source code available via: http://telegraphics.com.au/sw/#psd2xcf

–Toby
Related Tags
conversion gimp

Master Retouching Hair

Learn how to rescue details, remove flyaways, add volume, and enhance the definition of hair in any photo. We break down every tool and technique in Photoshop to get picture-perfect hair, every time.

L
ldo
Dec 23, 2010
In message
, toby
wrote:

I’d like to announce a command-line tool which converts PSD or PSB files to layered XCF (v1), in RLE or uncompressed formats. I am aware that Gimp imports PSD, but I’ve seen it reported that some files do not import in layers, while this utility always produces a layered XCF.

Why not just roll your code into improving the Gimp importer?

Also, there may be situations where this conversion is required but neither Photoshop nor Gimp is available.

Where can there be a situation where your app is downloadable but Gimp is not?
T
toby
Jan 19, 2011
On Dec 23 2010, 3:17 am, Lawrence D’Oliveiro <
central.gen.new_zealand> wrote:
In message
, toby
wrote:

I’d like to announce a command-line tool which converts PSD or PSB files to layered XCF (v1), in RLE or uncompressed formats. I am aware that Gimp imports PSD, but I’ve seen it reported that some files do not import in layers, while this utility always produces a layered XCF.

Why not just roll your code into improving the Gimp importer?

For one reason: it would have been at least 20x the effort, all things considered, including learning the Gimp codebase. I don’t have the time budget for that. This converter was only about 3 or 4 evenings’ work. If somebody wanted to sponsor improvements to Gimp I’m all ears. (Gimp devs have always been free to draw upon psdparse’s underlying code.)

Also, there may be situations where this conversion is required but neither Photoshop nor Gimp is available.

Where can there be a situation where your app is downloadable but Gimp is not?

It may not be an issue of ‘downloadable’. The runtime/resources requirements are completely different. My utility is perfectly suited to non-interactive, server based or on-the-fly conversion, and is fast and inexpensive.

–Toby

PS. Good to speak to you again. We met in person a very long time ago, not sure if you remember 🙂
JS
John Stafford
Jan 20, 2011
In article
,
toby wrote:

It may not be an issue of ‘downloadable’. The runtime/resources requirements are completely different. My utility is perfectly suited to non-interactive, server based or on-the-fly conversion, and is fast and inexpensive.

Did you use ImageMagick?
T
toby
Jan 21, 2011
On Jan 20, 5:03 pm, John Stafford wrote:
In article
,

 toby wrote:
It may not be an issue of ‘downloadable’. The runtime/resources requirements are completely different. My utility is perfectly suited to non-interactive, server based or on-the-fly conversion, and is fast and inexpensive.

Did you use ImageMagick?

No, it’s all my code.

MacBook Pro 16” Mockups 🔥

– in 4 materials (clay versions included)

– 12 scenes

– 48 MacBook Pro 16″ mockups

– 6000 x 4500 px

Related Discussion Topics

Nice and short text about related topics in discussion sections