Edit with and PIXELMATR
I am very happy with the Edit With feature that was added in 8.1. It works great with NIK products. However, when I try it with Pixelmator it does not work.
It creates the TIFF image in the catalog and then opens the file in Pixelmater. But no matter how I try to save the edited file (e.g., copy as TIFF) it does not show up as a thumb nail in C1.
The edited TIFF file is in the catalog; when I open the package contents (MAC) the file is there along with the original. I assume the cache directory is not getting updated, explaining why the edit does not show on the screen.
Anyone try this?
It creates the TIFF image in the catalog and then opens the file in Pixelmater. But no matter how I try to save the edited file (e.g., copy as TIFF) it does not show up as a thumb nail in C1.
The edited TIFF file is in the catalog; when I open the package contents (MAC) the file is there along with the original. I assume the cache directory is not getting updated, explaining why the edit does not show on the screen.
Anyone try this?
0
-
This is due to the way Pixelmator works. Saving in Pixelmator creates its own format, *.pxm and not the tiff you had sent to it.
You need to choose "Share" in Pixelmator and then the format you want (it's a bit like save as).0 -
Another route with similar result as HCS suggested, is that you go File > Save, Save copy as TIFF or JPEG.
Note that Pixelmator writes TIFF not TIF as extension. You have to manually correct that.0 -
This still doesn't work for me.
I even saved it as .psd. The .psd file gets sent back to the correct catalog directory, and that file shows the edits. However, it will not display in C1. I tried regenerating previews to no avail. The cache directory does not contain the edited file.0 -
[quote="NN635454525171036031UL" wrote:
This still doesn't work for me.
I even saved it as .psd. The .psd file gets sent back to the correct catalog directory, and that file shows the edits. However, it will not display in C1. I tried regenerating previews to no avail. The cache directory does not contain the edited file.
Then a support case should bring clarity to what's happening.0 -
CO8 does not read PSD, so you better let that out of the equation. 0 -
Good point.
There is no difference between TIFF & TIF image formats. The TIF(F) save didn't work.0 -
[quote="NN635454525171036031UL" wrote:
Good point.
There is no difference between TIFF & TIF image formats. The TIF(F) save didn't work.
Yes, but since Pixelmator uses the .tiff extension, and CO8 the .tif extension, you manually have to remove the last 'f' in the save dialog when you save in Pixelmator. This way you will overwrite the original .tif and CO8 will update the image in viewer and browser.0 -
Same issue here (v8.3.52)
• "edit with" in Pixelmator
• TIF variant gets created in the catalog that I see in the C1 browser
• Pixelmator opens with the TIF
• adjustments made to image
• saved both the .pxm file (with the layers) and .tif (gets flattened by Pixelmator and yes, TIF with one F) into the origin directory where C1 created the original TIF
• quit Pixelmator, back in C1 it displays the updated TIF with the edits. Great, the way it's supposed to be.
• quit C1
• open C1, that edited TIF nowhere to be found in the browser. Yet, it's sitting in the same location in the catalog where it was before I quit C1. WTF?
• furthermore, the NEF preview of that same file the TIF was created out of is now for some reason completely shot! It looks like a solarize filter was run over it. "Regenerate Previews" does absolutely nothing. Double WTF??
I mean, I'm not asking for much here, am I? What is this?0 -
[quote="dredlew" wrote:
Same issue here (v8.3.52)
• "edit with" in Pixelmator
• TIF variant gets created in the catalog that I see in the C1 browser
• Pixelmator opens with the TIF
• adjustments made to image
• saved both the .pxm file (with the layers) and .tif (gets flattened by Pixelmator and yes, TIF with one F) into the origin directory where C1 created the original TIF
• quit Pixelmator, back in C1 it displays the updated TIF with the edits. Great, the way it's supposed to be.
• quit C1
• open C1, that edited TIF nowhere to be found in the browser. Yet, it's sitting in the same location in the catalog where it was before I quit C1. WTF?
• furthermore, the NEF preview of that same file the TIF was created out of is now for some reason completely shot! It looks like a solarize filter was run over it. "Regenerate Previews" does absolutely nothing. Double WTF??
I mean, I'm not asking for much here, am I? What is this?
Ease up there 😲
I don't think the one issue has to do with the other.
So, please raise a support case to get clarity on the TIF issue from Pixelmator.
Then, please share of which camera the nef is. I've had the exact same thing happen to my D2H raws and i wasn't round tripping with any kind of software. That issue still isn't fixed (yes, i did raise a support case). So, after all, maybe you can raise a support case about this too and we'll have it fixed sooner.0 -
[quote="HCS" wrote:
Ease up there
Eh no, I think it's quite justified that I'm irritated about this. For one, why do I have to file a "support case" for each of the numerous bugs this software has? This is frankly the job of their QA department and not the user. I'm a software engineer myself and I'm quite familiar with the process. While it's impossible to catch every bug and some are bound to be discovered by the user, there are just too many basic and essential functions where this software doesn't deliver. Especially round-tripping, which is not some obscure edge case function, should have been thoroughly tested.
Case in point, I can go over to Aperture (which hasn't been updated in 3+ years and was coded when PixelMator didn't even exist), perform the same roundtrip and it works flawlessly. No issues, none!
Except the host app, everything is the same:- • NEF file (D750)
• PixelMator (or any other editor for that matter)
• OS
• Hardware
There is just no excuse for this not to work when you have such an apples-to-apples comparison. Again, I can't stress enough that Aperture's codebase hasn't been touched in forever and it still runs circles around C1 in most aspects. The more I use C1, the more I get frustrated by it. And that of course, is entirely my fault for not making most out of C1's trial period and running it through its paces. Now I'm paying the price for rushing into buying it...
Oh, and nice little tidbit about buying C1; so I finally decided to pull the trigger, went to their website and wanted to checkout. Well, you absolutely HAVE to create an account or you can't buy anything. However, it would refuse to let me create an account and dish up an unhelpful error message to the tune of "Cannot create profile". Yup, that sure clarifies it. After reporting that, it took a couple days for them to even respond (with no helpful advice I have to mention). I ended up buying it through Amazon because, lo' n' behold, that actually worked. - As you can see, a frustrating experience from the the get-go.0 -
@dredlew: there seems to be quite a bit of anger there. What i was trying to say with "ease up" is not that you aren't experiencing issues, of course you are, that's what you write. But, i mean, take a step (or two) back, cool down and get this resolved.
If you don't want to raise a support case, then you as a software engineer should know that Phase One can then never resolve your issue. I also know what you are talking about, since i'm in the same software business, so i know what i'm talking about too (not a software engineer though).
What i was also trying to say, is to not marry individual issues together, even when they are happening to you at the same time. Also this should ring a bell with you.
Now, if Phase One is not responding well, i cannot help that. I'm also just another user. I'm not having these issues though and i've shared some ways about this.
Anyway, i wish you more success getting your issues resolved and less frustration in that process.0 -
@HCS, not sure where you see anger there. It's plain frustration and disbelief at the lack of progress within a timespan of several years. Yes, there was lack of progress on Aperture, however everyone else has been trying to catch up to it in the meantime. So after no progression for 4 years I finally switch to a supposedly "superior" piece of software (since you know, development on C1 didn't actually stop), I have to find that the software is actually inferior in so many ways. It is beyond frustrating each time something does not work or is not there, I have to come over here, scour the forum for an answer and 90% of the time find out that a) the feature simply does not exist or b) the feature is there, it's supposed to work but it's broken. Go file a support case (let's call it a bug report, there is nothing really to support other than what's in the forum already) and eventually it might be fixed. It's not like they are rolling out patches on a bi-weekly schedule or whatever their Agile workflow is. So how exactly does that help me get my work done now?
Again, I'm looking to "upgrade" from Aperture, not "downgrade". I expect to see major improvements from what I had before and I'd say that's not an unreasonable expectation after 4 years. From my standpoint, Aperture does 90-95% of what C1 does today, whereas C1 does maybe 50-70% of what Aperture does today. This should be reversed for it to be a valuable upgrade to me.
And I know what you were trying to say, to which I said no... as in, no I don't need to ease up, because of the reasons mentioned above. And I'm aware that this is a user forum, that strangely enough has "support reps" that aren't support reps. Because if they want to be proactive about helping out with issues, then they would pick up and file those "support cases" on their own initiative, rather than telling you to go file one.
Anyway, at the moment I have come to a point where C1 just does not deliver on the needs that I have. It may work fine for you for whatever you need it to but not for me. Not wanting to go there but I'm currently taking a second look at Lightroom again, since it's the only other game in town unfortunately. I really wanted to like C1 but it's just not there yet and given the time they've had to catch up, I'm just not confident that they will in a reasonable amount of time. Who knows, I might give it another look two versions down the road...
Good luck to you then and thanks for being an active contributor in the forum, I think it definitely helps some folks.0 -
@ dredlew: thanks for further describing your perception and feelings about Phase One, Capture One and this forum. I better understand now.
In my defense, i'm not a native English speaker/writer, so i may have used words that trigger a certain emotion with you that i didn't intend. I apologize it that's the case.
On the topic of CO vs. Aperture, i do think CO is an improvement over Aperture, but not in the catalogueing area. IMHO even Aperture wasn't so great there, but that's just me.
I use a separate DAM system for my dam needs and use CO for its strength, which is image capture and conversion. Phase One has only been after the catalogueing thing since about 2 years, so there is a lot of catch up to do, as you've noticed.
I wish you good luck in finding another tool that works for you.
On the original topic, i was trying to establish what the individual issues were that you were facing, i still believe there are more and they are not the same.
I certainly didn't intend to come across patronizing or condescending. If i did, i apologize, please see my "line of defense" above.
Let's end with some 😄 😄 😄0 -
Because if they want to be proactive about helping out with issues, then they would pick up and file those "support cases" on their own initiative, rather than telling you to go file one
They sometimes do. But without info from your setup, it's much more of a crap shoot.
It is frustrating when companies seem to not handle things the way that you think you would in the same scenario. But there is info that Phase One ask for that most don't, and that when provided gets the problem solved much faster. For example, you haven't said which version of C1 you are using, or which OS you are on, or which version of Pixelmator you are using, etc, etc.
Swearing at the people who you would like to help you doesn't usually get the results you want (unless you meant something different by WTF).0 -
It worked here without issue in C1 8.3.0.52, Mac OS 10.10.x, Pixelmator 3.3.2. 16-bit uncompressed TIFF. Changed exported filename of "Save copy as" in Pixelmator to end in .tif. File remains in referenced Catalog without issue after restarting.
Also, are you using Catalog or Session, storing files in catalog or referenced?0 -
The edited TIFF file is in the catalog; when I open the package contents (MAC) the file is there along with the original
When you say along with the original, can you clarify that? Do you mean there is a .NEF file and the edited .tif, or there is a .NEF file, the original .tif, and the edited .tif?0
Post is closed for comments.
Comments
16 comments