Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I have found this app to be really buggy at the simplest things like loading and saving documents and in general it has issues starting up.

That's interesting. While I'd probably still call it Pixelmator 1.x, I've found that with basic items like you mention, it is nicely responsive and operates reasonably well.
 
The pixelmator folks did say they fixed that in 2.0.5. From their release notes:

• Resolves an issue that prevented using Pixelmator as an external editor in iPhoto and Aperture

I do recall having the same issue you did with at least one earlier version and some combo of Aperture and PM updates seemed to fix it, and it works well (for me) now. As you say, gotta be a difference somewhere on your system.

Thanks for the help, it wasn’t a preference option, its a bug in Pixelmator, if you have a Aperture library that is not located in the Pictures Folder the edit with… won’t work, it only seems to work if your library is located inside the Pictures folder.
 
That's interesting. While I'd probably still call it Pixelmator 1.x, I've found that with basic items like you mention, it is nicely responsive and operates reasonably well.

I guess it's a possibility it's my computer but every other program seems fine.
 
Thanks for the help, it wasn’t a preference option, its a bug in Pixelmator, if you have a Aperture library that is not located in the Pictures Folder the edit with… won’t work, it only seems to work if your library is located inside the Pictures folder.

Very interesting - great detective work :)
 
Apple needs to buy them before Adobe does. I can see this app being a serious threat to Adobe if Apple acquires them and puts serious money into feature matching PS.
 
Apple needs to buy them before Adobe does. I can see this app being a serious threat to Adobe if Apple acquires them and puts serious money into feature matching PS.

Agreed. We need a decent Photoshop competitor. I hope someone in Apple is taking a long hard look at this one.
 
I was going to ask if this can replace CS3 for pre-press work but without CMYK it's out of the question, shame even at it's full price it's a lot cheaper than the full price of Photoshop!


I don't personally deal in CMYK (though I may at some point), but the layer limitations and especially lack of even limited 16 bit support always keeps me from using it as my "jr" image pixel editor.

Maybe someday.
 
I've just looked at this and it's very good! It won't be replacing Photoshop, but I do wish Adobe would take a look at the UI of this application. It makes CS6 look old, tired and not at all intuitive.
 
I've just looked at this and it's very good! It won't be replacing Photoshop, but I do wish Adobe would take a look at the UI of this application. It makes CS6 look old, tired and not at all intuitive.

Speaking of UI... I would use this app a LOT more if I could switch the UI to a lighter, OSX-native, Aqua colour. It's a real eye-sore and I can't stand working more than a few minutes with it, just because it's too dark.
 
Agreed. We need a decent Photoshop competitor. I hope someone in Apple is taking a long hard look at this one.


There's a huge issue here, and that is that any image app that relies on Apple's Core Image is working within a very set bunch of parameters, both good and bad. They get to utilize system hooks and not write reams of extra code which keeps things neat and brisk. OTOH you can never, without doing programming that I've never seen in all of these Core Image based editors (and there is a handful) do things which are much different from what anyone else is doing. It all becomes about the interface and not much can be done about these features that people are asking for as long as it relies on CI. I'm not a programmer and don't know the nuts and bolts of what's under their hood, but people have been asking for the same features (some 16 bit support, less limits on layers, layer styles) for literally years. I don't see them as being in the cards given how the program relies so much on the system architecture Apple provides.

This is why Adobe can make products that go beyond what all these Core Image based programs offer (again, not that I'm faulting them in the least, but they are what they are), and also why people who desire these features are not going to find them in a CI editor, and why they won't ever quite be competition for Adobe products for those people. Different niche.
 
There's a huge issue here, and that is that any image app that relies on Apple's Core Image is working within a very set bunch of parameters, both good and bad. They get to utilize system hooks and not write reams of extra code which keeps things neat and brisk. OTOH you can never, without doing programming that I've never seen in all of these Core Image based editors (and there is a handful) do things which are much different from what anyone else is doing. It all becomes about the interface and not much can be done about these features that people are asking for as long as it relies on CI. I'm not a programmer and don't know the nuts and bolts of what's under their hood, but people have been asking for the same features (some 16 bit support, less limits on layers, layer styles) for literally years. I don't see them as being in the cards given how the program relies so much on the system architecture Apple provides.

This is why Adobe can make products that go beyond what all these Core Image based programs offer (again, not that I'm faulting them in the least, but they are what they are), and also why people who desire these features are not going to find them in a CI editor, and why they won't ever quite be competition for Adobe products for those people. Different niche.

I see. Good explanation. I myself use Elements for quite a lot of small image editing tasks and would like to give Pixelmator a chance. One thing that truly baffled me with the Pixelmator team is why are they taking ages to implement some basic Photoshop functionalities such as Layer Styles (still if Acorn has it why not Pixel?). The frustrating thing is, the developers never really took the time to explain why they seem to be dragging their feet on these features.

Thanks, now I have a plausible explication for it.
 
I see. Good explanation. I myself use Elements for quite a lot of small image editing tasks and would like to give Pixelmator a chance. One thing that truly baffled me with the Pixelmator team is why are they taking ages to implement some basic Photoshop functionalities such as Layer Styles (still if Acorn has it why not Pixel?). The frustrating thing is, the developers never really took the time to explain why they seem to be dragging their feet on these features.

Thanks, now I have a plausible explication for it.

I don't think it needs to be such a carbon copy in terms of functionality. That is more to keep users who previously came from photoshop in a zone of familiarity, but pixelmator has some nice things of its own from what I've seen. I have no idea how smooth the brushes are. Prior to CS6, Photoshop's brushes were outdated and buggy as hell compared to some of the paint packages (painter, manga studio, etc.). They just had so many annoying things that had to be worked around.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.