lhodaniel

Ok, I'm an idiot. (My only excuse is that I am suffering from a cold.) I had a non-pixel layer selected.

I did check that. It was 16 bit. I converted to 8 bit and they were still grayed out. The image was a tiff of a night time shot of a red ferris wheel. Isn't that a AP Workbook file? It was in Open Recents. Update: It's doing it again on one of my tiffs, definitely 16-bit Prophoto RGB. I guess I should take this up in another section since it's v1.67. Regards, Lloyd

It seems the 1.67 problem of being greyed out was file-specific. I used a .tiff that was a sample file (maybe a workbook file?). On one of my files, all plugins were there. I'm still having under-saturated previews. I'm suspecting that I'm still on v1.0 of Nik since the 1.1 update is supposed to address that. Lloyd

Color Efex Pro 4 and HDR Efex Pro shows a solid red window and goes into a perpetual search "updating fonts". Viveza, Dfine, and Sharpener load but still have a preview that is lower in saturation than the AP window. This is supposedly the Nik 1.1 update of this morning. I say "supposedly" because the upgrade system seems to still be giving 1.0. I dl'd the trial, uninstalled and reinstalled. DxO doesn't feel the need to put version numbers on the dmg's, so I'm not sure. FWIW, v1.67 is acting up as well. I haven't used AP lately. But my plugin links are all grayed out in spite of them showing in preferences. This is the first time I've run AP in Mojave. Lloyd

Here in the southern US, there is an old saying: "Dance with the one who brung ya." This is something to consider while you guys spew out other apps and Affinity Photo for windows, Mac, Ipad, Xbox, PS4, Commodore 64, etc. The last beta for Mac OS was on March 1. At this point, I've pretty much given up on AP and am back in the Adobe camp. You had me for awhile. But now Adobe will have to either substantially raise the rent or force cloud storage for me to think of Affinity again. I had a lot of hope and I am disappointed.

Great question! I'm unsure of how to use percentage vs pixels as well. I look forward to Affinity's answer on this, and why they chose that parameter.

Great work, guys! I'm still getting sRGB renders or panos direct from nefs with RC2. Even more troubling, I just ran a single nef through develop to try out the lens/noise stuff. In develop persona, the file is listed in 32-bit sRGB linear even though I have prefs set for Prophoto RGB linear. When I apply develop, the rendered file is showing Prophoto RGB.

Hmm. I tried v1.43 MAS and am still getting sRGB renders. Even my D800E is set for Adobe, though that shouldn't matter for raws.

When I do panoramas straight from Nikon .nef files, the resulting pano is rendered in sRGB color space even though I have Profoto RGB set as default in preferences. If I develop the pano parts and export as tif, then the render is indeed in Profoto. Accoriding to fellow forum member Fixx, version 1.43 MAS is correctly assigning profiles to panos straight from nefs. Bug? (See end of thread, "Panorama Exposure" in the Questions subforum.) Lloyd

Hmm. I'll raise this in the beta section. Thanks!

Now that is curious. I tried that again on a different image set before posting my last reply. Still got sRGB 16-bit output. I double-checked my default color spaces and they are Profoto RGB. Are you using v1.5 RC1? I'll try to investigate further tomorrow.

Just tried it by developing the pieces first and exporting to tiff. The resulting pano in this workflow was in Profoto, as I selected in prefs. Apparently, if you do the stitch with raws, you can only get sRGB. I'd like to see that changed. Lloyd

I just tried my first pano using 3 vertical images shot with an 85mm PC-E. Result is very good and easy to do. On this first blush, I just fed AP 3 D800E .nef files rather than developing each first. I have set AP's default working space to Profoto RGB for both 16 and 32 bit. The pano was rendered as sRGB and I see no way to change that. Is that a limitation of the pano stitcher in AP 1.5 RC1? Lloyd

Mike, What color space are your originals in? I am finding on all Nik and Topaz plugins that work, serious difference between the way the document looks in AP and the way it looks in the plugin preview. Most of the time, it is desaturation in the preview view. This is worst if the image is in Profoto RGB, less so if in Adobe RGB, and a match if in sRGB. It's as if the plugin is not color managed. This happens with other third party editors, but works as intended (of course) in Photoshop. An exception is Nik Viveza: there there are distorted colors in the main preview not fixable by changing working spaces. But the small navigator window has correct color at least. This problem makes any plugin designed to alter color or tonality useless since the previews are whacked, unless one only uses sRGB. I use Profoto. Since this happens with many different plugins from different publishers and with other non-Adobe editors, it seems that the problem lies with how these editors hand off data to the plugin. It would be great if AP became the first to conquer this issue. If you are getting a match between AP and Nik or Topaz with wide-gamut documents, please advise. Lloyd

Andy, Can you guys do something about plugin previews not syncing with the actual document in saturation for wider gamut working spaces? This is really a deal breaker for functional plugins that deal with tone and color. This isn't limited to AP. There is a thread on dpreview about it happening with ACDSee. With most plugins, one can get a match by converting the source to sRGB, but who wants that limitation?. Viveza is the worst: hues actually change to a sort of color infared film look not correctable by sRGB conversion. :( Lloyd