Jump to content

curio

Members
  • Content Count

    31
  • Joined

  • Last visited

About curio

  • Rank
    Member

Recent Profile Visitors

453 profile views
  1. Tried it myself, Viveza appears to work fine irrespective of color profile or bit depth.
  2. Has there been any progress on this with the new v3.0 release of the Nik plugins?
  3. Whenever I record a macro (in my case with a simple document size change) and then click attempt to save it to the library, AP freezes after the dialog prompting for the name, regardless of whether I close that dialog by OK or cancel. This is with AP v1.8.2.620 on Windows 10 Pro 64 bit. In this state, I need to force-close AP.
  4. Has anything changed? Last time I checked, color space and bit depth issues were still rampant with the “old” Nik suite, especially with Viveza and Color Efex, the two tools I mainly use, rendering AP's alleged support useless for me.
  5. Add to that color space issues, you need to convert to 8-bit sRGB.
  6. Any news on this? Edit: Never mind, retried things with the current beta. Seems to work better: transparency's gone, strange error message still pops up occasionally. Also, it suffers from the same color profile issues as do the Nik collection plugins in that ones other than sRGB result in false colors being displayed in-plugin.
  7. It's also the only one with which this happens out of those I use (entire Nik collection, Knoll Light Factory, and this). And to clarify, with "unresponsive" I mean that I can't interact with the application, clicking anywhere just gives a negative Windows "pling" (the kind you get clicking on a window with a modal dialog in the foreground), so I guess that some modality context isn't finished off as it should be or something.
  8. Attempting to run the Digital Film Tools Rays plugin (v2) on an image (pixel layer, no matter what color depth) gives me an error: "ChannelPorts not available". Not only doesn't the plugin work this way, once the message dialog has been closed, AP becomes unresponsive and needs to be killed via the task manager. This is on Windows 10 x64.
  9. Also, I've tested with GPU acceleration disabled (setting rendering to WARP, whatever that is): makes no difference, i.e., it's not a GPU acceleration issue.
  10. Meanwhile, I'd like to mention that when AP crashes, a window titled "CrashReport" pops up, telling me the the crash reporter cannot be started because it cannot find an error report to send or the error report ist empty.
  11. Thanks for confirming this! Granted, wrong colors aren't as much of an issue with Dfine as they are with Viveza.
  12. @AlainP: You sure about Dfine and there being no color space issues? Please try this: make an image 16-bit and ProPhoto RGB, then open it in Dfine. For me, colors in the latter are clearly wrong (blue sky becomes purple etc.) in both the main view and the preview of Dfine. This is with v1.5.1.54. Also, do you have hardware acceleration (GPU) enabled? If so, what GPU do you have? I do and will try without... I has nothing to do with the color space issues, in any case.
  13. It's not only Viveza; Dfine 2 at least also has color space issues. Can anyone who claims not to have any crashes please open an 8-bit sRGB image (mine are usually about 16 megapixels, in case that matters) in Viveza and make a greater number of adjustments (create, say, 20 control points and play with the sliders of each)? I'll almost guarantee you that you will get a crash doing that at some point. This has never happened to me with PS, which is why I'm blaming AP (supposing something about the context it provides to the plugins is buggy). The issues are, however, not straightforwardly reproducible, either — crashes happen randomly, but in a session of editing a single image using some of the Nik plugins including Viveza, I almost always get a crash (not only in Viveza, sometimes also in the apply stage of one of the other plugins) at some point which forces me to save early, save often (and even then it means work lost when it crashes in the middle of an extensive Viveza edit). Add to this that Viveza doesn't work with 16-bit/non-sRGB images and you see why I feel forced to stick with PS. :-/ I'm more than willing to create logs or dumps of any kind if there's a way to do that, to help Affinity diagnose the issues. My system is Windows 10 x64 and has a Core i7 6700K, 32 GB of RAM (memchecked, no issues), and a GeForce GTX 1070.
  14. I wonder if we'll ever get to the point where the Nik plugins will 1) work also with 16-bit, non-sRGB images and 2) not crash randomly every now and then? Both of these are no issues with Photoshop, so it's not the plugins themselves that are to blame. Honestly, this is the thing holding me back from switching from PS to AP for good.
  15. Is it intentional that Affinity Photo foregoes adding an EXIF Software (Exif.Image.Software) tag when exporting images, as about any other image processing software does? As things are, it retains the tag's value (if present), indicating, say, Photoshop as creating software if the image has previously been processed therein. It's nothing major, but I'd like to see AP put itself in the tag, so as to enable me, for example, to easily recognize AP-exported photos in my DAM software. Thoughts?
×
×
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.